Open topic with navigation
Agentless vSphere environment configuration
The fundamental function of Double-Take is to identify what you want to protect on your production server, known as the source, and replicate that to a backup server, known as the target. In an agentless vSphere job, there are multiple components which make up the source and target.
- You need your hosts. (The use of the word host is used generically to represent a standalone ESXi host or a cluster, which is typically defined as a group of ESXi hosts.) One is your source host and one is your target host. In some cases, the source and target could be the same host.
- You need virtual machines on your source host. These are the virtual machines you want to protect and are called your source virtual machines. Once you have established protection, you will have replicas of the source virtual machines on your target host. These are called your target virtual machines.
- Each source and target host must have a replication appliance, which controls sending data between the hosts. These replication appliances are referred to as the source replication appliance and the target replication appliance.
Beyond your source and target components, you need a controller appliance. The controller appliance handles communication from the Double-Take Console to the replication appliances. It also handles licensing for your agentless vSphere jobs. The controller appliance should not be located with your source host, in case your source host experiences a failure. Ideally, the controller appliance should be located with your target host or on its own.
You must also have the Double-Take Console in your environment.
- The Double-Take Console communicates with the Double-Take controller appliance.
- The controller appliance communicates with the various Double-Take replication appliances.
- The replication appliances on the source take the replication snapshots and send them to the target. The replication appliances on the target apply the replication snapshots and take point-in-time snapshots of the target. For details on the replication process, see Agentless vSphere replication process.
