HP Storage Mirroring V4.5 Software User Manual
Page 121

8 - 15
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.
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:
1.
Click on the button for the script you want to update. The script file will be displayed using your
machine’s default editor.
2.
Enter your changes.
3.
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.
The scripts can be overwritten by certain operations during setup. For example, any changes to
configuration options done in the Application Manager will overwrite previous script changes. If you
want to make permanent changes to a script, you must modify the appropriate .txt file within
the Application Manager installation directory. If there is more than one client machine that will be
configuring failover, the change must be made to all the appropriate .txt files.
Before running Application Manager multiple times (for example, when re-enabling protection after a
failover/failback), save a copy of your post-restore and pre-failback batch files. After Application
Manager executes, replace the default script file(s) with the customized file(s) that you saved.
Script
File name
Description
Failover
post_failover_
_bb.bat for distributed
environments, or
post_failover_
_sql_bb.bat for consolidated
environments
A post-failover script 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
pre_failback_
bb.bat for distributed
environments, or
pre_failback_
sql_bb.bat for consolidated
environments
A pre-failback script 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
post_restore_
_bb.bat for distributed
environments, or
post_restore_ server>_ server>_sql_bb.bat for consolidated environments 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 services on the source server.