Migrating applications and their associated volumes from one server to another can be a meticulous process, requiring careful planning and execution. In this guide, we will walk you through the steps involved in migrating App Volumes from an existing server to a new server while ensuring a seamless transition.
Step 1: Prepare the New Server
Before initiating the migration process, set up a new Windows server and add it to the domain. Assign a static IP to the new server on the DHCP server to ensure stability and reliability during the migration process.
Step 2: Install App Volumes on the New Server
Install the same version of App Volumes on the new server as the existing one. During the installation process, choose the option to connect to an existing SQL server and point the installation to the database used by the current App Volumes deployment. Ensure that certificate validation is unticked unless you are using this feature on the SQL server. Enter the details of the existing App Volumes SQL server and database when prompted.
Step 3: Verify App Volumes Manager Access on the New Server
After the installation is complete, open the App Volumes Manager on the new server to verify access and log in. If prompted, enter the details for the existing App Volumes manager, including IP, hostname, FQDN, username, and password for connectivity.
Step 4: Configure Certificates for the New Manager
If a Certificate Authority (CA) authority certificate was configured for the existing manager, ensure that a certificate is ready for the new manager. If a wildcard certificate was used, it can be reused. Install the certificate and reboot the server as per the relevant documentation provided by VMware.
Step 5: Update Load Balancer Configuration (If Applicable)
For environments with multiple managers and load balancing, update the load balancer configuration by adding the new manager. Follow the VMware documentation on load balancing (https://kb.vmware.com/s/article/91085) and ensure the new manager is added to the existing round robin pool.
Step 6: Reinstall App Volumes Agent on Parent Image or RDS
If there is only one App Volumes Manager, reinstall the App Volumes agent on the parent image, Remote Desktop Services (RDS), or any relevant Windows OS. During the installation, point the installer to the new server when prompted.
Step 7: Remove Old Manager from App Volumes Manager Console
Once the new manager is verified and the migration is successful, navigate to Configuration > Managers and delete the old manager from the App Volumes Manager console.
Step 8: Uninstall App Volumes from the Old Server
To complete the migration, uninstall App Volumes from the old server. This step ensures that no remnants of the old deployment interfere with the new server.
Conclusion:
Migrating App Volumes to a new server requires careful consideration and adherence to best practices. By following these step-by-step instructions, you can successfully transfer your application volumes while minimizing downtime and ensuring a smooth transition for end-users.
Thinkvirtuals 
Leave a comment