If you have not done so already, launch the Double-Take Availability Application Manager by selecting Start, Programs, Double-Take, Availability, Double-Take Availability Application Manager.
After protection is enabled, the Application Manager creates four resources on the target cluster: two generic script resources, an IP address resource, and a temporary name resource. The temporary name resource is the source EVS name with “_LN” appended to the end. The Application Manager uses the temporary name resource for the connection between the source and target clusters. The Application Manager gets the order of the source cluster resources from the Microsoft Cluster DLL, then builds the scripts with the resources in order and based off the source’s resources configuration.
Scripts are automatically generated by the Application Manager during configuration. The scripts are copied to the Double-Take Availability installation directory on the specified server using the administrative share for that server’s drive.
|
Script |
File name |
Description |
|---|---|---|
|
Failover |
post_failover_LN.txt |
A post-failover script is executed after the core failover processes have completed on the target server. The primary function of the post-failover script is to start the resources on the target. |
|
Failback |
pre_failback_LN.txt |
A pre-failback script is executed before failback processing occurs on the target server. The primary function of this script is to stop resources on the target. |
|
Restore |
post_restore_LN.txt |
A post-restore script is not executed automatically, though it is provided on the source to perform actions that are generally required after data has been restored from the target to source after a failover/failback. The primary function of this script is to restart resources on the source server. |
After the resources are online and the mirroring has completed, the source cluster is considered protected and the Application Manager starts monitoring the source for complete source failure.
|
Note: |
If you modify your configuration on the source cluster, you must disable protection, run validation and fix any issues, then re-enable protection to apply the changes to the Application Manager replication set. |
Next step: Failover and failback