EMC® Avamar® 6.1 for VMware
User Guide
P/N 300-013-353
REV 07
Copyright © 2001- 2012 EMC Corporation. All rights reserved. Published in the USA.
Published December, 2012
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect
to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular
purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
2
, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
EMC
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the
EMC online support website.
2
EMC Avamar 6.1 for VMware User Guide
CONTENTS
Preface
Chapter 1 Introduction
Chapter 2 Configuration and Setup
Avamar for VMware image backup and restore ............................................ 14
Guest backup and restore ........................................................................... 15
Choosing a data protection method ............................................................ 16
Changed block tracking............................................................................... 18
Additional VMware resources...................................................................... 18
Task road map ............................................................................................ 20
Enable support for multiple vCenters........................................................... 21
Download and install vSphere client software ............................................. 21
Download and install Avamar Administrator software.................................. 22
Configure vCenter-to-Avamar authentication ............................................... 24
Option 1: Install an authentication certificate on the Avamar MCS......... 24
Option 2: Turn off certificate authentication for all vCenter-to-Avamar MCS
communications ................................................................................... 25
Create dedicated vCenter user account........................................................ 26
Add vCenter client in Avamar Administrator................................................. 28
Deploy proxy clients.................................................................................... 30
Add DNS Entries.................................................................................... 30
Download proxy appliance template file................................................ 31
Deploy proxy appliance in vCenter......................................................... 32
Configure proxy virtual machine network settings in vCenter ................. 40
Configure proxy settings in Avamar Administrator ................................. 42
Upgrading Avamar proxy software ............................................................... 44
Protecting virtual machines with both guest and image backup................... 47
Chapter 3 Administration
Basic client administration.......................................................................... 50
How VMware clients appear in Avamar Administrator............................ 50
Adding virtual machine clients .............................................................. 51
Editing existing VMware clients............................................................. 56
Renaming a vCenter client..................................................................... 56
Viewing protected virtual machines....................................................... 58
Viewing replicated virtual machine name .............................................. 58
vCenter connection monitor .................................................................. 59
Groups and policy management.................................................................. 60
Groups and group behavior................................................................... 60
Adding a vCenter group......................................................................... 62
Editing a vCenter group ......................................................................... 65
Editing proxy datastore and group settings............................................ 66
VMware Image Dataset.......................................................................... 68
Best practices ............................................................................................. 69
Troubleshooting.......................................................................................... 70
EMC Avamar 6.1 for VMware User Guide
3
Contents
Chapter 4 Backup
Limitations.................................................................................................. 74
Performing an on-demand image backup .................................................... 74
Scheduling backups.................................................................................... 76
Chapter 5 Restore
Overview..................................................................................................... 78
Limitations.................................................................................................. 78
Guidelines for performing image restores versus file-level restores.............. 80
Restoring the full image or selected drives to the original virtual machine ... 80
Restoring the full image or selected drives to a different (existing) virtual
machine ...................................................................................................... 83
Restoring the full image or selected drives to a new virtual machine............ 86
Restoring specific folders or files................................................................. 89
Chapter 6 Protecting the vCenter Management Infrastructure
Overview..................................................................................................... 92
Backing up the vCenter management infrastructure..................................... 92
Task list ................................................................................................ 93
Task 1: Implement guest backups or VMware image backups................ 93
Task 2: Define a custom dataset for vCenter backups............................ 93
Task 3: Add a backup client for vCenter database hosts ........................ 94
Recovering vCenter management infrastructure from Avamar backups......... 95
Appendix A vSphere Data Ports
Communication ports.................................................................................. 98
Listen ports................................................................................................. 98
Appendix B Plug-in Options
How to set plug-in options ........................................................................ 100
Linux VMware Image plug-in options......................................................... 100
Windows VMware Image plug-in options ................................................... 101
Linux VMware File-level Restore plug-in options ........................................ 101
Windows VMware File-level Restore plug-in options................................... 101
Index
4
EMC Avamar 6.1 for VMware User Guide
TABLES
Title Page
1 Revision history ............................................................................................................ 8
2 Avamar client guides................................................................................................... 15
3 Minimum required vCenter user account privileges ..................................................... 26
4 New vCenter client settings ......................................................................................... 29
5 Proxy Network Property Settings.................................................................................. 38
6 New proxy client settings ............................................................................................ 43
7 How VMware clients appear in Avamar Administrator .................................................. 50
8 Virtual machine information in Avamar Administrator.................................................. 52
9 Select Virtual Machine dialog box functions................................................................ 53
10 New virtual machine client settings............................................................................. 53
11 Virtual machine information in Avamar Administrator.................................................. 55
12 Select Virtual Machine dialog box functions................................................................ 55
13 New vCenter group settings......................................................................................... 63
14 On-demand backup options........................................................................................ 75
15 Important vCenter management infrastructure components ........................................ 93
16 vSphere communication ports..................................................................................... 98
17 vSphere listen ports .................................................................................................... 98
18 Linux VMware image backup options ........................................................................ 100
19 Linux VMware image restore options......................................................................... 100
20 Windows VMware image backup options .................................................................. 101
21 Windows VMware image restore options ................................................................... 101
EMC Avamar 6.1 for VMware User Guide
5
Tabl eses
6
EMC Avamar 6.1 for VMware User Guide
PREFACE
Purpose
As part of an effort to improve its product lines, EMC periodically releases revisions of its
software, and hardware. Therefore, some functions described in this document might not
be supported by all versions of the software, or hardware currently in use. The product
release notes provide the most up-to-date information on product features.
Contact your EMC representative if a product does not function properly, or does not
function as described in this document.
Note: This document was accurate at publication time. New versions of this document
might be released on the EMC online support website. Check the EMC online support
website to ensure that you are using the latest version of this document.
This publication describes various methods and strategies for protecting VMware virtual
machines.
Audience
The information in this publication is intended for system administrators familiar with:
◆ Basic Avamar system administration principles, and procedures found in the
EMC
Avamar Administration Guide
◆ Other Avamar client software information (primarily installation, and configuration
procedures) found in various Avamar client guides
A comprehensive discussion of basic Avamar system administration concepts and
principles, such as clients, datasets, schedules, retention policies, groups, and group
policy, is beyond the scope of this publication. The
provides detailed information.
EMC Avamar Administration Guide
EMC Avamar 6.1 for VMware User Guide
7
Preface
Revision history
The following table presents the revision history of this document.
Table 1 Revision history
Revision Date Description
07 December 13,
06 November 1, 2012 Revised
05 October 25, 2012 Updates for release 6.1 Service Pack 1.
Revised the list of minimum required user account privileges in
2012
“Create dedicated vCenter user account” on page 26.
“File-level restore limitations” on page 79 to clarify
that ACLs are not restored.
Revised:
• “File-level restore limitations” on page 79 to clarify lack of
support for extended partitions.
“Restoring the full image or selected drives to a different
•
(existing) virtual machine” on page 83
post-restore options.
“Restoring the full image or selected drives to a new
•
virtual machine” on page 86
options.
• “Restoring specific folders or files” on page 89 to include
new post-restore options.
04 July 31, 2012 Revised:
“Where to get help” on page 10.
•
• “Create dedicated vCenter user account” on page 26 to
include Virtual machine > Provisioning > Allow disk access
permission.
“File-level restore limitations” on page 79 to include
•
partitioning limitations.
to include new post-restore
to include new
Related documentation
A03 June 30, 2012 Added “Enable support for multiple vCenters” on page 21.
Revised
Logical Volume Manager (LVM) limitations.
A02 June 15, 2012 Added the following topics:
•
“File-level restore limitations” on page 79 to include
“Server software upgrades require proxy reboots” on
page 78
• “Guidelines for performing image restores versus
file-level restores” on page 80
Updated “File-level restore limitations” on page 79 to note
that symbolic links cannot be restored or browsed.
A01 April 25, 2012 First release of Avamar 6.1.
The following EMC publications provide additional information:
◆
EMC Avamar Compatibility and Interoperability Matrix
◆
EMC Avamar Release Notes
◆
EMC Avamar Administration Guide
◆
EMC Avamar Operational Best Practices
◆
EMC Avamar Product Security Guide
8
EMC Avamar 6.1 for VMware User Guide
◆
IMPORTANT
EMC Avamar Backup Clients User Guide
◆
EMC Avamar for Exchange Guide
◆
EMC Avamar for IBM DB2 User Guide
◆
EMC Avamar for Lotus Domino User Guide
◆
EMC Avamar for Microsoft SharePoint Guide
◆
EMC Avamar for Oracle User Guide
◆
EMC Avamar for SQL Server User Guide
Conventions used in this document
EMC uses the following conventions for special notices:
DANGER indicates a hazardous situation which, if not avoided, will result in death, or
serious injury.
Preface
WARNING indicates a hazardous situation which, if not avoided, could result in death, or
serious injury.
CAUTION, used with the safety alert symbol, indicates a hazardous situation which, if not
avoided, could result in minor, or moderate injury.
NOTICE is used to address practices not related to personal injury.
Note: A note presents information that is important, but not hazard-related.
An important notice contains information essential to software, or hardware operation.
EMC Avamar 6.1 for VMware User Guide
9
Preface
Typographical conventions
EMC uses the following type style conventions in this document:
Normal
Bold
Italic
Courier Used for:
Courier bold Used for specific user input, such as commands
Courier italic Used in procedures for:
< >
[ ]
|
{ }
...
Used in running (nonprocedural) text for:
• Names of interface elements, such as names of windows, dialog boxes,
buttons, fields, and menus
• Names of resources, attributes, pools, Boolean expressions, buttons,
SQL statements, keywords, clauses, environment variables, functions,
and utilities
• URLs, pathnames, filenames, directory names, computer names, links,
groups, service keys, file systems, and notifications
Used in running (nonprocedural) text for names of commands, daemons,
options, programs, processes, services, applications, utilities, kernels,
notifications, system calls, and man pages
Used in procedures for:
• Names of interface elements, such as names of windows, dialog boxes,
buttons, fields, and menus
• What the user specifically selects, clicks, presses, or types
Used in all text (including procedures) for:
• Full titles of publications referenced in text
• Emphasis, for example, a new term
•Variables
• System output, such as an error message, or script
• URLs, complete paths, filenames, prompts, and syntax when shown
outside of running text
• Variables on the command line
• User input variables
Angle brackets enclose parameter, or variable values supplied by the user
Square brackets enclose optional values
Vertical bar indicates alternate selections — the bar means “or”
Braces enclose content that the user must specify, such as x, or y, or z
Ellipses indicate nonessential information omitted from the example
Where to get help
10
EMC Avamar 6.1 for VMware User Guide
The Avamar support page provides access to licensing information, product
documentation, advisories, and downloads, as well as how-to and troubleshooting
information. This information may enable you to resolve a product issue before you
contact EMC Customer Service.
To access the Avamar support page:
1. Go to https://support.EMC.com/products.
2. Type a product name in the Find a Product box.
3. Select the product from the list that appears.
4. Click the arrow next to the Find a Product box.
5. (Optional) Add the product to the My Products list by clicking Add to my products in
the top right corner of the Support by Product page.
Preface
Documentation
The Avamar product documentation provides a comprehensive set of feature overview,
operational task, and technical reference information. Review the following documents in
addition to product administration and user guides:
◆ Release notes provide an overview of new features and known limitations for a
release.
◆ Technical notes provide technical details about specific product features, including
step-by-step tasks, where necessary.
◆ White papers provide an in-depth technical perspective of a product or products as
applied to critical business issues or requirements.
Knowledgebase
The EMC Knowledgebase contains applicable solutions that you can search for either by
solution number (for example, esgxxxxxx) or by keyword.
To search the EMC Knowledgebase:
1. Click the Search link at the top of the page.
2. Type either the solution number or keywords in the search box.
3. (Optional) Limit the search to specific products by typing a product name in the Scope
by product box and then selecting the product from the list that appears.
4. Select Knowledgebase from the Scope by resource list.
5. (Optional) Specify advanced options by clicking Advanced options and specifying
values in the available fields.
6. Click the search button.
Live chat
To engage EMC Customer Service by using live interactive chat, click Join Live Chat on the
Service Center panel of the Avamar support page.
Service Requests
For in-depth help from EMC Customer Service, submit a service request by clicking Create
Service Requests on the Service Center panel of the Avamar support page.
Note: To open a service request, you must have a valid support agreement. Contact your
EMC sales representative for details about obtaining a valid support agreement or with
questions about your account.
To review an open service request, click the Service Center link on the Service Center
panel, and then click View and manage service requests.
Facilitating support
EMC recommends that you enable ConnectEMC and Email Home on all Avamar systems:
◆ ConnectEMC automatically generates service requests for high priority events.
◆ Email Home emails configuration, capacity, and general system information to EMC
Customer Service.
EMC Avamar 6.1 for VMware User Guide
11
Preface
Your comments
Your suggestions help us to continue to improve the accuracy, organization, and overall
quality of the user publications. Send your opinions of this document to:
BSGDocumentation@emc.com
Please include the following information:
◆ Product name and version
◆ Document name, part number, and revision (for example, 01)
◆ Page numbers
◆ Other details that will help us address the documentation issue
12
EMC Avamar 6.1 for VMware User Guide
CHAPTER 1
Introduction
This chapter discusses the following:
◆ Avamar for VMware image backup and restore ........................................................ 14
◆ Guest backup and restore ....................................................................................... 15
◆ Choosing a data protection method ........................................................................ 16
◆ Changed block tracking........................................................................................... 18
◆ Additional VMware resources.................................................................................. 18
Introduction
13
Introduction
Avamar for VMware image backup and restore
Avamar for VMware image backup and restore is built on the VMware vStorage API for Data
Protection (VADP).
Avamar for VMware image backup and restore is fully integrated with VMware vCenter
Server to provide easy detection of virtual machine clients within the vCenter, and enable
efficient centralized management of backup jobs.
Backups and restores require the use of proxy virtual machine clients. Each proxy virtual
machine client provides all of the following capabilities:
◆ Backup of Microsoft Windows and Linux virtual machines (entire images or specific
drives)
◆ Restore of Microsoft Windows and Linux virtual machines (entire images or specific
drives)
◆ Selective restore of individual folders and files to Microsoft Windows and Linux virtual
machines
Proxies run Avamar software inside a Linux virtual machine, and are deployed using an
appliance template (.ova) file.
14
EMC Avamar 6.1 for VMware User Guide
Guest backup and restore
Guest backup and restore is another way to protect virtual machine data. It is
implemented by installing Avamar client software in a virtual machine just as if it were a
physical machine, then registering and activating that client with an Avamar server. No
special configuration is required.
When registering virtual machine clients protected by guest backup, do not register them
to a vCenter domain. Doing so will prevent you from locating or managing that virtual
machine in Avamar Administrator. Instead register any virtual machine clients protected
by guest backup to some other domain or subdomain (for example, /clients).
The following Avamar client guides provide details about installing Avamar client software
in virtual machines:
Table 2 Avamar client guides
Client Client guide
Introduction
IBM AIX filesystems
Linux filesystems:
•CentOS
•Debian
• Red Hat
•SUSE
•Ubuntu
Novell NetWare filesystems
UNIX filesystems:
•FreeBSD
•HP-UX
• SCO Open Server and UnixWare
•Sun Solaris
IBM DB2 databases hosted on IBM AIX, Red Hat
and SUSE Linux, and Microsoft Windows
Lotus Domino databases
Mac OS X filesystems
Microsoft Exchange databases
Microsoft Office SharePoint implementations
Microsoft SQL Server databases
EMC Avamar Backup Clients User Guide
EMC Avamar Backup Clients User Guide
EMC Avamar Backup Clients User Guide
EMC Avamar Backup Clients User Guide
EMC Avamar for IBM DB2 User Guide
EMC Avamar for Lotus Domino User Guide
EMC Avamar Backup Clients User Guide
EMC Avamar for Exchange Guide
EMC Avamar for Microsoft SharePoint Guide
EMC Avamar for SQL Server User Guide
Microsoft Windows filesystems
Oracle databases hosted on IBM AIX, Red Hat, and
SUSE Linux, Sun Solaris, and Microsoft Windows
EMC Avamar Backup Clients User Guide
EMC Avamar for Oracle User Guide
Guest backup and restore
15
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 non-application 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. Managing backups from these virtual machines
is exceptionally easy.
Ease of implementation
Guest backup and restore:
◆ Supports any virtual machine running an operating system for which Avamar client
software is available
◆ Supports applications such as DB2, Exchange, Oracle, and SQL Server databases
◆ Easily fits into most existing backup schemes; day-to-day backup procedures do not
change
◆ Avamar client software must be individually installed, and managed inside each
virtual machine
Avamar for VMware image backup and restore:
◆ Can leverage vCenter to discover virtual machines, and add them to the Avamar server
in batches
◆ Requires moderate amount of initial setup and configuration
16
EMC Avamar 6.1 for VMware User Guide
Efficiency
Backup and restore
Introduction
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
Guest backup and restore:
◆ Applications are gracefully quiesced prior to each backup, ensuring a true “application
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)
Choosing a data protection method
17
Introduction
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 filesystem 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 filesystem 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.
Additional VMware resources
A comprehensive discussion of VMware technology is beyond the scope of this
publication. The following VMware documentation provides additional details:
◆
Introduction to VMware vSphere
◆
Getting Started with ESX
◆
ESX, and vCenter Server Installation Guide
◆
Basic System Administration
◆
vSphere Web Access Administrator's Guide
◆
ESX Configuration Guide
◆
Resource Management Guide
18
EMC Avamar 6.1 for VMware User Guide
CHAPTER 2
Configuration and Setup
This chapter provides essential configuration and setup procedures for both vCenter and
Avamar environments that must be performed before Avamar for VMware image backup
and restore can be used to protect virtual machine data. Topics in this chapter include:
◆ Task road map ........................................................................................................ 20
◆ Enable support for multiple vCenters....................................................................... 21
◆ Download and install vSphere client software ......................................................... 21
◆ Download and install Avamar Administrator software.............................................. 22
◆ Configure vCenter-to-Avamar authentication ........................................................... 24
◆ Create dedicated vCenter user account.................................................................... 26
◆ Add vCenter client in Avamar Administrator............................................................. 28
◆ Deploy proxy clients................................................................................................ 30
◆ Upgrading Avamar proxy software ........................................................................... 44
◆ Protecting virtual machines with both guest and image backup............................... 47
Configuration and Setup
19
Configuration and Setup
Task road map
Successfully configuring Avamar for VMware image backup and restore comprises the
following tasks, which must be performed in this specific order:
◆ “Enable support for multiple vCenters” on page 21 only required if Avamar server was
upgraded from a previous version)
◆ “Download and install vSphere client software” on page 21
◆ “Download and install Avamar Administrator software” on page 22
◆ For each vCenter, “Configure vCenter-to-Avamar authentication” on page 24, one of
the following:
• “Option 1: Install an authentication certificate on the Avamar MCS” on page 24
• “Option 2: Turn off certificate authentication for all vCenter-to-Avamar MCS
communications” on page 25
◆ For each vCenter, “Create dedicated vCenter user account” on page 26
◆ For each vCenter, “Add vCenter client in Avamar Administrator” on page 28
◆ “Deploy proxy clients” on page 30, all of the following:
• “Add DNS Entries” on page 30
• “Download proxy appliance template file” on page 31
• “Deploy proxy appliance in vCenter” on page 32
• “Configure proxy virtual machine network settings in vCenter” on page 40
• “Configure proxy settings in Avamar Administrator” on page 42
20
EMC Avamar 6.1 for VMware User Guide
Enable support for multiple vCenters
Avamar for VMware image backup and restore supports protecting up to 5 vCenters from a
single Avamar server. Beginning with Avamar 6.0, support for multiple vCenters is enabled
by default during new Avamar server software installations. However, if your Avamar
server was upgraded to from the previous version, you might need to perform the
following manual configuration in order to enable support for multiple vCenters.
To enable support for multiple vCenters, perform the following:
1. Open a command shell and log in using one of the following methods:
• To log in to a single-node server, log in to the server as admin.
• To log in to a multi-node server, log in to the utility node as admin.
2. Change directories by typing:
cd /usr/local/avamar/var/mc/server_data/prefs
3. Open mcserver.xml in a UNIX text editor.
4. Find the com.avamar.mc.vmware.max_number_of_vcenters node, as shown below:
Configuration and Setup
<root type="system">
<node name="com">
<node name="avamar">
<node name="mc">
<node name="vmware">
<entry key="max_number_of_vcenters" value="1" />
Note: Substantial portions of mcserver.xml have been omitted for clarity.
5. Change the max_number_of_vcenters entry to an integer value between 2 and 5.
This value must be equal to or greater than the maximum number of vCenters you will
be using with this Avamar server. Currently, the absolute maximum number of
vCenters that can be supported by a single MCS is 5.
6. Save your changes.
7. Restart the MCS by typing:
dpnctl stop mcs
dpnctl start mcs
8. Close the command shell.
Download and install vSphere client software
If you have not already done so, download and install vSphere client software by
performing the following:
1. From a Windows computer, point your web browser at the vSphere server by typing the
following URL:
HTTPS://VSPHERE
where VSPHERE is your actual vSphere server network hostname as defined in DNS, or
IP address.
Enable support for multiple vCenters
21
Configuration and Setup
Note: This URL must be a secure (HTTPS) web address.
The vSphere Welcome page appears.
2. Click Download vSphere Client.
Your browser might prompt you to either open the file “in-place” (on the server) or
save it to your local computer. Either method is acceptable. However, if you save the
file to your local computer, you must open (double-click) that installation file to
continue with this procedure.
3. Either open the installation file in place (on the server), or double-click the
downloaded installation file.
The installation wizard appears.
4. Follow the on-screen instructions.
5. When prompted, click Finish to complete the installation procedure.
The installation wizard closes.
Download and install Avamar Administrator software
If you have not already done so, download and install Avamar Administrator software by
performing the following:
1. From a Windows computer, point your web browser at the Avamar server by typing the
following URL:
http://AVAMARSERVER
where AVAMARSERVER is your actual Avamar server network hostname as defined in
DNS, or IP address.
You will be automatically redirected to the Avamar secure web server.
Depending on your browser security settings, a security alert dialog box might appear.
2. If a security alert dialog box appears, click Yes, or OK to allow redirection to the
Avamar secure web server.
The Secure Log On page appears.
3. Page down until the Documents and Downloads link is visible.
4. Click Documents and Downloads.
The Documents and Downloads page appears.
5. Page down until the Windows for x86 (32 bit) section is visible.
22
6. Click the Microsoft Windows XP, 2003, Vista, 2008, 7 link.
The Downloads for Microsoft Windows XP, 2003, Vista, 2008, 7 page appears.
7. Click the AvamarConsoleMultiple install package.
EMC Avamar 6.1 for VMware User Guide
Configuration and Setup
Your browser might prompt you to either open the file “in-place” (on the server) or
save it to your local computer. Either method is acceptable. However, if you save the
file to your local computer, you must open (double-click) that installation file to
continue with this procedure.
8. Either open the installation file in place (on the server), or double-click the
downloaded installation file.
The installation wizard appears.
9. Follow the on-screen instructions.
10. When prompted, click Finish to complete the installation procedure.
The installation wizard closes.
Download and install Avamar Administrator software
23
Configuration and Setup
Configure vCenter-to-Avamar authentication
Avamar VMware Image Backup will not work unless:
◆ A valid authentication certificate is present on the Avamar Management Console
Server (MCS).
◆ Certificate authentication for all MCS-to-vCenter communications is turned off.
You must perform this task for each vCenter you intend to protect.
Option 1: Install an authentication certificate on the Avamar MCS
Avamar VMware Image Backup will not work unless a valid authentication certificate is
present on the MCS. For security reasons, Avamar intentionally does not provide one. You
must either obtain your own authentication certificate, or use the default certificate
provided with vCenter, then install either certificate using this procedure.
This procedure assumes that you are installing the default certificate provided with
vCenter.
The procedure uses the java keytool command, a utility that manages certificate keys. The
keytool command is located in the Java bin directory (/usr/java/jreVERSION/bin), where
VERSION is the specific Java Runtime Environment (JRE) version currently installed on the
MCS. If this directory is not in your path, you can either add it to the path, or specify the
complete path when using keytool.
1. Open a command shell, and log in:
• If logging into a single-node server, log in to the server as admin.
• If logging into a multi-node server, log in to the utility node as admin.
2. Stop the MCS by typing:
dpnctl stop mcs
3. Switch user to root by typing:
su -
4. Copy rui.crt from the vCenter machine to /tmp on the utility node or single-node
server.
The default certificate provided with vCenter is:
• Windows 2008: C:\ProgramData\VMware\VMware VirtualCenter\SSL\rui.crt
• Other Windows versions: C:\Documents and Settings\All Users\Application
Data\VMware\VMware VirtualCenter\SSL\rui.crt
24
• Linux: /etc/vmware-vpx/ssl/rui.crt
5. Create a temporary version of the MCS keystore by copying the live keystore to /tmp by
typing:
cp /usr/local/avamar/lib/rmi_ssl_keystore /tmp/
EMC Avamar 6.1 for VMware User Guide
Configuration and Setup
6. Add the default vCenter certificate to the temporary MCS keystore file by typing:
cd /tmp
$JAVA_HOME/bin/keytool –import –file rui.crt -alias ALIAS
-keystore rmi_ssl_keystore
where ALIAS is a user-defined name for this certificate, which can often be the file
name.
7. When prompted for a password, type the root password.
The following appears in the command shell:
Trust this certificate?
8. Type yes, and press Enter.
9. Back up the live MCS keystore by typing:
cd /usr/local/avamar/lib
cp rmi_ssl_keystore rmi_ssl_keystore.DATE
where DATE is today’s date.
10. Copy the temporary MCS keystore to the live location by typing:
cp /tmp/rmi_ssl_keystore /usr/local/avamar/lib/
11. Exit the root subshell, and restart the MCS by typing:
exit
dpnctl start mcs
Option 2: Turn off certificate authentication for all vCenter-to-Avamar MCS communications
1. Open a command shell, and log in:
• If logging into a single-node server, log in to the server as admin.
• If logging into a multi-node server, log in to the utility node as admin.
2. Stop the MCS by typing:
dpnctl stop mcs
3. Open /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml in a UNIX text
editor.
4. Locate the ignore_vc_cert preference.
5. Change the ignore_vc_cert preference setting to true.
For example:
<entry key="ignore_vc_cert" value="true" />
6. Save your changes.
7. Restart the MCS by typing:
dpnctl start mcs
Configure vCenter-to-Avamar authentication
25
Configuration and Setup
Create dedicated vCenter user account
EMC strongly recommends that you set up a separate vCenter user account that is strictly
dedicated for use with Avamar. Use of a generic user account such as “Administrator”
might hamper future troubleshooting efforts because it might not be clear which
“Administrator” actions are actually interfacing, or communicating with the Avamar server.
Using a separate vCenter user account ensures maximum clarity if it becomes necessary to
examine vCenter logs.
You must perform this task for each vCenter you intend to protect.
This vCenter user account must have the following minimum privileges:
Table 3 Minimum required vCenter user account privileges (page 1 of 2)
Setting Minimum required privileges
Datastore • Allocate space
• Browse datastore
• Low level file operations
• Move datastore
•Remove datastore
•Remove file
• Rename datastore
Folder • Create Folder
Global • Cancel task
• Disable methods
•Enable methods
• Licenses
• Log event
•Settings
Network • Assign network
•Configure
Resource • Assign virtual machine to resource pool
Sessions • Validate session
Tasks • Create task
• Update task
vApp • Export
26
EMC Avamar 6.1 for VMware User Guide
Table 3 Minimum required vCenter user account privileges (page 2 of 2)
Setting Minimum required privileges
Virtual machine > Configuration • Add existing disk
• Add new disk
• Add or Remove device
• Advanced
•Change CPU count
• Change Resource
• Disk change Tracking
•Disk Lease
• Host USB device
•Memory
• Modify device setting
•Raw device
• Reload from path
• Remove disk
• Rename
• Reset guest information
•Settings
• Swapfile placement
• Upgrade virtual hardware
• Extend Virtual disk
Configuration and Setup
Virtual machine > Interaction • Acquire guest control ticket
• Console interaction
•Power Off
• Power On
• Reset
• VMware Tools install
Virtual machine > Inventory • Create new
•Register
•Remove
•Unregister
Virtual machine > Provisioning • Allow disk access
• Allow read-only disk access
• Allow virtual machine download
• Mark as Template
Virtual machine > State • Create snapshot
• Remove Snapshot
• Revert to snapshot
Create dedicated vCenter user account
27
Configuration and Setup
Add vCenter client in Avamar Administrator
The vCenter must exist, and be operational before this type of client can be added. Avamar
Administrator attempts to make a connection with the vCenter.
If the vCenter client is already registered as a normal client (for example, to support guest
level backup), adding that same vCenter client again will fail because the system will not
allow you to register the same client twice. If this occurs, you must retire the existing client
instance in Avamar Administrator, add the vCenter client (using the following procedure),
then re-invite the vCenter client as a normal client to support guest level backup from the
vCenter server.
You must perform this task for each vCenter you intend to protect.
Adding a vCenter client in Avamar Administrator automatically:
◆ Adds the vCenter client to the Default Group.
However, this client is not activated as normal Avamar clients are. Therefore, no
backups are performed for it on behalf of the Default Group.
◆ Creates a default vCenter server with the same name as the vCenter's fully qualified
hostname.
◆ Creates a VirtualMachines subdomain within that vCenter server.
◆ Creates a Default Virtual Machine Group.
This group performs scheduled backups for the target virtual machines. This group
cannot be deleted without first deleting the virtual center domain.
To add a vCenter client:
1. In Avamar Administrator, click the Administration launcher button.
The Administration window appears.
2. Click the Account Management tab.
3. In the tree, select the top-level (root) domain.
4. Select Actions > Account Management > New Client…
The New Client dialog box appears.
28
EMC Avamar 6.1 for VMware User Guide
5. For Client Type, select VMware vCenter.
6. Complete the following settings:
Configuration and Setup
Table 4 New vCenter client settings
Setting Description
New Client Name or IP Fully-qualified DNS name, or IP address of the vCenter.
Port vCenter web services listener port. Default setting is port 443.
User Name vCenter user account name you previously created.
Password Password for the vCenter user account you previously created.
Verify Password Type the password again.
Contact Optional contact name.
Phone Optional contact telephone number.
Email Optional contact email address.
Location Optional contact location.
7. Click OK.
The New Client dialog box closes.
Add vCenter client in Avamar Administrator
29
Configuration and Setup
Deploy proxy clients
Backups and restores require deployment of proxy virtual machine clients. Once
deployed, each proxy virtual machine client provides all of the following capabilities:
◆ Backup of Microsoft Windows and Linux virtual machines (entire images or specific
drives)
◆ Restore of Microsoft Windows and Linux virtual machines (entire images or specific
drives)
◆ Selective restore of individual folders and files to Microsoft Windows and Linux virtual
machines
Proxies run Avamar software inside a Linux virtual machine, and are deployed using an
appliance template (.ova) file.
Proxy clients are allowed in any part of Avamar Administrator account management tree
except the vCenter server domain or subdomains.
Although it is possible to restore across datacenters (that is, use a proxy deployed in one
datacenter to restore files to a virtual machine in another datacenter), restores will take
noticeably longer than if the proxy and the target virtual machine are both located in the
same datacenter. Therefore, for best performance, deploy at least one proxy on each
datacenter you are protecting.
Add DNS Entries
For best results, always register and activate proxies from the client during deployment (as
described in “Configure proxy virtual machine network settings in vCenter” on page 40).
Using the alternative method of inviting the proxy client to register with the Avamar server
from Avamar Administrator is known to have unpredictable results.
During “Deploy proxy appliance in vCenter” on page 32, you will be asked to assign a
unique IP address to each proxy. vCenter performs a reverse DNS lookup of that IP address
to ensure that it is resolvable to a hostname. For best results, configure all required DNS
entries for proxies you plan to deploy before proceeding with the remainder of this
procedure.
30
EMC Avamar 6.1 for VMware User Guide
Loading...