Adding servers

1. Select Get Started from the toolbar.
2. Select Add servers and click Next.
3. On the Manual Entry tab, specify the server information.
• Server—This is the name or IP address of the server or appliance to be added to the console. For agentless vSphere jobs, insert your controller appliance. See the following NAT configuration section if you have a NAT environment.
• User name—For a server, specify a user that is a member of the Double-Take Admin or Double-Take Monitors security group on the server. For an appliance, specify the root user or another user that has the administrator role on the appliance.
• Password—Specify the password associated with the User name you entered.
4. You can expand the More Options section to configure the following settings.
• Domain—If you are working in a domain environment, specify the Domain.
• Associate with Double-Take Linux Appliance—If you will be creating a full server to ESX appliance job, specify the name or IP address of your virtual recovery appliance. Your Linux source is now considered a proxied server.
5. After you have specified the server or appliance information, click Add.

6. Repeat steps 3 through 5 for any other servers or appliances you want to add.

   For agentless vSphere jobs, you can insert any other controller appliances, but do not insert your replication appliances. The replication appliances will be inserted into the console using the Add Replication Appliances page. See Adding replication appliances.

    

7. If you need to remove servers or appliances from the list of Servers to be added, highlight a server and click Remove. You can also remove all of them with the Remove All button.

8. When your list of Servers to be added is complete, click OK.

   NAT configuration

   If you are going to create a files and folders (non-cluster) job, a full server job without reverse protection, or a full server to ESX appliance job, then your servers can be in a NAT environment. Other job types do not support a NAT environment.

   The name or IP address you use to add a server to the console is dependent on where are you are running the console. It is also dependent on the job type you are using. If you are using a full server to ESX appliance job, the console only communicates with the appliance. Therefore, you need to use the address which the appliance has access to when adding the source server. Use the one of the following tables to determine what name or IP address to use when adding a server or appliance to the console.

   In these tables, public addresses are those addresses that are publicly available when a server is behind a NAT router. Private addresses are those addresses that are privately available when a server is behind a NAT router. An address that is not labeled as public or private are for servers that are not behind a NAT router. This is generally a public address but is not named as such in these tables to try to more clearly identify when a public NAT address needs to be used.

    

   Files and folders (non-cluster) jobs and full server jobs without reverse protection

   Location of servers	Location of Double-Take Console	How to add the server to the Double-Take Console
   If your source and target are behind individual NAT routers,	and your Double-Take Console is located behind the NAT router with the source,	specify the name or private IP address of the source and the public IP address of the target (which is the public IP address of the target's NAT router).
   	and your Double-Take Console is located behind the NAT router with the target,	specify the public IP address of the source (which is the public IP address of the source's NAT router) and the name or private IP address of the target.
   	and your Double-Take Console is located between the two NAT routers,	specify the public IP address of the source (which is the public IP address of the source's NAT router) and the public IP address of the target (which is the public IP address of the target's NAT router).
   	and your Double-Take Console is located behind a third NAT router,
   If your source is behind a NAT router but your target is not,	and your Double-Take Console is located behind the NAT router with the source,	specify the name or private IP address of the source and the name or IP address of the target.
   	and your Double-Take Console is located on the target network,	specify the public IP address of the source (which is the public IP address of the source's NAT router) and the name or IP address of the target.
   If your target is behind a NAT router but your source is not,	and your Double-Take Console is located behind the NAT router with the target,	specify the name or IP address of the source and the name or private IP address of the target.
   	and your Double-Take Console is located on the source network,	specify the name or IP address of the source and the public IP address of the target (which is the public address of the target's NAT router).
   If your source and target are both behind a single NAT router with multiple public NICs,	and your Double-Take Console is located outside of the router,	specify the public IP addresses for the source and the target.

    

   Full server to ESX appliance jobs

   Location of source and appliance	Location of Double-Take Console	How to add the source and appliance to the Double-Take Console
   If your source and appliance are behind individual NAT routers,	and your Double-Take Console is located behind the NAT router with the source,	specify the public IP address of the source (which is the public IP address of the source's NAT router) and the public IP address of the appliance (which is the public IP address of the appliance's NAT router).
   	and your Double-Take Console is located behind the NAT router with the appliance,	specify the public IP address of the source (which is the public IP address of the source's NAT router) and the name or private IP address of the appliance.
   	and your Double-Take Console is located between the two NAT routers,	specify the public IP address of the source (which is the public IP address of the source's NAT router) and the public IP address of the appliance (which is the public IP address of the appliance's NAT router).
   	and your Double-Take Console is located behind a third NAT router,
   If your source is behind a NAT router but your appliance is not,	and your Double-Take Console is located behind the NAT router with the source,	specify the public IP address of the source (which is the public IP address of the source's NAT router) and the name or IP address of the appliance.
   	and your Double-Take Console is located on the appliance network,	specify the public IP address of the source (which is the public IP address of the source's NAT router) and the name or IP address of the appliance.
   If your appliance is behind a NAT router but your source is not,	and your Double-Take Console is located behind the NAT router with the appliance,	specify the name or IP address of the source and the name or private IP address of the appliance.
   	and your Double-Take Console is located on the source network,	specify the name or IP address of the source and the public IP address of the appliance (which is the public address of the appliance's NAT router).
   If your source and appliance are both behind a single NAT router,	and your Double-Take Console is located outside of the router,	specify the name or private IP address of the source and the public IP address of the appliance (which is the public address of the apliance's NAT router).

   As noted above, make sure you insert your virtual recovery appliance into your console session before inserting your source servers because a source server needs to be associated with an appliance that is already inserted in the console.

    

1. Select Get Started from the toolbar.
2. Select Add servers and click Next.
3. Select the Automatic Discovery tab.
4. Click Discover to search Active Directory for servers running Double-Take.
5. If you need to remove servers from the list of Servers to be added, highlight a server and click Remove. You can also remove all of them with the Remove All button.
6. When your list of Servers to be added is complete, click OK.
7. Because the Active Directory discovery uses pass-through authentication, you will need to update the credentials for each server from the Manage Servers page, so that explicit credentials can be used when you go to create a job. Click Provide Credentials and provide credentials for a user that has privileges to that server and is a member of the Double-Take Admin security group.

You can share the console server and group configuration between machines that have the Double-Take Console installed. The console server configuration includes the server group configuration, server name, server communications ports, and other internal processing information.

To export a server and group configuration file, select File, Export Servers. Specify a file name and click Save. After the configuration file is exported, you can import it to another console.

When you are importing a console server and group configuration file from another console, you will not lose or overwrite any servers that already exist in the console. For example, if you have server alpha in your console and you insert a server configuration file that contains servers alpha and beta, only the server beta will be inserted. Existing group names will not be merged, so you may see duplicate server groups that you will have to manually update as desired.

To import a server and group configuration file, select File, Import Servers. Locate the console configuration file saved from the other machine and click Open.