The steps you need to take to verify your DR configuration depend on the type of replication you are using.
After the DR wizard has completed, you can confirm the following to verify the DR configuration:
For Volume Replicator replication, confirm that the configuration of disk groups and volumes at the DR site have been created by the DR wizard storage cloning.
Confirm that the application VCS service group has been created in the DR cluster including the same service group name, same resources, and same dependency structure as the primary site's application VCS service group.
Confirm that the application service group is online at the primary site. The application service group should remain offline at the DR site.
For Volume Replicator replication:
Ensure Volume Replicator replication configuration. This includes ensuring that the RVGs have been created at primary and secondary with the correct volume inclusion, replication mode, Replicator Log configuration, and any specified advanced options.
Confirm that the replication state matches what was specified during configuration. If specified to start immediately, ensure that it is started. If specified to start later, ensure that it is stopped.
Ensure that the Volume Replicator RVG VCS service group is configured on the primary and secondary clusters, including the correct dependency to the application service group, the specified IP for replication, and the correct disk group and RVG objects within the RVG VCS service group.
Confirm that the RVG service groups are online at the primary and secondary sites.
Confirm that the RVG Primary resources are online in the primary cluster's application service group. If they are offline, then bring them online in the primary site's cluster's application service group. Do not bring them online in the secondary site application service group.
For array-based replication, verify that the required array resource is created in the primary and secondary cluster's application service group and that a dependency is set between the VMDg resource and the array resource.
For EMC SRDF replication, verify that the SRDF resource is online in the primary cluster's application service group. If not, bring it online.
For Hitachi TrueCopy replication, verify that the HTC resource is online in the primary cluster's application service group. If not, bring it online.
For Hitachi TrueCopy replication, you must perform a manual Volume Manager rescan on all the secondary nodes after setting up replication and other dependent resources, in order to bring the disk groups online. This must be performed only once, after which the failover works uninterrupted. For more information, see Cluster Server Hardware Replication Agent for Hitachi TrueCopy Configuration Guide.
Ensure that the application service groups are configured as global.
Check to ensure that the two clusters are communicating and that the status of communication between the two clusters has a state of Alive.
If you are using Volume Replicator for replication and configuring an additional DR site, verify the heartbeat and replication configuration between all sites.
If you are using Volume Replicator for replication and chose to start replication manually in the DR wizard, to avoid replicating large amounts of data over the network the first time, then you will need to start the process necessary to synchronize from checkpoint.
This process typically consists of the following tasks:
Starting a Volume Replicator replication checkpoint
Performing a block level backup
Ending the Volume Replicator replication checkpoint
Restoring the block level backup at the DR site
Starting replication from the Volume Replicator replication checkpoint
To learn more about the process of starting replication from a checkpoint, refer to the Volume Replicator Administrator's Guide.
Do not attempt a wide area failover until data has been replicated and the state is consistent and up to date. The Solutions Configuration Center provides a Fire Drill Wizard to test wide area failover for Volume Replicator-based replication.