Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware Validated Design Update from 5.1.1 to 5.1.2 (79047)

Last Updated: 5/26/2020Categories: How toTotal Views: 2816Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Purpose

This article outlines the procedures to update VMware software in a Software-Defined Data Center (SDDC) that is deployed according to VMware Validated Design 5.1.1.

You update the following components to the versions described in the bill of materials for VMware Validated Design 5.1.2:

Platform Service Controller appliances

vCenter Server appliances

vSphere Update Manager Download Service.

ESXi hosts.

VMware Software Versions in the Update

Product Name

Product Version in VMware Validated Design 5.1.1

Product Version in VMware Validated Design 5.1.2

Platform Services Controller

6.7 Update 3b

6.7 Update 3g

vCenter Server

6.7 Update 3b

6.7 Update 3g

vSphere Update Manager Download Service

6.7 Update 3b

6.7 Update 3g

ESXi

6.7 ESXi670-201912001

6.7 ESXi670-202004002

Impact / Risks

This update does not impact the SDDC design and implementation, ensures interoperability, and introduces bug fixes.

Updates That Are Not Validated by VMware Validated Design

VMware makes available patches and releases to address critical security and functional issues for several products. Scalability and functional tests for individual patches, express patches, or hotfixes are not typically performed against a VMware Validated Design.

If a patch must be applied to your environment, follow the VMware published practices and VMware Knowledge Base articles for the specific patch. If an issue occurs during or after the process of applying a patch, contact VMware Technical Support.

If after applying a patch, the new product version no longer adheres to the bill of materials, or interrupts the upgrade to the next published version of the design, you must continue to follow the upgrade path to a version of the design that includes this product version.

Prerequisites

Before you upgrade the virtual infrastructure layer of the SDDC, verify that your existing VMware Validated Design environment meets certain general prerequisites.

Verify that your environment implementation follows exactly the software bill of materials for VMware Validated Design 5.1.1.

Download the vCenter Server Appliance patch VMware-VCSA-all-6.7.0-build_number-patch-FP.iso file locally to a Windows host that has access to the SDDC management network.

Download the vCenter Server Appliance installation VMware-VCSA-all-6.7.0-build_number.iso file locally to a Windows host that has access to the SDDC management network.

Verify that the vSphere clusters have the vSphere DRS set to fully automated mode in both the management and the workload domains.

Note: If set to manual or partially automated then you may need to manually migrate VMs off the host during the remediation process

Verify that any integrations with the Management vCenter Server Appliances are quiesced.

Verify that you have current backups for each Platform Services Controller appliance and each vCenter Server Appliance.

In the VMware Validated Design Upgrade documentation, see General Prerequisites for the SDDC Upgrade, and Best Practices in SDDC Upgrades.

Resolution

Workflow

This is a general overview of the update procedures for this validated design.

Update the Platform Services Controller appliances and the Management vCenter Server appliances in Region A and Region B.

Take snapshots of the Platform Services Controller appliances and of the Management vCenter Server appliances in Region A and in Region B.

Redirect the traffic to the Compute Platform Service Controller in Region A.

Update the Management Platform Services Controller in Region A.

Restore load balancing for the traffic to the Platform Services Controller appliances in Region A.

Redirect the traffic to the Management Platform Services Controller in Region A.

Update the Compute Platform Services Controller in Region A.

Restore load balancing for the traffic to the Platform Services Controller appliances in Region A.

Update the Management vCenter Server Appliance in Region A.

Repeat steps b-h to update the Platform Services Controller appliances and for the Management vCenter Server appliances in Region B.

Update the vSphere Update Manager Download Service in Region A.

Update the ESXi hosts in the management clusters in Region A.

If your Management hosts use vSAN storage, perform the remediation in Region A.

Verify that the vSAN Build Recommendation Engine Health test passes in Region A.

Scan for updates by using vSphere Update Manager in Region A.

Remediate the management ESXi hosts that use vSAN in Region A.

If your Management hosts use stretched vSAN storage, perform the following remediation in Region A.

Verify that the vSAN Build Recommendation Engine Health test passes in Region A.

Scan for updates by using vSphere Update Manager in Region A.

Remediate the management ESXi hosts that use vSAN stretched storage in Region A.

If your Management hosts use traditional storage, perform the following remediation in Region A.

Create a new fixed baseline in the Update Manager in Region A.

Scan for updates by using vSphere Update Manager in Region A.

Remediate the management ESXi hosts that use traditional storage in Region A.

Perform Post-Upgrade Procedures for the Management Cluster in Region A.

Verify the status of the NSX Data Center for vSphere for all ESXi hosts in Region A.

Review the hardware compatibility status for vSAN for the management cluster in Region A.

Remediate VMware Tools in the management cluster in Region A.

Repeat Chapters 2-4 for the Respective Components in Region B to Complete the Update of the Management Cluster in Region B.

Update the Compute vCenter Server Appliances and the ESXi hosts in the shared edge and compute clusters in Region A and Region B.

Take snapshots of the Compute vCenter Server Appliances in Region A and in Region B.

Update the Compute vCenter Server appliance in Region A.

Remediate the compute ESXi hosts that use a vSAN storage in Region A.

Update the Compute vCenter Server appliance in Region B.

Remediate the compute ESXi hosts that use vSAN storage in Region B.

Delete the snapshots for the Compute vCenter Server appliances in Region A and Region B.

Update the SDDC Deployment Details on each vCenter Server Appliance in Region A and Region B.

Cleanup snapshots and perform backups.

Procedure

1. Update the Platform Services Controller appliances and the Management vCenter Server appliances in Region A and Region B.

Take snapshots of the Platform Services Controller appliances and of the Management vCenter Server Appliance instances in Region A and in Region B.

In a web browser, log in to Management vCenter Server by using the vSphere Client.

Setting

Value

URL

https://sfo01m01vc01.sfo01.rainpole.local/ui

User name

[email-masked]

Password

vsphere_admin_password

Click VM and Templates

Navigate to the Management Platform Services Controller appliance.

Right-click the Management Platform Services Controller and select Snapshots > Take Snapshot.

In the Take VM Snapshot dialog box, enter the following settings and click OK.

Setting

Value

Name

VMware Validated Design 5.1.2 Virtual Infrastructure Layer Update

Description

-

Snapshot the virtual machine's memory

Deselected

Quiesce guest file system (Needs VMware Tools installed)

Deselected

Repeat steps c-e to take snapshots for all remaining Platform Services Controller appliances and the Management vCenter Server appliances in Region A and Region B.

Redirect the traffic to the Compute Platform Services Controller in Region A.

From the Menu, select Networking & Security > NSX Edges.

From the NSX Manager drop-down menu, select the 172.16.11.65 NSX Manager, and click the ID of the NSX Edge device for sfo01psc01.

Select Load Balancer tab > Pools.

Select the psc-https-443 load balancer pool and click Edit.

In the Edit Pool dialog box, from the Members pane, select sfo01m01psc01 and click Edit.

In the Edit Member dialog box, from the State drop-down menu, select Disable, and click OK.

In the Edit Pool dialog box, click Save.

Repeat steps d-g for the psc-tcp-389 load balancer pool.

On the Pools page, click Show Status and verify that both psc-https-443 and psc-tcp-389 show status DOWN for sfo01m01psc01.

Update the Management Platform Services Controller in Region A.

Mount the update VMware-VCSA-all-6.7.0-build_number-patch-FP.iso file to the Management Platform Services Controller appliance.

In a Web browser, log in to the Management Platform Services Controller by using the Virtual Appliance Management Interface (VAMI).

Setting

Value

URL

https://sfo01m01psc01.sfo01.rainpole.local:5480

User name

root

Password

psc_root_password

In the left pane, click Update.

In the Update pane, click Check Updates and select Check CDROM.

Click Stage & Install.

In the End User License Agreement section, accept the EULA and click Next.

If you see the Join CEIP section, choose if you want to join or not, else go to next step.

In the Backup Platform Services Controller section, check the I have backed up Platform Services Controller and its associated databases checkbox and click Finish.

Note: You will be logged out of the UI. You will not be able to log in while the update is in progress. Please wait about 10-15 min before logging back in.

After the update completes, log back into the Management Platform Service Controller and in the Installing Upgrades dialog box click Close.

In the left pane, click Update.

In the Update pane, verify that you see the updated version number.

Restore load balancing for the traffic to the Platform Services Controller appliances in Region A.

Use the vSphere Web Client to log in to the Management vCenter Server Appliance by navigating to https://RegionA-management-vc-FQDN/ui.

From the Menu, select Networking & Security > NSX Edges.

From the NSX Manager drop-down menu, select the management-nsx-manager-IP , and double-click the Region-A-PSC-LB NSX Edge device.

On the Manage tab, click Load Balancer > Pools.

Select the psc-https-443 load balancer pool and click Edit.

In the Edit Pool dialog box, from the Members pane, select RegionA-Management-PSC, and click Edit.

In the Edit Member dialog box, from the State drop-down menu, select Enable, and click OK.

In the Edit Pool dialog box, click OK.

Repeat steps e-h for the psc-tcp-389 load balancer pool.

On the Pools page, click Show Pools Statistics and verify that both psc-https-443 and psc-tcp-389 report status UP for RegionA-Management-PSC.

Disconnect the attached update .iso file from the Management Platform Services Controller in Region A.

Repeat steps 2-4 respectively to update the Compute Platform Services Controller in Region A.

Update the Management vCenter Server in Region A.

Mount the update VMware-VCSA-all-6.7.0-build_number-patch-FP.iso file to the Management vCenter Server appliances from the vSphere Web Client.

Log in to the appliance management interface of the Management vCenter Appliance by navigating to https://management-vc-FQDN:5480.

In the left pane, click Update.

In the Update pane, click Check Updates and select Check CDROM.

Click Stage & Install.

In the End User License Agreement section, accept the EULA and click Next.

In the Backup Platform Services Controller section, check the I have backed up Platform Services Controller and its associated databases checkbox and click Finish.

After the update completes, in the Installing Upgrades dialog box click OK.

Log back into the appliance management interface of the Management Platform Service Controller and in the left pane, click Update.

In the Update pane, verify the version number.

Disconnect the attached update .iso file from the Management vCenter Server in Region A.

Repeat steps 2-6 respectively to update the Platform Services Controller appliances and for the Management vCenter Server Appliance Instances in Region B.

2. Update vSphere Update Manager Download Service in Region A

Follow the guidance in Upgrade vSphere Update Manager Download Service in Region A from the VMware Validated Design 5.1.1 documentation and use the VMware-VCSA-all-6.7.0-build_number.iso vCenter Server Appliance installation file to perform the update.

3. Update the ESXi Hosts in the Management Cluster in Region A

If your Management Hosts Use vSAN Storage, Perform the Following Remediation in Region A

Use the vSphere Web Client to log in to the Management vCenter Server Appliance by navigating to https://RegionA-management-vc-FQDN/ui.

Verify that the vSAN Build Recommendation Engine is healthy by using your Customer Connect credentials to download the latest recommendations.

Click Menu > Hosts and Clusters

In the Hosts and Clusters inventory, select the RegionA-management-cluster.

On the Monitor tab, scroll down to Skyline Health under vSAN.

Expand the vSAN Build Recommendation.

Click the vSAN Build Recommendation Engine Health test name and click the Login to customerconnect.vmware.com button.

In the Login dialog box, enter your Customer Connect account credentials and click OK. There should be no issues and status should be green.

Configure the remediation settings for hosts and virtual machines.

Click Menu > Update Manager.

From the Update Manager drop-down menu, select RegionA-management-vc. Click the Settings tab.

Under Remediation Settings, click Hosts.

Click Edit, enter the settings for host remediation, and click Save.

Setting

Value

VM Power state

Do not change the VM power state

Retry entering maintenance mode in case of failure.

Deselected

Allow installation of additional software on PXE booted hosts

Deselected

Migrate powered off and suspended VMs to other hosts in the cluster, if a host must enter maintenance mode

Selected

Disconnect removable media devices that might prevent a host from entering maintenance mode

Deselected

Enable quick boot

Deselected

Under Remediation Settings, click VMs.

Click Edit, enter the default settings for VM rollback, and click Save.

Setting

Value

Take snapshot of VMs

Selected

Do not delete snapshots

Selected

Scan the cluster for upgrades against the new baseline for compliance.

Click Menu > Hosts and Clusters

In the Hosts and clusters inventory, select the RegionA-management-cluster

On the Updates tab, click Host Updates.

In the Hosts are non-compliant pane, click Check Compliance.

After the compliance check finishes, the Status column shows as Non-Compliant.

Remediate the management cluster and upgrade the ESXi hosts that it contains.

On the Updates tab, under Attached Baselines and Baseline Groups, select the vSAN Cluster RegionA-management-cluster baseline and click Remediate.

Select all hosts to remediate in Remediate wizard page and click Remediate.

After the remediation finishes, the Status column for the baseline shows as Compliant. The remediation process might take several minutes.

If your Management Hosts Use vSAN Stretched Storage, Perform the Following Remediation in Region A

Use the vSphere Web Client to log in to the Management vCenter Server Appliance by navigating to https://RegionA-management-vc-FQDN/ui.

Verify that the vSAN Build Recommendation Engine is healthy by using your Customer Connect credentials to download the latest recommendations.

Click Menu > Hosts and Clusters

In the Hosts and Clusters inventory, select the RegionA-management-cluster.

On the Monitor tab, scroll down to Skyline Health under vSAN.

Expand the vSAN Build Recommendation.

Click the vSAN Build Recommendation Engine Health test name and click the Login to customerconnect.vmware.com button.

In the Login dialog box, enter your Customer Connect account credentials and click OK. There should be no issues and status should be green.

Configure the remediation settings for hosts and virtual machines.

Click Menu > Update Manager.

From the Update Manager drop-down menu, select RegionA-management-vc. Click the Settings tab.

Under Remediation Settings, click Hosts.

Click Edit, enter the settings for host remediation, and click Save.

Setting

Value

VM Power state

Do not change the VM power state

Retry entering maintenance mode in case of failure.

Deselected

Allow installation of additional software on PXE booted hosts

Deselected

Migrate powered off and suspended VMs to other hosts in the cluster, if a host must enter maintenance mode

Selected

Disconnect removable media devices that might prevent a host from entering maintenance mode

Deselected

Enable quick boot

Deselected

Under Remediation Settings, click VMs.

Click Edit, enter the default settings for VM rollback, and click Save.

Setting

Value

Take snapshot of VMs

Selected

Do not delete snapshots

Selected

Scan for updates by using vSphere Update Manager in Region A.

Click Menu > Hosts and Clusters

In the Hosts and clusters inventory, select the RegionA-management-dc.

Note: In the data center object you can access the hosts in Availability Zone 1, Availability Zone 2 and the vSAN witness host. If you use the cluster object, you can only access Availability Zone 1 and Availability Zone 2.

On the Updates tab, click Host Updates.

In the Hosts are non-compliant pane, click Check Compliance.

After the compliance check finishes, the Status column shows as Non-Compliant.

Remediate the management ESXi hosts in Availability Zone 1 of the vSAN stretched cluster in Region A.

In the Hosts and clusters inventory, select the RegionA-management-cluster.

On the Updates tab, under Attached Baselines and Baseline Groups, select the vSAN Cluster RegionA-management-cluster baseline and click Remediate.

Select all hosts to remediate in Remediate wizard page and click Remediate.

After the remediation finishes, the Status column for the baseline shows as Compliant. The remediation process might take several minutes.

After you remediate the hosts in Availability Zone 1, repeat step 5 to remediate the hosts in Availability Zone 2.

After you remediate the hosts in both availability zones, update the vSAN witness host.

Note: The vSAN witness host appears as light-blue in the list of target objects.

If your Management Hosts Use Traditional Storage, Perform the Following Remediation in Region A

Use the vSphere Web Client to log in to the Management vCenter Server Appliance by navigating to https://RegionA-management-vc-FQDN/ui/.

Create a baseline for the ESXi image.

Click Menu > Update Manager.

From the Update Manager drop-down menu, select RegionA-management-vc

Click the Baselines tab and click New > Baseline.

In the Create Baseline wizard, follow the prompts and configure the following settings for Name and Description section. Click Next.

Create Baseline Wizard Page

Setting

Value

Name and Description

Name

VMware Validated Design ESXi 6.7 P02 U3g Upgrade

Description

-

Content

Patch

In the Select Patches Automatically section, uncheck Automatically update this baseline with patches that match the following criteria. Click Next.

In the Select Patches Manually section, sort descending by Release Date column and select the latest VMware ESXi 6.7 Patch Release. Click Next.

In Summary section click Finish

Configure the remediation settings for hosts and virtual machines.

Click Menu > Update Manager.

From the Update Manager drop-down menu, select RegionA-management-vc. Click the Settings tab.

Under Remediation Settings, click Hosts.

Click Edit, enter the settings for host remediation, and click Save.

Setting

Value

VM Power state

Do not change the VM power state

Retry entering maintenance mode in case of failure.

Deselected

Allow installation of additional software on PXE booted hosts

Deselected

Migrate powered off and suspended VMs to other hosts in the cluster, if a host must enter maintenance mode

Selected

Disconnect removable media devices that might prevent a host from entering maintenance mode

Deselected

Enable quick boot

Deselected

Under Remediation Settings, click VMs.

Click Edit, enter the default settings for VM rollback, and click Save.

Setting

Value

Take snapshot of VMs

Selected

Do not delete snapshots

Selected

Attach the baseline to the management cluster.

Click Menu > Hosts and Clusters

In the Hosts and clusters inventory, select the RegionA-management-cluster

Click the Updates tab.

Under Attached Baselines and Baseline Groups, click Attach > Attach Baseline or Baseline Group, select VMware Validated Design ESXi 6.7 P02 U3 Upgrade, and click Attach.

Scan the cluster for upgrades against the new baseline for compliance.

On the Updates tab, click Host Updates.

In the Hosts are non-compliant pane, click Check Compliance.

After the compliance check finishes, the Status column for the VMware Validated Design ESXi 6.7 P02 U3 Upgrade baseline shows as Non-Compliant.

Remediate the management cluster and upgrade the ESXi hosts that it contains.

On the Updates tab, under Attached Baselines and Baseline Groups, select the VMware Validated Design ESXi 6.7 P02 U3 Upgrade baseline and click Remediate.

Select all hosts to remediate in Remediate wizard page and click Remediate.

After the remediation finishes, the Status column for the baseline shows as Compliant. The remediation process might take several minutes.

4. Perform Post-Upgrade Procedures for the Management Cluster in Region A

After updating all management ESXi hosts, review the NSX Data Center for vSphere status in the management cluster.

Use the vSphere Web Client to log in to the Management vCenter Server Appliance by navigating to https://RegionA-management-vc-FQDN/ui.

Click Menu > Networking & Security.

In the Navigator, select Installation and Upgrade.

On the Host Preparation tab, from the NSX Manager menu select management-nsx-manager-IP and verify that the Installation Status for all management ESXi hosts is green.

Verify that the vSAN Hardware compatibility tests have passed for the management cluster.

Click Menu > Hosts and Clusters

In the Hosts and Clusters inventory, select the management-cluster object.

On the Monitor tab, scroll down to Skyline Health under vSAN.

Verify that the Hardware compatibility tests have passed and are green.

If you see a warning test result, expand the Hardware compatibility tests, review the individual warning test result, and perform the following troubleshooting steps.

Test That Results in a Warning

Troubleshooting

Controller firmware

Update Storage Controller Drivers and Firmware in the Administering VMware vSAN documentation

Controller disk group

VMware Knowledge Base article vSAN Health Service - Hardware Compatibility - Disk Group Type Check

Controller driver

Update Storage Controller Drivers and Firmware in the Administering VMware vSAN documentation

Controller

VMware Knowledge Base article vSAN Health Service - vSAN HCL Health - Controller Release Support

SCSI controller

VMware Knowledge Base article vSAN Health Service - vSAN HCL Health – SCSI Controller on vSAN HCL

vSAN

VMware Knowledge Base article vSAN Health Service - vSAN HCL Health – vSAN HCL DB up-to-date

Remediate VMware Tools in the management cluster in Region A. See Remediate VMware Tools in the Management Cluster in Region A in the VMware Validated Design Upgrade documentation.

5. Repeat Chapters 2-4 for the Respective Components in Region B to Complete the Update of the Management Cluster in Region B.

6. Update the Compute vCenter Server Appliances and the ESXi Hosts in the Shared Edge and Compute Clusters in Region A and Region B

Update the Compute vCenter Server Appliance in Region A.

Mount the update VMware-VCSA-all-6.7.0-build_number-patch-FP.iso file to the Compute vCenter Server Appliance.

Log in to the appliance management interface of the Compute vCenter Server Appliance by navigating to https://compute-vc-FQDN:5480.

In the left pane, click Update.

In the Update pane, click Check Updates and select Check CDROM.

Click Stage & Install.

In the End User License Agreement section, accept the EULA and click Next.

In the Backup Platform Services Controller section, check the I have backed up Platform Services Controller and its associated databases checkbox and click Finish.

After the update finishes, in the Installing Upgrades dialog box click Close.

Log back into the appliance management interface of the Compute vCenter Server Appliance and click Update in the left pane.

Verify the version number in the Update pane.

Disconnect the attached update .iso file from the Compute vCenter Server in Region A.

Repeat steps under Chapter 3. Update the ESXi Hosts in the Management Clusters and Chapter 4. Complete the Update in the Management Clusters to update ESXi Hosts for Compute Custer in Region A.

Repeat steps 1-3 in this chapter for the Compute vCenter Server and on the ESXi hosts in the shared edge and compute cluster in Region B.

7. Update the SDDC Deployment Details on Each vCenter Server Appliance in Region A and Region B

From the Menu of the vSphere Web Client, select Global Inventory Lists.

In the Navigator, under Resources click vCenter Servers.

Select the Management vCenter Server Appliance and click the Configure tab.

Under the Settings pane, click Advanced Settings and click the Edit Settings button.

In the Edit Advanced vCenter Server Settings dialog box, configure the following property and click Save. (Navigate to next page if needed)

Name

Value

config.SDDC.Deployed.Version

5.1.2

Repeat the procedure for the remaining vCenter Server appliances in Region A and Region B.

8. Cleanup Snapshots and Perform Backups

After all update operations are successfully completed, verify the operations of your environment. You may use the VMware Validated Design Operational Verification guide to assist in your validation procedures.

Once verified, you may remove all pre-upgrade snapshots for each vCenter Server and Platform Services Controller instance.

Delete the snapshots for the Platform Services Controller appliances and Management vCenter Server instances in Region A and Region B.

Use the vSphere Web Client to log in to the Management vCenter Server Appliance by navigating to https://RegionA-management-vc-FQDN/ui.

Navigate to the Management Platform Services Controller.

Right-click the Management Platform Services Controller and select Snapshots > Delete All Snapshots.

In the Confirm Delete dialog box, click Ok.

Repeat steps a-d for all Platform Services Controller appliances and the Management vCenter Servers in Region A and Region B.

Delete the snapshots for the Compute vCenter Server instances in Region A and in Region B.

Use the vSphere Web Client to log in to the Management vCenter Server Appliance by navigating to https://RegionA-compute-vc-FQDN/ui.

Navigate to the Compute vCenter Server.

Right-click the Compute vCenter Server and select Snapshots > Delete All Snapshots.

In the Confirm Delete dialog box, click Ok.

Repeat steps a-d for the Compute vCenter Server instances in Region B.

Initiate a new image-based backup for each vCenter Server and Platform Services Controller using supported vSphere APIs for Data Protection (VADP) enabled backup solution.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
VMware Workspace ONE Web 7.13 for Android リリースのお知らせ (79051)

KB
•
Workspace ONE Tunnel 5.6 for Android リリースのお知らせ (79048)

KB
•
VMware AirWatch Relay Service 4.3 for Android リリースのお知らせ (79016)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Validated Design for Software-Defined Data Center (SDDC) 5.1.x

VMware Validated Design for Software-Defined Data Center (SDDC)

Take Our Survey

Support Assistant