EMC Avamar 7.0 VMware 用户指南：最新版技术详解

5星 · 超过95%的资源需积分: 9 69 浏览量更新于2024-07-23 收藏 1.84MB PDF 举报

本资源是EMC Avamar 7.0 for VMware User Guide，是一份详细的用户手册，适用于EMC Avamar 7.0在VMware环境下的操作与管理。EMC Avamar是一款专为数据保护设计的企业级解决方案，旨在提供高效、灵活的数据备份和恢复服务，特别针对虚拟化平台如VMware进行优化。该指南涵盖了以下关键知识点： 1. **系统概述**：介绍了Avamar 7.0的主要功能，包括实时数据保护、增量备份、灾难恢复以及对VMware环境中虚拟机数据的高效管理和保护。 2. **安装与部署**：详细说明了如何在VMware环境中安装和配置Avamar代理，确保其与VMware vSphere或vMotion等组件无缝集成。 3. **备份策略**：提供了创建和管理备份策略的指导，包括全量备份、增量备份、差异备份以及基于时间点的恢复选项。 4. **虚拟机保护**：强调了Avamar对虚拟机数据的特殊处理，如快照和一致性点，以及如何确保在虚拟化环境中数据的一致性和完整性。 5. **性能优化**：讨论了如何通过调整设置来提升Avamar在VMware环境中的性能，包括网络、存储和资源管理的最佳实践。 6. **故障排查与维护**：包含了常见问题的解决方法，以及如何监控Avamar运行状态，以确保系统的稳定性和可靠性。 7. **许可证和法律声明**：强调了使用EMC软件的版权和许可要求，以及免责声明，提醒用户在使用过程中需遵守相关规定。 8. **更新与支持**：指引用户访问EMC在线支持网站获取最新的产品和技术文档，以便获取最新的合规性和技术支持。 9. **法规遵从性**：鼓励用户参考最新的技术文档和顾问建议，以确保他们的Avamar部署符合当前的法规要求。这份用户指南为VMware用户提供了全面的Avamar 7.0使用指南，帮助他们充分利用这一数据保护工具，实现高效、安全的虚拟化环境管理。

EMC Avamar 7.0 for VMware User Guide

Introduction

Choosing a data protection method

This topic explores the various advantages and considerations associated with image

backup and restore versus guest backup and restore.

Note: A virtual machine can be protected by both guest backup and image backup. For

example, a daily guest backup might be used to protect selective files, and a less frequent

or on-demand full image backup might be used to protect the full machine. This scheme

accommodates scenarios with limited backup windows.

Types of virtual machines

Guest backup is generally the preferred strategy for protecting application servers such as

Microsoft Exchange, Microsoft Office SharePoint, Microsoft SQL Server, and Oracle. The

reason that guest backup is particularly suited for this is that the Avamar agent gracefully

quiesces applications prior to backup, ensuring a true “application consistent” backup.

Guest backup and restore is also the only way to back up virtual machines, such as

desktops and laptops, that are not hosted within a vCenter.

Avamar for VMware image backup and restore is generally the preferred strategy for

protecting any nonapplication intensive virtual machines that are hosted within a vCenter.

Avamar's integration with vCenter enables multiple virtual machines to be protected with

the least amount of effort.

UNIX file systems:

•FreeBSD

•HP-UX

• SCO Open Server and UnixWare

•Sun Solaris

EMC Avamar Backup Clients User Guide

IBM DB2 databases hosted on IBM AIX, Red Hat

and SUSE Linux, and Microsoft Windows

EMC Avamar for IBM DB2 User Guide

Lotus Domino databases

EMC Avamar for Lotus Domino User Guide

Mac OS X file systems

EMC Avamar Backup Clients User Guide

Microsoft Exchange databases

EMC Avamar for Exchange Guide

Microsoft Office SharePoint implementations

EMC Avamar for Microsoft SharePoint Guide

Microsoft SQL Server databases

EMC Avamar for SQL Server User Guide

Microsoft Windows file systems

EMC Avamar Backup Clients User Guide

Oracle databases hosted on IBM AIX, Red Hat, and

SUSE Linux, Sun Solaris, and Microsoft Windows

EMC Avamar for Oracle User Guide

Table 2 Avamar client guides (page 2 of 2)

Client Publication

EMC Avamar 7.0 for VMware User Guide

Introduction

Avamar for VMware Image backup and restore:

◆ Image backups are supported for all machines that are currently supported by VMware

◆ Individual folder and file 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 file system 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)

Required VMware knowledge

Guest backup and restore requires no advanced scripting or VMware knowledge.

Avamar for VMware Image backup and restore requires moderate VMware knowledge.

Integrators should have working knowledge of actual vCenter topology in use at that

customer site (that is, which ESX Servers host each datastore, and which datastores store

each virtual machine’s data), and the ability to log in to vCenter with administrator

privileges.

Changed block tracking

Changed block tracking is a VMware feature that tracks which specific file system blocks

on a virtual machine have changed between backups.

Changed block tracking identifies unused space on a virtual disk during the initial backup

of the virtual machine, and also empty space that has not changed since the previous

backup. Avamar data deduplication performs a similar function. However, using this

feature provides valuable I/O reduction earlier in the backup process. Changed block

tracking dramatically improves performance if SAN connectivity is not available.

If changed block tracking is not enabled, each virtual machine file system image must be

fully processed for each backup, possibly resulting in unacceptably long backup windows,

and excessive back-end storage read/write activity.

Changed block tracking can also reduce the time required to restore (“roll back”) a virtual

machine to a recent backup image by automatically eliminating unnecessary writes during

the restore process.

Changed block tracking is only available with the following types of virtual machines that

use the following specific types of virtual disk formats:

• Virtual machine versions 7 and later

The earlier version 4 is commonly used on ESX 3.X hosts and in virtual machines

deployed from templates that support both ESX 3.x and 4.0 hosts. The version of a

virtual machine does not change when the underlying ESX host is upgraded. Many

commercial appliances exist in version 4 to allow deployment on ESX 3.x hosts.

Virtual Machine Quiescing

Introduction

vCenter version 4 provides the ability to upgrade version 4 virtual machine

hardware from to version 7 virtual machine hardware. This upgrade is irreversible

and makes the virtual machine incompatible with earlier versions of VMware

software products. Refer to vCenter online help for details.

• Disks cannot be physical compatibility RDM

• The same disk cannot be mounted by multiple virtual machines

• Virtual machines must be in a configuration that supports snapshots

Enabling changed block tracking will not take effect until any of the following actions occur

on the virtual machine: power on, resume after suspend, migrate, snapshot create, delete,

or revert.

Virtual Machine Quiescing

Avamar for VMware image backup and restore does not provide any additional virtual

machine quiescing capabilities other than those provided by VMware Data Recovery

(VDR).

Prior to performing a backup, three levels of virtual machine quiescing are possible:

◆ Crash-consistent quiescing

◆ File system-consistent quiescing

◆ Application-consistent quiescing

Crash-consistent quiescing is the least desirable level of quiescing because the virtual

disk image being backed up is consistent with what would occur by interrupting power to a

physical computer. File system writes might or might not be in progress when power is

interrupted. Because of that, there is always a chance of some data loss.

File system-consistent quiescing is more desirable because the virtual machine is allowed

to complete any file system writes before the disk is backed up. This level of quiescing is

only available on Windows virtual machines capable of providing Windows Volume

Snapshot Service (VSS) services, and that are running VMware Tools.

Application-consistent quiescing is the most desirable level of quiescing because, in

addition to the advantages provided by file system-consistent quiescing, applications are

notified that a backup has occurred so that they can clear their transaction logs.

Application-consistent quiescing is only available on Windows 2008 32-bit/64-bit, and

Windows 2008 R2 virtual machines that are running VMware Tools. Additionally, for

application-consistent quiescing to be available, the following conditions must be met:

◆ The UUID attribute must be enabled. This is enabled by default on virtual machines

created on ESX 4.1 hosts.

◆ The virtual machine must use only SCSI disks. For example, application-consistent

quiescing is not supported for virtual machines with IDE disks.

◆ The virtual machine cannot use dynamic disks.

A complete discussion of virtual machine quiescing and VDR is beyond the scope of this

publication. Refer to your

VMware Data Recovery Administration Guide

for details

including specific platform capabilities and limitations.

剩余109页未读，继续阅读

luczuo

粉丝: 0
资源: 1

EMC Avamar 7.0 VMware 用户指南：最新版技术详解

EMC Avamar for VMware用户指南.pdf

用于VMware环境的EMC Avamar备份和恢复

EMC-Avamar安装配置管理手册.pdf

docu50619_NetWorker-8.1-SP1-Avamar-Integration-Guide

docu91837_Avamar-18.2-and-Data-Domain-System-Integration-Guide.pdf

avamar-备份与恢复软件

Avamar 6.1 User Guide

EMC-Avamar_官方售前售后培训文档

EMC_Avamar_VMware虚拟机数据保护解决方案.pptx

E20-594avamar认考试题库.pdf

最新资源