How to build a backup plan for VMware machines: start by checking compatibility, continue with orderly configuration, and finish with a test restore. Because a backup we haven’t tried to restore is a bit like an umbrella we bought but haven’t opened in the rain.
Before Starting
- Make sure that the license and version include Virtual Machine Edition and that they support your VMware version.
- In the manufacturer's guide from which the procedure was built, vSphere 6.0 and above is specified. This is the historical threshold of that guide; check the updated supported versions list before deployment.
- Make sure there is a valid host or address, an account with the required administrator permissions for connection, network access, and a storage target with sufficient capacity.
- Note which machines, disks, and restore points are required. Backing up every machine “just in case” can grow faster than the storage account.
Configuration in the management console
-
Open a new plan.
In the console, go to Remote Management, find the computer on which the component is installed Virtual Machine Edition, open the gear menu and select Show Plans. In the area Backup , click the plus sign and select VMware.
-
, provide a name and select a target.
Give the plan a name that can be identified in reports. Select the storage target and the type of backup. According to the default setting of the documented procedure, the plan settings are saved in storage; check the option to save the configuration locally.
-
Connect to the host and select machines.
Enter the host details and the connection account with the required permissions and click. Connect. After displaying the list of machines, select all of them, only the running ones, or specific machines. Narrow the selection to what is required to control volume, time, and cost.
-
Decide on CBT and consistency.
If the environment supports it, enable it. Use Changed Block Tracking (CBT). After the first full backup, CBT identifies changed disk segments and allows the incremental backup to transfer only the changes. On a running machine it is possible to enable Quiesce guest file system to bring the data on the disk to a state more suitable for backup. Ensure VMware Tools and compatibility, and do not assume that quiescing guarantees application-level consistency in every app.
-
Choose disks and protection.
Mark the required virtual disks. Set compression and encryption according to your policy. If you chose encryption, store the password in a secure and separate place: without it, you may not be able to recover.
-
Set retention and schedule.
Determine how many versions and how long to retain. In a custom policy, you can set expiration for deletion, number of versions, andpurge delay — the time between deleting the data from the machine and deleting the copy from storage. For a one-time run, choose No schedule or a date. For recurring runs, define separately the Recurring For incremental backups and the corresponding option for full backup; usually, the full backup is scheduled less frequently.
-
Actions, alerts, and retention
As needed, define a script before or after the program, or an additional backup program that will start afterward. Choose who and when to send alerts. Review the summary and save.
Configuration via the backup agent
- Open the agent, select VMware On the home screen, choose the storage type and storage account; a new account can be added if required.
- Name the program, enter the host name and the authorized user details. The option Remember password saves the login details in the agent; use it according to the organization’s secret security policy.
- Select machines: all, only running, or manual selection. Enable CBT and quiescing only if suitable for the environment.
- Choose disks, compression, and encryption; set version retention, schedule, pre/post actions, and alerts.
- Review the program summary and run according to the appropriate maintenance window.
Post-run check
- Check status, warnings, machines, and disks in the report — not just that the task is completed.
- Make sure a restore point appears at the destination and that the retention policy matches the requirement.
- Restore a file or machine to an isolated environment and check the data and applications.
Sources and notes
This procedure was adapted from the manufacturer’s VMware backup configuration documentation. Numbers and option names were retained; check compatibility with the installed version.


