Hello All!
Today I began examining vSphere Data Protection 5.5.1.356 (because I have a 5.1 vCenter) for our lab environment as it is included in the Enterprise and Enterprise Plus license. The vDP is based on EMCs Avamar technology and builds a 4 CPU, 4 GB RAM VM for use as the proxy.
The setup is fairly simple with only a couple of issues along the way.
http://www.vmware.com/files/pdf/products/vsphere/VMware-vSphere-Data-Protection-Administration-Guide.pdf
Today I began examining vSphere Data Protection 5.5.1.356 (because I have a 5.1 vCenter) for our lab environment as it is included in the Enterprise and Enterprise Plus license. The vDP is based on EMCs Avamar technology and builds a 4 CPU, 4 GB RAM VM for use as the proxy.
The setup is fairly simple with only a couple of issues along the way.
http://www.vmware.com/files/pdf/products/vsphere/VMware-vSphere-Data-Protection-Administration-Guide.pdf
- Download the Virtual Appliance from the VMware website, and place it in a convenient place for you to install it from.
- Create a DNS entry for this Virtual Appliance as it is very picky about using DNS.
- Wait some time to verify the DNS is replicated.
- Deploy the OVA for the Virtual Appliance.
- Provide the Networking information during the deployment and let it run.
- Once it is running, login to the web interface to configure the VA.
- Although odd you have to specify a 9 digit password w/ a letter and number
- Also the account for this appliance also has to have access to the environment and cannot be provided permissions through group membership.
- Once running and pointed to the vCenter, you can only access vDP through the Web Client of vCenter. So the demise of the VIClient continues.
- First run places the vDP interface at the home location within the Web Client and is fairly intuitive on how it lays out the interface.
I will post more pictures as I make them and post a second part as per usability.
C
Comments