Open topic with navigation

Configuring failover processing

1. Make sure you have a valid domain and servers specified, click Configure from the main Application Manager page, and then select the Failover tab.

   The fields on the Failover tab will vary depending on the type of application you are protecting.

    

2. Specify the Failover Type which is the name resolution method that will be used to redirect users to the target in the event the source fails. Ideally, you should use DNS failover to reduce downtime and avoid server name or IP address conflicts. However, you may want to select identity failover if access to the domain controller or DNS server is not available, the time required to propogate DNS updates is unacceptable, or your end-users are configured to connect to an IP address and not a server name. For cluster environments, DNS failover is the only option available.

   

• DNS Failover—With DNS failover, DNS records associated with the source will be updated to point to the target's IP address. This includes A, MX, and PTR-type DNS records. Clients will resolve the source server name to the target server's name and IP address at failover. Click Configure to specify the DNS failover settings.

• Identity Failover—With identity failover, the target will assume the source server's name and IP address. This option can potentially cause name and/or IP address conflicts if the source is brought back online while the target is standing in. Click Configure to specify the identity failover settings.

  If you select identity failover, you will not be using the Application Manager for failover, failback, or restoration. You must manually complete failover and failback and restoration.

  If you are protecting Exchange 2010 with DAG, Double-Take Availability will automatically update SPNs, move user mailboxes, and perform Active Directory updates during failover. DNS updates are not made during failover, but can be scripted manually if needed.

   

3. Application Manager automatically determines the appropriate application services or resources to start and stop based on the application you are protecting, your operating system, and your application configuration. If necessary, modify the list of services or resources.

   

   

1. Click Add to insert a service or resource into the list. Specify the service or resource name and make sure that Service must be stopped on target is enabled so that replication can update files on the target.
2. Click Remove to remove a service or resource from the list. The services you can remove depend on the application you are protecting. For example, if you are protecting Exchange, you can only remove services or resources that you have manually added.
3. If you are configuring your services, highlight a service and click the up or down arrow to reorder the list. The services will be stopped and started in the order displayed.
4. If you are using a cluster source and standalone target configuration, you can toggle between the services and resource configuration by clicking the Services button.
4. Click OK to save the settings.