Backup VMs according to cluster or data store.
In this cluster scenario, the VMware environment consists of more than 3,000 VMs. Host clusters are used to manage the hardware resources. Although most of these clusters contain from 3 to 4 ESXi hosts each, some clusters contain as many as 10 ESXi hosts. However, some ESXi hosts are running from 1 to 3 VMs for larger, mission critical VMs. In order to manage the load, additional VMware hosts are frequently added or removed as needed. Each ESXi host in the cluster manages 10 - 30 VMs. Since the total number of VMs in each cluster ranges from 100 to 200, each host cluster is backed up to a dedicated vStorage Backup Server. Each server uses a dedicated data mover node to run the backup operation.
You can select host clusters to back up with the Data Protection for VMware vSphere GUI Schedule a Backup wizard. In the Data Protection for VMware vSphere GUI Getting Started window, click Define a backup task to open the Schedule a Backup wizard.
domain.vmfull vmhostcluster=TivDev01
domain.vmfull vmhostcluster=TivDev02,TivDev03;-vm=VMTest*
domain.vmfull vmhostcluster=TivSVT01,TivSVT02,TivSVT03,TivSVT04
These domain.vmfull vmhostcluster= statements can be repeated for each host cluster.
The VMware environment is similar to the environment described in the Cluster Scenario. However, this environment contains individual host clusters that contain too many VMs for a single data mover node backup window. A data mover can be assigned for each host or added to an existing data mover that is already processing a host cluster. This type of implementation can also be applied to individual VMs.
These host scenarios plan for a vStorage backup server (data mover) for each host on production systems that contain larger VMs or an increased data change rate.
You can select hosts to back up with the Data Protection for VMware vSphere GUI Schedule a Backup wizard. In the Data Protection for VMware vSphere GUI Getting Started window, click Define a backup task to open the Schedule a Backup wizard.
domain.vmfull vmhost=TivProd01,mycompany.com
domain.vmfull vmhost=TivProd02.mycompany.com,TivProd03.mycompany.com;-vm=MailDept*
domain.vmfull vm=MailDept*
This domain.vmfull
vm= statement can be repeated for each host.vm=prod1*,*testvm,*dept*,dept4?prod
This
command (with wildcards) produces a list that includes only those
VMs that match the domain.vmfull filter string with
no duplicates. The order of the domain keywords does not affect the
results. Exclusion statements are always processed at the end. As
a result, the end statements override the inclusion statements.In these wildcard scenarios, a separate data mover is defined to back up the VMs based on their naming convention. New VMs can be added and included the scheduled backup operation.
domain.vmfull vm=MailDept*
domain.vmfull vm=TrainingVM*
domain.vmfull all-vm;-vm=MailDept*,TrainingVM*