How to configure and use NetBackup 6.5.1 for VMware Symantec TechNote 293350

Transcription

Symantec TechNote 293350
How to configure and use
NetBackup 6.5.1 for
VMware
This document describes how to configure and use NetBackup 6.5.1 to back up
and restore VMware virtual machines.
11/21/07
■
“NetBackup for VMware: introduction” on page 2
■
“NetBackup for VMware environment” on page 2
■
“Configuration tasks: overview” on page 7
■
“Configure NetBackup” on page 9
■
“Back up VMware files” on page 19
■
“Restore VMware files” on page 20
■
“Best practices” on page 26
■
“Support matrices” on page 28
■
“VMware logging” on page 30
■
“Troubleshooting” on page 31
■
“Terminology” on page 34
2 How to configure and use NetBackup 6.5.1 for VMware
NetBackup for VMware: introduction
Symantec Corporation
11/21/07
NetBackup for VMware: introduction
NetBackup for VMware provides backup and restore of the VMware virtual
machines that run on VMware ESX servers. NetBackup for VMware takes
advantage of VMware Consolidated Backup (VCB) technology. The backup
process is off-loaded from the ESX server to a separate host that is called the
VMware backup proxy server.
The main features of NetBackup for VMware
NetBackup for VMware does the following.
■
Reduces the backup processing load on the VMware ESX server.
■
Automatically creates quiesced snapshots using the VMware sync driver
(Windows only).
■
Uses snapshot technology to keep virtual machines 100% available to users.
■
Backs up and restores individual files or the full virtual machine.
■
Restores the individual files from a full virtual machine backup, by means of
the NetBackup FlashBackup-Windows policy type.
■
Backs up virtual machines even when they are powered off.
NetBackup for VMware environment
This section describes the components of NetBackup for VMware.
NetBackup for VMware components
VMware backup proxy server
NetBackup for VMware uses a special host that is called a VMware backup proxy
server. The VMware backup proxy server is a NetBackup client that performs
backups on behalf of the virtual machines. The proxy server can also be
configured as a NetBackup master or media server.
The VMware backup proxy server is the only host on which NetBackup client
software is installed. No NetBackup client software is required on the VMware
virtual machines.
Virtual machine
Virtual machines provide complete guest operating systems on virtualized
hardware. In a NetBackup policy, a virtual machine is configured as a NetBackup
http://entsupport.symantec.com/docs/293350
Symantec TechNote
11/21/07
How to configure and use NetBackup 6.5.1 for VMware
client, even though NetBackup client software is not installed on the virtual
machine.
Alternative configurations are possible.
See the Symantec white paper titled Veritas NetBackup 6.5 for VMware 3.x Best
Practices Guide.
ESX server
The VMware ESX server presents a virtualized hardware environment to
multiple virtual machines; each virtual machine runs an independent operating
system. Users can run applications in the virtualized OS as if the OS was
installed in its own physical machine.
VirtualCenter server
The VMware VirtualCenter server coordinates multiple ESX servers and work
loads by migrating virtual machines from one ESX server to another. The
VirtualCenter server is optional in the NetBackup for VMware environment.
Converter server
The VMware Converter server assists in full virtual machine restores to the ESX
server. The Converter must be installed on the same host as the VMware backup
proxy server.
VMware NetBackup Integration Module (VNIM) not required!
The VMware NetBackup Integration Module (VNIM) is not required for
NetBackup for VMware. Conflicts can occur between NetBackup 6.5.1 for
VMware policies and any older script-based policies that use VNIM.
See under “Notes and tips” on page 31.
Symantec TechNote
3
11/21/07
Environment diagram
The hardware components for NetBackup for VMware are shown in Figure 1-1.
Figure 1-1
NetBackup for VMware: backup environment
NetBackup
master server
1
2
LAN / WAN
5
NetBackup
storage unit
(disk or tape)
SAN
3
4
acting as both NetBackup
media server and Snapshot
Client off-host client
VMware virtual disk files
(datastore)
must be available on SAN or iSCSI
to both VMware backup proxy
server and VMware ESX server
VMware ESX server
runs virtual machines
Basic backup process:
1
The NetBackup master server initiates the backup.
2
The NetBackup client on the VMware backup proxy server initiates a
VMware snapshot.
3
The VMware sync driver synchronizes the file system on the virtual
machine.
4
The VMware backup proxy server does one of the following:
5
■
For full virtual machine backup: copies the disk files from the VMware
virtual disk datastore.
■
For file-level backup: mounts individual disk volumes from the VMware
virtual disk datastore.
The NetBackup media server reads the data from the VMware snapshot on
the proxy server and writes the data to the NetBackup storage unit.
Symantec TechNote
11/21/07
The NetBackup for VMware environment may have a VMware VirtualCenter
that manages multiple ESX servers.
Figure 1-2
VirtualCenter with multiple ESX servers
NetBackup
master server
LAN / WAN
NetBackup
storage unit
(disk or tape)
VMware backup proxy
server
VMware
VirtualCenter
SAN
VMware virtual disk files
(datastore)
VMware ESX
servers
Backup type: file-level and full virtual machine
NetBackup for VMware supports two kinds of backup of virtual machines:
file-level and full virtual machine.
■
File-level: backs up ordinary files and folders on the virtual machine. The
backed up files and folders can be individually restored. Does not support
restore of the guest OS or of the virtual machine.
Note: a file-level backup cannot back up the following:
■
The VMware virtual disk files that define the virtual machine.
■
Windows system protected files (System State).
■
Windows system directories such as the following:
C:\WINDOWS\system
C:\WINDOWS\system32
■
■
Symantec TechNote
Windows system database files (such as RSM Database and Terminal
Services Database).
Full virtual machine: backs up an entire virtual machine as a set of virtual
disk files. The backup includes all files and folders as well as operating
system files and VMware virtual disk files. Supports restore of the guest OS
and of the entire virtual machine. Also supports individual file restore for a
Windows guest OS if the backup was made with the 2-Mapped FullVM
option.
5
11/21/07
Notes and restrictions
Note the following about NetBackup for VMware:
■
NetBackup for VMware does not work with the VMware NetBackup
Integration Module (VNIM). Conflicts can occur between NetBackup 6.5.1
for VMware policies and any older script-based policies that use VNIM.
See under “Notes and tips” on page 31.
■
NetBackup master and media servers and the VMware backup proxy server
must run NetBackup 6.5.1 or later.
■
The VMware backup proxy server must run Windows 2003. The supported
hardware types are the same as for any NetBackup Windows client. Further
information is available on supported guest operating systems and VMware
components and versions.
See “Support matrices” on page 28.
■
Symantec recommends that the proxy server is also the NetBackup media
server.
■
NetBackup for VMware does not support the NetBackup Instant Recovery
feature.
■
For UNIX and Linux virtual machines, NetBackup for VMware supports full
virtual machine backup and full virtual machine restore only.
■
For backups of the entire virtual machine that allow individual file restore
(2-Mapped FullVM), incremental backups are not supported.
■
VMware does not support VCB snapshots of virtual machines if a drive is
assigned to the virtual machine in raw device mapping (RDM) mode.
■
To restore individual NTFS encrypted files, you must install a NetBackup
client on the virtual machine.
License requirements
NetBackup for VMware requires the NetBackup Snapshot Client license, which
is included in the NetBackup Enterprise Client license.
Symantec TechNote
11/21/07
Configuration tasks: overview
VMware tasks
The VMware components including ESX servers and virtual machines must be
set up before you configure NetBackup. These VMware-specific tasks are only
briefly described in this guide. Further assistance with these tasks may be found
in your VMware documentation.
Table 1-1
VMware tasks
Tasks for the VMware administrator
1
Set up disk storage on Fibre Channel or iSCSI. The disk storage must be
accessed by the VMware backup proxy server and by the ESX servers or
VirtualCenter server.
2
Install the VMware ESX server and virtual machines.
3
Install VMware Tools on the virtual machines that you plan to back up.
4
Optional: install a VirtualCenter server.
The VirtualCenter server must not be installed on the same host as the
VMware backup proxy server.
5
Install the VMware Converter server on the VMware backup proxy
server.
Note: the proxy server must be installed on Windows 2003.
6
Install a supported version of VMware Consolidated Backup (VCB) on
the VMware backup proxy server.
Symantec recommends that the NetBackup media server and the
VMware backup proxy server be installed on the same host.
See Table 1-2.
Notes:
Symantec TechNote
■
Ensure that the hardware and the SAN are configured properly. The VMware
datastore where the target virtual machine files exist must be accessible to
both the ESX server and the VMware backup proxy.
■
VMware has specific hardware and configuration requirements. VMware
SAN requirements can be found in the VMware SAN Configuration guide.
See http://www.vmware.com/pdf/vi3_san_guide.pdf
7
11/21/07
NetBackup tasks
Table 1-2 lists the NetBackup configuration tasks that are described later in this
chapter and in other NetBackup documentation, as indicated.
Table 1-2
NetBackup tasks
Tasks for the NetBackup administrator
1
Install the NetBackup 6.5.1 master server and media server.
See the NetBackup 6.5 Installation Guide.
Symantec recommends that the NetBackup media server and the
VMware backup proxy server be installed on the same host.
2
Install the NetBackup 6.5.1 Snapshot Client license on the master
server, and install Snapshot Client 6.5.1 software on the VMware
backup proxy server.
See the Installation chapter of the NetBackup Snapshot Client Guide.
Note: the proxy server must be installed on Windows 2003.
3
Set NetBackup access credentials for the VMware VirtualCenter (if any)
or VMware ESX servers.
See “Add NetBackup credentials for VMware” on page 9.
4
Add the VMware backup proxy server to your NetBackup configuration.
See “Add proxy server to NetBackup configuration” on page 10.
5
Configure incremental backups for VMware.
See “Configure incremental backups for VMware” on page 10.
6
Create a NetBackup Snapshot Client policy for VMware.
See “Configure a VMware policy” on page 10.
7
Perform a backup or restore.
See “Back up VMware files” on page 19 and “Restore VMware files” on
page 20.
8
Recheck the configuration.
See “Best practices” on page 26 and “Troubleshooting” on page 31.
Symantec TechNote
11/21/07
Configure NetBackup
Configure NetBackup
This section describes the NetBackup configuration procedures.
Add NetBackup credentials for VMware
NetBackup requires logon credentials to access the VMware ESX servers or the
VMware VirtualCenter.
To add NetBackup credentials
1
Start the NetBackup Administration Console:
On UNIX, enter: /usr/openv/netbackup/bin/jnbSA &
On Windows, click Start > Programs > Veritas NetBackup > NetBackup
Administration Console.
2
Click Media and Device Management > Credentials > Virtual Machine
Servers.
3
Click Actions > New > New Virtual Machine Server and enter the fully
qualified domain name of the virtual machine server (VirtualCenter or ESX
server).
4
In the Credentials pane of the Virtual Machine Server dialog box, enter the
following:
Virtual Machine Server Type
Select the type of virtual machine:
■
VMware VirtualCenter server: for a VirtualCenter that manages
multiple VMware ESX servers. Note: if you have a VirtualCenter, do not
enter logon credentials for individual ESX servers. NetBackup uses
credentials for the VirtualCenter only.
■
VMware ESX server: for ESX servers where there is no VirtualCenter.
Use this dialog box to enter credentials for each ESX server.
VMware Converter: Not currently implemented.
User name
Enter the user name for the virtual machine server.
Password
Enter the password (and confirm it) for the virtual machine server.
Port Number
Specify the Internet port for the virtual machine server. Set the port to 443
if the VMware backup proxy has VCB 1.1; for older versions of VCB, set the
port to 902.
■
5
Symantec TechNote
Click OK.
9
Configure NetBackup
6
11/21/07
If your site has multiple ESX servers but no VMware VirtualCenter, use the
Virtual Machine Server dialog box to enter credentials for each ESX server.
Add proxy server to NetBackup configuration
You must add the VMware backup proxy server to your NetBackup
configuration. In the NetBackup Administration Console, do the following.
1
Click Host Properties > Master Server > double click NetBackup master
server > Virtual Machine Proxy Servers.
2
Click Add.
3
In the New Server dialog box, enter the name of the VMware backup proxy
server, and click Add.
4
When you are finished adding proxies, click Close.
5
Click Apply and then OK.
Configure incremental backups for VMware
Incremental backups of virtual machines must be based on timestamps, not on
archive bit. You must configure the NetBackup client on the VMware backup
proxy server as follows.
To configure the client on the proxy server for incremental backups:
1
Start the Backup, Archive, and Restore interface from the NetBackup client
that is installed on the VMware backup proxy server. For example: click
Start > Programs> Veritas NetBackup > Backup, Archive, and Restore.
2
Click File > NetBackup Client Properties.
3
On the General tab, make sure Perform incrementals based on archive bit is
clear (unchecked).
Configure a VMware policy
The following procedure describes how to create a policy for VMware backup.
You can also use the Snapshot Policy Configuration wizard to create a policy.
1
Start the NetBackup Administration Console as follows:
On UNIX, enter: /usr/openv/netbackup/bin/jnbSA &
On Windows, click Start > Programs > Veritas NetBackup > NetBackup
2
Click on Policies and select Actions > New > New Policy.
Symantec TechNote
11/21/07
Configure NetBackup
Select the policy type:
MS-Windows-NT or
FlashBackup-Windows
Select storage unit or group
Click Perform
snapshot backups
and
Perform off-host
backup.
Click Use virtual machine
proxy and select the
VMware proxy.
3
Select one of the following policy types:
MS-Windows-NT
For backup of individual drives or individual folders and files (Windows
only). Cannot back up the entire virtual machine. For a backup of the entire
virtual machine, choose FlashBackup-Windows.
FlashBackup-Windows
For backup of individual drives (Windows), or backup of the entire virtual
machine (any supported virtual machine).
For UNIX and Linux virtual machines, FlashBackup-Windows is the only
supported policy type.
The FlashBackup-Windows policy type has the following advantages:
■
Symantec TechNote
Increases the backup speed as compared to standard file-order backup
methods, if the virtual machine is heavily populated with small files.
11
Configure NetBackup
■
11/21/07
Can create a backup from which you can restore either individual files
or the full virtual machine.
4
Select a policy storage unit or storage unit group.
Storage unit groups are described in the NetBackup Administrator’s Guide,
Volume I.
5
Select Perform snapshot backups.
If Bare Metal Restore is installed, you must deselect Collect disaster
recovery information for Bare Metal Restore to select Perform snapshot
backups.
The FlashBackup-Windows policy type automatically selects Perform
snapshot backups.
6
Select Perform off-host backup and Use virtual machine proxy.
7
In the Virtual Machine Proxy Server field (Off-host backup machine on
Windows): select the name of the VMware backup proxy server from the
pull-down list.
If the proxy server does not appear in the pull-down, make sure it was added
to the Host Properties setting.
See “Add proxy server to NetBackup configuration” on page 10.
You may have to close and reopen the policy for the added proxy server to
appear in the list.
8
Click Snapshot Options.
Symantec TechNote
11/21/07
Configure NetBackup
Automatically selected when
you choose
Use virtual machine proxy on
Attributes tab.
Specify these options
Specify these values for the VMware snapshot method:
Snapshot mount point
A folder on the VMware backup proxy server. An example mount point is:
G:\mnt
If the folder does not exist on the VMware backup proxy, NetBackup creates
it.
This folder is used in one of two ways, depending on the Virtual Machine
Backup parameter value you choose:
Symantec TechNote
■
For file-level backups (0-File), the VMware backup proxy server mounts
snapshots of individual virtual disk volumes in this folder. These
snapshots are links to the virtual datastore. No virtual machine data is
copied to this folder.
■
For full virtual machine backups (1-FullVM or 2-Mapped FullVM), the
VMware backup proxy server creates a snapshot of the entire virtual
machine in this folder. This snapshot contains copies of all virtual disk
files on the virtual datastore that constitute a point-in-time image of
the entire virtual machine. Enough space must be available on the
proxy server to contain the snapshot.
13
Configure NetBackup
11/21/07
Note: For Windows virtual machines, the mount point must be a local drive,
not network mounted.
Virtual Machine Backup parameters
0-File: For backup of either of the following:
■
Individual folders and files, individual drives, or all local drives, with
the MS-Windows-NT policy type.
Individual drives or all local drives, with the FlashBackup-Windows
policy type.
The 0-File option cannot be used to back up Windows system files or
VMware virtual disk files.
See “Backup type: file-level and full virtual machine” on page 5.
1-FullVM: For backup of the entire virtual machine. This option works with
the FlashBackup-Windows policy type only. Individual files cannot be
restored from this backup.
2-Mapped FullVM: For backup of the entire virtual machine. This option
works with the FlashBackup-Windows policy type only. Two kinds of
restore are possible: restore of the entire virtual machine or of individual
folders and files.
A tabular presentation of these parameters is available.
See “VMware backup options compared” on page 18.
■
9
To save these settings, click OK and then Apply.
10 Use the Schedules tab to define a schedule.
11 On the Clients tab, click New to specify virtual machines to back up.
Symantec TechNote
11/21/07
Configure NetBackup
ESX server or
VirtualCenter
■
Select a VirtualCenter or ESX server, or select individual virtual
machines.
■
To discover virtual servers on the network, click the Browse Virtual
Machines box.
Use the Find field to locate a virtual machine in the list.
■
To enter the name of a virtual machine manually, uncheck the Browse
Virtual Machines box and enter the fully qualified name of the virtual
machine.
■
The machine names that are listed may be derived from a cache file.
Using the cache file is faster than rediscovering the machines on the
network if your site has a large number of virtual machines. To update
the cache file and re-display virtual machines, click the refresh option
to the right of the Last Update field. This field shows the date and time
of the most recent cache file that contains the names of virtual
machines.
For NetBackup to access the virtual machines, the following are
required:
■
Symantec TechNote
The VMware VCB must be installed on the VMware backup proxy
server.
15
Configure NetBackup
■
11/21/07
The NetBackup master server must have credentials for the
VMware VirtualCenter or ESX server(s).
See “Add NetBackup credentials for VMware” on page 9.
The browsing time-out value must not be set too low.
See “Change the browsing time-out for virtual machine discovery”
on page 31.
The virtual machines you selected are listed in the Clients tab.
■
12 Use the Backup Selections tab to specify the virtual machine files to back
up.
Click New. You can make entries manually, or click on the pull-down (UNIX)
or hand icon (Windows) to select from available directives.
Note: for VMware snapshot backup, the System_State directive (Windows
2000) and the ShadowCopy Components directive (Windows 2003) are not
supported.
Enter any of the following and then click Add (on UNIX) or press Enter
(Windows):
■
Individual Windows folders and files, if the policy type is
MS-Windows-NT.
Symantec TechNote
11/21/07
Configure NetBackup
■
Individual drive letters. The drive letter format depends on the policy
type:
MS-Windows-NT policy type
Enter the drive letter as follows (for example):
E:\
The drive letter must not be a network (shared) drive: it must specify a
drive on the virtual machine.
For MS-Windows-NT policies, you cannot back up the following:
Windows System State, Windows ShadowCopy Components, Windows
OS partitions that contain Windows system files (usually C:), or
VMware virtual disk files. To back up these files, use the
ALL_LOCAL_DRIVES directive in a FlashBackup-Windows policy.
FlashBackup-Windows policy type
Enter the drive letter as follows (for example):
\\.\E:
The drive must be designated exactly as shown (E:\ is not correct).
■
The ALL_LOCAL_DRIVES directive backs up all local drives on the
virtual machines that are selected on the Clients tab. This entry is the
only one supported for UNIX and Linux virtual machines.
IMPORTANT: the kinds of files that are included in an
ALL_LOCAL_DRIVES backup depend on the policy type and the
VMware snapshot options, as follows.
■
MS-Windows-NT policy: the ALL_LOCAL_DRIVES directive backs
up all data files on the virtual machines that are selected on the
Clients tab. This directive does not back up the following: Windows
System State, Windows OS partitions that contain the Windows
system files (usually C:), or VMware virtual disk files.
■
FlashBackup-Windows policy: the ALL_LOCAL_DRIVES directive
backs up all data files on the virtual machines.
The ALL_LOCAL_DRIVES directive also backs up the following, if
the snapshot option is 1-FullVM or 2-Mapped FullVM: Windows
System State files, Windows OS partitions that contain the
Windows system files (usually C:), and VMware virtual disk files.
See “VMware backup options compared” on page 18 for more
details.
For FlashBackup-Windows: if you chose value 1 or 2 for the Virtual
Machine Backup parameter, ALL_LOCAL_DRIVES is the only entry
allowed under Backup Selections.
13 On the policy Attributes tab: if you click Apply or OK, a validation process
checks the policy and reports any errors. If you click Close, no validation is
performed.
Symantec TechNote
17
Configure NetBackup
11/21/07
VMware backup options compared
This section describes the available VMware policy configuration options.
Table 1-3 is for MS-Windows-NT policies and Table 1-4 is for
FlashBackup-Windows policies. A brief description of each policy type is
available.
See under step 3 on page 11.
Table 1-3
VMware backup options for MS-Windows-NT policies
Backup Selections entry
Virtual Machine
What is backed up
Backup parameter
What can be restored
Individual folders and files
0-File
Specified folders and files
only, excluding Windows
system files
Individual drives
0-File
All data files and folders in
specified drives, excluding
Windows system files
0-File
All data files and folders on all Individual folders and files
local virtual machine drives,
excluding Windows system
files
For example: E:\
ALL_LOCAL_DRIVES
directive
Table 1-4
VMware backup options for FlashBackup-Windows policies
Backup Selections
entry
Virtual Machine
What is backed up
Backup parameter
What can be restored
Individual drives
0-File
Individual drives as raw devices.
Individual folders and files,
or entire drive (not including
operating system or VMware
virtual disk files)
ALL_LOCAL_DRIVES
directive
0-File
All individual drives in virtual
machine as raw devices.
Individual folders and files,
or entire drives (not including
operating system or VMware
virtual disk files)
ALL_LOCAL_DRIVES
directive
1-FullVM
VMware virtual disk files. Backup Entire virtual machine only
is “raw partition” type.
ALL_LOCAL_DRIVES
directive
2-Mapped FullVM
VMware virtual disk files. Backup Entire virtual machine or
is “raw partition” type.
individual folders and files
For example: \\.\E:
Symantec TechNote
11/21/07
Back up VMware files
Back up VMware files
You can initiate a VMware backup in the same manner as any NetBackup
backup.
For instance: to start a backup manually, click on the Policies node in the
NetBackup Administration Console, select the policy, and click Actions > Manual
Backup.
See the NetBackup Backup, Archive, and Restore Getting Started Guide for
further instructions.
Note: NetBackup for VMware does not support user backups: only manual or
scheduled backups are allowed.
Symantec TechNote
19
Restore VMware files
11/21/07
You can use the NetBackup Backup, Archive, and Restore interface to restore
from NetBackup for VMware backups, as explained in this section.
VMware restore procedures: overview
Individual file restore
The following restore procedures are supported.
■
One-stage process: restore individual files to the virtual machine by
restoring to the backup proxy. The VMware virtual machine drives to which
restores are to be directed must be configured in one of two ways:
■
The virtual machine drives must be shared through the guest operating
system on the virtual machine.
NetBackup client software must be installed on the VMware virtual
machine.
See “Set up NetBackup Client Service for restore to a shared virtual
machine drive” on page 21.
■
■
Two-stage process:
1, Restore individual files from the VMware backup proxy server to a
NetBackup Windows client (not to the virtual machine).
See the NetBackup Backup, Archive, and Restore Getting Started Guide on
how to restore to different locations.
2, Manually copy the restored files to the Windows virtual machine.
(NetBackup does not perform this step.)
Full VMware virtual machine restore
The following restore procedure is supported.
Restore all virtual machine files to the VMware backup proxy server, which is
used as a staging machine. Then do one of the following:
■
Let NetBackup issue a VMware-provided script to restore the virtual
machine to a designated virtual machine server. The virtual machine files
are then removed from the staging machine.
■
Use the VMware Converter application on your own to restore the virtual
machine from the staging machine to the virtual machine server.
Symantec TechNote
11/21/07
Set up NetBackup Client Service for restore to a shared
virtual machine drive
To restore individual files to a Windows virtual machine which has a shared
drive, note: the “NetBackup Client Service” must be logged on as the
Administrator account (not as the Local System account). The Administrator
account lets NetBackup write to the directories on the virtual machine to which
the data is restored.
If you try to restore files while the NetBackup Client Service is logged on as the
Local System account, the restore fails.
To log on the NetBackup Client Service as Administrator
1
In Windows Services on the VMware backup proxy server, double-click the
NetBackup Client Service.
2
Check the Log On tab: if the service is not logged in as Administrator, stop
the service.
3
Change the logon to the Administrator account in the domain in which both
the virtual machine and the proxy server reside.
4
Restart the service.
5
Retry the restore.
Notes
Note the following.
■
Unless a NetBackup client is installed on the virtual machine, NetBackup for
VMware backups do not support user-directed restore. Only server-directed
restores performed by the administrator are allowed.
■
In the NetBackup Backup, Archive, and Restore interface, restore types
labeled “proxy restore” do not apply to VMware backups. An example of
such a restore type is “from Normal Backup as a Proxy.” These restore types
do not refer to the VMware backup proxy server. Use the restore procedures
that are described in this chapter.
■
For VMware files that were encrypted on the virtual machine using
Windows NTFS encryption, you must install a NetBackup client on the
virtual machine.
Restore individual folders and files
If the VMware backup was made with either of the following, you can restore
individual files:
Symantec TechNote
21
11/21/07
■
An MS-Windows-NT policy.
■
A FlashBackup-Windows policy with a Virtual Machine Backup parameter
set to either 0-File or 2-Mapped FullVM.
To restore individual folders or files:
1
Start the NetBackup Backup, Archive, and Restore interface.
On UNIX servers, you can start the interface from the NetBackup
On Windows, you must start the Backup, Archive, and Restore interface
separately.
2
Specify the source client and destination client and type of policy:
UNIX: on the Restore Files tab, click
Windows: click Files > Specify NetBackup Machines and Policy Type.
3
Specify the following:
■
Server to use for backup and restores: the NetBackup master server
that directed the backup.
■
Source client for restores: the VMware virtual machine that was
backed up.
■
Destination client for restores: specify one of the following:
■
■
The VMware virtual machine that was originally backed up, if
NetBackup client software has been installed on the virtual
machine.
■
The VMware backup proxy server.
Note that NetBackup Client Service must be logged on as
Administrator.
See “Set up NetBackup Client Service for restore to a shared virtual
machine drive” on page 21.
Policy type for restores: the type of policy that made the backup
(MS-Windows-NT or FlashBackup-Windows).
4
Select the type of restore:
UNIX: on the Restore Files tab, select Normal Backups.
Windows: click Files > Select Files and Folders to Restore > from Normal
Backup
5
UNIX: enter the Browse directory that contains the folders or files to
restore.
6
Click the files you want to restore.
7
Start the restore:
UNIX: click Restore.
Symantec TechNote
11/21/07
Windows: click Actions > Restore...
8
Windows: if NetBackup client software is not installed on the virtual
machine, select one of the following:
■
Restore everything to a different location
Restore individual folders and files to different locations
Destinations must be entered as UNC pathnames that refer to shared
drives on the virtual machine.
For example, to restore the file E:\folder1\file1 on virtual machine
vm1, enter the following destination:
■
\\vm1\e$\folder1\file1
Restore the full VMware virtual machine
If the VMware backup was made with both of the following, you can restore the
entire virtual machine:
■
A FlashBackup-Windows policy.
■
The Virtual Machine Backup parameter was set to 1-FullVM or 2-Mapped
FullVM.
To restore the full virtual machine
1
Start the NetBackup Backup, Archive, and Restore interface as described
under “Restore individual folders and files” on page 21.
2
Specify the source client and destination client and type of policy:
UNIX: On the Restore Files tab, click
Windows: click Files > Specify NetBackup Machines and Policy Type.
3
Specify the following:
4
Symantec TechNote
■
Server to use for backup and restores: the NetBackup master server
that directed the backup.
■
Source client for restores: the VMware virtual machine that was
backed up.
■
Destination client for restores: the VMware backup proxy server.
■
Policy type for restores: FlashBackup-Windows.
Select the type of restore:
UNIX: on the Restore Files tab, select Restore type > Virtual Machine
Backups.
Windows: click the down arrow on the
option to select
Restore from Virtual Machine Backup. A restore window displays the
backups available for restore.
23
5
11/21/07
Select the virtual machine backup to restore.
UNIX:
■
On the Restore Files tab, specify the Start date and End date within
which to search for the backup. Click either of these options:
■
Specify root (/) in the Browse directory field and press Enter.
■
Click on the root folder that is displayed under Directory Structure.
Windows:
In the NetBackup History pane, click on the VMware backup, then click on
the item that is displayed under All Folders. You cannot select individual
files. You must select the entire virtual machine.
Symantec TechNote
11/21/07
6
Select restore options.
UNIX: click Restore.
Windows: click Actions > Restore.
7
Select from the following options on the Restore Marked Files dialog box:
Restore Options
■
Restore the entire virtual machine
Restores all virtual machine files to the staging machine that is
specified on this dialog box. NetBackup then issues a VMware-provided
script to restore the virtual machine to the Virtual machine server you
specify. After the restore is complete, the restored virtual machine is
powered off. The virtual machine files are then removed from the
staging machine.
Note: If the virtual machine display name already exists on the Virtual
machine server, the restore fails.
Restore all virtual machine files to the staging machine
Restores all virtual machine files to the staging machine. NetBackup
does not restore the files to the Virtual machine server. You can use the
VMware Converter application to restore the entire virtual machine
from the staging machine to the Virtual machine server.
See your VMware documentation.
Restore Destination Choices
■
■
Symantec TechNote
Virtual machine server:
25
Best practices
11/21/07
Select or enter the virtual machine server to which to restore the files.
The list includes only the machines for which NetBackup has
credentials. The default server is the one stored in the backup image
information.
8
■
Staging machine for restoration:
Select or enter the VMware backup proxy server to which the VMware
files are temporarily restored. If you chose Restore the entire virtual
machine, the files are then restored to the Virtual machine server and
deleted from this staging server.
The default is the VMware backup proxy server that was used for the
backup. The name of that proxy server is stored in the backup image
information. On this dialog box, the pull-down list for staging machines
includes the VMware backup proxy servers that are defined in existing
NetBackup policies.
■
Restore staging location:
Enter a Windows file path on the staging machine to which the virtual
machine files are temporarily restored. The default is the VMware
backup proxy server mount point that was stored in the backup image
information.
Click Start Restore.
Best practices
■
For a more efficient backup, the NetBackup media server and the VMware
backup proxy server should be installed on the same host.
■
VMware recommends that you run no more than four simultaneous backups
of virtual machines that reside on the same datastore.
■
On the VMware backup proxy server, the file system that contains the
snapshot mount point undergoes extensive I/O during full virtual machine
backup. For this reason, the file system should reside on a high performance
device.
■
On the VMware backup proxy server, the file system that contains the
snapshot mount point should be reserved for snapshots only. It should also
be on a dedicated SCSI or Fibre Channel bus.
■
The file system that contains the snapshot mount point should be routinely
defragmented. A heavily fragmented file system can adversely affect the
performance of a FlashBackup-based backup.
■
To increase backup throughput on the VMware backup proxy, define
multiple snapshot mount points. Each mount point should be created on a
Symantec TechNote
11/21/07
Best practices
disk that is connected on its own disk bus (such as SCSI or IDE). Thus, I/O
activity that one policy creates can be isolated from I/O activity that other
policies create.
■
Successful VMware snapshots depend on the following:
■
The amount of I/O that occurs on the virtual machine datastore.
Backups should be scheduled when relatively little I/O activity is
expected. Reducing the number of simultaneous backups can also help.
(Use the Limit jobs per policy attribute in the NetBackup policy.)
■
The design of the I/O substructure that is associated with each virtual
machine datastore. For correct I/O design and implementation, consult
your VMware documentation.
■
Include in a single NetBackup policy those virtual machines that use the
same datastore. This practice lets you control the amount of backup-related
I/O that occurs per datastore and thus limit the backup impact on the target
virtual machines.
■
NetBackup supports multiple VMware backup proxy servers. When a single
backup proxy is saturated with a backup process, another proxy can be
added to increase backup throughput.
■
Upgrade to the latest version of VMware Virtual Infrastructure, which
includes the latest version of ESX server, VirtualCenter Server, and VCB.
More information
More information about VMware and NetBackup for VMware can be found in
the following:
■
VMware Inc. provides an extensive set of manuals on VMware products.
See the VMware ESX Server and VirtualCenter documentation at:
http://www.vmware.com/support/pubs/
Symantec TechNote
■
Veritas NetBackup 6.5 for VMware 3.x Best Practices Guide (Symantec white
paper).
■
Veritas NetBackup 6.5 for VMware 3.x Implementation Guide (Symantec
white paper).
■
Further information on NetBackup for VMware is also available.
See the Veritas NetBackup 6.5 Snapshot Client Configuration Guide at:
http://entsupport.symantec.com/docs/288300.
27
Support matrices
11/21/07
Support matrices
This section describes support information for NetBackup for VMware.
Supported VMware components
NetBackup for VMware supports the following.
Table 1-5
Supported VMware components and versions
VMware component
Version
ESX server (including VMware
Tools)
3.0, 3.0.1, 3.0.2, and 3.5.
VMware Consolidated Backup
(VCB)
1.x
Supported operating systems for VMware backup proxy server
The VMware backup proxy server must be installed on a Windows 2003 host.
The supported hardware types are the same as for any NetBackup Windows
client.
Supported disk arrays
NetBackup for VMware can be used with any storage array that VMware
Consolidated Backup (VCB) supports. Make sure the datastore for the ESX server
is on storage that VCB supports.
VMware guest operating systems tested
The following table lists VMware guest operating systems that tested
successfully with NetBackup 6.5.1.
Table 1-6
VMware guest OS
Notes
Windows XP 32bit/64bit
Windows XP 64bit requires VMware Tools
3.0.1 (not supported with 3.0.2)
Windows 2003 32bit/64bit
Windows 2000 32bit
Windows NT 4.0
Symantec TechNote
11/21/07
Support matrices
Table 1-6
VMware guest OS
Notes
RHEL 2.1
RHEL 3.0
RHEL 4 32bit/64bit
SLES 9 32bit/64bit
SLES 10 32bit/64bit
Solaris 10 64bit
Supported file systems
The following table lists supported file systems (left column). The supported
NetBackup backup types (0-File, 1-FullVM, 2-Mapped FullVM) are shown for
each policy type and file system combination. The backup types are described
following the table.
Table 1-7
Supported file systems
NetBackup policy type
File system
MS-Windows-NT
FlashBackup-Windows
NTFS
0-File
1-FullVM
0-File
0-File
1-FullVM
2-Mapped FullVM
0-File
1-FullVM
Not supported
1-FullVM
Notes
(Windows NT)
NTFS
(Windows 2000
and later)
FAT
All features of
NetBackup for
VMware are
supported.
(all Windows
versions)
Other
(Any VMware
guest OS)
Policy backup
selections must
specify
ALL_LOCAL_DRIVES
Description of backup types:
■
Symantec TechNote
0-File: For backup of individual files. Cannot back up Windows system files
or VMware virtual disk files.
29
VMware logging
11/21/07
■
1-FullVM: For backup of the entire virtual machine only.
■
2-Mapped FullVM: For backup of the entire virtual machine. Allows restore
of the entire virtual machine or of individual files.
More information is available on these backup types.
See “Virtual Machine Backup parameters” on page 14.
Note: Up-to-date support information on NetBackup for VMware is available.
See the Veritas NetBackup 6.5 Snapshot Client Configuration Guide, at:
http://entsupport.symantec.com/docs/288300.
VMware logging
For log messages about VMware backup or restore, see the following NetBackup
legacy log folders.
Table 1-8
The NetBackup logs that contain VMware messages
Log folder
Contains
Resides on
install_path\NetBackup\logs\bpfis Messages on snapshot creation VMware backup proxy server
and backup
install_path\NetBackup\logs\bpcd
Messages on snapshot creation VMware backup proxy server
and backup
install_path\NetBackup\logs\bprd
Messages on restore
NetBackup master server
Note: These log folders must already exist in order for logging to occur. If these
folders do not exist, create them.
More detail is available on snapshot logs, logging levels, and the required
folders.
See the NetBackup 6.5 Snapshot Client Administrator’s Guide.
A broader discussion of NetBackup logging is available.
See the NetBackup Troubleshooting Guide.
Symantec TechNote
11/21/07
Troubleshooting
Troubleshooting
This section covers a variety of topics.
VMware environment—important!
Unsupported equipment can cause many problems. Ensure that your VMware
environment (including ESX servers, SAN devices, and backup proxy) conforms
to all requirements and recommendations that are spelled out by VMware. For
instance, if VMware does not support your HBAs, device drivers, or guest
operating systems, NetBackup cannot work.
For support details, see VMware documentation at the VMware support site (for
example, the VMware compatibility guides).
Change the browsing time-out for virtual machine discovery
You can adjust the time available for browsing for virtual machines in the
NetBackup policy.
To change the browsing time-out value
1
In the NetBackup Administration Console, click on the Policies node.
2
From the main menu, click View > Options, then click the Policies tab.
3
Adjust the VMware connect timeout value.
4
Click OK.
■
Make sure you have the latest version of the VMware Consolidated Backup
(VCB) on the VMware backup proxy server.
■
NetBackup for VMware does not work with the VMware NetBackup
Integration Module (VNIM). Note the following!
Notes and tips
■
Symantec TechNote
■
If VNIM is installed, do not configure a NetBackup for VMware policy
(with the VMware snapshot method) to call any scripts that use VNIM.
Such a policy results in a backup that fails.
■
Do not run any NetBackup for VMware policy at the same time as a
script-based policy that calls VNIM. If the two policies require access to
the same virtual machine, a conflict may result and the backup may
fail.
For incremental backups, make sure the VMware backup proxy server is
correctly configured. Otherwise, NetBackup performs only full backups.
31
Troubleshooting
11/21/07
See “Configure incremental backups for VMware” on page 10.
■
You cannot restore Windows operating system files from a file-level backup
of a virtual machine. You can restore standard data files only. A restore of
the operating system requires a full virtual machine backup.
■
Make sure the VMware Tools are installed on each virtual machine.
Otherwise, communication problems and other problems can result.
■
You cannot restore VMware files onto the virtual machine itself, except
under certain conditions.
See “VMware restore procedures: overview” on page 20.
Backup and restore problems
NetBackup cannot obtain the volume ID of a drive
If NetBackup cannot obtain the volume ID of a drive that is listed in the policy’s
Backup Selections list, note: none of the drives that are listed in the policy for
the client are backed up. The backup fails with NetBackup status code 156. Try
one of the following:
■
Use the ALL_LOCAL_DRIVES directive in the Backup Selections list,
instead of listing individual drives.
■
A drive letter that is specified in the policy’s Backup Selections list may
be incorrect, or the drive may be down. Update the client’s include list
(Exceptions to exclude list), and fix or remove the drive entry in the
Backup Selections list.
The backup fails with status 156
A backup failure with status 156, “snapshot error encountered,” can occur for
several reasons:
■
You cannot run more than one backup per virtual machine at a time. If you
start a second backup of the same virtual machine while the first backup is
active, the second job fails with a status 156.
■
If the VMware backup proxy server has insufficient space in which to mount
a snapshot of the virtual machine, the backup fails with status 156. The
bpfis log on the VMware backup proxy server may contain a message such as
the following:
13:35:37.859 [5536.1276] <2> onlfi_vfms_logf:
[2007-09-21
13:35:34.578 'vcbMounter' 2204 error] Error: Failed to export
the disk: There is not enough space on the disk
Free up additional space on the proxy server and rerun the backup.
■
If the VMware backup proxy server does not have access to the VMware
datastore (VMware virtual disk files), the backup fails with status 156. The
Symantec TechNote
11/21/07
Troubleshooting
bpfis log on the VMware backup proxy server may contain messages such as
the following:
13:08:24.356 [5060.4416] <2> onlfi_vfms_logf:
[2007-10-22
13:08:17.247 'App' 556 trivia] Attempting to open
LVID:46c1a2b1-4adde8ca-19bc-00188b32734b/46c1a2af-7a2af812-2023
-00188b32734b/1.
13:08:24.356 [5060.4416] <2> onlfi_vfms_logf:
[2007-10-22
13:08:17.247 'App' 556 error] No path to device
LVID:46c1a2b1-4adde8ca-19bc-00188b32734b/46c1a2af-7a2af812-2023
-00188b32734b/1 found.
13:08:24.356 [5060.4416] <2> onlfi_vfms_logf:
13:08:17.247 'BlockList' 556 error]
[2007-10-22
13:08:24.356 [5060.4416] <2> onlfi_vfms_logf:
[2007-10-22
13:08:17.466 'BlockList' 556 info] Closing connection
steeple:902:Administrator
13:08:24.356 [5060.4416] <2> onlfi_vfms_logf:
[2007-10-22
13:08:17.466 'blocklist' 556 verbose] Shutting down VMDB
service...
13:08:24.356 [5060.4416] <2> onlfi_vfms_logf:
[2007-10-22
13:08:17.466 'blocklist' 556 verbose] Unregistering callback...
13:08:24.356 [5060.4416] <2> onlfi_vfms_logf:
13:08:17.466 'blocklist' 556 verbose] ...done
[2007-10-22
13:08:24.356 [5060.4416] <2> onlfi_vfms_logf:
[2007-10-22
13:08:17.466 'vcbMounter' 556 error] Error: Failed to open the
disk: One LUN could not be opened
■
A disk was mounted on a virtual machine but the disk is assigned to the
virtual machine in raw mode. As a result, the attempt to create a snapshot of
the virtual machine fails. The bpfis log on the VMware backup proxy server
may contain a message such as the following:
12:46:27.175 [2636.5628] <2> onlfi_vfms_logf:
[2007-10-17
12:46:27.019 'App'
1976 verbose] Fault Msg: "Virtual machine is configured to use a
device that prevents the snapshot operation: Device '' is a raw
disk, which is not supported."
Symantec TechNote
33
Terminology
11/21/07
Terminology
For further explanations of VMware terminology, refer to your VMware
documentation.
datastore
In NetBackup for VMware, the datastore is a disk that contains the virtual
machines files. The datastore must be available to both the VMware backup
proxy server and the ESX server, by means of Fibre Channel or iSCSI.
guest OS
An operating system that runs on a virtual machine.
hypervisor
A software virtualization layer that lets different operating systems run
simultaneously on the same physical machine.
sync driver
Flushes OS buffers (Windows only) before VMware snapshots are initiated. The
sync driver is installed by means of VMware Tools.
VCB
See VMware Consolidated Backup.
virtual machine
An execution environment that is created by the computer hardware and the
hypervisor. The resulting virtualized environment allows different operating
systems to run simultaneously on the same physical machine.
vmdk file
In a VMware ESX server, one or more vmdk files make up the disk image or
virtual drive in a virtual machine. The .vmdk files contain the operating system,
applications, and data in the virtual machine.
An off-host backup server in a NetBackup for VMware environment. The
VMware backup proxy server performs backups on behalf of virtual machines.
At a minimum, the VMware VCB software and a NetBackup client must be
installed on the backup proxy.
Symantec TechNote
11/21/07
Terminology
VMware Consolidated Backup
An off-host backup application programming interface (API) created by
VMware. Designed to off load backups from the ESX server.
VMware Tools
Installed inside each VMware virtual machine. Enhances the virtual machine
performance and adds backup-related functionality.
Symantec TechNote
35
Terminology
11/21/07
Symantec TechNote

How to configure and use NetBackup 6.5.1 for VMware Symantec TechNote 293350

Transcription

Similar documents

dcVAST — Symantec Appliance / NetBackup Media Server

esxRanger … Hot Backup

(C) Engine - Automotriz En Video

esxRanger datasheet 2005.ai

Storage and Information Management Brief VERITAS and Network

VMware Professional Services: Business Continuity and Disaster Recovery Practice

How to Install and Use SSS\Progman with Carsoft or INPA interface

CheCk ServiCeS