Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Disaster recovery deployment architecture (Oracle)


The architecture of the disaster recovery system varies according to the database you use. If you are using SAP SQL Anywhere, see Disaster-recovery-deployment-architecture-Sybase.

This overview presents the following topics:

Disaster recovery system architecture for Infrastructure Management

The disaster recovery system consists of two BMC TrueSight Infrastructure Management 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 TrueSight Infrastructure Management Server so that data and service availability are continued.

dr_oracle.png

Components of Infrastructure Management disaster recovery system

Component

Description

Primary and recovery BMC TrueSight Infrastructure Management Servers

The recovery BMC TrueSight Infrastructure Management Server is the backup server for the primary BMC TrueSight Infrastructure Management Server and must be up when the primary BMC TrueSight Infrastructure Management Server fails. Both the servers must have the following configuration with Infrastructure Management 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 TrueSight Infrastructure Management 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 TrueSight Infrastructure Management Server is up and running.

The backed-up files are critical to bring up the recovery BMC TrueSight Infrastructure Management 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 TrueSight Infrastructure Management Server at the time of a disaster so that the monitoring of the devices and data collection continue to function normally.

Disaster recovery system architecture for TrueSight Report Engine with Oracle Data Guard

The following diagram illustrates the Infrastructure Management architecture with BMC TrueSight Reporting and Oracle Data Guard.

dr_oracle_data_guard.png

Related topics

Configuring-the-disaster-recovery-system-Oracle

Disaster-recovery-backup-and-recovery

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*