Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[EOL/EOE] How to backup a current NSM install.

0

0

Article ID: KB10375 KB Last Updated: 18 Oct 2020Version: 6.0
Summary:
Note: A product listed in this article has either reached hardware End of Life (EOL) OR software End of Engineering (EOE).  Refer to End of Life Products & Milestones for the EOL, EOE, and End of Support (EOS) dates.
How to backup a current NSM install.
Symptoms:
Before performing an NSM upgrade, it is recommended to backup the current running NSM install.
What is the best way to back up a current NSM install?
Solution:

warning Backup the current NSM binaries, configuration files and device database files before upgrading. This will allow a quick restore if something goes wrong with the upgrade. (NSM makes a backup of the database before upgrading but making a complete manual backup is recommended.)

note: These instructions assume a default installation where the GuiSvr and DevSvr are installed in /var/netscreen. If a different installation path was chosen, check where the files are by ls -al /usr/netscreen/GuiSvr.

note: Please substitute the backup day's date for in the following commands.

For Linux:
  1. Check the available disk space in /usr and /var/netscreen. If there is not enough space to make a complete backup, a disk upgrade should be considered.
    df -h
    du -sh /usr/netscreen
    (The applications could require up to 1GB of diskspace.)
    du -sh /var/netscreen/GuiSvr (The GuiSvr database could be several Gigabytes.)
    (DevSvr will need up to 350MB, since traffic logs will be excluded from the backup)
  2. Shutdown the running services. If running in High Availability (two or more servers), shut down the secondary servers haSvr first.
    /etc/init.d/haSvr stop
    /etc/init.d/guiSvr stop
    /etc/init.d/devSvr stop
  3. Backup the application binaries:
    tar cvf /usr/netscreen.backup..tar /usr/netscreen
  4. Backup the guiSvr files:
    tar cvf /var/netscreen/GuiSvr.backup..tar /var/netscreen/GuiSvr
  5. Backup the devSvr files:

    (Make an exclude file to exclude making a backup of the traffic logs, which can be several GB in size. Traffic logs are not NSM version specific and so they do not need to be backed up. Also, Traffic logs ARE OS specific so it is not possible to move them from Linux to Solaris or vice versa.)
    touch /tmp/excludeFromBackup
    echo /var/netscreen/DevSvr/logs > /tmp/excludeFromBackup
    tar cvfX /var/netscreen/DevSvr.backup..tar /tmp/excludeFromBackup /var/netscreen/DevSvr

For Solaris:

The only difference between the Solaris and Linux instructions is to run the tar that is installed with NSM in /usr/local/bin. This tar is GNU tar and does not have the 100 character path limitation that some Solaris tar versions have.

  1. Check the available disk space in /usr and /var/netscreen. If there is not enough space to make a complete backup, a disk upgrade should be considered.
    df -h
    du -sh /var/netscreen/GuiSvr

    (devSvr will need up to 300M, since traffic logs will be excluded from the backup)
  2. Shutdown the running services. If running in High Availability (two or more servers), shut down the secondary servers haSvr first.
    /etc/init.d/haSvr stop
    /etc/init.d/guiSvr stop
    /etc/init.d/devSvr stop
  3. Backup the guiSvr files:
    /usr/local/bin/tar cvf /var/netscreen/GuiSvr.backup..tar /var/netscreen/GuiSvr
  4. Backup the devSvr files:

    (Make an exclude file to exclude making a backup of the traffic logs, which can be several gigs. Traffic logs are not NSM version specific and so they do not need to be backed up. Also, Traffic logs ARE OS specific so it is not possible to move them from Linux to Solaris or vice versa.)
    touch /tmp/excludeFromBackup
    echo /var/netscreen/DevSvr/logs > /tmp/excludeFromBackup
    /usr/local/bin/tar cvfX /var/netscreen/DevSvr.backup.tar /tmp/excludeFromBackup /var/netscreen/DevSvr

Once these directions are followed, there are copies of all the most important NSM files.

It is now safe to upgrade NSM.
Modification History:
2020-10-18: Tagged article for EOL/EOE.
 
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search