Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring Automated NE Database-backup Operations

    The PSM server automatically backs up all discovered NEs on a daily basis. The backups are scheduled to run at 4:15 AM by default but this can be changed. PSM automatically uses the (S)FTP server installed on the PSM server and places the backup files in the default /home/ftpadmin/NeDbBackups directory. If an alternative location is desired then the (S)FTP server and subdirectory can be changed using the procedure in this section.

    PSM uses the following format when naming backup files:

    IP address_BTI7xxxVersionnumber_Date_Time

    For example:

    There is no indication on the PSM client that the scheduled backups have run, unless one fails. If a database backup operation fails for a particular network element, an alarm, which must be cleared manually, is raised to PSM server.

    Only one attempt at a database backup operation is made on each network element during each schedule. The PSM server does not send additional database backup requests after an operation fails. However, if the backup operation is set to run regularly, it sends a database backup request at the next scheduled backup time.

    1. On the workstation where the PSM server is installed, open the file /var/local/ems9001/conf/

      Note: The /var/local/ems9001/conf/ file contains many settings that affect the behavior of the PSM server. Only those attributes explicitly described in this guide should be changed. Changing any other attributes might have unintended consequences, and must only be performed under the guidance of Juniper Networks Support.

    2. Specify the backup time and frequency. In the /var/local/ems9001/conf/ file, set the property schedule.neDbBackup.cron to specify the time at which the PSM server will send a database-backup request to each network element it manages. See Example: Scheduling Using Quartz CronTrigger Format for examples on how to specify the schedule.
    3. Specify the destination FTP server and subdirectory. In the /var/local/ems9001/conf/ file, set the properties neDbBackup.ftpServerId or neDbBackup.sftpServerId to specify the FTP or SFTP server to which the database is to be backed up. The format is <ip address>:<port>:<user>:<subdirectory>.
      • <ip address> is the IP address of the (S)FTP server.
      • <port> is the port number on which the (S)FTP server is listening.
      • <user> is a username that is allowed to log in to the (S)FTP server.
      • <subdirectory> is the name of the subdirectory where the backup files are to be placed (specified with a path relative to the FTP root directory). If you do not specify the subdirectory explicitly, the backup files are placed in the FTP root directory.

      Note: The specified server with the above parameters (including the subdirectory if present) must exist in the PSM (S)FTP server list. See the proNX Service Manager User Guide for information on how to add servers to the PSM (S)FTP server list. If the (S)FTP server with the above parameters does not exist in the PSM (S)FTP server list, backups will not take place.

      Note: You must manually create the specified subdirectory on the (S)FTP server.

      Note: If you do not specify an (S)FTP server, the database is backed up to the default /home/ftpadmin/NeDbBackups directory on the local (S)FTP server included as part of the PSM server installation.

    4. Save and close the /var/local/ems9001/conf/ file.
    5. Track changes to the /var/local/ems9001/conf/ file with Git by committing this update to the Git repository.

      For example:

      [user ~]# cd /var/local/ems9001/conf
      [user conf]# git commit -m "Configured automated NE backups.  By"

      This update can now be seen in the Git log. For more information on Git, see Using Git to Track

    6. To activate changes made to the file, restart the PSM server.

      Note: NE database backup related alarms do not automatically clear themselves once the problem has been resolved. Any NE database backup alarms that occur must be manually cleared.

      The restart command successfully completes when the 'Ems-' processes all change to 'running' state. Type <ctrl> c to exit the Linux watch command window.

    Modified: 2017-11-07