Add a backup client for vCenter database hosts

Backing up the vCenter management infrastructure 101

Task 1: Implement guest backups

To protect the vCenter management infrastructure with guest backup:

• Install and register Avamar Client for Windows software on the vCenter host as described in the EMC Avamar Backup Clients User Guide.

• Install and register the correct Avamar database software on each database host as described in various database-specific documentation such as the EMC Avamar for SQL Server User Guide.

Task 2: Define a custom dataset for vCenter backups

For best results, define a custom dataset strictly for use in backing up the following vCenter management infrastructure components:

Use of a custom dataset will not only shorten backup and restore times, but will also allow you to use Avamar backups to facilitate vCenter upgrades (for example, upgrading the vCenter host from a 32- to a 64-bit Windows virtual machine).

1. In Avamar Administrator, select Tools > Manage Datasets. The Manage All Datasets window appears.

2. Click New.

The New Dataset dialog box appears.

3. Type a name for this new dataset (for example, vCenter-1).

Table 5 Important vCenter management infrastructure components Component Default Location

License files The exact location depends on the specific VMware and Windows version, but is typically one of the following folders:

• C:\Program Files(x86)\VMware\Infrastructure\VirtualCenter Server\licenses\site

• C:\Program Files\VMware\VMware License Server\Licenses

SSL certificates The exact location depends on the specific VMware and Windows version, but is typically one of the following folders:

• C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL

• C:\ProgramData\VMWare\VMware VirtualCenter\SSL

Audit logs The exact location depends on the specific VMware and Windows version, but is typically one of the following folders:

• C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs

• C:\ProgramData\VMWare\VMware VirtualCenter\Logs Windows guest

customization (sysprep) files

The exact location depends on the specific VMware and Windows version, but is typically one of the following folders:

• C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep

Note: Do not use any of the following characters in your dataset name: ~!@$^%(){}[]|,`;#\/:*?<>'"&.

4. Click the Source Data tab.

The Source Data tab is where you define a list of source data plug-ins that contribute data to this dataset.

5. Select Enter Explicitly and select the Windows File System plug-in from the Select Plug-In Type list.

6. In the list of backup targets at the bottom of the dialog box, delete every entry except for the Windows File System plug-in by selecting an entry and clicking -.

7. Add each vCenter management infrastructure component to the dataset as follows: a. Select Files and/or Folders and click ...

The Select Files And/Or Folders dialog box appears. b. Browse to the correct license file folder and select it. c. Click OK.

The Select Files And/Or Folders dialog box closes. The license file folder appears in the list of backup targets at the bottom of the New Dataset dialog box.

d. Repeat steps a–c for the remaining important vCenter management infrastructure components (that is, the SSL certificates, audit logs, and windows guest

customization (sysprep) files). 8. Click OK.

The New Dataset dialog box closes.

Task 3: Add a backup client for vCenter database hosts

The location of the database used by vCenter, UpdateManage, SRM, and so forth can be determined by running the Windows Data Sources (ODBC) administrative tool.

Install Avamar database backup agents on the database hosts as described in the database-specific documentation, such as the EMC Avamar for SQL Server User Guide. Configure a scheduled backup to protect the databases.

You should truncate vCenter database transaction logs after each backup. This can be done by selecting the SQL Server plug-in Truncate database log option. Truncating database transaction logs ensures that logs will not grow too large, and consume excessive amounts of space on the Avamar server.

Recovering vCenter management infrastructure from Avamar

backups

Recovering vCenter management infrastructure from Avamar backups is a two-step process in which you first create a restore target virtual machine with a fresh operating system image, then restore the vCenter management infrastructure components from the

vSphere Data Ports 103

vSphere Data Ports

This appendix lists Avamar port usage in a typical vSphere environment. Topics in this chapter include:

• Communication ports... 104

Communication ports

All ports are TCP.

Legend:

*V= Defined by VMware < or > indicates port direction

Listen ports

All ports are TCP unless specifically designated as UDP.

Legend:

*V= Defined by VMware

Table 6 vSphere communication ports

VMware Avamar

vCenter ESXServer Proxies Backup Clients

VMw

are vCenter n/a *V 443< n/a

ESX Server *V n/a 902< n/a

Proxies n/a n/a n/a n/a

MCS

> 443 n/a > 28002 28001<

> 28002 28001<

Table 7 vSphere listen ports

Initiator

VMware Avamar

vCenter ESXServer Proxies UtilityNode

VMw

are vCenter n/a *V 443 443

ESX Server *V n/a 902 n/a

Proxies n/a n/a n/a 28002

Utility Node

n/a n/a 137 (UDP) 138 (UDP) 139 445 27000 28001- 28009 29000 n/a

Plug-in Options 105

Plug-in Options

The following topics provide information about backup and restore plug-in options for various Avamar for VMware image backup and restore plug-ins:

• How to set plug-in options ... 106

• Linux VMware Image plug-in options ... 106

• Windows VMware Image plug-in options ... 107

• Linux VMware File-level Restore plug-in options ... 107

How to set plug-in options

Plug-in options enable you to control specific actions for on-demand backups, restores, and scheduled backups. The plug-in options that are available depend on the operation type and client plug-in type.

You specify plug-in options for on-demand backup or restore operations or when you create a dataset for a scheduled backup. You can set options by using the graphical controls and by typing options and values in the Enter Attribute and Enter Attribute Value fields.

No error checking or validation is performed on free text entries. Additionally, free text entries override settings made using the graphical controls.

Detailed instructions on how to access and set plug-in options during a backup or restore are available in “Backup” on page 69 and “Restore” on page 75.

Linux VMware Image plug-in options

This topic describes the available options for the Avamar Linux VMware Image plug-in.

Table 8 Linux VMware image backup options Setting Description Use Changed Block Tracking

(CBT) to increase performance

If selected, the VMware changed block tracking feature is used to identify areas of the virtual machine file system that have changed since the last backup and only process those changed areas during the next backup.

Note: Changed block tracking must be enabled at the virtual machine level in order for this feature to work.

Store backup on Data

Domain system To store the backup on a Data Domain system instead of the Avamar server, select the checkbox and then select the Data Domain system from the list.

Note: To enable this option, add a Data Domain system to the Avamar configuration. The EMC Avamar and Data Domain Integration Guide provides instructions.

Table 9 Linux VMware image restore options Setting Description Use Changed Block Tracking

(CBT) to increase performance

Note: Changed block tracking must enabled at the virtual machine level in order for this feature to work.

Windows VMware Image plug-in options 107

Windows VMware Image plug-in options

This topic describes the available options for the Avamar Windows VMware Image plug-in.

Linux VMware File-level Restore plug-in options

Backup operations are not supported by the Avamar Linux VMware File-level Restore plug-in, and no user-configurable restore options are available.

Windows VMware File-level Restore plug-in options

Backup operations are not supported by the Avamar Windows VMware File-level Restore plug-in, and no user-configurable restore options are available.

Table 10 Windows VMware image backup options Setting Description Use Changed Block Tracking

(CBT) to increase performance

Note: Changed block tracking must be enabled at the virtual machine level in order for this feature to work.

Store backup on Data

Domain system To store the backup on a Data Domain system instead of the Avamar server, select the checkbox and then select the Data Domain system from the list.

Note: To enable this option, add a Data Domain system to the Avamar configuration. The EMC Avamar and Data Domain Integration Guide provides instructions.

Table 11 Windows VMware image restore options Setting Description Use Changed Block Tracking

(CBT) to increase performance

Note: Changed block tracking must enabled at the virtual machine level in order for this feature to work.

EMC Avamar 7.0 for VMware User Guide 109

Symbols

.iso files 42 .ova files 16, 32, 33, 34, 36

A

Activity monitor 60 adding

backup client for vCenter database hosts 102 image proxy appliance in vCenter 33, 34, 35 vCenter client 31

virtual machine clients 42 agents, Avamar 18, 56 AIX 17, 18 appliance, VMware 16, 32, 33, 34, 35, 36, 42 authentication certificates 26, 27, 28, 66, 94 installing on MCS 27 Avamar Administrator Activity monitor 60 datasets 58, 59, 62, 66, 67, 73, 100, 101, 102, 106 Default Group 31

Default Proxy Group 59

Default Virtual Machine Group 31, 58, 59, 61

domains 17, 31, 32, 35, 38, 57, 59, 62, 63, 64, 66, 106, 107

installing 26

REPLICATE domain 57

Restore Options dialog box 76, 80, 81, 82, 83, 84, 85, 86, 87, 88, 90

retention policies 62, 72, 73, 100 schedules 62, 73, 100

vCenter Connection Monitor 57 vCenter groups 58, 59, 61, 64

virtual machine and proxy client relationships 59 Avamar Client for Linux

installing 46 Avamar server 38, 39, 55, 62, 72, 73, 80, 82, 84, 86, 88 MCS 26, 27, 28, 46, 47, 56, 66, 94, 104 multi-node 46, 56 read-only state 31, 62 single-node 27, 46, 56 utility node 16, 27, 46, 56, 104 Avamar Web Access 22

B

backups errors 94 full 70 guest 17, 18, 19, 20, 46, 51, 66, 100, 101 monitoring 72 on-demand 106 scheduling 73

vCenter management infrastructure 100

VMware image 16, 18, 19, 20, 21, 23, 24, 26, 38, 44, 46, 49, 57, 59, 66, 80, 81, 83, 94, 105 Browse for Granular Restore toolbar button 76, 85, 87 Browse for Image Restore toolbar button 76, 80, 81, 83, 90

C

CentOS Linux 17

changed block tracking 20, 21, 53, 54, 59, 66, 95, 106, 107 changing

D

data deduplication 19, 20 port 32, 94, 103, 104 data deduplication 19, 20

Data Domain systems 66, 106, 107 data port 32, 94, 103, 104 databases IBM DB2 18, 19 Lotus Domino 18 Microsoft Exchange 18 Microsoft SQL Server 18, 19, 102 Oracle 18, 19 datasets 58, 59, 62, 66, 67, 73, 100, 101, 102, 106 datastore, VMware 20, 29, 42, 43, 60, 64, 94 DB2 databases 18, 19 Debian Linux 17 default gateway 35, 37 Default Group 31 Default Proxy Group 59

Default Virtual Machine Group 31, 58, 59, 61 DHCP 35, 37

DNS 32, 34, 36, 38, 55, 56

Domain Name System (DNS) 32, 33, 34, 35, 36, 38, 55, 56, 66

domains 17, 31, 32, 35, 38, 57, 59, 62, 63, 64, 66, 106, 107 Domino databases 18

dpnctl program 27, 28, 46, 47, 56

E

errors

“Backup Does Not Start” 94

when adding vCenter Server as Avamar client 94 ESX Server 19, 20, 21, 22, 34, 35, 37, 42, 53, 66, 67, 104

fully-qualified hostnames, importance of 66 Exchange databases 18

F

file-level restore 38, 107 files .iso 42 .ova 16, 32, 33, 34, 36 log 19, 20, 34, 42, 44, 46, 56, 91, 94, 102 mcserver.xml 28, 46, 59 FreeBSD 18 full backups 70

G

groups Default Group 31 Default Proxy Group 59

Default Virtual Machine Group 31, 58, 59, 61 guest backup 17, 18, 19, 20, 46, 51, 66, 100, 101

H

hostnames 31, 33, 34, 36, 37, 38, 39, 53, 66, 94 HP-UX 18

I

IBM

AIX operating system 17, 18 DB2 databases 18, 19

image backups, VMware 16, 18, 19, 20, 21, 23, 24, 26, 33, 38, 42, 44, 46, 49, 57, 59, 66, 76, 80, 81, 83, 94, 105, 106, 107

image proxy clients 16, 32, 33, 34, 35, 36, 37, 38, 39, 42, 43, 44, 53, 55, 59, 60, 64, 70, 77, 94, 104 image restore 76, 80, 81, 83, 90, 106, 107 installing authentication certificates on MCS 27 Avamar Administrator 26 vSphere Client 25

installing Avamar Client software Linux 46 IP address 32, 33, 35, 37, 38, 55, 56, 66 ISO images 42

J

Java JRE 27 keytool program 27

Java Runtime Environment (JRE) 27 JRE 27

K

keys OpenSSH 56 keytool program 27

L

log files 19, 20, 34, 42, 44, 46, 56, 91, 94, 102 Lotus Domino databases 18

M

Mac OS X 18 management console

See Avamar Administrator

Management Console Server (MCS) 26, 27, 28, 46, 47, 56, 66, 94, 104 mcserver.xml file 28, 46 Microsoft Exchange databases 18 Office SharePoint 18 SQL Server databases 18, 19, 102 Windows operating system 16, 18, 32 modifying

Default Virtual Machine Group 64 existing VMware clients 55 monitoring

backups 72 restores 72

multi-node Avamar server 46, 56

N

netmask 35, 37 networks/networking default gateway 35, 37 DHCP 35, 37 DHCPs 35, 37 DNS 32, 33, 34, 35, 36, 38, 55, 56, 66 hostnames 31, 33, 34, 36, 37, 38, 39, 53, 66, 94 IP address 32, 33, 35, 37, 38, 55, 56, 66 netmask 35, 37 SSL 27, 28, 66, 100, 101, 102 SSL encryption 27, 28, 66, 100, 101, 102 nodes, Avamar server

utility 16, 27, 46, 56, 104 Novell NetWare 17

O

on-demand backups 106 OpenSSH keys 56 operating systems CentOS Linux 17 Debian Linux 17 FreeBSD 18 HP-UX 18 IBM AIX 17, 18 Mac OS X 18 Microsoft Windows 16, 18, 32 Novell NetWare 17

EMC Avamar 7.0 for VMware User Guide 111

Red Hat Linux 17, 18 SCO Open Server 18 SCO UnixWare 18 SUSE Linux 17, 18 Ubuntu Linux 17 Oracle databases 18, 19 OS X 18

P

plug-in 59, 102, 105, 106, 107 port, data 32, 94, 103, 104 programs

See also commands dpnctl 27, 28, 46, 47, 56 keytool 27

proxy client 16, 32, 33, 34, 35, 36, 37, 38, 39, 42, 43, 44, 45, 53, 55, 56, 59, 60, 64, 70, 77, 94, 104

R

read-only server state 31, 62

recovering vCenter management infrastructure using Avamar backups 102

Red Hat Linux 17, 18 REPLICATE domain 57 requirements

VMware image backup 20 VMware knowledge 20 restore

file-level 76, 85, 87

full image 76, 80, 81, 83, 90 selected drives 76, 80, 81, 83, 90

Restore Options dialog box 76, 80, 81, 82, 83, 84, 85, 86, 87, 88, 90

restores

monitoring 72 restoring

all virtual disks 76, 80, 81, 83, 90 virtual machine

to a different (existing) virtual machine 81 to a new virtual machine 83

to the original virtual machine 79 retention policies 62, 72, 73, 100

S

schedules 62, 73, 100 scheduling backups 73 SCO Open Server 18 UnixWare 18

Secure Socket Layer (SSL) 27, 28, 66, 100, 101, 102 security

SSL 27, 28, 66, 100, 101, 102

SSL encryption 27, 28, 66, 100, 101, 102 server, Avamar

See Avamar server

single-node Avamar server 27, 46, 56 Solaris 18

SSL 27, 28, 66, 100, 101, 102 storage

SAN 20

Storage Area Network (SAN) 20 SUSE Linux 17, 18

T

templates virtual machine 31, 33, 34, 35, 36, 52, 53, 77, 79

U

Ubuntu Linux 17 UnixWare 18 user accounts 32, 94 vCenter login 29, 32, 94 user authentication certificates 26, 27, 28, 66, 94 installing on MCS 27

utility node, Avamar server 16, 27, 46, 56, 104 utilize_changed_block_list setting 59

V

VADP 16 vCenter 16, 17, 18, 19, 20, 22, 23, 26, 27, 28, 29, 31, 32, 33, 34, 35, 36, 39, 42, 44, 51, 52, 53, 55, 56, 57, 58, 59, 60, 61, 62, 64, 66, 91, 94, 99, 100, 101, 102, 104 Avamar client 31, 32, 55, 56

configuring for image backup and restore 29 Connection Monitor 57

groups, in Avamar Administrator 58, 59, 64 login user account 29, 32, 94

server 16, 33, 34, 35, 42, 44, 51, 56, 91, 94 vCenter Connection Monitor 57

vCenter groups 58, 59, 61

vCenter Server 16, 22, 31, 32, 34, 42, 44, 51, 52, 55, 56, 59, 60, 62, 91, 94

virtual machine

Avamar client 16, 32, 55, 72, 73

relationship with proxy clients in Avamar Administrator 59

template 31, 33, 34, 35, 36, 52, 53, 77, 79 viewing protected in Avamar Administrator 57

viewing replicated client name in Avamar Administrator 57

VMware 66

appliance 16, 32, 33, 34, 35, 36, 42 appliance .ova files 33, 34, 36 appliance files 16, 32, 33, 34, 36 datastore 20, 29, 42, 43, 60, 64, 94 ESX Servers 19, 20, 21, 22, 34, 35, 37, 42, 53, 66, 67, 104 image backups 16, 18, 19, 20, 21, 23, 24, 26, 29, 33, 38, 42, 44, 46, 49, 57, 59, 66, 76, 80, 81, 83, 94, 105, 106, 107 knowledge required 20 proxies 16, 32, 33, 34, 35, 36, 37, 38, 39, 42, 43, 44, 45, 53, 55, 56, 59, 60, 64, 70, 77, 94, 104 requirements for image backups with Avamar 20 tools 30

vSphere 21, 22, 25, 33, 34, 35, 42, 43, 44, 45, 54, 56, 79, 81, 87, 91, 94, 95, 100, 103, 104

vSphere Client 25, 33, 34, 35, 42, 43, 44, 45, 54, 56, 79, 81, 87, 91, 94, 95

VMware Image Dataset 58, 66

VMware vStorage API for Data Protection (VADP) 16 vSphere 25, 33, 34, 35, 42, 43, 44, 45, 54, 56, 79, 81, 87,

91, 94, 95, 100, 103

client 25, 33, 34, 35, 42, 43, 44, 45, 54, 56, 79, 81, 87, 91, 94, 95

In document EMC Avamar 7.0 for VMware (Page 100-112)