The disaster-recovery strategy for the BMC Remedy ITSM 8.1 value paths involves setting up disaster recovery for each product in the value paths. All products need to be available and updated in the disaster-recovery data center in case the production data center is unavailable for any reason. In many cases, these products share a database that becomes the focus of disaster-recovery configuration.
Although the BMC Remedy ITSM Suite contains several databases common to BMC Remedy ITSM, the BMC Remedy ITSM value paths can include products that need additional configuration to work properly in a disaster-recovery situation.
Common disaster-recovery requirements
Although each product has its own requirements for setting up disaster recovery, the following requirements are common to all products:
- The disaster-recovery installation must have the same product version and patch level as the production installation.
- If any configuration or file changes (such as applying patches) are made to the production data center, the same changes must be repeated on the disaster-recovery data center.
- As the production system is used, all data changes must be replicated to the disaster-recovery data center. These changes can be database changes or file system changes, depending on the product in use.
- Replicating data changes imposes additional demands on the resources in the production system. To keep these demands to a minimum, the replication schedule should be carefully considered. If continuous replication is needed, the production system must be given additional resources (CPU and memory) to reduce the performance impact.
Also consider recovery from a secondary location if a failover event occurs.
Overall disaster recovery for IT Service Management
The following diagram shows different points where replication is needed to keep the disaster-recovery data center installation up to date (each point marked with a yellow dot). Each component needs to be ready and available for the disaster-recovery installation to start functioning. For example, if the production databases are being replicated every three hours, transaction information for the last three hours might not yet exist in the disaster-recovery databases, and might need to be copied over and restored manually by using the database transaction logs. Another example can be when network changes need to be put in place manually before disaster recovery can take over.
To accommodate such scenarios, the following architecture does not include automatic failover from production. This is an essential consideration for BMC Atrium Orchestrator. If the disaster-recovery strategy for BMC Atrium Orchestrator is based on a High Availability Configuration Distribution Peer (HA CDP) in the disaster-recovery data center, this CDP automatically starts processing the workflow if production fails. If the rest of the products are not yet ready, the processes start failing.
The following diagram does not show disaster recovery for BMC Analytics for BSM and BMC Dashboards for BSM because they largely refer to the data in the BMC Remedy ITSM database and so benefit from the replicated BMC Remedy AR System database. Any additional data that they set up can be easily re-created in the disaster recovery environment if required.
The following BMC product name abbreviations are used in the diagram:
- ADDM = BMC Atrium Discovery and Dependency Mapping
- BAO = BMC Atrium Orchestrator
- ITBM = BMC IT Business Management