Configuring the disaster recovery system (SAP SQL Anywhere)
Process for configuring 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 (SAP SQL Anywhere) |
2 | Configure the primary TrueSight Infrastructure Management Server. | Configuring the primary Infrastructure Management Server (SAP SQL Anywhere) |
3 | Configure all the remote event cells. | |
4 | Configure the recovery TrueSight Infrastructure Management Server. | Configuring the recovery Infrastructure Management Server (SAP SQL Anywhere) |
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 Infrastructure Management Server located in Amsterdam, Netherlands. It has its recovery Infrastructure Management 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 Infrastructure Management Server at Amsterdam fails. Calbro Services also wants its primary Infrastructure Management Server to resume services after the issue has been fixed. It also uses a DNS server that resolves to the recovery Infrastructure Management Server at the time of a disaster. Both of the servers run Infrastructure Management as a standalone installation.
The following names are assigned to the servers:
Servers | Name |
|---|---|
Primary Infrastructure Management Server at Amsterdam | amsterdam.calbro.com |
Recovery Infrastructure Management Server at New York | newyork.calbro.com |
Alias name to be set for the primary and recovery 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.
- 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.
Related topics
Disaster recovery deployment architecture (SAP SQL Anywhere)
Worksheet to configure disaster recovery for Infrastructure Management (SAP SQL Anywhere)
Troubleshooting connectivity issues with the Presentation Server
Comments
Log in or register to comment.