HP Storage Mirroring V5 Software - Manual (Page 76)

66 Protecting a File Server
To add a replication set rule, click Add . In the Add Repset Rule window, enter the rule path (the directory that
you want to protect or exclude), select whether to include/exclude the path, and whether the directory should
be recursive or non-recursive, then press Enter . When you have entered all of your replication set rules, click
Add to return to the Advanced configuration tab.
NOTE: You will need to manually verify that the rule path is correct since the Application Manager does not
validate rule paths
To remove a rule, select one or more rules, then click Remove . You can only remove rules that you added
manually through the Application Manager. Rules that are automatically added by Application Manager
cannot be removed or changed through the Application Manager interface.
To reset the rules to the auto-generated rules and to re-enable the File Shares control, remove the selection from
the Override Generated Rules checkbox.
Failover/failback scripts
Scripts are executed at different points during the failover/failback process to perform the actions necessary to
make the file shares available on the appropriate server. Scripts perform steps such as starting/stopping
services, modifying mailbox values in Active Directory to point users to the appropriate server, and modifying
DNS entries on the DNS server to point users to the appropriate server.
Editing scripts is an advanced feature.
Do not edit scripts unless you fully understand what each command is
doing.
Three scripts are automatically generated by 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.
• Failover Script —A post-failover script (
post_failover_FilePrint.txt
) is executed after the core failover
processes have completed on the target server. The primary functions of the post-failover script are to start
the services on the target and to modify DNS and Active Directory entries as necessary.
• Failback Script —A pre-failback script (
pre_failback_FilePrint.txt
) is executed before failback
processing occurs on the target server. The primary functions of this script are to stop services on the target
and to move DNS and Active Directory entries as necessary.
• Restore Script —A post-restore script (
post_restore_FilePrint.txt
) 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
services on the source server.
• Post Failback Script —A post-failback script (
post_failback_FilePrint.txt
) is executed on the target
before the post-restore script runs. The primary function of this script is to re-start the “server” service and
all dependent services on the source in order to refresh client connections.
By default, Application Manager generates all the required scripts for you automatically based on your system
configuration. You can also edit the scripts to add, modify, or delete specific commands. To edit a script, click
on the button for the script you want to update and the script file will be displayed using your machine’s default
editor. Enter your changes, then save the script file. Any change you make to the script in the editor will be
copied to the appropriate server when configuration changes are accepted, thus overwriting any changes that
have been made outside the Application Manager.