Related Topics
If you have not done so already, launch the Application Manager by selecting Start, Programs, Double-Take, Availability, Double-Take Availability Application Manager.
The following sections describe the manual processes you can use to manage failover. These manual processes are required if you chose to perform Identity failover.
You will be using the Double-Take Replication Console, Failover Control Center, and/or Text Client to manage identity 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. Acknowledge the manual intervention prompt to start failover.
|
Note: |
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 Failing over for information on monitoring a failure. |
The post-failover script created earlier will automatically run. During failover, Windows Event Viewer, the Double-Take Availability log, DFO log, and Application Manager logs 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: |
The DFO and Application Manager log files are located in the same directory as the Application Manager. 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.
Next step: Fail back using identity