DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.


The SBC EMA provides the ability to generate a system backup file. The user can restore the configuration files from the storage location. During this process, the system will restart and the user has to re-login, once the system is up and running. This is useful if you upgrade the SBC and need to reload the old configurations.

SBC provides an option to upload backup files from an external source.  

Note

If you wish to reinstall the SBC at any time, perform a backup of the configuration to restore it when needed. The backup files can now be stored in an external space. 



Note

All the backup files should start with the naming convention:

  • "config_<System_Name>_<File_Name>", and should end with ".tar.gz"

or

  • "auto_backup_config_<System_Name>_<File_Name>", and should end with ".tar.gz"

For example: "config_SBC001_BackupFile1.tar.gz" or "auto_backup_config_SBC001_BackupFile1.tar.gz".

The system creates and maintains daily automatic backups for the last seven days and you can take up to 10 configuration backups.


Perform the following tasks to Restore the configuration :

  1. Navigate to Administration > System Administration > Backup/Restore.

    System backup/Restore Screen

  2. Highlight the file from the list ofLastBackup which you want to restore.

  3. Click Restore. A confirmation message is displayed seeking your permission to load the selected configuration and to restart the applications on active/standby servers as shown below:

    Backup Current Software

  4. Click OK to load the selected configuration file and to restart the applications on both Active and Standby servers.


Note

When you load config dump taken from SBC versions older than 8.0, the SBC internally converts Oracle based policy dump to the Postgres format. This process takes approximately 25 minutes to complete.