Skip to content

Instantly share code, notes, and snippets.

@sneal
Last active July 19, 2023 19:34
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save sneal/e65b2ca2d01db783dd88c01eae9e867a to your computer and use it in GitHub Desktop.
Save sneal/e65b2ca2d01db783dd88c01eae9e867a to your computer and use it in GitHub Desktop.
This topic describes how to migrate your VMware Tanzu Operations Manager (Ops Manager) installation to a new vSphere datastore.
Prerequisites
Both the new and existing vSphere datastores must reside in the same data center.
To avoid service disruption, VMware recommends that you configure your overall Ops Manager deployment for high availability (HA). In addition, check for configurations necessary to achieve HA in each of your installed product tiles.
If your environment has any single points of failure, service might be disrupted as a result of the migration.
Before You Begin
The following sections describe the steps you can do prior to the migration.
Step 1: Back Up Your Environment
Ensure that your Ops Manager environment is fully backed up.
For more information about how to back up Ops Manager, see Backing Up Deployments.
Step 2: Document Current Environment Settings
Document your current environment settings before you proceed with the datastore migration. Record which VMs are running and in which datastore they reside. If you experience any issues during or after the migration, you must have this information to restore your environment.
To obtain this information:
Run one of these commands:
bosh -e BOSH-ENVIRONMENT instances --details > instances.txt
Where BOSH-ENVIRONMENT is the alias you assigned to your BOSH Director.
Save the resulting instances.txt file to a safe location.
Note the datastore where each VM resides in vSphere.
Step 3: Check System Health
Check the Status tab in your runtime product tiles, such as VMware Tanzu Application Service for VMs (TAS for VMs) or VMware Tanzu Kubernetes Grid Integrated Edition (TKGI), and make sure there are no errors or reported issues.
Step 4: Check Installed Products Health
In each tile installed in your Ops Manager deployment, check the Status tab and make sure there are no errors or reported issues.
Step 5: Check BOSH Director Status
To check the status of your BOSH Director:
Verify that there are no pending changes and that the status of all tiles is green.
Make sure the last Installation Log does not contain any errors.
Procedure: Migrate Ops Manager to a New Datastore
To migrate your Ops Manager deployment to a new datastore:
Go to the Ops Manager Installation Dashboard.
Click the BOSH Director tile.
Select vCenter Config.
Update the Ephemeral Datastore Names and Persistent Datastore Names fields to reflect the new datastore names.
Note: If you use the datastore clustering feature in vSphere, provide only the datastore cluster name in the Persistent Datastore Cluster Names // Ephemeral Datastore Cluster Names fields.
Click Save.
Click Review Pending Changes, then uncheck the Select All Products checkbox so that only the BOSH Director tile is still selected. Click Apply Changes.
Confirm that the BOSH Director VM has persistent disk on the new datastore.
From vCenter find the BOSH Director VM
In the Related Objects section verify the Storage has been updated to the new datastore.
In the BOSH Director tile, select Director Config.
Select the Recreate VMs deployed by the BOSH Director option.
Click Review Pending Changes.
If you use any service tiles, select the Recreate All On-Demand Service Instances errand for each of the tiles you migrate.
Click Apply Changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment