Veeam Home | Support | Downloads
Best Practices for Veeam Backup & Replication 7.0 for VMware

Veeam Management Pack Help Center  > Best Practices for Deployment & Configuration >  Backup Job Setup > Object Selection

Object Selection

Previous page Next page Print this Topic

Table of contents

Veeam Backup and Replication provides flexible selection of objects that should be included in the job. In the Virtual Machines step of the job wizard, the Add Objects screen offers various “views” into the vCenter architecture that match the views provided by the vSphere client.

vmware_backup_vms_zoom80

This screen also includes advanced methods of exclusion that allow you to select a parent object, but then exclude child objects, or even individual disks within a VM. You can switch between the Hosts and Clusters, VMs and Templates or Datastores and VMs view by pressing the appropriate button on the backup object selection screen.

More guidelines on object selection can be found in the table below:

Recommendation

Explanation

Create jobs that contain a manageable amount of data.

For maximum performance and reliability, it is recommended to meet the following guidelines for total size of VM data within a job:

Local Target (1MB blocks): 32TB

LAN Target (512KB blocks): 16TB

WAN Target (256KB blocks): 8TB

Note: These are maximum suggested job sizes based on the backup architecture; however, there can be very good reasons to keep jobs smaller than this: smaller backup files are easier to manage or move to new storage, they need less time and space when running a full backup, and require smaller staging areas for restores from tape.

Group similar VMs in the same job, especially those created from the same or similar templates.

VMs created from the same or similar templates will increase dedupe, but keep in mind backup windows and size of the job for manageability.

Select objects based on resource pools, virtual infrastructure folders, or datastores. For example, if you need to perform backup of VMs residing on one datastore, instead of creating several backup jobs working with this datastore, you can create a single backup job and add the datastore as a VM container to it.SAS

Creating jobs based on resource pools, folders, or datastores can simplify management of backups. New machines that become members of these groups are automatically included in the backup job.

Notes:

This approach requires monitoring of jobs to make sure there is enough space.

If using datastores (or a mix of resource pools), make sure you do not get overlap in object selection, since VMs have disks in multiple datastores.

Limit the number of exclusions used in backup object selection.

While exclusions can be very useful, virtual infrastructure has a tendency to be dynamic and changes over time, and you must carefully consider their use in your environment. It’s quite easy for a VM to be moved to a folder or resource pool that is excluded and move jobs, or become unprotected.

Table of contents