
20
Figure 11. Failover/Failback resource property
Disaster recovery
Cluster node recovery (failback)
Because there is no disruption to the SAN or intersite links in either the Site A single node failure
scenario or the Site A all node failure scenario, the SQL Server application can be manually moved
back to the original nodes on Site A. Once the nodes in Site A are back online, you can manually
move the SQL Server application by using Windows Failover Cluster Manager and HP CLX EVA.
Manual failback is performed by using Windows Failover Cluster Manager, which takes the SQL
Server instance offline and brings it back online on Site A. During testing, it took less than 1 minute to
perform manual failback.
For maximum SQL Server instance availability, allow resynchronization to complete before attempting
to move the SQL cluster group back to Site A. Otherwise, the SQL Server instance remains offline until
resynchronization completes.
During the failover operation, HP CLX EVA reverses the data replication direction of the disk resources
to replicate from Site A to Site B, thus returning the source/destination relationship of the DR group to
its pre-failure state.
Comentarios a estos manuales