Deploying the OVF virtual machine
- Locate the .ova installation file. For example, for version 8.2, the installation file name might be dtvra_8.2.1.1124.0.ova. If necessary, copy this file to a location that is accessible from your vSphere client.
- From your vSphere client, select the root of your tree, select File, Deploy OVF Template, and specify the dtvra_<version_number>.ova file. Click Next to continue.
- Review the OVF template details and click Next to continue.
- If you are connected to a vCenter, review the Carbonite license agreement. You must accept the license agreement by clicking Accept. If you do not have vCenter, you will need to accept the license agreement when the appliance first starts. Click Next to continue.
- Specify the name and location where you want to install the appliance. This should be the same datacenter where your target ESX host is located. Click Next to continue.
- Select the ESX host where you want to install the appliance. This is your target ESX host. Click Next to continue.
- If desired, select the resource pool where you want to install the appliance. You will not have this option if you do not have resource pools. Click Next to continue.
- Select the datastore where you want to store the appliance files. Make sure the datastore has at least 16 GB of space available. Click Next to continue.
- Select the type of disk to create. The names you see displayed will be dependent on your vSphere client.
- Flat or Thick Provision Lazy Zeroed—This disk type allocates the full amount of the disk space immediately, but does not initialize the disk space to zero until it is needed. This option is only available for ESX version 5 and later.
- Thick or Thick Provision Eager Zeroed—This disk type allocates the full amount of the disk space immediately, initializing all of the allocated disk space to zero.
- Thin Provision—This disk type does not allocate the disk space until it is needed.
- Click Next to continue.
- If your selected ESX host has multiple networks, map the network on the appliance to a network on your ESX host, and click Next to continue.
- If you are connected to a vCenter, assign the virtual machine and networking properties. If you do not have vCenter, you will need to configure these settings after the appliance starts.
- Root password—Set a password for the root login. If you do not make a change, the default password will be used. The default password is carbonite.
- Time zone setting—Select the virtual machine's time zone. The default setting is UTC.
- Hostname—Specify the hostname or full qualified domain name to assign to the virtual machine. If you leave this option blank, Carbonite Availability and Carbonite Migrate will use reverse DNS lookup for the identification.
- Default gateway—Specify the virtual machine's default gateway.
- DNS server—Specify the virtual machine's DNS server.
- Network IP address—Specify the IP address to assign to the virtual machine. You must use an IPv4 address.
- Network subnet mask—Specify the subnet mask for the assigned IP address.
- Click Next to continue.
- Review the Deployment settings. If you want to make any changes, click Back. If not, enable the Power on after deployment option, and click Finish.
- After the appliance deployment is complete, click Close.
After the appliance has been installed, you will need to install the Carbonite Replication Console on a Windows machine, if you haven't already. See the instructions Installing the Carbonite Replication Console. Make sure you select the Client Components Only installation option.
Once the appliance has been installed and configured, you should not need to access or use it. However, if you need to change any network settings, you can modify them using the Configure Network menu on the appliance or by using the web interface by going to https://ip_address:5480, where ip_address is the current IP address of the appliance. Keep in mind if you change the network settings using the web interface, you will lose your connection to that interface because it will still be using the original IP address.
You should not change the hostname after deployment because the name change will not be persisted if the appliance is rebooted.
The appliance menu runs as root, so make sure you take advantage of VMware security to restrict access to the appliance. See your VMware documentation for details on limiting access to the appliance's console.