The AVM is generated as an OVA file from the Axcint Web Application. Once the OVA is generated, the user must create a VM on the target host using the OVA file.
The Axcient Virtual Manager (AVM) is the entity which relays replicated data from the target VMs to the Axcient Cloud. As long as the AVM is properly configured and has outbound network capabilities, it will transmit data to the Axcient Cloud. If the AVM is offline, or otherwise nonoperational, replicated data will not be transmitted to the Axcient Cloud and replication jobs will fail.
The AVM agent is not a local appliance, meaning that there is no replicated data stored locally on the AVM.
The AVM is deployed on the host ESX server where the target VMs are located. The AVM transmits replicate data only for the devices on the host ESX server. The user will need to deploy multiple AVM agents if the protected environment has multiple ESX host server, where each ESX host has an AVM agent deployed.
AVM Sizing Considerations
The AVM sizing consideration matrix is designed to help the user successfully plan the technical resources in order to meet business recovery point objectives and requirements. These sizing considerations are for the AVM virtual machine that is created in order to replicate date of protected the ESX host and the target devices to the Axcient Cloud.
The matrix below is a guideline for how to allocate resources for the AVM virtual machine given a number of target guest VMs and what the desired RPO needs to be.
Be aware that these are guidelines and other factors may effect the total RPO time such as network bandwidth and hardware limitations.
|Number of Devices||1 Hour RPO||2 Hour RPO||4 Hour RPO|
|4 Guest VMs||4 vCPUs, 8GB RAM||4 vCPUs, 4GB RAM||4 vCPUs, 2GB RAM|
|5 Guest VMs||4 vCPUs, 10GB RAM||4 vCPUs, 5GB RAM||4 vCPUs, 3GB RAM|
|10 Guest VMs||4 vCPUs, 10GB RAM||4 vCPUs, 5GB RAM||4 vCPUs, 3GB RAM|
|15 Guest VMs||4 vCPUs, 10GB RAM||4 vCPUs, 5GB RAM||4 vCPUs, 3GB RAM|
Protecting Devices Using the AVM
Once the AVM has been successfully deployed on the ESX host, it will automatically detect and protect all live VMs on the host using the configured Protection Policy.
In the event that a new VM is created, or an offline VM is powered on after the AVM is deployed, the AVM will automatically detect the new VMs and begin replicating them using the configured Protection Policy.
To deploy the AVM agent, do the following:
|Step 1 – The user will first need to get the AVM Agent Installation link. These can be found in the following ways:
Click the Click to Highlight button, or use the mouse to highlight the link, to copy it.
|Step 2 – Paste the AVM Agent Installation link in a preferred Internet browser to download the AVM agent OVA file.The AVM agent OVA file will be downloaded to the local device. Be sure that the device has access to ESX host through vSphere. Make note of where the AVM agent OVA file is downloaded. This will be needed in Step 4.|
| Step 3 – Log in to the vSphere Client (either Web or Windows will do).To begin deploying the AVM agent, do the following:
|Step 4 – In the Source page, click the Browse button to navigate and select the AVM agent OVA file downloaded in Step 2. Click Next to continue.|
|Step 5 – In the OVF Template Details page, the user is able to review the specific OVF template details. Click Next to continue.|
|Step 6 – In the Name and Location page, name the AVM something to make it easily identifiable. It is recommended that this be noted somewhere for future reference. Click Next to continue.|
|Step 7 – In the Disk Format page, select the desired provision type. Axcient recommends selecting Thin Provision. Click Next to continue.|
|Step 8 – In the Network Mapping page, select the appropriate VM network.The AVM must be on the same network as the target VMs that will be protected. Click Next to continue.|
|Step 9 – In the Ready to Complete page, review the OVF details. Once the user has confirmed the OVF details, click Finish button. Power on the AVM and navigate back to the Axcient Web Application Dashboard.|
|Step 10 – Once the AVM agent VM has been powered on, the user will need to navigate back to the Axcient Web Application Dashboard.Expand the Activities of Interest section to see the New AVMs alert. Hover the mouse over the right-hand side of the alert to expose the Enter Credentials link and click it.|
| Step 11 – The user will now need to enter the ESX host credentials where the AVM agent is located:
If the ESX host belongs to a vCenter, check the My Host Belongs to a vCenter box and enter the following:
Click Save to complete the AVM deployment process.