Backing up data

Backup allows you to capture and archive data configured and/or provisioned on a specific NOAMP or SOAM server. All files that are part of the backup are archived into a single file in the file management storage area. For information on file storage and file name format conventions, see Files.

A backup of configuration and/or provisioning data on the NOAMP or on an SOAM server can be initiated or terminated from the Database Status page. The status of a backup can viewed from the Backup and Archive page.

Note:

You must be logged into the active server to backup data for that server. For example, to perform a backup of NOAMP configuration or provisioning data, you must be logged into the active NOAMP. To perform a backup of SOAM configuration data, you must be logged into the active SOAM. Data backup is handled solely by NOAMP servers in systems that do not support SOAMs.

Note:

Depending on the application, the Provisioning button may not be functional. For example, on the active DSR NOAMP, the Provisioning button displays, but it is disabled. The active UDR NOAMP presents the button as functional and the user may toggle the selection as desired.

Note:

Only Configuration data can be backed up on SOAM. The Provisioning button is not functional on SOAM and cannot be checked. Only the Configuration button is active.

Use this procedure to backup data for a server.

1. Click Status & Manage > Database.
2. Click Disable Provisioning and click OK.
   Provisioning and configuration updates are disabled for all servers, and the Disable Provisioning button changes to Enable Provisioning.

   Note:

   On an NOAMP, this means provisioning and configuration are disabled system-wide. On an SOAM, configuration is disabled only on the SO level.
3. Click to select the Active server in the Network Element that contains the data you want to backup.
4. Click Backup.
5. Select the data to be backed up, either Provisioning, Configuration, or both.

   Note:

   Only Configuration data can be backed up on SOAM. The Provisioning button is not functional on SOAM and cannot be checked. Only the Configuration button is active.
6. Select the backup archive compression algorithm, either gzip, bzip2, or none.

   Note:

   When backing up a database above 300M for SDS provisioning, it is recommended that you do not use bzip2.
7. Enter a comment in the Comment field to identify the backup file.
   This information is stored as part of the backup file and is displayed before a restore of the file occurs.
8. Change the Archive Filename, if desired.
9. Click OK.
   The backup begins. When the backup begins, the Tasks box is displayed with the long running task which is managing the backup. You can follow the progress of the backup from the Tasks box. After refreshing the page, the status of the backup appears in the Information message box with a message similar to this.

   Backup on <server_name> status MAINT_IN_PROGRESS.

   The only action that can be taken for this server while a backup is in progress is Report. The backup is complete when the status message changes to this one.

   Backup on <server_name> status MAINT_CMD_SUCCESS. Success

10. Click Enable Provisioning and click OK.

    Note:

    You do not have to wait until the backup is complete to re-enable provisioning and configuration updates.

    Provisioning and configuration updates are enabled for all servers, and the Enable Provisioning button changes to Disable Provisioning.

The backed up data is stored in a compressed file and copied to the file management storage area of the server that was backed up. Use the Status & Manage > Files option to access this file. To transfer the file off-site, use the procedure, Transferring a File to Off-site Storage.