How to migrate some VMware applications to a different datacenter

Products

• VMware Aria Suite

Issue/Introduction

The article provides guidance of moving some VMware applications to a new datacenter. See the Environment section for a list of those products.

Environment

• VMware Aria Automation 8.x
• VMware Identity Manger 3.3.7
• VMware Aria Suite Lifecycle 8.x

Resolution

Pre-Req: Clean-up

• Review the temp folders of the appliances for any files that can be removed (old patches, hprof files no longer needed)
• Following this procedure will result in the applications being inaccessible to end users. Perform this during a scheduled maintenance window.

Clone the appliances to backup Aria Automation and Identity Manager:

• Time estimate: Cloning times to be added by the end user. Reboot/Redeploy = ~1 hour.
  • Verify Aria Auto cluster is in a healthy state by using the following command: vracli service status
  • Shutdown Aria Auto appliances, vIDM appliance and clone them, and place in an isolated folder:
  • Command to shut down Aria Automation services (this does not shut down the guest operating system): /opt/scripts/deploy.sh –shutdown
  • During this cloning period, Aria Auto/vIDM will be unavailable.
  • Power on the Aria Automation appliances
  • Redeploy Aria Automation services by using the following command: /opt/scripts/deploy.sh

1. Aria Automation

• Time estimate: 10 minutes or less
  
  • Following steps 1 and 2 for each node: Change IP address of vRA Node or Cluster

2. VMware Identity Manager

• Time estimate: time may to move vIDM will be provided by end user. Steps to Re-IP: ~30 minutes
  • Follow the steps 1-4 from Change IP Address in a VMware Identity Manager Single Node Standard Instance
  • Move vIDM appliance to the new vCenter
  • Follow the steps 5-9 from Change IP Address in a VMware Identity Manager Single Node Standard Instance

3. Continue with Aria Automation

• Time estimate: A majority of time during this procedure will be spent moving. The estimated time will vary widely and can only be provided by the end user based upon knowledge of their infrastructure.

• 1. Shut down services
  2. Shutdown PhotonOS with a Guest Operating System shutdown for each node in the cluster.
  3. Move the appliances to the target vCenter.
  4. After the migration of appliances is complete, power on the appliances.

4. Update Load Balancer settings

• Time estimate: ~15 mins
  • Update for the Aria Auto Load Balancer (vIDM is a single node in this example and has no LB).
    • The updates will be to the pools and virtual server details. See LB guide for the LB brand.

5. Update DNS / resolvers as necessary

6. Change to a new IP for Aria Automation as needed.

• Time estimate: Majority of time is the Reboot/Redeploy = ~1 hour

  • Run Step 5 to change the IP of Aria Auto on each node in the cluster.
  • Run Steps 6 and 7 to reboot Aria Auto and redeploy the services.

Note: Aria Auto services will be unavailable during this time.

7. Update Aria Suite Lifecycle appliance IP address. Additional guidance in the following blog.

• Time estimate: 30 minutes
  • Take Snapshot of vRLCM (No Memory and No Quiescing)
  • Modify existing DNS records to accommodate new IP Address
  • Execute command to access the process to change network configuration of this appliance

Note: Your session will be disconnected as soon as it says “Reconfiguring eth0” which is expected as the IP Address has now changed

• • Open a new session and execute the same command to display the new network configuration
  • Additional appliancelidation is to check by rebooting the vRLCM appliance and review its state.
  • You can also access the system settings and check the new configuration.

8. Execute Inventory Sync in the Aria Suite Lifecycle Repository to update the new IP address in the Aria Suite Lifecycle Manager inventory

• Time estimate: ~5 minutes
  • Follow the step 10 from “Change IP Address in a VMware Identity Manager Single Node Standard Instance” from the vIDM link

Additional Information

Aria Suite Lifecycle: 
Blog: https://www.arunnukula.com/post/changing-the-ip-address-of-vrlcm-after-it-s-deployment