Browse this section

Requesting virtual-machine changes safely

A request to change a virtual machine should identify both the new resource requirement and the effect on the application. Some changes can be made online in certain environments, while others require a restart or migration. Do not assume that every guest supports the same procedure.

Provide a complete change request

  • Service and virtual-machine name, current resources, desired CPU, RAM or storage, and the reason for the change.
  • Operating system and application dependencies, including any licences tied to hardware characteristics.
  • Current backup status, permitted downtime and the person who will validate the application.
  • A rollback plan, noting that expanding a filesystem or disk may not be easily reversible.

We will confirm the supported method, capacity and charges before proceeding. After completion, check the operating system, application, monitoring and backups. A successful hypervisor task does not by itself confirm that the application is functioning correctly.

Was this guide helpful?

Related guides

When to choose a managed private cloud

A private cloud can help organise multiple virtual machines on a planned cluster, with shared operational controls and capacity management. It is most useful when the environment needs to b…

Understanding usable capacity in a vSAN cluster

Raw drive capacity is not the same as space available to virtual machines in a distributed storage cluster. Protection policies, layout, metadata, operational reserves and rebuild requireme…

Need help applying this to your service?

Tell us your service reference and what you need to achieve. Never include passwords or private keys in a ticket.

Contact support →
← All knowledgebase topics