There are two ways to backup VMWare using Avamar. One is to perform a regular guest backup, installing an agent as if the VM were a physical machine. The other is using VMWare's vStorage API for Data Protection, or VADP. This uses a proxy node and has an automatic detection of virtual machine clients within the vCenter and is an efficient method of backing up entire images. It functions for Windows and Linux VMs, including selective restore of individual files and folders. The proxy is a Linux VM running Avamar software, deployed using an OVA.
Guest backup gives the highest level of dedupe and allows applications to be gracefully quiesced. Any OS that is supported by Avamar is supported and all normal limitations apply regarding power and connectivity. Restoring from guest VM backup typically employs a "bootstrap" image that is installed with applications and OS followed with a restore of unique data.
Image backup is performed through a proxy and is integrated with Avamar Administrator. It tracks changed blocks (CBT) so they don't have to be scanned each backup, saving considerable amounts of I/O.
Image backup creates a snapshot and backs up the snapshot using a proxy to handle the deduplication. Multiple proxies can be used for load-balancing. You need a different proxy for Windows and Linux, and file-level restore is supported up to 5000 files. Images can be restored to the original or a new VM.
vCenter groups are created in the Avamar Administrator in the vCenter domain and is where you specify which proxy is used. The default VM group cannot be deleted. There is also a default proxy group that holds all proxies and cannot be deleted.
Image level restore can be to the original VM, a different VM or a new VM. The target VM must be powered off.
File level restores into the VM File System but ACLs are not restored. Encrypted and redirected files must be restored to the original location, and the client must be powered on.
Using FQDN for ESX servers will reduce network lookup traffic for vCenter groups, and it is also a good idea to throttle guest backup on the ESX host so as not to consume all available resources.
No comments:
Post a Comment