Overview of disaster recovery (Oracle)

This overview presents the following topics:

Disaster recovery system architecture for BMC ProactiveNet

The disaster recovery system consists of two BMC ProactiveNet Servers, a primary server and a recovery server. They are connected to separate database servers that run Oracle Database. During a disaster, the DNS alias name resolves to the recovery BMC ProactiveNet Server so that data and service availability are continued.

Components of BMC ProactiveNet disaster recovery system

Primary and recovery BMC ProactiveNet Servers

The recovery BMC ProactiveNet Server is the backup server for the primary BMC ProactiveNet Server and must be up when the primary BMC ProactiveNet Server fails. Both the servers must have the following configuration with BMC ProactiveNet Performance Management installed:

Identical operating system version
Identical hardware configuration
Located in the same domain
Configured logical fully qualified domain names
Identical time zone, location, and language settings

Primary and recovery database servers

The primary and recovery database servers must run on the same operating system. They must run Oracle Database in ARCHIVELOG mode. They must have the same hardware and software configurations. The database servers and their corresponding BMC ProactiveNet Servers must be on the same subnet.

Database replication solution

A database replication solution keeps the data in the recovery database in sync with the primary database.

If you do not have a database replication solution, you can also use a database replication tool to back up the database files and then transfer the files to the recovery database server. The database replication solution helps reduce system down time when compared to the manual backup process.

Note

Check with your Oracle Database administrator for the appropriate database replication solution or tool. You must use an Oracle-certified database replication solution or tool.

Storage replication solution

A storage replication solution automatically backs up the configuration files at frequent intervals even when the primary BMC ProactiveNet Server is up and running.

The backed-up files are critical to bring up the recovery BMC ProactiveNet Server at the time of a disaster.

If you do not have a storage replication solution, you can also manually back up these files. The storage replication solution helps reduce system down time when compared to the manual backup process.

Note

Check with your IT administrator for the appropriate storage replication solution.

DNS server

The DNS server resolves to the recovery BMC ProactiveNet Server at the time of a disaster so that the monitoring of the devices and data collection continue to function normally.

Assumptions to configure a disaster recovery system for BMC ProactiveNet

The configuration settings to achieve a disaster recovery system for your BMC ProactiveNet environment are based on the following assumptions:

Your system uses two standalone BMC ProactiveNet Servers located at two different geographic locations or data centers.
Your system uses two database servers running Oracle Database in ARCHIVELOG mode, one each for the standalone BMC ProactiveNet Servers.
BMC ProactiveNet Servers must be on the same subnet as their respective database servers.
No data changes will be made to the BMC Atrium Configuration Management Database, BMC UDDI registry server, or BMC BladeLogic Service Automation during disaster recovery operation. If data changes are made during the disaster recovery operation, then the common data will become out of sync between these products and their integrated BMC ProactiveNet Servers.
BMC ProactiveNet Servers must be on different networks.
Your system uses a Domain Name System (DNS) alias name.
Your system has the routing and firewall settings properly configured.
Your system has only one BMC ProactiveNet Server running at any given time.

Configuration scenario for a disaster recovery system

The following scenario explains the disaster recovery setup on which these best practices are based:

Calbro Services has several branch offices across the world. It has its primary BMC ProactiveNet Server and primary Oracle Database server located in Amsterdam, Netherlands. It has its recovery BMC ProactiveNet Server and recovery Oracle Database server in New York, United States of America, on a different network.

Calbro Services wants its server in New York to be up and running whenever its primary BMC ProactiveNet Server at Amsterdam fails. Calbro Services also wants its primary BMC ProactiveNet Server to resume services after the issue has been fixed. It also uses a DNS server that resolves to the recovery BMC ProactiveNet Server at the time of a disaster. Both the servers run BMC ProactiveNet Performance Management as a standalone installation.

The following names are assigned to the servers:

The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.