User manual HP STORAGEWORKS STORAGE MIRRORING V4.4.2 SOFTWARE

[. . . ] HP OpenView Storage Mirroring user's guide Storage Mirroring Application Manager Part number: T2558-96005 Fourth edition: September 2006 Legal and notice information © Copyright 1999, 2006 Hewlett-Packard Development Company, L. P. Valid license from HP required for possession, use or copying. Consistent with FAR 12. 211 and 12. 212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U. S. Government under vendor's standard commercial license. [. . . ] Consequently, the user will have to manually failback and restore their data. You will need to perform the following steps: If the original owning node (the owning node at the time of failover) is still available: 1. Move the Exchange virtual server to that node. If the original owning node is not available: 1. Disconnect the source-to-target server connection. Create a connection in the Storage Mirroring Management Console from the target owning node to the source server owning node that includes the protected Exchange data. After the mirror is complete, disconnect the connection. Remove the Deny ACE entry for the cluster administrator from the source server's DNS object in Active Directory. Run the pre_failback. bat script in the Storage Mirroring installation directory on the target owning node. Run the post_restore. bat script in the Storage Mirroring installation directory on the source owning node. Identity failover, failback, and restoration The following sections describe the manual processes you can use to manage failover, failback, and restoration. These manual processes are required if you chose to perform Identity failover. You will be using the Storage Mirroring Management Console, Failover Control Center, and/or Text Client to manage identity failover and failback. For more information about using Storage Mirroring, refer to the Storage Mirroring User's Guide. Initiating a failover If a failure occurs and the Failover Control Center Time to Fail counter reaches zero (0), a dialog box will appear in the Failover Control Center requiring user intervention to initiate failover. (If the Failover Control Center is not open when the failure occurs, the dialog box will appear the next time the Failover Control Center is opened and you are logged on to the target. See the Storage Mirroring User's Guide for information on monitoring a failure. ) Acknowledge the manual intervention prompt to start failover. The post-failover script created earlier will automatically run. During failover, Windows Event Viewer, the Storage Mirroring log, DFO log, and Storage Mirroring Application Manager logs (both log files are located in the same directory as the Storage Mirroring Application Manager) record the failover events. When failover is complete, the target will have the application services started, the databases mounted, and the users pointed to the target. NOTE: If you are failing over Exchange, after the changes have propagated through your environment, clients can connect through Outlook® or Outlook Web Access to receive their e-mail. Users that had Outlook open during the failure will need to restart the Outlook client (excluding Outlook Web Access clients on a LAN). If DNS failover was selected, the clients will have to wait for the IP cache to expire, or type in "ipconfig /flushdns" in a command window. This time can be adjusted by lowering the TTL (Time to Live) setting within your DNS server's configuration. For more information, refer to your DNS server documentation. HP OpenView Storage Mirroring Application Manager User's Guide 45 Failback and restoration If your source experiences a failure, such as a power, network, or disk failure, your target machine will stand in for the source while you resolve the source machine issues. [. . . ] For example, the following command could be executed from a command line or included in a batch file: "c:\Program Files\StorageMirroring\dfo. exe" /dnssrvname dnsserver_name /srcname source_name /srcip source_ip /tarname target_name /tarip target_ip /verbose DNS Failover Utility Command Syntax Command Description Syntax dfo Used in script files to failover the DNS server name dfo [/dnssrvname [dnsservername] /srcname [sourceFQDN] /srcip [sourceip] /tarip [targetip] /tarname [targetFQDN] /recordtype [recordtype] /username [username] /password [password] /dnszone [dnszonename] /dnsdomain [dnsdomainname] /logfile [logfilename] /failback [fbswitch] /setpassword [username] [password] /getpassword /trustee [trusteename] /verbose /test /debug /?| /help ] 70 Options · · · · · · · · · · · · dnsservername--The name of the source domain/zone's primary DNS server (optional; local machine name used if missing) sourceFQDN--The source machine's Fully Qualified Domain Name (required for modify) sourceip--The source machine's IP address (required for modify) targetip--The target machine's IP address (required for modify) targetFQDN--The target machine's Fully Qualified Domain Name (required for modify on failback) recordtype--The type of DNS resource records to modify or list (optional). Values can be: ALL (default), MSEXCHANGE, A, CNAME, MX, or PTR username--The user account's domain name (optional; the account running the program is used if missing) password--The user account's password (optional) dnszonename--The name of the DNS zone or DNS container, used to refine queries (optional) dnsdomainname--The name of the DNS domain, used to refine queries (optional) logfilename--The name of the log file (optional) fbswitch (optional)--By default, the DFO will only failback records in the dfo_failback_config. dat file. fbswitch allows you to enter a search criteria to identify the records to change back, even if they are not in the configuration file. [. . . ]