Volume manager server upgrade#
When installation is complete, navigate to the svmanager_setup.log file in the App Volumes Manager Log folder and verify that the upgrade was successful.Įxample path: C:\Program Files (x86)\Cloud Volumes\Manager\Log In the svmanager_setup.log file, which contains a list of migration steps performed, verify that the last entry is AddTimeStampsToMachineManager.
![volume manager server volume manager server](https://d282q3w9o1r1mp.cloudfront.net/Images/Doc/ServerManager2.png)
Note: Be sure to turn off this option once the upgrade is complete and functionality has been verified. If you have any issues with your certificates or communications between components, you can try an alternate route (HTTP), which streamlines troubleshooting. This is optional but recommended when performing an upgrade.
![volume manager server volume manager server](https://www.partitionwizard.com/images/uploads/articles/2019/05/partition-manager-windows-server-2003/partition-manager-windows-server-2003-7.png)
It is important to replace the self-signed certificates with CA-signed certificates, especially for AppVolumes implementations in a production environment.
Volume manager server update#
In this model, you update the App Volumes Manager component on one server at a time, rolling through the upgrade process until all servers are upgraded.
Volume manager server full#
Full change window – In an ideal world, we recommend planning a full change window (outage), meaning you would take the App Volumes Manager servers offline and make sure no users are connected to the environment.
![volume manager server volume manager server](http://www.server-partition-software.com/img/newtu/windows-server2008-volume-manager-software.jpg)
There are basically two strategies for upgrading during a scheduled maintenance window: