This document explains the steps involved in disabling all the XP CLX components that can cause automatic XP CA disk pair resynchronization. This is helpful while someone manually suspends the CA replication, may be for XP online firmware upgrade or for some maintenance work, and does not want any software components to initiate automatic CA disk pair resynchronization, which can cause an error.

 

The primary purpose of a failover cluster (also called server cluster) is to increase application availability, and at the same time, ensure that only one instance of an application is online at any point in time. The mechanism of ensuring that there are never two instances of one application running is one of the core technologies of every cluster. The Microsoft Failover Clustering implementation is the quorum mechanism. It also supports geographically dispersed clusters. Microsoft Failover Clustering supports shared access quorum disk and the majority node set quorum approach.

 

HP StorageWorks XP Cluster Extension (XP CLX) for Windows extends a Microsoft cluster across two sites. This improves availability by providing disaster tolerance in case of core component failures such as storage systems and site disasters like fire, power outage, and even larger natural disasters. XP CLX enables monitoring of HP StorageWorks XP Continuous Access-mirrored disk pairs and allows access to the remote data copy if an application becomes unavailable on the local site. XP CLX supports both shared quorum disk and majority node set quorum clusters.

 

This document explains the steps involved in disabling all the XP CLX components that can cause automatic XP CA disk pair resynchronization. This is helpful while someone manually suspends the CA replication, may be for XP online firmware upgrade or for some maintenance work, and does not want any software components to initiate automatic CA disk pair resynchronization, which can cause an error.

White Paper here