Since VMware announced, the end of vSphere Data Protection, there is a choice to migrate existing deployment to EMC Avamar. More about EOA can be found in this link here.
In this article, we will be looking at deploying Avamar Virtual Edition 7.2. You can go ahead and download the required version of AVE from EMC download portal. The version I will be using is Avamar 7.2.1.
Login to Web Client or vSphere Client, Select the ESXi host where you want to deploy your AVE and select File > Deploy OVF. Browse the location for the AVE download and add the file. Click Next.
![]()
Review the details of the OVF template and click Next.
![]()
Accept the EULA and click Next.
![]()
Provide a name for this AVE virtual machine. Click Next.
![]()
If available and required select a resource pool in which you want to place this VM. Click Next.
![]()
Select the datastore where you want to deploy this. Remember the vmdk bundled with AVE is just the OVF, the data drives are configured later just like a VDP appliance. Click Next.
![]()
Select a disk provisioning type. Thick provision is recommended. Click Next.
![]()
Select a network where this AVE should be connected to. Click Next.
![]()
Review the changes and click Finish. Do not check Power On after deployment, because there are couple of steps to be done once the OVF deployment is completed.
![]()
Just like VDP, the AVE comes with 4 supported available backup storage. You can refer the below table to size your AVE accordingly.
![]()
Once you choose the deployment type, you will need to refer the below table to plan the drive sizes. Just like in VDP a 512GB deployment will have 3 drives of 256 GB each. The additional space is for the checkpoint maintenance overhead.
So the rule goes like:
Total size = GSAN capacity + 1/2 of GSAN capacity.
GSAN capacity would be the actual space for storing backup data.
![]()
So go ahead and add three disks manually (Depending on your AVE configuration) to this VM. Only Thick Provisioning is supported for AVE. I will be using Thin because of space constraints.
![]()
Once the drives are added, power on the AVE virtual machine.
The default login is root and changeme
First, we will have to configure network settings for the AVE machine. Post the login to AVE from VM console, run yast2 to begin the networking configuration. You will see a similar interface:
![]()
Select Network Devices and then Network Services to begin the network configuration wizard and you should see something similar:
![]()
You will need to Set IP Configuration in Overview, Hostname / DNS settings and Gateway under Routing.
Once the appliance is configured with network, restart the guest and then verify the network by ping and nslookup. If this works good proceed to Part 2 in the below link.
VDP - Avmar Migration: Part-2: Configuring Avamar Virtual Edition 7.2
In this article, we will be looking at deploying Avamar Virtual Edition 7.2. You can go ahead and download the required version of AVE from EMC download portal. The version I will be using is Avamar 7.2.1.
Login to Web Client or vSphere Client, Select the ESXi host where you want to deploy your AVE and select File > Deploy OVF. Browse the location for the AVE download and add the file. Click Next.
Review the details of the OVF template and click Next.
Accept the EULA and click Next.
Provide a name for this AVE virtual machine. Click Next.
If available and required select a resource pool in which you want to place this VM. Click Next.
Select the datastore where you want to deploy this. Remember the vmdk bundled with AVE is just the OVF, the data drives are configured later just like a VDP appliance. Click Next.
Select a disk provisioning type. Thick provision is recommended. Click Next.
Select a network where this AVE should be connected to. Click Next.
Review the changes and click Finish. Do not check Power On after deployment, because there are couple of steps to be done once the OVF deployment is completed.
Just like VDP, the AVE comes with 4 supported available backup storage. You can refer the below table to size your AVE accordingly.
So the rule goes like:
Total size = GSAN capacity + 1/2 of GSAN capacity.
GSAN capacity would be the actual space for storing backup data.
So go ahead and add three disks manually (Depending on your AVE configuration) to this VM. Only Thick Provisioning is supported for AVE. I will be using Thin because of space constraints.
Once the drives are added, power on the AVE virtual machine.
The default login is root and changeme
First, we will have to configure network settings for the AVE machine. Post the login to AVE from VM console, run yast2 to begin the networking configuration. You will see a similar interface:
Select Network Devices and then Network Services to begin the network configuration wizard and you should see something similar:
You will need to Set IP Configuration in Overview, Hostname / DNS settings and Gateway under Routing.
Once the appliance is configured with network, restart the guest and then verify the network by ping and nslookup. If this works good proceed to Part 2 in the below link.
VDP - Avmar Migration: Part-2: Configuring Avamar Virtual Edition 7.2