HP StorageWorks Storage Mirroring user's guide (T2558-96073, February 2008)

16 - 14
14. By default, Manual Intervention is enabled, allowing you to control when failover occurs. When a failure occurs, a
prompt appears in the Failover Control Center and waits for you to manually initiate the failover process. Disable this
option only if you want failover to occur immediately when a failure occurs. This option is not configurable if the
Method
to Monitor for Failover
is set to No Monitoring.
15. If the Shares selection under Items to Failover is selected, verify that the Use .SHR Share Mapping File check box is
selected if you would like to use the Storage Mirroring share mapping file to create shares on the target during failover. If
this option is not selected, shares will be created using the information gathered when the machine was selected as a
source to be monitored.
16. By default, Failover Hostname is disabled. This option automatically removes the host SPN (Service Principle Name)
from Active Directory on the source and adds it to Active Directory on the target. If you are using Active Directory,
enable this option or you may experience problems with failover.
17. Failback Hostname returns the host SPN on the source and target back to their original settings on failback. If you are
using Active Directory, enable this option or you may experience problems with failback.
18. If you are failing over or failing back hostnames, you need to specify an Active Directory user that has update privileges
within Active Directory. Click
Credentials and identify a user and the associated password that has privileges to create
and delete SPNs. The username must be in the format
fully_qualified_domain\user. Click OK to return to the
Monitor Settings dialog box.
19. If you are using any failover or failback scripts, click Scripts and enter the path and filename for each script type. Scripts
may contain any valid Windows command, executable, or batch file. Examples of functions specified in scripts include
stopping services on the target before failover because they may not be necessary while the target is standing in for the
source, stopping services on the target that need to be restarted with the source’s machine name and IP address,
starting services or loading applications that are in an idle, standby mode waiting for failover to occur, notifying the
administrator before and after failover or failback occurs, stopping services on the target after failback because they are
no longer needed, stopping services on the target that need to be restarted with the target machine’s original name and
IP address, and so on.
Specify each script that you want to run and the following options, if necessary.
 If you want to pass any arguments to your script, specify the arguments.
 If you want to delay the failover or failback processes until the associated script has completed, mark the appropriate
check box.
 If you want the same scripts to be used as the default for future monitor sessions, mark the appropriate check box.
 If you want to specify a user account to run the scripts, specify the credentials for the source and target. If no account
is specified, the scripts will be processed using the same account that is configured to run the Storage Mirroring
service.
Click
OK to return to the Monitor Settings dialog box.
20. Click OK on the Monitor Settings dialog box to save your monitor settings and begin monitoring for a failure.
NOTE: If the Shares selection under Items to Failover is not selected, shares will not be failed over to the target
regardless of the Use .SHR Share Mapping File selection.
NOTE: The Active Directory account password cannot be blank.
NOTE: Failover scripts will run but will not be displayed on the screen if the Storage Mirroring service is not set
to interact with the desktop. Enable this option through the Services applet.
With these flexible scripting features, application failover using Storage Mirroring can be seamless to the
end user. HP tests many of the popular applications on the market today. The results of these testing
procedures are written up into formal Application Notes that describe how Storage Mirroring should be
configured to work correctly with certain applications, including scripting examples. For a complete list of
Storage Mirroring Application Notes, visit the HP web site.
NOTE: If your target is a cluster, you need to repeat these steps to establish failover monitoring on all nodes of the
cluster, so that any node that could be the owning node of the target cluster will be monitoring the source.