Professional Documents
Culture Documents
11/21/07
2 How to configure and use NetBackup 6.5.1 for VMware Symantec Corporation
NetBackup for VMware: introduction 11/21/07
Virtual machine
Virtual machines provide complete guest operating systems on virtualized
hardware. In a NetBackup policy, a virtual machine is configured as a NetBackup
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.
Environment diagram
The hardware components for NetBackup for VMware are shown in Figure 1-1.
NetBackup
master server
1
LAN / WAN
2 5 NetBackup
storage unit 3
SAN
(disk or tape)
4
VMware backup proxy server VMware virtual disk files VMware ESX server
acting as both NetBackup (datastore) runs virtual machines
media server and Snapshot must be available on SAN or iSCSI
Client off-host client to both VMware backup proxy
server and VMware ESX server
NetBackup
master server
LAN / WAN
VMware
NetBackup VirtualCenter
storage unit
(disk or tape)
SAN
License requirements
NetBackup for VMware requires the NetBackup Snapshot Client license, which
is included in the NetBackup Enterprise Client license.
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.
3 Install VMware Tools on the virtual machines that you plan to back up.
Notes:
■ 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
NetBackup tasks
Table 1-2 lists the NetBackup configuration tasks that are described later in this
chapter and in other NetBackup documentation, as indicated.
3 Set NetBackup access credentials for the VMware VirtualCenter (if any)
or VMware ESX servers.
See “Add NetBackup credentials for VMware” on page 9.
Configure NetBackup
This section describes the NetBackup configuration procedures.
6 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.
Click Perform
snapshot backups
and
Perform off-host
backup.
■ 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.
Note: For Windows virtual machines, the mount point must be a local drive,
not network mounted.
ESX server or
VirtualCenter
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.
■ 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.
Backup Selections entry Virtual Machine What is backed up What can be restored
Backup parameter
Individual folders and files 0-File Specified folders and files Individual folders and files
only, excluding Windows
system files
Individual drives 0-File All data files and folders in Individual folders and files
For example: E:\ specified drives, excluding
Windows system files
ALL_LOCAL_DRIVES 0-File All data files and folders on all Individual folders and files
directive local virtual machine drives,
excluding Windows system
files
Individual drives 0-File Individual drives as raw devices. Individual folders and files,
or entire drive (not including
For example: \\.\E:
operating system or VMware
virtual disk files)
ALL_LOCAL_DRIVES 0-File All individual drives in virtual Individual folders and files,
directive machine as raw devices. or entire drives (not including
operating system or VMware
virtual disk files)
ALL_LOCAL_DRIVES 1-FullVM VMware virtual disk files. Backup Entire virtual machine only
directive is “raw partition” type.
ALL_LOCAL_DRIVES 2-Mapped FullVM VMware virtual disk files. Backup Entire virtual machine or
directive is “raw partition” type. individual folders and files
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.
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.
■ An MS-Windows-NT policy.
■ A FlashBackup-Windows policy with a Virtual Machine Backup parameter
set to either 0-File or 2-Mapped FullVM.
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.
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
■ Virtual machine server:
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.
■ 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.
8 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
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/
■ 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.
Support matrices
This section describes support information for NetBackup for VMware.
Windows NT 4.0
RHEL 2.1
RHEL 3.0
RHEL 4 32bit/64bit
SLES 9 32bit/64bit
SLES 10 32bit/64bit
Solaris 10 64bit
VMware logging
For log messages about VMware backup or restore, see the following NetBackup
legacy log folders.
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.
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).
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.
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.
VMware Tools
Installed inside each VMware virtual machine. Enhances the virtual machine
performance and adds backup-related functionality.