- Deploy the OVA appliance (Unlike VDP 5.1, you will not see appliance per capacity. In VDP 5.5, you will have only 1 appliance which can be configured for 0.5TB,1TB & 2TB in vdp-configure wizard)
- Note– You would still need a IPv4 static IP for VDP 5.5 with proper DNS Name assigned (Check forward and reverse lookup before using the IP for deployment)
- Once the OVA is deployed, you can notice the appliance settings as below.
- Once the appliance is powered ON, you should be able to access the vdp-configure page unless you have any network issues.
- https://<IP of the appliance>:8543/vdp-configure/in the browser
- Default User – root
- Default Password – changeme
- Self Explanatory (Network Settings)
- Self Explanatory (Time zone)
- Self Explanatory (VDP Credentials)
- vCenter registration : For vCenter username, do *NOT* use the format User@Domain, instead use Domain\User in case you are specifying a domain. (Using @ format will create issues while generating VDP related tasks in web client). Also note that, the user should be provided administrator role)
- Create Storage: This is newly introduced in VDP 5.5 (You have an option to choose the capacity here OR attach backup disks from another VDP appliance)
- Device Allocation: This is new as well in VDP 5.5 (Unlike VDP 5.1, you have an option now to choose datastores for each of the data disk OR you can choose to store with the appliance as well)
- 0.5 TB (3 disks of 256 GB each)
- 1 TB (6 disks of 256 GB each) & 2TB (12 disks of 256 GB each)
- You have the option to choose the number of storage disks for each datastore
- Ready to Complete (Performance Analysis - Optional): This is again new in VDP 5.5. (You have an option to run performance analysis. If chosen to run, VDP will execute (Write, Read & Seek) tests onto the above selected datastores and reports information about the write/read/seek throughput and whether the datastores met the minimal performance recommendations of VDP)
- First starts with creating/configuring disks on the datastore
- Secondly, runs the performance analysis
- Once done, restart the appliance. You should be able to monitor the progress of the VDP appliance configuration from the web client
- Once the configuration is completed, re-login into the web client and you should see the VDP plug-in (vSphere Data Protection 5.5) in the web client. (To avoid common connection issues, make sure the VDP appliance time is in sync with the VM/Host time on which SSO is deployed)
- Due some technical reasons,VDP 5.5 create's separate plugin (vSphere Data Protection 5.5) in the web-client without merging to older 5.1 plugin (vSphere Data Protection). Older VDP 5.1 appliance's can be accessed using the old plugin(vSphere Data Protection), and VDP 5.5 appliances using new plugin(vSphere Data Protection 5.5).