What We Provide
XTIVIA’s DB2 team will provide recommendations, strategies and implementation services to set up IBM DB2 High Availability Disaster Recovery (HADR) with IBM Tivoli System Automation for Multiplatforms (TSAMP) environments to meet your organizational disaster recovery objectives. XTIVIA also deliver Virtual-DBA and consulting services that can monitor your environment. XTIVIA can address the following items:
- Deliver initial assessments and review requirements
- Design HADR and TSAMP systems
- Define the implementation approach & plan
- Estimate the schedule and cost of services and software
- Perform installation
- Test and validate the disaster recovery solution
- Train your staff to administer HADR and TSAMP
- Monitor HADR ad TSAMP using Virtual-DBA when requested
HADR for DB2 is a feature that keeps a primary and standby database synchronized and allows an administrator the ability to manually switch control to a standby DB2 server in the event the Primary DB2 server is unable to process transactions. HADR is a valuable feature that solves many disaster recovery requirements.
TSAMP comes packaged with DB2 and when integrated with HADR, provides a framework to automate a database failover of resources to the standby DB2 server when a problem is detected. For many clients this is necessary to meet SLAs.
TSAMP can be used to monitor DB2 resources, and automate the starting, stopping, and failover of the database. For example, if a DB2 server has hardware problem that crashes DB2, TSAMP will failover resources to the standby server.
Here are some bullet points to remember when planning or working with HADR and TSAMP
- DB2 v9.5 and higher provides a set of scripts that allow TSAMP to control the DB2 resources. These scripts start, stop and monitor DB2 resources.
- DB2 v9.5 and higher also provides a utility called ‘db2haicu’ that is used to set up the definitions and relationships.
- HADR on its own will not detect a node outage or NIC failure.
- HADR cannot take automated actions in the event of a failed primary instance, node outage, or NIC failure.
- Without TSAMP, a DB administrator must monitor the HADR pair manually and issue appropriate takeover commands in the event of a primary database interruption
- This is where TSAMP’s automation comes into play :
- TSAMP can perform restart actions when instances die
- TSAMP can perform a HADR takeover automatically when certain problems are detected on the primary server
- TSAMP can also manage a virtual IP making failover nearly transparent to applications
- TSAMP can use a private network for HADR and TSAMP traffic to prevent this traffic from impacting other network activity such as incoming connections
Additional complications may come into play when there is more than one DB2 instance on a server. More than one Virtual IP may be needed. We can help you identify how to properly implement and manage a more complicated setup.
Please contact XTIVIA if you have more questions or would like to set up a time to discuss how we can implement HADR and TSAMP in your LUW environment.