EMC Avamar 6.1 Manual de usuario descargar pdf (Pagina 18)

A system’s boot drive and its data drive have different performance and storage requirements. This

wizard addresses both in one GUI, and it permits a single-step recovery to multiple locations.

Avamar also configures the creation of the container for a VM. Avamar’s approach to protection

protects the .VMX file of a VM, the configuration container for a VM. If Avamar did not create the

containers as it does, and should a disaster occur, the administrator would have to log on to vCenter

and create all the containers needed before conducting any recoveries. This Avamar capability is

superior to the traditional approach that relied on detailed tracking via spreadsheet listings of the VM-

to-container mappings.

File-level recovery from an image backup

The administrator can do file-level recoveries (FLR) for Windows VMs from the image-based backup.

To do this, Avamar leverages the VMware VM tools along with an Avamar Windows FLR proxy. The

proxy is a Windows 2003 server provided by the administrator, with code provided by Avamar. No

agents are needed within the VM for this recovery type. The key is that Avamar moves no data until

there is a need to recover data, and that no other interface nor client-side software is needed for this

recovery.

The Avamar Administrator console is used to manage and monitor FLR jobs.

When backups are selected for recovery, the FLR proxy server reads the VMDK data from the

Avamar system and creates a browse tree, as shown in Figure 6 in the Avamar Administrator -

Backup and Restore window.

Figure 6. File-level recovery: selecting files and directories to restore.

1 2 ... 13 14 15 16 17 18 19 20 21 22 23 ... 39 40

Sin comentarios

EMC Avamar 6.1 Manual de usuario Pagina 18