At a data backup, the exchange data for program units is stored in the file system. When a program unit is reloaded, exchange data for all program units is restored to prevent exchange data inconsistency.
Restore of exchange data can result in loss of exchange data. However, the exchange data in the system is consistent after a complete data restore.
As part of certain error recovery routines, the exchange data will be restored from the backup in order to revert the system to the last known state with data consistency.
Exchange data includes:
System configuration data
Application data (for example, extensions and trunks). The application data are altered either by command (for example, adding extensions) or by extension procedure (for example, call diversion)
Exchange data should be saved to a backup regularly. The data should also be stored after:
Loading the system initially
Changing hardware configuration
Upgrading a program unit
Altering application data by command (for example, adding extensions)
A new directory is created for each backup in the directory: /var/opt/eri_sn/<version>/xdata/ where <version> is the version of MX-ONE Service Node. The backup directory is named xdata_y_z, where y is MX-ONE Service Node number and z is a time stamp (date and time). A backup file for each program unit that has exchange data is created in the backup directory. Only program units that have exchange data have files in the backup directory. Cassandra CQL CSV files are also created in the backup directory. The CQL CSV file contains a snapshot of the exchange data in the system database at the time for the backup. The system database data is stored in Cassandra Query Language Format.
Information about valid backups are stored in the Cassandra Database. The three latest backups are stored. If more backups are made, the oldest backup is deleted.
At a data restore, the newest valid backup is used. Exchange data in the entire system is restored from the data backup and the start phase after data restore is executed in all program units in the system.
To succeed with a backup, all program units in the system must have status Started. A program unit must have status Alive, Half-started, or Started to restore any data.
Restore of exchange data can result in loss of exchange data. However, the exchange data in the system is consistent after a complete data restore.
As part of certain error recovery routines, the exchange data will be restored from the backup in order to revert the system to the last known state with data consistency.
Exchange data includes:
System configuration data
Application data (for example, extensions and trunks). The application data are altered either by command (for example, adding extensions) or by extension procedure (for example, call diversion)
Exchange data should be saved to backup regularly. The data should also be stored after:
Loading the system initially
Changing hardware configuration
Upgrading a program unit
Altering application data by command (for example, adding extensions)
A new directory is created for each backup in the directory /var/opt/eri_sn/xdata/xdata_<version> where <version> is the version of MX-ONE Service Node. The backup directory is named xdata_y_z, where y is MX-ONE Service Node number and z is a time stamp (date and time). A backup file for each program unit that has exchange data is created in the backup directory. Only program units that have exchange data have files in the backup directory. Cassandra CQL CSV files are also created in the backup directory. The CQL CSV file contains a snapshot of the exchange data in the system database at the time for the backup. The system database data is stored in Cassandra Query Language Format.
The latest backup directories are stored. If more backups are made, the oldest backup directory is deleted.
At a data restore, the newest valid backup file is used. Exchange data in the entire system is restored from the data backup and the start phase after data restore is executed in all program units in the system.
To succeed with a backup, all program units in the system must have status Started. A program unit must have status Alive, Half-started, or Started to restore any data.