Enabling protection, Enabling protection -5 – HP Storage Mirroring V4.5 Software User Manual
Page 46

4 - 5
9.
On the Configure DNS window, you can modify the TTL value for the DNS record. You can also
specify the user credentials needed to modify DNS. When you are finished, you can click Test to
test the DNS configuration for the selected DNS server(s), or click OK to return to the
Configure Protection window.
10.
After you have changed the configuration parameters, click OK to apply the settings and return
to the Manage Exchange window. If you click Cancel, any changes you have made will be
discarded and the previous configuration parameters will be used.
11.
Click Validate to validate the selected cluster pair. The validation proceeds exactly like
validation for other methods of failover.
12.
Click Enable Protection to enable protection for the source cluster.
Enabling protection
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 Storage Mirroring installation directory on the specified server using the administrative
share for that server’s drive.
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:
Decreasing the TTL value will increase the speed at which clients get the updated
information.
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.
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.