When new VMs are deployed, they are added automatically to the backup job, which is undesired.
If a VM is excluded from the backup job, when migrated, VM is not automatically excluded from the backup job on another ESXi host if the backups are created on the ESXi hosts. The VMs need to be excluded again by editing the backup job.
The automatic inclusion of VMs is by design, we have alternatives to avoid this but new jobs need to be configured.
We have two alternatives:
- Create the jobs on the VMware Folders instead of the Cluster.
- In My Inventory, in the same tool bar where we can add, edit and remove inventory vCenter and Hosts, to the right side there is an Icon that looks like 'Hosts and Clusters' from vCenter, click it and a drop-down menu will appear, select 'Virtual Machines and Templates'.
- The inventory will reload, expand and the Folders will be visible, right click the folder where the backup job is desired and follow the wizard. VMs that need to be protected can be added to that folder from the vSphere Client and they will be added to the job at this moment. This works as an automated inclusion list per folder.
- Use Backup Groups.
- At the bottom of your Inventory, a tab collapsed tab called Backup Groups is visible, click it and an inventory will appear. Right-click the empty space and select 'Add Backup Group'.
- Give it a name, expand the inventory and check the VMs that need to be protected. Note that if a cluster, host, folder or any item that contains VMs is selected, all the VMs underneath it will be included in the job automatically. Please check only the desired VMs or Folders, this works as a manual inclusion list.
