Backup policy configuration example

Example details

The following example describes an NFM-P backup policy configuration using appropriate parameter values for most scenarios. The Backup Policy form contains the parameters in the example; see To configure a backup policy for the configuration information.

The sample backup policy specifies that the NFM-P obtains the backup files by FTP from the NE once every hour regardless of configuration activity, and after every 25 configuration changes. The policy also specifies that the NFM-P backs up the device configuration file, license file, and boot options file, or BOF, only when a newer file is present, and uses gzip file compression. The NFM-P is to retain at most 30 backup versions, and purge versions that are more than 30 days old.

The following figure illustrates the activities of the NFM-P backup and restore process.

Figure 23-1: NFM-P backup process
NFM-P backup process

The labels in Figure 23-1, NFM-P backup process correspond to events in the following sequence:

  1. At the interval specified, which is every hour in the example, the NFM-P issues a request to all NEs for a backup.

  2. The NEs send the BOF, configuration files, and license file to the NFM-P.

  3. The NFM-P stores the new versions of the received files.

  4. A GUI client operator views the backup status on the Backup/Restore Status tab of the Backup Policy form.

  5. If the NFM-P system is redundant, the active and standby main servers synchronize the backup files.

  6. An NFM-P operator uses the Backup/Restore form to perform on-demand and scheduled backups, restores, and configuration saves, as required.

  7. A third-party application periodically sends a copy of the backup files from the NFM-P to a remote storage location for safekeeping.

The policy parameters and values are the following: