Reconfiguring a VM
When a VM is running in cloud, its settings can be changed using the "Reconfigure Cloud Instance" wizard in the Velostrata plug-in for vCenter Web Client. You can change the instance type (for example, select an instance that performs better for this workload, or an instance that costs less, and so on). When changing the instance type, a reboot is required, however the instance Private IP address and other identifiers remain the same. You can also reconfigure the storage policy from Write Back to Write Isolation, and vice-versa.
All virtual machine state and data created in cloud in write-isolation mode will be lost when machines are moved back on-premises. Related virtual machines, which are part of the same application, should be moved together to align application state. Make sure to copy out to a persistent location any data you wish to keep prior to moving such machines back to on-premises.
A typical scenario for changing the storage from Write Isolation to Write Back is for a Dev-Test environment or a project that is nearing an end. By changing the VM to run from Write Isolation to Write Back, the data is written back to on-premises. Once the data is backed up, you can then run the VM back on-premises.
When switching from Write Back to Write Isolation, the edge node stops transferring the data from the cloud instance. This may result in an inconsistent snapshot.
To reconfigure a VM:
- On the vSphere Web Client, select the desired Virtual Machine.
- Right-click on the required VM and select Velostrata Operations > Reconfigure virtual machine.
- Select new Instance Type.
- Click Next.
Note: You cannot reconfigure the storage on a cloned VM or on a spot instance.
- To change the storage policy, select either Write Back or Write Isolation and then click Next.
- For GCP, enter the Network Tags (in a comma-separated list) and click Next.
- Review the summary (where changes are noted with the small blue icon) and then click Finish (or click Cancel to leave the current VM configuration as is).