Cisco Systems 10200 Backing up the EMS Database

3-20

Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.x

OL-16000-07

Chapter 3 Monitoring and Backing Up the BTS

Exporting Provisioned Data

<hostname>#flarcreate -n <hostname> -X /tmp/excluded_dir -c /mnt/<hostname>.archive

<hostname>#mv /bin/date /bin/.date

<hostname>#mv /bin/date.archive /bin/date

Step 11 Unmount the NFS server, enter <hostname>#umount /mnt.

Step 12 From the active EMS switch over all platforms, enter:

<hostname>#ssh optiuser@<hostname>

cli>control bdms id=BDMS01;target-state=standby-active;

cli>control element-manager id=EM01;target-state=standby-active;

Step 13 Repeat the procedure starting with Step 3 to back up the PRIMARY EMS/BDMS.

Backing up the EMS Database

This procedure is for experienced UNIX users. It tells you how to save the provisioning database from

the EMS to a remote server. The remote server must be:

• Connected to a corporate LAN.

• Backed up daily by default, the daily hot backup is not turned on at installation

The back up processes:

• ora_hot_backup.ks—Backs up database data files, control files, and archive logs

• ora_arch_backup.ksh—Backs up archive logs

The target backup directory on both primary and secondary EMS systems is /opt/oraback. Backup files

in /opt/oraback directory are later transferred to the /opt/backup directory in a remote archive site.

After the files are transferred, they are purged from /opt/oraback.

Step 1 Cross check the databases on the primary and secondary EMSs before backing up.

Caution Cross check before ora_hot_backup.ksh and ora_arch_backup.ksh are scheduled. This

validates database and archived log files for RMAN processes.

a. Log in as oracle, or su - oracle.

b. Enter dbadm -E backup_crosscheck..

c. Ensure the log file has no errors (except the “validation failed for archived log” messages). Ignore

these messages of the /data1/arch/opticalx_yyy.arc files because the validation directs RMAN not

to look for *.arc files. ora_purge_archlog.ksh purges *.arc files.

RMAN-06157: validation failed for archived log

RMAN-08514: archivelog filename=/data1/arch/optical1_25.arc recid=1 stamp=461878656

Step 2 Remove the archive log purge process and schedule the backup processes.

Note Do this on the primary and secondary EMSs.

a. Disable the ora_purge_archlog.ksh process.

b. Enable the ora_hot_backup.ksh process.

Contents

Main Page CONTENTS Page Page Page Page Page Preface Organization Document Change History Obtaining Documentation and Submitting a Service Request Page Page Starting and Shutting Down the BTS Meeting Power Requirements Starting BTS Hardware Shutting Down BTS Hardware Starting BTS Software Page Page Managing BTS Users and Commands Using EMS Logging into the EMS Using CLI Managing Users Page Page Managing Commands Adapter and User Security Solaris OS Security and BTShard Package Page Page Operator Interface Vulnerabilities in H.323 Message Processing Authentication, Authorization and Accounting Support Pluggable Authentication Module Support User Security Account Management Sun Microsystems Configurations Page Solaris OS Patches Trace Normal Forms (TNF) Support XML Libraries Device GLM Patch Security CE Patch Security Bad_Trap Patch Java SDK Patches Page Monitoring and Backing Up the BTS Detecting and Preventing BTS Congestion Monitoring BTS Hardware Checking BTS System Health Using BTS System-Health Reports Checking BTS System Time Checking the OS Log of Each Host Machine Checking Disk Mirroring on Each Host Machine CA/FS Side A CA/FS Side B EMS Side A EMS Side B Auditing Databases and Tables Exporting Provisioned Data 3-9 Limitations Creating Numbering Resource Utilization/Forecast (NRUF) Reports Creating Reports for Nonrural Primary and Intermediate Carriers Creating Reports for Rural Primary and Intermediate Carriers Page Page Backing Up the Software Image Full Database Auditing Checking Shared Memory From CA/FS Side A From CA/FS Side B Backing Up the Full BTS Backing Up the CA/FS Backing up the EMS/BDMS Backing up the EMS Database Using FTP to Setup File Transfer Using SFTP to Setup File Transfer Page Archiving Your Database Examining Heap Usage Checking the DNS Server Log Archive Facility (LAF) Secure Transfer of Files Other Capabilities Provisioning LAF Example 1 Example 2 Example 3 Setup Non-Interactive SSH Login to External Archive Server Adding Static Routes LAF Alarm Information Moving Core Files Page Operating the BTS Managing Subscribers Page Page Page Viewing Calls Using Status and Control Commands Page Using Show and Change Commmands Using ERAC Commands Page Page Managing Transactions Scheduling Commands Limitations Page Managing External Resources Viewing BTS System-Wide Status Page Managing Trunk Groups and Trunks Page Page Page Page Page Page Page Page Managing Subscriber Terminations Page Page Page Managing Gateways Page Managing Other External Resources Page Learning External Resource Dependencies Page Page Page 5-24 Source Token 5-25 5-26 Figure 5-3 ISDN Administrative and Operational Maintenance States for a Trunking Gateway 5-27 GigE Support Prerequisites Provisioning the GigE Interface Page Page Using BTS Measurements Using Measurements Learning the Measurement Types ISDN Measurements Page Page Call Processing Measurements Page Page Page Page Page Page MGCP Adapter Measurements DQoS Measurements SIP Measurements Page Page Service Interaction Manager Measurements POTS Local FS Measurements Page Page Page Page Page POTS Application Server Measurements POTS Miscellaneous FS Measurements Page POTS Class of Service FS Measurements POTS Screen List Editing FS Measurements POTS Customer Originated Trace FS Measurements POTS Automatic Callback, Recall, and Call Return Measurements Page POTS Limited Call Duration (Prepaid/Postpaid) with RADIUS Interface to AAA Measurements POTS Call Forwarding Combination Measurements AIN Services FS Measurements Page SCCP Protocol Measurements Page TCAP Protocol Measurements Page Page Page SUA Measurements Page M3UA Protocol Measurements Page SCTP Measurements Page Page IUA Measurements Page ISUP MeasurementsI Page Page Page 6-50 6-51 ISUP (ANSI) Measurements Page Page ISUP (France) Measurements ISUP (Poland) Measurements ISUP (ITU-China) Measurements Page Page ISUP (ITU-Mexico) Measurements Page ISUP (ITU-HongKong) Measurements Page Audit Measurements SIP Interface Adapter Measurements Page Call Detail Block Measurements Page Event Messaging Measurements Dynamic QoS Measurements PCMM Measurements SNMP Protocol Measurements Trunk Group Usage Measurements Page Page Announcement Measurements H.323 Protocol Measurements Page Page Page Call Tools Measurements AIN Tools Measurements PCT Tools Measurements CPU Usage Measurements Memory Usage Measurements Disk Usage Measurements Network I/O Usage Measurements Page System Load Usage Measurements Disk I/O Usage Measurements ENUM Measurements Diameter Message Counters Single Number Reach Counters Using the BTS SNMP Agent Managing User Access to the SNMP Agent Viewing SNMP Trap Reports Page Viewing and Managing BTS Components Page Querying the SNMP Agent Enabling NMS to Query/Poll Solaris SNMP Agent Page Page APPENDIX A Feature Tones Tones per Feature Page Page request when Page Tone Frequencies and Cadences Page Page APPENDIX B FIM/XML Understanding the Configurable FIM/XML Feature Advantages of the FIM/XML Tool Tool Requirements Writing an External FIM/XML File Defining Features Elements in the External FIM/XML File Define Element Precedence-Exception Element Inhibit Others Element Inhibit Me Element Response Profile Element Error Operation Installing the FIM/XML File Using the Offline FIM/XML Tool Page FIM/XML File and Shared iFC File Features Defined in FIM/XML and Shared iFC Provisioning iFC Defining a New feature as the Originating Feature Defining a VSC Defining the SIP Trigger Profile Feature Configuration Feature Restrictions and Limitations