Versions Compared

Old Version 7

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1pmohan
REV5gnimmagadda
REV6avalente
REV3paramachandra
REV1dajeru
REV2kconger

The

Spacevars
0product
 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 back-up backup files from an external source.  

Info
iconfalse
titleNote

For any reason, if If you wish to re-install reinstall the SBC Applicationat any time, take perform a back up backup of the configuration to restore it when needed. The back-up backup files can now be stored in an external sourcespace. 



Info
iconfalse
titleNote

Re-installing a SBC system from an ".iso" image followed by restoring SBC configuration from a tar.gz backup file may lead to loss of encrypted configuration parameters in the following scenarios:

  • re-installing a standalone SBC from an ".iso" image followed by restoring SBC configuration from a "tar.gz" backup file
  • re-installing both nodes in an HA SBC pair from an ".iso" image followed by restoring SBC configuration from a "tar.gz" backup file

Activities like replacing a single node in an HA pair (as an RMA for example) or re-installing a single node in an HA pair at a time are safe. The node that has just been re-installed will take the current configuration from the active node.

For details please refer to Sonus Warning: Warning-17-00022737.

Info
iconfalse
titleNote

All the back-up 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".

...

Info

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.

    Caption
    0Figure
    1System backup/Restore Screen


  2. Highlight the file from the list of Last Backup 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:

    Caption
    0Figure
    1Backup Current Software


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


Info
titleNote

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.

Pagebreak