Adding servers

The first time you start the console, the Manage Servers page is empty. In order to protect and monitor your servers, you must insert your servers and/or appliances in the console. For some jobs, you can insert servers and appliances during job creation, or you have three other methods for inserting servers into the console.

Inserting servers manually

Select Get Started from the toolbar.
Select Add servers and click Next.
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. 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.
Password—Specify the password associated with the User name you entered.
Domain—If you are working in a domain environment, specify the Domain.

After you have specified the server or appliance information, click Add.
Repeat steps 3 and 4 for any other servers or appliances you want to add.
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.

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

If you are using domain credentials for your Double-Take servers and you change those credentials, you will continue to receive a Windows Security pop-up in the Double-Take Console, even if you enter correctly updated credentials in the pop-up. This is an unavoidable Windows WCF communication issue, and you must update the credentials for the Double-Take servers in the Double-Take Console Manage Servers page in order to terminate the repeated pop-ups.

NAT configuration

The name or IP address you use to add a server to the console is dependent on where you are running the console. Use the following table to determine what name or IP address to enter depending on the location where you are running the console.

In this table, 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 this table to try to more clearly identify when a public NAT address needs to be used.

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.

Inserting servers through Active Directory discovery

Select Get Started from the toolbar.
Select Add servers and click Next.
Select the Automatic Discovery tab.
Click Discover to search Active Directory for servers running Double-Take.
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.
When your list of Servers to be added is complete, click OK.
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.

Importing and exporting servers from a server and group configuration file

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.