Use the workflow to upgrade VMware Data Services Manager from version 2.0.3 to version 2.1.
Note: As part of VMware integration with Broadcom, Tanzu Network is no longer available for the software downloads and updates. Use the Broadcom’s Customer Support Portal at
https://support.broadcom.com/ as a software distribution channel. See
a knowledge base article (ID#: 367105) .
When you perform the upgrade, keep in mind the following considerations:
- VMware Data Services Manager supports upgrades to version 2.1 only from version 2.0.3. If you use VMware Data Services Manager version earlier than 2.0.3, upgrade it to 2.0.3 before upgrading to 2.1.
Note: When you upgrade VMware Data Services Manager from earlier releases to 2.0.3, you must perform additional steps and manually run a script to complete the upgrade. This script creates a standby vCenter service account that would help in service account password rotations. For more information, see What's New in Release 2.0.3.
- Because Tanzu Network is no longer available, you cannot download VMware Data Services Manager from Tanzu Network using the Tanzu Network Refresh Token. You must instead use the Provider Repo and manually populate the Provider Repo with the new version of VMware Data Services Manager to upgrade from 2.0.3 to 2.1.
- Provider Repo still exists in VMware Data Services Manager 2.0.3 and can be used for upgrades. Starting with the 2.1 version, VMware Data Services Manager no longer supports the Provider Repo and removes it after you perform the upgrade to version 2.1.
- When upgrading VMware Data Services Manager version 2.0.3 to 2.1, the log forwarding settings from version 2.0.3 are not migrated. You must reconfigure log forwarding in VMware Data Services Manager 2.1 after the upgrade.
Follow these upgrade steps if you used an environment with configured VMware Tanzu Network Refresh Token or an air-gapped environment to set up VMware Data Services Manager version 2.0.3.
- Use the VMware Data Services Manager console to remove the Tanzu Network Refresh Token that you previously configured.
This step applies only to the environment where VMware Tanzu Network Refresh Token has been configured.
Note: VMware Data Services Manager version 2.1 no longer supports the Tanzu Net Token for software updates.See Remove the Tanzu Net Token from VMware Data Services Manager.
- Download
dsm_update_bundle.zipbundle of VMware Data Services Manager version 2.1 from Broadcom’s Customer Support Portal. - Populate the Provider Repo with new database templates and software updates.
- If you configured VMware Data Services Manager 2.0.3 with VMware Tanzu Network, set up the Provider Repo and populate the Provider Repo with the VMware Data Services Manager version 2.1 bundle.
See Set Up the Provider Repo for VMware Data Services Manager Version 2.1.
- In the air-gapped environment, make changes necessary for an upgrade and populate the Provider Repo with the version 2.1 bundle.
See Prepare the Provider Repo for an Upgrade of VMware Data Services Manager from Version 2.0.3 to 2.1.
- If you configured VMware Data Services Manager 2.0.3 with VMware Tanzu Network, set up the Provider Repo and populate the Provider Repo with the VMware Data Services Manager version 2.1 bundle.
- Initiate an upgrade to VMware Data Services Manager version 2.1.
See Check for Upgrades from the DSM Console.
Note: During an upgrade from 2.0.3 to 2.1, you can see a warning requesting you to accept the new certificate to proceed with the upgrade. - Verify that the update is available and displayed in the Available Upgrades table.
Note: After an upgrade from version 2.0.3 to 2.1, when you ssh to a Provider VM, you can see a host identification warnings. This is expected because the appliance ssh keys have been regenerated.
