Protecting VMware virtual machines with file-level backups
In most cases, Unitrends recommends that you use host-level backups to protect your VMware virtual machines. However, in some instances, you might wish to protect your VMs at the guest level in the same way you would protect physical machines, using file-level backups. Host- and file-level backups provide you with different options.
Use the following topics to determine whether to run host- or file-level backups of VMware virtual machines:
General features of VMware host-level and file-level protection are given here:
Notes:
To protect a VM with both host-level and file-level (agent-based) backups, be sure to adhere to the following:
• | Ensure that the VM's host-level and file-level jobs do not overlap. Running both simultaneously may lead to undesirable results. |
• | If protecting hosted SQL or Exchange databases with agent-based application backups, do not use application-aware protection for host-level backups. Doing so may compromise log truncation changes and lead to other undesirable results. |
VMware protection strategy |
Considerations |
||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Host-level backups |
|
||||||||||||||||||||||||||||||
File-level backups |
File-level application backups provide these benefits: Note: Application backups schedules cannot be created through SLA policies.
|
Specific instances when you might want to protect VMs at the asset level are described below. For instructions on setting up file-level protection, see Protected assets.
VM type |
Protection considerations |
||||||
---|---|---|---|---|---|---|---|
Hosted applications |
|
||||||
Hosted applications for which you need more granular control. |
Use file-level application backups to select individual databases to back up and recover. |
||||||
Exchange |
Do one of the following:
|
||||||
SQL |
For simple recovery model databases, do one of the following:
For full or bulk-logged recovery model databases, use file-level application protection. (Host-level protection is not supported) |
||||||
SharePoint |
Use file-level application protection. (Host-level protection is not supported.) |
||||||
Oracle |
Use file-level application protection. (Host-level protection is not supported.) |
||||||
Disk configuration |
|
||||||
Cluster with fault tolerant disks |
Use file-level protection. (Host-level protection is not supported.) |
||||||
Physical RDM disks |
Use file-level protection. (These disks are automatically excluded from host-level backups.) |
||||||
Independent or pass-through disks |
Use file-level protection. (These disks are automatically excluded from host-level backups.) |
||||||
Sparse disks |
Use file-level protection. (Host-level protection is not supported.) |
||||||
Other VM considerations |
|
||||||
Dynamic MAC address |
Use file-level protection. (Host-level protection is not supported.) |
||||||
VMs hosted on free ESXi versions |
Use file-level protection. (Host-level protection is not supported.) |
||||||
Virtualized Active Directory (AD) servers for which you are not following Microsoft’s best practices |
Use file-level protection. |
||||||
VMs in Distributed File System environments for which you are not following Microsoft’s best practices |
Use file-level protection. |
||||||
VMs for which you would like to exclude volumes or large numbers of files when running backups |
Use file-level protection and exclude files from backups. (With host-level you can exclude virtual disks only. File-level provides more granular control.) |
||||||
VMs functioning as large file servers for which you may need to frequently recover files |
Use file-level protection so you can search for files to recover by name. |
||||||
Windows VMs that you would like to protect with Windows replicas |
Use file-level protection. |