Yota PCRF. Backup and Recovery. Product version: 3.6 Document version: 1.6

Transcription

1 Yota PCRF Backup and Recovery Product version: 3.6 Document version: 1.6 Yota 2013

2 Revision History Date Version Author Revision Maxim Kumskoy Document created Evgenia Martynyuk Updated "Introduction" section and "Database Recovery" chapter Evgenia Martynyuk Added tables to recovery list Evgenia Martynyuk Updated "Database Backup", "Database Recovery" chapters Evgenia Martynyuk Added new tt_import utility options Evgenia Martynyuk Updated "Data Recovery" section Evgenia Martynyuk The list of tables not to backup was updated Yota

3 Table of Contents Introduction... 4 Database Backup... 5 PCRF Database Backup... 6 DDF Database Backup... 6 Database Recovery... 7 PCRF Cluster Database Recovery... 8 Data Recovery... 8 DDF Cluster Database Recovery... 9 Yota

4 Introduction Yota PCRF 3.6 Backup and Recovery Yota PCRF system is a set of DDF and PCRF clusters, where every cluster consists of two nodes. Database replication is configured between cluster nodes. Clustering provides high reliability and data availability. TimesTen database is entirely stored in the main memory during DDF and PCRF components operation. Regular data storing is performed by means of TimesTen to the hard disk, what precludes data loss due to power failure or the server reboot. For system restoration purposes after total cluster node failure, or after accidents caused by human factors (e.g., incorrect manual table removal from the database), the built-in recovery tools of Oracle TimesTen and special Yota PCRF utilities are used. Starting with version 3.4 only full database backup is supported. Yota

5 1 Database Backup PCRF Database Backup DDF Database Backup Yota

6 To perform database backup special Yota PCRF utilities are used. PCRF Database Backup Yota PCRF 3.6 Backup and Recovery PCRF database backup is performed on the secondary cluster node by db_backup.sh utility. All database tables are coped except session information tables. The following tables are not backed up: Table Name NMS_DATA SESSION_DATA_B SESSION_TO_KILL RX_SESSION EVENT LOCATION_ATTRIBUTE SESSION_ATTRIBUTE LOCATION_SESSION SESSION_CHANNEL_INFO NOTIFY_MSG Description Contains statistical data from NMS Contains service session information Contains the list of sessions to terminate Contains Rx sessions information Contains Gx sessions events Contains information about location (sector) attributes Contains information about session attributes Contains information about session count in the location Contains service session information Contains notify messages Full backup is performed every 3 hours on the secondary node by utility: /opt/pcrf_utils/bin/db_backup.sh Operation description in cron job scheduler: /etc/cron.d/pcrf_utils_slave 0 */3 * * * root /opt/pcrf_utils/bin/db_backup.sh Database backup copies are stored for one week only in the following directory: /var/timesten/backup/ DDF Database Backup DDF cluster database backup is performed the same way as PCRF database backup. See section "PCRF Database Backup" for more details. Yota

7 Database Recovery PCRF Cluster Database Recovery DDF Cluster Database Recovery Yota 2013

8 PCRF Cluster Database Recovery Yota PCRF 3.6 Backup and Recovery Data recovery is possible after the replication is configured and operates between cluster nodes. The recovery procedure is performed on the cluster primary node. Any interaction via Gx protocol (port 3868) must be disabled until a complete system recovery. Also, on DDF node, it is required to turn off subscriber profiles migration to region, where data recovery is performed, by setting Enable=0 for the PCRF nodes under restoration (in DDF O&M Console go to: Configuration -> Network Topology -> Peers). Data Recovery PCRF data is restored from the last backup file by utility: /opt/pcrf_utils/bin/tt_import Command syntax: /opt/pcrf_utils/bin/tt_import [-n <file_name>] Where <file_name> backup file name, which the data will be restored from. Command example: /opt/pcrf_utils/bin/tt_import -n db_dump_5_10.dat.gz If required it is possible to set tables or even table columns that will not be restored by the following keys: --exclude-tables <TABLE_NAME> --exclude-columns <TABLE_NAME>.<COLUMN_NAME> Information More information about tt_import utility keys that can be used for data restoration can be seen by command: /opt/pcrf_utils/bin/tt_import -h After PCRF data restoration the following checks must be performed: 1. Check if cluster table data in PCRF O&M Console is valid. (Configuration -> Network Topology -> Clusters). 2. Check if peers table data in PCRF O&M Console is valid (Configuration -> Network Topology -> Peers). 3. Check if server settings table data in PCRF O&M Console is valid (Configuration -> Server Settings). 4. Check if base stations data in PCRF O&M Console is valid (Congestions -> NMS Statistics). 5. Make sure all users have read (write) permissions on GRAPI scripts. 6. Check if all GRAPI scripts are *.lua files. 7. Activate profile migration from DDF and interaction via Diameter interfaces (Gx, I0, etc ). Yota

9 DDF Cluster Database Recovery DDF Cluster Database Recovery Before performing recovery procedure on DDF it is required to disabled subscriber profiles requesting of subscriber profiles from DDF on every PCRF node by setting configuration parameter use_ddf_subscriber_info to 0. In every PCRF node O&M Console go to: Configuration -> Server Settings and set use_ddf_subscriber_info=0. Data recovery procedure on DDF node is the same as on PCRF and described in section "PCRF Cluster Database Recovery". After DDF data restoration the following checks must be performed: 1. Check if cluster table data in DDF O&M Console is valid (Configuration -> Network Topology -> Clusters). 2. Check if Diameter peers table data in DDF O&M Console is valid (Configuration -> Network Topology -> Peers). Yota