NE backups and restores
Backup policies
An NFM-P backup policy specifies the conditions under which the NFM-P performs device configuration backups. The NFM-P stores the backups, which can quickly be restored in the event of an NE failure. Each managed NE that is not associated with a policy is assigned to a default policy, but you can create multiple additional policies and assign NEs to the policies according to your requirements.
A backup policy specifies settings that include the following:
An NFM-P operator that has the network element software management scope of command role can perform device configuration save, backup, and restore operations.
Note: An NFM-P user that has the lawful intercept management scope of command role can back up and restore an LI configuration. Backup data is saved only when the LI Local Save Allowed parameter on the Polling tab of the NE properties form is selected.
Note: An on-demand backup takes priority over scheduled backup operations, and is processed as soon as the NFM-P has the required resources.
You can export backup files from the NFM-P to a GUI client file system, and can import NE backup file sets to the NFM-P. In a redundant NFM-P system, the backup files are synchronized between the primary and standby main servers.
You can configure the NFM-P to automatically delete device backup files after the associated NE is unmanaged; see the chapter on NFM-P database management in the NSP System Administrator Guide for more information.
When a device configuration requires replacement, for example, when it is corrupt, you can restore a previous configuration. Unless otherwise specified, the NFM-P restores the most recent configuration backup. See To perform an on-demand backup, restore, or configuration save and To restore a device configuration other than the most recent for information about restoring device backups.
A restore works implicitly with a backup policy; there is no explicit restore policy. An operator must manually restore a device backup.
Before you can delete a backup policy, you must remove from the policy all NEs that are assigned to the policy.
GNE backups
The NFM-P NE backup function is supported for GNEs, depending on the device type and release. Backing up a GNE configuration requires a valid NFM-P GNE driver that supports the function.
Note: Some GNE devices may have specific backup requirements. Before you attempt to perform a GNE backup operation, see the appropriate domain user guide for information about driver capabilities and driver-specific information, including backup requirements.
GNE backups are configured and performed using the policy-based mechanism that is used for natively managed devices; the type of backup policy required for GNEs is Generic NE Node. In a Generic NE Node backup policy, you must specify the transfer protocol and user credentials, and a directory on the main server that is used for transferring the backup files from the GNEs.
Note: GNE backups have the following special requirements.
-
FTP, SFTP, or TFTP must be enabled on each main server, depending on which protocol you use.
-
If a firewall is used, the required FTP, SFTP, or TFTP ports must be open.
-
The FTP, SFTP,or TFTP user that you specify in a backup policy must be a valid FTP, SFTP, or TFTP user on each main server station, and must belong to the sam user group on each main server station.
-
The nsp user requires read, write, and execute access to the directory that you specify in the policy.