Configuring the disaster recovery system (Oracle)
This section explains the steps you must perform to configure the disaster recovery system for the servers that run Infrastructure Management.
Note
BMC recommends that you validate these recommendations before you actually implement them in a production environment.
Sequence to configure the disaster recovery system
Step | Task | Reference |
|---|---|---|
1 | On the DNS server, set an alias name for the primary TrueSight Infrastructure Management Server. | Setting an alias name for the primary Infrastructure Management Server (Oracle) |
2 | Configure the primary TrueSight Infrastructure Management Server. | Configuring the primary TrueSight Infrastructure Management Server (Oracle) |
3 | Configure all of the remote event cells. | |
4 | Configure the recovery TrueSight Infrastructure Management Server. | Configuring the recovery Infrastructure Management Server (Oracle) |
| 5 | If applicable, configure disaster recovery for the Infrastructure Management Reporting Engine with Oracle Data Guard. | Configuring disaster recovery for TrueSight Operations Management Report Engine with Oracle Data Guard |
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 TrueSight Infrastructure Management Server and primary Oracle Database server located in Amsterdam, Netherlands. It has its recovery TrueSight Infrastructure Management 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 TrueSight Infrastructure Management Server at Amsterdam fails. Calbro Services also wants its primary TrueSight Infrastructure Management Server to resume services after the issue has been fixed. It also uses a DNS server that resolves to the recovery TrueSight Infrastructure Management Server at the time of a disaster. Both the servers run Infrastructure Management Performance Management as a standalone installation.
The following names are assigned to the servers:
Servers | Name |
|---|---|
Primary TrueSight Infrastructure Management Server at Amsterdam | amsterdam.calbro.com |
Primary Oracle Database server at Amsterdam | amsterdamDB.calbro.com |
Recovery TrueSight Infrastructure Management Server at New York | newyork.calbro.com |
Recovery Oracle Database server at New York | newyorkDB.calbro.com |
Alias name to be set for the primary and recovery TrueSight Infrastructure Management Servers | pronet |
Assumptions to configure a disaster recovery system for Infrastructure Management
The configuration settings to achieve a disaster recovery system for your Infrastructure Management environment are based on the following assumptions:
- Your system uses two standalone TrueSight Infrastructure Management 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 TrueSight Infrastructure Management Servers.
- TrueSight Infrastructure Management Servers must be on the same subnet as their respective database servers.
- No data changes will be made to the Atrium Configuration Management Database, BMC UDDI registry server, or 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 TrueSight Infrastructure Management Servers.
- TrueSight Infrastructure Management 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 TrueSight Infrastructure Management Server running at any given time.
Comments