Migrating Ops Manager to a New Datastore in vSphere

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 datacenter.

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 may be disrupted as a result of the migration.

Before You Begin

These sections describe the steps you should perform 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 proceeding 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:

1. Run one of these commands:

   • If you use BOSH CLI v2, run:

     bosh -e BOSH-ENVIRONMENT instances --details > instances.txt
     

     Where BOSH-ENVIRONMENT is the alias you assigned to your BOSH Director.

   • If you use the original version of the BOSH CLI, run:

     bosh-old instances --details > instances.txt
     

2. Save the resulting instances.txt file to a safe location.

3. 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:

1. Check that there are no pending changes and that the status of all tiles is green.

2. Make sure the last Installation Log does not contain any errors.

3. Before proceeding with the migration, click Review Pending Changes and Apply Changes to make sure there are no errors in the Installation Log.

Procedure: Migrate Ops Manager to a New Datastore

To migrate your Ops Manager deployment to a new datastore:

1. Navigate to the Ops Manager Installation Dashboard.

2. Click the BOSH Director tile.

3. Select vCenter Config.

4. 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.

5. Click Save.

6. Click Review Pending Changes, then Apply Changes.

7. Confirm that the BOSH Director VM has persistent disk on the new datastore.

   1. Select vCenter Resource Pools and select the Resource Pool that contains your Ops Manager deployment VMs and new datastore.
   2. Click the Related Objects tab.
   3. Click Virtual Machines.
   4. Locate the Ops Manager VM and verify that the VM has an expected value in the Provisioned Space column.

   

8. In the BOSH Director tile, select Director Config.

9. Select the Recreate VMs deployed by the BOSH Director option.

10. Click Review Pending Changes.

11. If you are using any service tiles, select the Recreate All On-Demand Service Instances errand for each of the tiles you migrate.

12. Click Apply Changes.