EasyManua.ls Logo

EMC Avamar 6.1 - Page 17

EMC Avamar 6.1
106 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Choosing a data protection method
17
Introduction
Efficiency
Guest backup and restore:
Offers highest level of data deduplication efficiency
Backups do not consume ESX server CPU, RAM, and disk resources
Backups consume small amounts of guest virtual machine CPU, RAM, and disk
resources when backups are occurring
Avamar for VMware Image backup and restore:
Moderate deduplication efficiency
Backups do not consume guest virtual machine CPU, RAM, and disk resources
Backups consume ESX server CPU, RAM, and disk resources when backups are
occurring
Backup and restore
Guest backup and restore:
Applications are gracefully quiesced prior to each backup, ensuring a trueapplication
consistent” backup
Backups are highly optimized (temp files, swap files, and so forth not included)
Backups are highly customizable (supports full range of include and exclude features)
Database backups support transaction log truncation, and other advanced features
Unused filesystem space is not backed up
Individual file and directory (folder) restores supported
Backup and restore jobs can execute pre- and post-processing scripts
Virtual machines must have a network connection to Avamar server
Virtual machines must be running for backups to occur
Avamar for VMware Image backup and restore:
Image backups are supported for all machines that are currently supported by VMware
Individual file and directory (folder) restores supported for both Windows and Linux
virtual machines
Virtual machines need not have a network connection to Avamar server
Virtual machines need not be running for backups to occur
Unused filesystem space is backed up
Backups not optimized (temp files, swap files, and so forth are included)
Backups can comprise an entire virtual machine image (all drives) or selected drives
(vmdk files)

Table of Contents