When you update the vSphere Data Protection instances for version 4.0 of this VMware Validated Design, you update the instance in Region A and then in Region B, or update the two vSphere Data Protection instances in parallel.

About this task

Perform the upgrade outside of the backup windows.

Upgrading vSphere Data Protection is a single-step operation in which you upgrade the virtual appliances in each region.

Table 1. vSphere Data Protection Nodes in the SDDC



IP Address

Fully Qualified Domain Name

Region A

Backup Node


Region B

Backup Node



VMware Validated Design 4.1 introduces a new convention for host and object names in the SDDC. The step-by-step upgrade guidance uses the new names for both the pre- and post-upgrade SDDC setups. For information about the new convention, see Mapping Component Names Between Versions 4.0 and 4.1 of VMware Validated Design.



If you are not using vSphere Data Protection ensure that the 3rd party software has been validated from your vendor and is compatible to work with vSphere 6.5, then follow the vendor's prescribed upgrade documentation.

  • Download the vSphere Data Protection upgrade vSphereDataProtection-6.1.x.iso file to a shared datastore for mounting to the virtual appliances.

    If you have space on your NFS datastore, upload the file there.

  • Verify that approximately 2 GB are free on Hard Disk 1.

    Use the mccli server show-prop command on each appliance over SSH.

  • Verify that the maintenance window is in a time period in which no backup jobs are running or scheduled to run.

  • Verify that no alarms on the vSphere Data Protection virtual appliances exist in both the vSphere Web Client and the vSphere Data Protection configuration interface.

What to do next

  • Verify that vSphere Data Protection functions flawlessly after the upgrade. See Validate vSphere Data Protection in the Operational Verification documentation.