netbackup 7x in virtual environments october 2 2014 update

8/10/2019 NetBackup 7x in Virtual Environments October 2 2014 Update

1/46

Support for NetBackup 7.xin virtual environments

IntroductionThis tech note (TECH127089) describes support for NetBackup in virtual

environments.

Symantec Corporation is committed to serving the virtualization and hypervisor

market by offering our customers the benefits of NetBackup Enterprise data

protection solutions. We welcome your feedback. Please contact your Symantec

account representative for assistance.

http://www.netbackup.com

Recent changes to this tech noteThis tech note was last published on October 2, 2014.

Table 1 Recent changes to this tech note

Publication date for this changeDescription of changes

October 2, 2014Added a vCloud Director column to the Supported VMware

versions table.SeeSupported VMware versions and backup host operating

systemson page 17.

October 2, 2014Updated BMR support details for VMware, and added a new

section on BMR Direct VM Conversion support.

SeeBMR Direct VM Conversion support on page 14.
http://www.netbackup.com/http://www.netbackup.com/


2/46

Table 1 Recent changes to this tech note(continued)


September 9, 2014Updated BMR support details for Hyper-V.

SeeBMR client support details for Hyper-Von page 11.

August 6, 2014Update to list of supported VMware versions and backup hosts

for NetBackup 7.6.0.3.

SeeSupported VMware versions and backup host operating

systemson page 17.

June 10, 2014NetBackup 7.6.0.2 adds support for Linux disks partitioned with

the GUID Partition Table.

SeeSupported file systems for VMware on page 24.

May 22, 2014Noted support of Windows 2012 R2 as a VMware guest OS with

file-level recovery.

SeeSupported VMware guest operating systemson page 22.

May 22, 2014Updated BMR support in NetBackup 7.6.0.2.

SeeBare Metal Restoreon page 9.

May 22 , 2014New topic on Hyper-V restore failure with VMs on a Cluster

Shared Volume (CSV).

SeeHyper-V restore may fail if the VM was created on a CSV

and the CSV is a reparse point on the destination drive

on page 45.

May 21, 2014New topic on VMware hotadd backup issues caused by Windows

disk signature collisions.

SeeHotadd backup issues caused by Windows disk signature

collisionson page 31.

May 21, 2014Minor update to list of supported VMware versions and backup

hosts.


systemson page 17.

May 7, 2014Updated list of supported VMware versions and backup hosts for

NetBackup 7.6.0.2.


systemson page 17.

2Support for NetBackup 7.x in virtual environmentsRecent changes to this tech note


3/46

Table 1 Recent changes to this tech note(continued)


May 7, 2014Updated list of supported Hyper-V versions for NetBackup 7.6.0.2.

See Supported Hyper-V components and versions on page 37.

SeeSupport for Hyper-V on Windows 2012on page 38.

May 7, 2014New topic on online backups and Hyper-V integration services.

SeeHyper-V online backups require proper version of Hyper-V

integration services in the VMon page 41.

May 7, 2014NetBackup appliance 2.6.0.2 adds support for SAN dynamic

multipathing.

SeeNetBackup for VMware support for SAN multipathing witha Linux backup hoston page 21.

December 17, 2013Updates throughout this tech note for NetBackup 7.6 (7.6.0.1).

October 15, 2013Update to list of supported VMware versions for NetBackup

7.5.0.6.


systemson page 17.

October 15, 2013For Linux backup hosts: A 7.5.0.1 or later master server is

required if the master server is not on the backup host.


systemson page 17.

October 15, 2013Update to list of supported file systems for the VMware policy for

NetBackup 7.5.0.6.

SeeSupported file systems for VMware on page 24.

General NetBackup support in virtual environments

Ideally, every NetBackup configuration supported in a traditional physicalenvironment would also be supported in any virtual environment without qualification.

While that is our mission, it is not always possible.

Therefore, the purpose of this section is to:

Clarify differences between NetBackup support in physical vs. virtual

environments.

Describe general guidelines for support in virtual environments.

3Support for NetBackup 7.x in virtual environmentsGeneral NetBackup support in virtual environments


4/46

Describe the impact of a virtual environment on specific NetBackup components,

such as clients, servers, and other options.

Provide notes on virtualization technologies and links to related tech notes.

Terminology

The following terms are used in this document.

Table 2 Terminology

DefinitionTerm

The operating system that is installed in a virtual machine.Guest OS

The software platform running on a physical server that hosts one or

more virtual machines.

Hypervisor

The emulation of a single physical machine within a hypervisor.Virtual machine

General guidelines for support

Symantec provides support for NetBackup within a virtual environment. For the

purpose of this document, a virtual environment is defined as: any on-site, off-site,

or public cloud IaaS virtualization solution where NetBackup can be installed into

a supported guest operating system.

NetBackup has an open support policy for virtualization platforms, as follows:

NetBackup is qualified on physical configurations.

If the same configuration can be virtualized, it is supported without explicit

qualification on the virtualization platform (unless otherwise noted in this

document).

The published NetBackup software and hardware compatibility listings reflect this

support policy. The listings are available here:

http://www.symantec.com/docs/TECH59978

Note the following limitations of NetBackup support within a virtual environment:

Support of hardware or software as published in the NetBackup compatibility

listings is subject to mutual support by the hardware/software vendor and the

hypervisor vendor.

Specifically:

The hardware/software vendors must support their products within the

hypervisor.

http://www.symantec.com/docs/TECH59978http://www.symantec.com/docs/TECH59978


5/46

The hypervisor vendor must support use of the hardware/software product

within the hypervisor.

Such hardware/software products include operating systems, cluster servers,

peripherals, drivers, patches, databases, applications, and so forth.

When operating NetBackup within a virtual machine, the hypervisor may

introduce conditions (such as contention for shared resources or other

interruptions) that were not present during standard qualification. Additional

tuning may be required to address any resulting delay, retry, or timeout

conditions. Contact the hypervisor vendor first for tuning suggestions.

NetBackup may experience lesser performance within the hypervisor. It may

be necessary to increase system resources to address a performance issue.

Using a hypervisor vendors interface to suspend, resume, or otherwise disrupt

execution of NetBackup is not supported. The impact upon NetBackup operations

and data is unknown. Only NetBackup management interfaces are supported

for NetBackup control.

Using NetBackup within VM high availability, replication, or transfer solutions is

supported but not qualified by Symantec. Examples of such solutions are vSphere

HA, host-based replication, vMotion, and Storage vMotion (but not limited to

VMware). As a virtualized application, NetBackup is unaware of being deployed

within a VM, and support for such operations is provided by the hypervisor

vendor.

In the event of a support escalation, NetBackup technical support will make

every reasonable attempt to resolve the issue within the virtual environment. Inrare circumstances, Symantec reserves the right to qualify, limit, exclude, or

discontinue implicit support for a NetBackup configuration due to unforeseen

incompatibilities within the hypervisor environment. In the rare case of a

NetBackup failure due to a hypervisor operation, it may be necessary to recover

from a backup.

Virtual master server

The NetBackup master server is supported within a virtual machine, under the

limitations described in the General guidelines for support.

Refer to the following NetBackup Operating System compatibility document for a

list of supported NetBackup 7.x master server platforms:




6/46

Virtual media server

The NetBackup media server is supported within a virtual machine, under the

limitations described in the General guidelines for support.

The following storage units are supported within a virtual machine:

Basic Disk

AdvancedDisk

Media Manager (tape storage units)

For details on the supported virtualization technologies, see Table 3.

Media Server Deduplication Pool (MSDP)

For MSDP requirements, see the NetBackup Deduplication Guide and the

following deduplication tech note:


PureDisk Deduplication Pool (PDDO) including the Symantec NetBackup 5000

Series Appliances.

OpenStorage, where the Data Interface is Ethernet.

For details on OpenStorage device compatibility, see the NetBackup 7.x

Hardware Compatibility List:


For a list of supported NetBackup 7.x media server platforms, see the NetBackup

7 Operating System Compatibility List:


Table 3 Virtualization technologies supported for Media Manager storage

units

NotesTape supportVirtualization technology

The following document contains details on

NetBackup support for IBM virtual machines:


Shared with driver, or

dedicated hardware path.

IBM virtual machines

The following document contains details onNetBackup support for HP-UX Integrity virtual

machines and vPars:


Shared with driver, ordedicated hardware path.

HP-UX Integrity virtual machinesand vPars

The following document contains details on

NetBackup support for Hitachi virtual LPARs:


Dedicated or shared

hardware path.

Hitachi Virtage LPARs

http://www.symantec.com/docs/TECH77575http://www.symantec.com/docs/TECH76495http://www.symantec.com/docs/TECH76648http://www.symantec.com/docs/TECH162738http://www.symantec.com/docs/TECH162739http://www.symantec.com/docs/TECH130529http://www.symantec.com/docs/TECH130529http://www.symantec.com/docs/TECH162739http://www.symantec.com/docs/TECH162738http://www.symantec.com/docs/TECH76648http://www.symantec.com/docs/TECH76495http://www.symantec.com/docs/TECH77575


7/46

Table 3 Virtualization technologies supported for Media Manager storage

units(continued)

NotesTape supportVirtualization technology

The following documents contain details on

NetBackup support for LDOMs and zones:


(for NetBackup 7)


(for NetBackup 6.5)

See links under Notes.Oracle Solaris Logical Domains

(LDOMs) and zones

Hard partitioning physically segments a server, by taking a single large server and

separating it into distinct systems. Each separated system acts as a physicallyindependent, self-contained server, with its own CPUs, operating system, separate

boot area, memory, input/output subsystem, and network resources.

Virtual clients and database agents

NetBackup operating system clients and database agents are supported within a

virtual machine, under the limitations described in the General guidelines for

support.

Refer to the following NetBackup 7 Database Agent compatibility document for a

list of supported NetBackup database agent platforms:

Support for Red Hat Enterprise Virtualization

NetBackup can be used to protect virtual machines within Red Hat Enterprise

Virtualization (RHEV) deployments and the RHEV Manager. For more information,

see the following Red Hat Reference Architecture document:

https://access.redhat.com/articles/340293

Virtual PureDisk Remote Office Edition

The PureDisk operating system (PDOS) and PureDisk Remote Office Edition are

supported within a virtual machine, under the limitations described in the General

guidelines for support.

Note:

See the following for a list of supported NetBackup PureDisk Remote Office

Edition platforms:


http://www.symantec.com/docs/TECH162994http://www.symantec.com/docs/TECH65627https://access.redhat.com/articles/340293http://www.symantec.com/docs/TECH60158http://www.symantec.com/docs/TECH60158https://access.redhat.com/articles/340293http://www.symantec.com/docs/TECH65627http://www.symantec.com/docs/TECH162994


8/46

For information on a VMware virtual machine that has PureDisk Remote Office

Edition pre-installed, refer to the Symantec NetBackup PureDisk Virtual Appliance

Guide.

Virtual Snapshot Client

This section describes the use of Snapshot Client when installed in a virtual machine.

Note however that NetBackup has special backup agents for VMware and Hyper-V

that do not require installation of a client on virtual machines. See the NetBackup

for VMware and NetBackup for Hyper-V sections in this document.

Support for VMware

NetBackup Snapshot Client can be used within a VMware virtual machine in

conjunction with Raw Device Mapping (RDM) to provide off-host backup capabilities.

Because of RDM limitations, other backup methods are not supported at this time.

The following section contains more information:

SeeSupport for VMware raw device mapping (RDM)on page 34.

Consult the following NetBackup 7.x Snapshot Client compatibility listing to determine

which off-host combinations are supported:


See also the following section for support information on NetBackup for VMware:

SeeNetBackup for VMware Compatibilityon page 17.

Support for Hyper-V

NetBackup Snapshot Client can be used within a Hyper-V virtual machine in

conjunction with Hyper-V pass-through disks to provide off-host backup of snapshots.

The following section contains more information:

SeeSupport for Hyper-V pass-through diskson page 44.

Consult the following NetBackup 7.x Snapshot Client compatibility listing to determine

which off-host combinations are supported:


See also the following section for support information on NetBackup for Hyper-V:

SeeNetBackup for Hyper-V Compatibilityon page 37.

http://www.symantec.com/docs/TECH126901http://www.symantec.com/docs/TECH126901http://www.symantec.com/docs/TECH126901http://www.symantec.com/docs/TECH126901


9/46

Support for Citrix XenServer

NetBackup supports backup and recovery of virtual machines in a Citrix XenServer

virtualized environment, by means of a Snapshot Client off-host backup method.

For a description of this backup approach, see the following document:

http://support.citrix.com/article/CTX122191

Bare Metal Restore

Due to the inherent physical dependencies in the Bare Metal Restore (BMR) option,

BMR is not covered by the General guidelines for support section. Instead, BMR

is explicitly qualified and supported within specific virtual environments, as listed

below.

Note:For general BMR support details such as the minimum NetBackup level

required for the BMR client OS, see the Bare Metal Restore section of the NetBackup

7.x Operating System Compatibility List:


VMware: the BMR master server and boot server are supported on a guest OS.

The BMR client is also supported on a guest OS.

SeeBMR client support details for VMwareon page 10.

SeeBMR Direct VM Conversion supporton page 14.

Windows Hyper-V: the BMR master server and boot server are supported on a

Hyper-V guest OS. The BMR client is also supported on a guest OS.

SeeBMR client support details for Hyper-Von page 11.

Xen Hypervisor: the BMR master server and boot server are supported on a

guest OS. The BMR client is also supported on a guest OS.

SeeBMR client support details for Xenon page 11.

Solaris Logical Domains (LDOMs): the BMR master server is supported in the

LDOM Control Domain and on guest domains. The BMR client is supported on

an LDOM guest domain that has UFS attached.

SeeBMR client support details for Oracle VM Server for SPARCon page 12.

IBM PowerVM: the BMR master server, boot server, and BMR client are

supported on a guest OS.

SeeBMR client support details for IBM PowerVMon page 13.

http://support.citrix.com/article/CTX122191http://www.symantec.com/docs/TECH76648http://www.symantec.com/docs/TECH76648http://support.citrix.com/article/CTX122191


10/46

BMR client support details for VMware

NetBackup 7.x supports BMR protection for guest operating systems running on

VMware ESX 4.1, 5.0, 5.1, and 5.5 servers. The following table describes NetBackup

7.x support for the BMR client on VMware.

Table 4 VMware guest operating systems supported for BMR client

BMR client supported as

boot server running in

guest OS?

Type of restore supportedGuest OS

Yesvirtual-to-virtual self restore

virtual-to-virtual DSR restore

virtual-to-physical DSR restore

physical-to-virtual DSR restore

Windows 2003 (32-bit and 64-bit)

Windows 2008 SP1, SP2 (32-bit

and 64-bit)

Windows 2008 R2 (64-bit)

Windows 2012 (64-bit)




Windows 8.1 (32-bit and 64-bit)


virtual-to-virtual DDR restore

Support for physical-to-virtual DSR and

virtual-to-physical DSR is subject to the conditions

specified in the following BMR UNIX DSR tech note:


Red Hat Enterprise Linux 4, 5, 6

(64-bit)

Oracle Enterprise Linux 4, 5, 6

(64-bit)

SUSE Linux Enterprise Server 10

SP3, SP4


GA and SP1, SP2, SP3







Solaris 10 Update 8, 9, 10, 11

(64-bit)

The following section contains information on BMR Direct VM conversion for

VMware:

SeeBMR Direct VM Conversion supporton page 14.



11/46

BMR client support details for Hyper-V

NetBackup 7.x supports BMR protection for guest operating systems running on

Windows 2008 and 2008 R2 Hyper-V servers.

The following table describes NetBackup 7.x support for the BMR client on Hyper-V.

Table 5 Hyper-V guest operating systems supported for BMR client



guest OS?




virtual-to-physical DSR restorephysical-to-virtual DSR restore



and 64-bit)


Windows 2012 (64-bit)








(64-bit)

Oracle Enterprise Linux 4, 5, 6

(64-bit)


SP3, SP4

SUSE Linux Enterprise Server 11GA, SP1, SP2, SP3



Solaris 10 Update 8 (64-bit)

BMR client support details for Xen

The following table describes NetBackup 7.x support for the BMR client on Xen.



12/46

Table 6 Xen guest operating systems supported for BMR client



guest OS?





physical-to-virtual DSR restore



and 64-bit)








NetBackup 7.6.0.2 adds the following:

Support for Red Hat Enterprise Linux 6.

Support for the xvda disk format on Red Hat

Enterprise Linux 6.


(64-bit)

Oracle Enterprise Linux 4, 5 (64-bit)


GA, SP1



Solaris 10 Update 8 (64-bit)

BMR client support details for Oracle VM Server for SPARC

The following table describes NetBackup support for Oracle VM Server and BMR

clients on Solaris 10 LDOM.



13/46

Table 7 BMR client support details for Oracle VM Server for SPARC (Solaris

10 LDOM)

Support detailsNetBackup release

You can restore BMR clients configured on Solaris 10 LDOM as follows:

You can restore a BMR client that is installed on an LDOM guest domain that has

UFS attached.

An LDOM guest domain that has UFS attached can be restored on another LDOM

guest domain that is in the same primary domain. Note however that you can restore

the backup of an LDOM guest domain only on a new LDOM guest domain that BMR

has not already backed up


guest domain in the DR site.

NetBackup 7.1

You can back up and restore BMR clients configured on Solaris 10 LDOM as follows:

You can back up and restore a BMR client that is installed on a LDOM guest domain

that has UFS attached.


guest domain that is in the same primary domain. Note however that you can restore

the backup of an LDOM guest domain only on a new LDOM guest domain that BMR

has not already backed up


guest domain in the DR site.

NetBackup 7.5

Please refer to the following tech note to import the original LDOM guest domainconfiguration:

Transferring Bare Metal Restore (BMR) data to an AIR/DR site

http://www.symantec.com/docs/HOWTO65776

BMR client support details for IBM PowerVM

The following table describes NetBackup 7.x support for the BMR client on IBM

PowerVM (on IBM AIX guest operating systems).

http://www.symantec.com/docs/HOWTO65776http://www.symantec.com/docs/HOWTO65776


14/46

Table 8 IBM AIX guest operating systems supported for BMR client



guest OS?





physical-to-virtual DSR restore is subject to the

conditions specified in the following BMR UNIX DSR

tech note:


AIX 6.1 TL6

AIX 7.1 TL0

BMR Direct VM Conversion support

BMR Direct VM Conversion support has been explicitly qualified within specific

virtualization environments as listed in this section.

Note:BMR Direct VM Conversion support starts at NetBackup 7.6.

For general BMR support details such as the minimum NetBackup level required

for the BMR client OS, see the Bare Metal Restore section of the NetBackup 7.x

Operating System Compatibility List:


BMR Direct VM conversion support into VMware virtual environments

The following table describes NetBackup 7.x support for BMR Direct VM conversion

into VMware.

Table 9 NetBackup 7.x support for BMR Direct VM conversion into VMware

CommentsBMR Client OS VersionHypervisor Type and

Version

Windows 2003, 2008, 2008

R2, and Windows 7

VMware ESX/vCenter 4.1

Windows 2003, 2008, 2008

R2, and Windows 7


Windows 2003, 2008, 2008

R2, 2012, and Windows 7

and 8




15/46

Table 9 NetBackup 7.x support for BMR Direct VM conversion into VMware

(continued)

CommentsBMR Client OS VersionHypervisor Type and

Version

Support starts at NetBackup

7.6.0.2.

Windows 2003, 2008, 2008

R2, 2012, and Windows 7

and 8


Note: NetBackup 7.6.0.2 Windows x86-32 clients cannot be used as Virtual Instance

Converters (VICs) for BMR physical to virtual conversions. NetBackup 7.6.0.2 uses

VMware VDDK 5.5 libraries, which do not support the Windows x86-32 bit platform.

Note: BMR Direct VM Conversion does not support conversion for a Windows client

that has Storage Spaces configured.

Other NetBackup optionsThe following NetBackup options or features are supported in a virtual machine.

NetBackup OpsCenter (formerly NOM and VAR.)

Symantec professional servicesSymantec professional services can be hired for qualification of a specific

configuration of NetBackup within a hypervisor. Contact your Symantec account

representative for assistance, or go to the following:

http://www.symantec.com/services

Links to related information

See the following Symantec documents for support and configuration information.

http://www.symantec.com/serviceshttp://www.symantec.com/services


16/46

Table 10 Symantec documents related to virtualization

Description and linkDocument

Contains the entire listing for all NetBackup Server,NetBackup Enterprise Server, and NetBackup PureDisk

Remote Office Edition compatibility lists available for 6.x and

7.x. Includes compatibility for hardware, operating systems,

and agents and options, such as NDMP, databases,

snapshots, and desktop/laptop.


Main listing of NetBackupcompatibility lists

Describes how to configure and use NetBackup 7.1 for

VMware to protect VMware virtual machines.

http://www.symantec.com/docs/DOC3663

NetBackup 7.1 for VMware

Administrator's Guide











Describes how to use the NetBackup plug-in in vSphere

Client to monitor virtual machine backups and recover virtual

machines.


NetBackup 7.6 Plug-in for

VMware vCenter Guide


Hyper-V to protect Hyper-V virtual machines.


NetBackup 7.1 for Hyper-V



Hyper-V to protect VMware virtual machines.


NetBackup 7.5 for Hyper-V


Describes how to configure and use NetBackup 7.6 forHyper-V to protect VMware virtual machines.


NetBackup 7.6 for Hyper-VAdministrator's Guide

Describes a method of Windows virtual machine backup

using NetBackup and the Citrix XenServer VSS Provider,

which is supported by both Symantec and Citrix:

http://support.citrix.com/article/CTX122191

Citrix XenServer: Virtual

Machine Backup

http://www.symantec.com/docs/TECH59978http://www.symantec.com/docs/DOC3663http://www.symantec.com/docs/DOC5162http://www.symantec.com/docs/DOC6461http://www.symantec.com/docs/DOC6288http://www.symantec.com/docs/DOC3662http://www.symantec.com/docs/DOC5161http://www.symantec.com/docs/DOC6460http://support.citrix.com/article/CTX122191http://support.citrix.com/article/CTX122191http://www.symantec.com/docs/DOC6460http://www.symantec.com/docs/DOC5161http://www.symantec.com/docs/DOC3662http://www.symantec.com/docs/DOC6288http://www.symantec.com/docs/DOC6461http://www.symantec.com/docs/DOC5162http://www.symantec.com/docs/DOC3663http://www.symantec.com/docs/TECH59978


17/46

NetBackup for VMware CompatibilityThe following topics describe NetBackup for VMware support. NetBackup for

VMware protects VMware virtual machines by integrating with VMware vStorageAPIs for Data Protection.

Note the following about VMware updates:

VMware updates to vSphere 4 and 5 are supported, unless otherwise noted.

vCloud Director 5.1.x and 5.5.x updates are supported, unless otherwise noted.

Supported VMware versions and backup host operating systems

NetBackup 7.x for VMware includes vStorage, and automatically uses the vStorage

APIs.

Table 11contains the following information:

Supported VDDK versions are provided with links to the VDDK release notes

in the middle column. Use those links to find the supported VMware versions.

Supported vCloud Director versions.

Supported operating systems for the backup or restore host (proxy).

Note:A NetBackup client must be installed on the backup host and on any restore

host and optional backup media server.

Note:NetBackup 7.6 dropped support for 32-bit backup/restore hosts and backup

media servers.

1Support for NetBackup 7.x in virtual environmentsNetBackup for VMware Compatibility


18/46

Table 11 Supported VMware versions and backup host operating systems

Supported operating systems for

backup/restore host and backup

media server

vCloud

Director

version

VDDK version supports

these VMware versions

***IMPORTANT!*** Click

the VDDK release note

links in this row for the

official list of supported

vCenter and ESXi

versions

VDDK

version

NetBackup version

All 64 bit only:

Windows Server 2012

Windows Server 2008 and 2008 R2

Windows Server 2003 R2

Red Hat Enterprise Linux (RHEL) 5.9,

6.2, 6.3, 6.4

SUSE Linux Enterprise Server (SLES)

10.4, 11.1, 11.2

5.1, 5.5For supported vCenter and

ESXi versions, see the

VMware VDDK 5.5.1 release

notes

5.5 U17.6.0.3

All 64 bit only:

Windows Server 2012




6.2, 6.3, 6.4


10.4, 11.1, 11.2

5.1, 5.5For supported vCenter and



notes

5.57.6.0.1 with EEB3318872

7.6.0.2

All 64 bit only:

Windows Server 2012



Red Hat Enterprise Linux (RHEL) 6.1


11 SP2

5.1For supported vCenter and


VMwareVDDK 5.1 release

notes

For information on VDDK 5.1U1, see theVDDK 5.1.1

release notes

5.1 U17.6.0.1 (7.6)

https://www.vmware.com/support/developer/vddk/vddk-551-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-551-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-550-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-550-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-511-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-511-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-511-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-511-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-550-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-550-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-551-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-551-releasenotes.html


19/46


(continued)


backup/restore host and backupmedia server

vCloud

Directorversion







vCenter and ESXi

versions

VDDK

version

NetBackup version

Windows Server 2012 (64-bit only)

Windows Server 2008 R2 (64-bit only)


Red Hat Enterprise Linux (RHEL) 6.1


11 SP2

For supported vCenter and



notes

For information on VDDK 5.1

U1, see theVDDK 5.1.1

release notes

5.1 U17.5.0.6 with EEB3263410

7.5.0.7



5.4, 5.5


10 and 11

If the master server is on a separate

host (not on the Linux backup host),

the master server must be at

NetBackup 7.5.0.1 or later.




notes

For information on VDDK 5.0

U1, see theVDDK 5.0 U1

release notes

5.0 U17.5.0.5

7.5.0.6



10 and 11

If the master server is on a separate

host (not on the Linux backup host),

the master server must be atNetBackup 7.5.0.1 or later.

See NetBackup appliance as backup

hoston page 21.




notes

5.07.5.0.3 (added support for

Linux backup host)

7.5.0.4

Windows Server 2008 and 2008 R2For supported vCenter and



notes

5.07.1.0.3 or later in 7.1.x line

7.5 and 7.5.0.1

https://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-511-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-511-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-501-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-501-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-501-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-501-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-511-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-511-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.html


20/46


(continued)


backup/restore host and backupmedia server

vCloud

Directorversion







vCenter and ESXi

versions

VDDK

version

NetBackup version






notes

1.2.17.1 to 7.1.0.2






notes

1.1.17.0

7.0.1

Also note the following:

For vSphere 4.1, NetBackup 7.0.1 does not support the NBDSSL transport type.

NetBackup 7.0.1 does not support hotadd backup or restore with ESX/ESXi 4.1.

VMware version information can also be obtained from the VMware ProductInteroperability Matrix, and is subject to change by VMware. For the latest

information, see the following:

http://www.vmware.com/resources/compatibility/sim/interop_matrix.php

Unless otherwise stated, NetBackup for VMware supports VMware updates.

NetBackup supports installation of the backup host in a virtual machine (VMware

"hotadd"). The guest operating systems that NetBackup supports for hotadd are

the same as the above.

Support for ESX and ESXiNetBackup for VMware supports both ESX and ESXi servers. In this document,

any reference to ESX also refers to ESXi. Note however that VMware no longer

supports ESX in the latest versions of vSphere.

Because NetBackup for VMware leverages vStorage APIs for Data Protection,

there are no NetBackup support restrictions for ESX or ESXi servers.

https://www.vmware.com/support/developer/vddk/VDDK-1.2.1-Relnotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-1.2.1-Relnotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-1.1.1-Relnotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-1.1.1-Relnotes.htmlhttp://www.vmware.com/resources/compatibility/sim/interop_matrix.phphttp://www.vmware.com/resources/compatibility/sim/interop_matrix.phphttps://www.vmware.com/support/developer/vddk/VDDK-1.1.1-Relnotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-1.1.1-Relnotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-1.2.1-Relnotes.htmlhttps://www.vmware.com/support/developer/vddk/VDDK-1.2.1-Relnotes.html


21/46

NetBackup appliance as backup host

Starting with the NetBackup appliance version 2.5, the appliance is supported as

the VMware backup host. A separate Windows host is not required for the backup

host (but see the following notes).

For further information on the appliance as backup host, see the NetBackup for

VMware Administrator's Guide 7.5.0.x:


Note the following:

The appliance must be version 2.5 or later. If the master server is on a separate

host (not on the backup host), the master server must use NetBackup 7.5.0.1

or later.

On the host that runs the NetBackup Administration Console or the Backup,Archive, and Restore interface, NetBackup must be at 7.5.0.1 or later.

You must use the VMware policy type. The FlashBackup-Windows policy type

is not supported.

A Windows backup host is required for VMware Instant Recovery.

The appliance does not support iSCSI connections.

NetBackup for VMware support for SAN multipathing with aLinux backup host

NetBackup for VMware on Windows supports dynamic multipathing (DMP) between

the vSphere ESXi storage and the NetBackup for VMware agent (Windows backup

host). DMP can provide SAN I/O high-availability and improved backup throughput.

The following describes NetBackup for VMware support for DMP in a SAN

environment with a Linux backup host:

The NetBackup appliance (starting at 2.6.0.2) supports SAN DMP for VMware

backups. I/O is redirected through the volume manager DMP Node.

For more information, refer to the NetBackup Appliance Administrator's Guide

for version 2.6.0.2.

Otherwise, for a Linux backup host that is not a NetBackup appliance, NetBackupfor VMware is unable to support DMP. This limitation results from incompatibilities

between the Linux operating system, VMware vStorage APIs for Data Protection,

and vendor-specific DMP solutions.

As a result, NetBackup for VMware cannot support DMP with a Linux backup

host (non-appliance) that is on either of the following platforms:

NetBackup for VMware on SLES

http://www.symantec.com/docs/DOC5605http://www.symantec.com/docs/DOC5605


22/46

NetBackup for VMware on RHEL

Note the following:

This issue does not affect NetBackup support for VMwares Native Multipathing

(NMP). NMP is multipathing between the ESXi host and storage.

This issue does not affect NetBackup for VMware on Windows backup hosts.

The Windows OS has integrated multipathing support. The following Microsoft

guide contains more information:

http://microsoft.com/mpio

Supported VMware guest operating systems

NetBackup for VMware supports virtual machine backup and recovery on all guest

operating systems supported by VMware. To check VMware support for a particularoperating system, consult the VMware Compatibility Guide:

http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software

Note also that NetBackup for VMware supports file-level recovery from a virtual

machine backup on the following guest operating systems.

Table 12 VMware guest operating systems supported for file-level recovery

NotesVMware guest OS

Requires NetBackup 7.5.0.6 or later.Windows 8 (32bit/64bit)

Windows 7 (32bit/64bit)

Windows Vista (32bit/64bit)

Windows XP 64 bit requires VMware Tools

3.0.1 (not supported with 3.0.2).

Windows XP (32bit/64bit)

Requires NetBackup 7.5.0.6 or later.

Same restrictions as for Windows 2012.

Windows 2012 R2 (64bit)

http://microsoft.com/mpiohttp://www.vmware.com/resources/compatibility/search.php?deviceCategory=softwarehttp://www.vmware.com/resources/compatibility/search.php?deviceCategory=softwarehttp://microsoft.com/mpio


23/46

Table 12 VMware guest operating systems supported for file-level recovery

(continued)

NotesVMware guest OS

Requires NetBackup 7.5.0.6 or later.

Note the following:

Does not support the ReFS file system.

You can back up and restore the entire VM,

but files cannot be individually restored to

a ReFS file system.

Note:File-level recovery is supported for

NTFS and FAT files, but NTFS and FAT

files cannot be restored to ReFS.

Does not support files that use Microsoftdata deduplication.


Supported for vStorage but not for VCB.Windows 2008 R2 (64bit)


Windows 2003 R2 (32bit/64bit)


Windows 2000 (32bit)

RHEL 4 (32bit*/64bit)


Requires NetBackup 7.5 or later.RHEL 6 (32bit*/64bit)

SUSE 10 (32bit*/64bit)


* NetBackup 7.x no longer includes Linux 32-bit clients. Consequently, file-level

restore directly to the Linux 32-bit virtual machine is not possible. As an alternative,

you can perform a file-level restore to network shared storage. Recovery of theentire virtual machine is supported for both 32-bit and 64-bit Linux virtual machines.

For guest operating systems not listed in the table, you can recover the entire virtual

machine but not individual files.



24/46

Supported file systems for VMware

NetBackup 7.5 introduced a policy type called VMware. The NetBackupVMware

policy type presents all backup options on the VMwaretab.

Note: On the VMware tab, the olderFull VM backup and Mapped full VM backup

options in NetBackup 7.1 are combined in a single option: Enable file recovery

from VM backup. Selecting this option is the equivalent of the Mapped full VM

backupoption in NetBackup 7.1.

The following tables list the supported file systems, by policy type.

Table 13 Supported file systems for the VMware policy type (requires

NetBackup 7.5 master server or later)

Notes"Enable file recovery from

VM backup" option

supported

File system

Planned for a future release.ReFS (Windows 2012)

Requires NetBackup 7.5.0.6 or later.YesNTFS (Windows 2012 with Data

Deduplication disabled)

Requires NetBackup 7.5.0.6 or later.NoNTFS (Windows 2012 with Data

Deduplication enabled)

NoNTFS (Windows NT)

Supports these partition tables:

Master Boot Record (MBR)

Extended Boot Record (EBR)

GUID Partition Table (GPT)

Logical Disk Manager - dynamic

(LDM)

Note:Availability of the partition table

type depends on the particular Windows

OS. Check your Microsoft documentation.

YesNTFS (Windows 2000 and later)

YesFAT (all Windows versions)



25/46

Table 13 Supported file systems for the VMware policy type (requires

NetBackup 7.5 master server or later)(continued)

Notes"Enable file recovery from

VM backup" optionsupported

File system

Support for the GUID Partition Table

(GPT) starts at NetBackup 7.6.0.2.

LVM2 volume manager is also supported.

Support for ext4 starts at RHEL 5.4 and

SUSE 11.

Yesext2, ext3, ext4

NoOther (any VMware guest OS)

Table 14 Supported file systems for the FlashBackup-Windows policy type

(through NetBackup 7.6.x)

NotesSupported backup typesFile system

Planned for a future releaseReFS (Windows 2012)

Requires NetBackup 7.5.0.6 or later.Full backup with file level

incremental, Full VM backup,

Mapped full VM backup.

NTFS (Windows 2012 with Data

Deduplication disabled)

Requires NetBackup 7.5.0.6 or later.Full backup with file level

incremental,Full VM backup

NTFS (Windows 2012 with Data

Deduplication enabled)

Supports these partition tables:

Master Boot Record (MBR)

Extended Boot Record (EBR)

GUID Partition Table (GPT)

Logical Disk Manager - dynamic

(LDM)

Note:Availability of the partition table

type depends on the particular Windows

OS. Check your Microsoft documentation.

Full backup with file level

incremental, Full VM backup,

Mapped full VM backup.

NTFS (Windows 2000 and later)

Full VM backup.NTFS (Windows NT)

Mapped full VM backup is supported on

Windows 2000 and later.

Full VM backup,Mapped full

VM backup.

FAT (all Windows versions)



26/46

Table 14 Supported file systems for the FlashBackup-Windows policy type

(through NetBackup 7.6.x)(continued)

NotesSupported backup typesFile system

Support for the GUID Partition Table

(GPT) starts at NetBackup 7.6.0.2.

LVM2 volume manager is also supported.

ext4 requires NetBackup 7.5.


SUSE 11.

Full VM backup,Mapped full

VM backup

ext2, ext3, ext4

Full VM backup.Other (Any VMware guest OS)

Note: The policy backup selections must specify ALL_LOCAL_DRIVES. However,

if a NetBackup client is installed in the virtual machine, you have the option of

backing up individual drives.

NetBackup feature support for vSphere and vCloud Director

The following table describes NetBackup support for vSphere and vCloud Director

on a feature-by-feature basis.

Table 15 NetBackup support for vSphere and vCloud Director

vCloud DirectorvSphereNetBackup feature

YesYesNetBackup for VMware, including VMware

Intelligent Policy and all forms of recovery (VM,

file, database, granular).

YesYesAccelerator for VMware

YesYesReplication Director for VMware

NoYesNetBackup Plug-in for vCenter

NoYesInstant Recovery for VMware

YesYesVM recovery command (nbrestorevm)

SeeGuidelines for using NetBackup with vCloud Directoron page 27.

SeeNetBackup support for automatic virtual machine selectionon page 32.



27/46


28/46

To recover virtual machines provisioned by vCloud Director (NetBackup 7.5)

1 Use the NetBackup Backup, Archive, and Restore interface to restore the virtualmachine to a vCenter server accessible to the vCloud Director infrastructure.

On the Recovery Destination dialog, underRecover virtual machine to, select

Alternate location. Do not restore the virtual machine to its original location.

vCloud cannot import a virtual machine from that location.

Note:Restore the virtual machine to a datastore that was configured for the

provider vDC on which the organization vDC is based.

For complete instructions on how to restore virtual machines to an alternate

location, see theNetBackup for VMware Administrator's Guide.

2 Log into vCloud Director as the vCloud administrator.

3 Go to your Organization vDC and import the virtual machine as a new vCloudvApp from theImport from vSphereicon.

SelectMove VM. (Do not select Copy VM: that option leaves a copy of the

virtual machine in the source vSphere.)

Note: Do not try to overwrite the original virtual machine. To replace the corrupt

virtual machine, use the following steps.

4 Make a note of the name and network settings of the corrupt virtual machineand delete it from the vApp.

5 Move the recovered virtual machine from the newly created vApp to the originalvApp.

6 Set the appropriate virtual machine name and network details in the MoveVirtual Machine wizard.

7 You can now delete the newly created vApp.

vSphere support in NetBackup 7.5.0.5 and earlier

Support for vSphere 5.1 in NetBackup 7.5.0.5

NetBackup 7.5.0.5 supports backup and recovery of vSphere 5.1.



29/46

Note: vSphere 5.1 adds guest operating system support for Windows 8 and Windows

Server 2012. In 7.5.0.5, NetBackup supports recovery of the entire virtual machine

for those guest operating systems. File-level and application-level recovery will be

supported in a future release.


Support for vSphere 5.1 in NetBackup 7.5.0.4

NetBackup 7.5.0.4 supports backup and recovery of vSphere 5.1.

The following issues will be resolved in a future release:

VM hardware version 9

In vSphere 5.1, the latest virtual machine hardware version is 9. NetBackup

7.5.0.4 does not recognize version 9, as follows:

When restoring to vCenter 5.1, virtual machines with hardware version 9 are

restored with hardware version 8. To restore to version 9, use a VMware

interface after recovery to upgrade the virtual machine to version 9.

When restoring to vCenter 5.1, virtual machines with hardware version 7 or

earlier are restored with hardware version 8 if you do not select the

NetBackupRetain original hardware versionoption. To restore to version

9, use a VMware interface after recovery to upgrade the virtual machine to

version 9.

When building a query for automatic selection of virtual machines in the

NetBackup VMware policy, the virtual machine version "vmx-09" is not

recognized. As a workaround, use a query that specifies vmx-08, such as

VMVersion Greater "vmx-08".

For a description of VMware version numbers, see the section on virtual machine

compatibility in the following VMware document:

Whats New in VMware vSphere 5.1 Platform

The VMware document explains how to set a default virtual machine compatibility

level (for a hardware version other than 9).

Windows 8 and Windows Server 2012 guest operating systems

vSphere 5.1 adds guest operating system support for Windows 8 and Windows

Server 2012. At this time, NetBackup supports recovery of the entire virtual

machine for those guest operating systems. File-level and application-level

recovery will be supported in a future release.


http://www.vmware.com/files/pdf/techpaper/Whats-New-VMware-vSphere-51-Platform-Technical-Whitepaper.pdfhttp://www.vmware.com/files/pdf/techpaper/Whats-New-VMware-vSphere-51-Platform-Technical-Whitepaper.pdf


30/46

Support for vSphere 5.0 in NetBackup 7.1.0.3 and later

NetBackup 7.1.0.3 adds support for vSphere 5.0, including support for datastore

clusters. This feature also includes support for Linux vCenter 5.0.

For a vSphere 5 environment, you must upgrade your VMware backup hosts

(NetBackup clients) to 7.1.0.3 or later.

NetBackup 7.0.1 for VMware supports vSphere 4.1 but not theNBDSSL transfer type

NetBackup 7.0.1 adds support for VMware vSphere 4.1 but does not support the

NBDSSL transfer type.

You can select NBDSSL as the transfer type in the NetBackup 7.0.1 graphical

interfaces. However, support for NBDSSL varies, as follows:

Backup of a virtual machine that is earlier than VMware 4.1 is supported with

the NBDSSL transfer type.

Backup of a 4.1 or later virtual machine is not supported with the NBDSSL

transfer type (the backup fails).

Restore of a virtual machine (any VMware level) with the NBDSSL transfer type

is not supported (the restore fails).

Note: For full support of vSphere 4.1 (including the NBDSSL transfer type), you

should upgrade to NetBackup 7.1.

NetBackup 7.0 and 7.0.1: Hotadd backup or restore fails if thebackup or recovery host (virtual machine) is hosted on ESX/ESXi4.1

A backup or restore using the hotadd transfer type fails if the ESX/ESXi server is

4.1. (Hotadd transfer is used when the VMware backup host or restore host is

installed in a virtual machine.) VMware has reported this problem in SR#

1557258751.

The hotadd backup or restore fails with NetBackup status code 23. The detailedstatus log includes a message similar to the following:

ERR -Error opening the snapshot disks using given

transport mode: Status 23

As a workaround, use a backup or restore host that resides on an ESX/ESXi server

at 4.0 or earlier.

In NetBackup 7.1, hotadd backups and restores with ESX/ESXi 4.1 work correctly.



31/46

Hotadd backup issues caused by Windows disk signature collisionsFor the hotadd transport mode with a backup host on Windows 2008 server or

earlier, a Windows disk signature collision may cause the following problems:

At NetBackup 7.0 and later: A backup using the hotadd transport mode may

change a VMs disk signature in the backup image if multiple VMs are backed

up simultaneously and some of their disks have the same Windows disk

signature. This problem can occur in any of the following cases:

One or more of the VMs in the backup is a clone of another VM that is backed

up simultaneously by the same backup host.

VMs that are backed up simultaneously are linked clones that share disks

with the same parent.

A VM in the backup is a clone of the backup host.

In any of these cases, file-level recovery from the VM's file systems may not

succeed.

In addition: If the guest OS of the backed up VM is Windows Server 2008, the

recovered virtual machine may fail to start. In that case, the disk signature issue

on the recovered VM must be fixed. See the following Symantec article:


At 7.6.0.1 and later: If the backup was made with the Accelerator feature, a VM

disk signature collision may cause a hotadd backup to fail with status 84, media

write error.

Workaround: Use a different transport mode (not hotadd), or avoid simultaneous

backup of the VMs. If a VM in the backup is a clone of the backup host, use a

different backup host that is not a clone of the VM.

For further information on this issue, see Windows proxy HotAdd can cause differing

disk signatures in the following VMware article:

https://www.vmware.com/support/developer/vddk/vddk-550-releasenotes.html

Note:These issues do not apply if the backup host is Windows Server 2008 R2 or

later.

Backup of the ESX host by means of the ESX console is notsupported

NetBackup 6.x supported the backup of the ESX host by means of a NetBackup

Linux client installed on the ESX host. Since VMware is discontinuing this capability,

NetBackup 7.x does not support backup of the ESX host in this manner.

http://www.symantec.com/docs/TECH200480https://www.vmware.com/support/developer/vddk/vddk-550-releasenotes.htmlhttps://www.vmware.com/support/developer/vddk/vddk-550-releasenotes.htmlhttp://www.symantec.com/docs/TECH200480


32/46

To back up VMware virtual machines, you can use either of the following:

NetBackup for VMware, as described in theNetBackup for VMware

Administrators Guide.

As an alternative, you can install NetBackup clients in the virtual machines.

Replication Director for virtual machines

NetBackup 7.6 supports Replication Director for protecting virtual machines in a

snapshot and replication environment.

Note the following about Replication Director:

Supports vCenter version 4.0 and later. Earlier vCenter versions are not

supported.

Supports NFS datastores only. Does not support replication solutions that are

deployed with RDM or VMFS datastores.

To protect virtual machines on unsupported datastores, do one of the following:

Use the NetBackup policy typeVMwarebut without Replication Director.

Use Replication Director and install a NetBackup client in each virtual

machine.

With a client in the virtual machine, you can use Replication Director to

protect each virtual machine as though it is a physical computer, with a policy

type other thanVMware.

NetBackup support for automatic virtual machine selection

NetBackup 7.1 and later can automatically select virtual machines for backup by

means of rules configured in the policy. The NetBackup policy Clients tab includes

a Query Builder for creating the rules.

Note the following requirements:

NetBackup 7.1 or later is required for the master server, media server, and the

VMware backup host.

Automatic virtual machine selection is not supported in VCB environments.vStorage is required.

In NetBackup 7.6, automatic virtual machine selection is required for backups

in vCloud Director or for Replication Director for VMware.

To function correctly, certain Field keywords in the Query Builder require vSphere

4.0 or later or vCloud Director 5.1 or later.

See the following tables.



33/46

Table 17 Minimum vCloud Director version for Query Builder keywords added

in NetBackup 7.6

Minimum version of vCloud Director

required

Field keywords in Query Builder

vCloud Director 5.1vCDCatalog

vCDIsExpired

vCDIsvAppTemplate

vCDOrg

vCDOrgvDC

vCDServer

vCDvApp

Table 18 Minimum vSphere version for Query Builder keywords added in

NetBackup 7.5

Minimum version of vSphere requiredField keywords in Query Builder

vSphere 4.0DatastoreFolder

DatastoreNFSHost

DatastoreNFSPath

DatastoreType

NetworkFolder

VMXDatastoreFolder

VMXDatastoreNFSHost

VMXDatastoreNFSPath

VMXDatastoreType

vSphere 5.0DatastoreCluster

All other keywords have the same vSphere requirements as NetBackup for vStorage.

See Supported VMware versions and backup host operating systems on page 17.

Support for configuring thin provisioned virtual disks on restoredvirtual machines

NetBackup 7.1 includes a restore option called Create thin provisioned disks.

In NetBackup 7.5 and later, this option is named Thin provisioning.



34/46

This option configures the restored virtual machine with thin provisioned disks, even

if the original virtual machine used thick provisioning at the time of the backup. The

ability to create thin provisioned disks depends on the release level of the VMware

server on which the virtual machine is restored, as described in the following table.

Table 19 NetBackup support for creation of thin provisioned virtual disks in

restored virtual machine

Can configure restored virtual machine to

have thin provisioned virtual disks

Release level of destination server

for restore

YesvCenter server 4.0 or later with any

version of ESX

YesVirtualCenter server 2.5 with ESX 3.5

YesVirtualCenter server 2.5 with ESX 3.0.2

YesESX 4.0 or later (*standalone)

YesESX 3.5 (*standalone)

No. Thin provisioning requires vStorage, which

does not work with standalone ESX servers older

than 3.5.

ESX server earlier than 3.5

(*standalone)

*standalone means the ESX server is not managed by a vCenter or VirtualCenter

server.

See Supported VMware versions and backup host operating systems on page 17.

Support for VMware raw device mapping (RDM)

Raw device mapping allows a non-VMDK disk to be accessed by the guest OS. To

back up a raw mapped device (RDM), you must install NetBackup client software

in the virtual machine. Any device that NetBackup supports in a physical (non

hypervisor) environment is supported for RDM, provided that the device vendor

supports the device in a virtual environment.

For environments that require VCB: with versions of VCB that are earlier than 1.5,a NetBackup backup of a virtual machine fails if the virtual machine uses raw device

mapping. At VCB 1.5, NetBackup can back up the virtual machine successfully,

but the raw mapped device is not included in the backup.

For more information on using NetBackup to back up a disk in RDM mode, refer to

the Backup of VMware raw devices (RDM) appendix of the NetBackup for VMware




35/46

Support for VMware VCB and vCenter Converter

VMware Consolidated Backup (VCB) is not supported by VMware and is no longer

supported by NetBackup as of 7.6. Instead of VCB, Symantec strongly recommends

the use of vSphere APIs for Data Protection (VADP). VADP is available in vSphere

4.0 and later and NetBackup 7.1 and later.

Table 20 NetBackup 7.x support for VCB

NoteVCB RestoreVCB BackupBackup host

(NetBackup client)

NoNoNetBackup 7.6

Compatible with

NetBackup 7.6 Server

YesNoNetBackup 7.5

Compatible with

NetBackup 7.5 and

7.6 Server

YesYesNetBackup 7.1

NetBackup 7.1 attempts to use VMware Consolidated Backup (VCB) and Converter

when operating with the following:

ESX Server versions earlier than 3.5, or

VirtualCenter Server versions earlier than 2.5

Table 21 NetBackup 7.1 support for VMware VCB

NotesLatest VMware version

supported

Earliest VMware version

supported

Both ESX and ESXi are

supported

VCB 1.5 U2

ESX 4.1

vCenter Server 4.1

Converter standalone 4.3

VCB 1.5 U1

ESX 3.5 U5

vCenter Server 2.5 U6

Converter standalone 3.0.2

U1

Note: VMware version information was obtained from the following VMware

document:

http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf

http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdfhttp://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf


36/46


37/46

Windows client can be installed in the Windows virtual machine to perform file-level

backup.

NetBackup VCB-based file-level backups may failDue to an error identified by VMware, NetBackup VCB file-level backups may fail

in the following case:

The guest OS is not installed on the virtual machine's first virtual hard disk.

The NetBackup Virtual machine backup option isFile level snapshot using

VCBorFull backup with file level incremental.

The backup job fails with status 156 (snapshot creation failed), and the following

error may appear in the NetBackup bpfis log:

'vcbMounter' 636 error] Error: Cannot query guest OS information.The mount directory path is invalid.

Note:The NetBackup Release Notes for 7.0.1 incorrectly state that this issue is

limited to the Windows 2008 R2 or Windows 7 guest operating systems. The issue

can occur with any operating system.

For more details on this issue from the VMware perspective, refer to the following

VMware VCB documentation:

http://www.vmware.com/support/vsphere4/doc/vsp_vcb_15_u1_rel_notes.html

http://www.vmware.com/support/vsphere4/doc/vsp_vcb_15_u2_rel_notes.html

NetBackup for Hyper-V CompatibilityThis section provides support information on NetBackup for Hyper-V. NetBackup

for Hyper-V provides snapshot-based backup of virtual machines that run on

Windows Hyper-V Server.

Note: Before configuring NetBackup for Hyper-V, make sure that you have Windows

and the Hyper-V role installed correctly. Refer to your Windows and Hyper-V

documentation and Hyper-V release notes for requirements and installation

instructions.

Supported Hyper-V components and versions

NetBackup for Hyper-V supports the following environments.

3Support for NetBackup 7.x in virtual environmentsNetBackup for Hyper-V Compatibility
http://www.vmware.com/support/vsphere4/doc/vsp_vcb_15_u1_rel_notes.htmlhttp://www.vmware.com/support/vsphere4/doc/vsp_vcb_15_u2_rel_notes.htmlhttp://www.vmware.com/support/vsphere4/doc/vsp_vcb_15_u2_rel_notes.htmlhttp://www.vmware.com/support/vsphere4/doc/vsp_vcb_15_u1_rel_notes.html


38/46

Table 22 Components supported for Hyper-V

What is supportedComponents

Windows Server 2008, 2008 R2, 2012, 2012 R2.

Support for Windows Server 2012 begins at NetBackup 7.5.0.6.

Support for Windows Server 2012 R2 begins at NetBackup 7.6.0.2.


Hyper-V

Windows Server 2008, 2008 R2, 2012, 2012 R2.

Support for Windows Server 2012 begins at NetBackup 7.5.0.6.


Failover Cluster

NetBackup for Hyper-V has an open support policy for VSS

providers, as described in the NetBackup Snapshot Client

Compatibility Listing:


NetBackup for Hyper-V is supported on the Windows versions noted

in this table. Any vendors that support VSS snapshot providers on

those versions are supported for NetBackup for Hyper-V.

VSS providers

NetBackup for Hyper-V has an open support policy for CSV-based

virtual machine backups. Any vendors that support CSV-based

virtual machine backup on the Windows versions in this table are

supported for NetBackup for Hyper-V.

CSV-based virtual

machine backups

Support for Hyper-V on Windows 2012

Table 23 describes NetBackup support for Hyper-V on Windows 2012 and Windows

2012 R2.



39/46

Table 23 Support for Hyper-V on Windows 2012 and Windows 2012 R2

Notes and limitationsNetBackup version

Adds support for Microsoft Hyper-V Server 2012. NetBackup 7.5.0.6 and later supportWindows 8 as a guest OS.

NetBackup limitations on Hyper-V Server 2012:

VMs must reside on the NTFS file system (ReFS is not supported).

Block-level incremental backup is not supported.

File-level recovery from a Hyper-V backup is not supported in any of the following cases:

The files inside a VM reside in a Resilient File System (ReFS) volume.

The files inside a VM reside in an NTFS deduplicated volume.

The VM is composed of VHDX file(s).

File-level recovery is supported when the files inside the VM reside in an NTFS volume

and the VM is composed of VHD files.

7.5.0.6* and 7.5.0.7*

Adds support for Microsoft Hyper-V Server 2012 R2. Also adds support for VHDX files.

NetBackup limitations on Hyper-V Server 2012 and Hyper-V Server 2012 R2:

VMs must reside on the NTFS file system (ReFS is not supported).

Block-level incremental backup is not supported.

File-level recovery from a Hyper-V backup is not supported in any of the following cases:

The files inside a VM reside in a Resilient File System (ReFS) volume.

The files inside a VM reside in an NTFS deduplicated volume.

NetBackup 7.6.0.2: The files are in a VM (any guest OS) that resides on a Hyper-V

2012 R2 server with the Windows Server 2012 R2 update of April 2014.

For more information on the update, see the following Microsoft article:

http://support.microsoft.com/kb/2919355

Note: This file-level recovery issue with the Windows Server 2012 R2 update of April

2014 is fixed in NetBackup 7.6.0.3. For NetBackup 7.6.0.2, it is fixed in the following

EEB: NB_7.6.0.2_ET3500731_1.zip. For more information on that EEB, see the

following Symantec article:


Apart from the above restrictions, file-level recovery is supported when the files inside the

VM reside in an NTFS volume and the VM is composed of VHD or VHDX files.

7.6.0.2* and later

*Backup of virtual machines within Cluster Shared Volumes (CSV) is supported. In

Hyper-V Server 2008 R2, CSV has a limitation that requires serialized backups. In

Hyper-V Server 2012, CSV supports concurrent backups without that limitation.

Consequently, the CSV timeout setting in the NetBackup Hyper-V policy is only

used in Hyper-V Server 2008 R2 deployments.

http://support.microsoft.com/kb/2919355http://www.symantec.com/docs/TECH217531http://www.symantec.com/docs/TECH217531http://support.microsoft.com/kb/2919355


40/46

Supported Hyper-V guest operating systems

NetBackup for Hyper-V supports virtual machine backup and recovery on all guest

operating systems supported by Hyper-V. For a list of operating systems that

Hyper-V supports, consult the following:

http://support.microsoft.com/kb/954958

Note also that NetBackup for Hyper-V supports file-level recovery from a virtual

machine backup on the following operating systems.

Table 24 Hyper-V guest operating systems supported for file-level recovery

NotesHyper-V guest OS

Support for Windows 8 begins at NetBackup

7.5.0.6.Support has the same limitations as for

Windows 2012.

See Support for Hyper-V on Windows 2012

on page 38.

Windows 8

Support for Windows 7 begins at NetBackup

7.0.1.

Windows 7

Windows Vista (32bit/64bit)

Windows XP (32bit/64bit)

Support for Windows 2012 R2 begins at

NetBackup 7.6.0.2.


on page 38.


Support for Windows 2012 begins at

NetBackup 7.5.0.6.


on page 38.




Windows 2003 R2 (32bit/64bit)



http://support.microsoft.com/kb/954958http://support.microsoft.com/kb/954958


41/46

Table 24 Hyper-V guest operating systems supported for file-level recovery

(continued)

NotesHyper-V guest OS

ext2, ext3 file systems, LVM2 volume

manager


ext2, ext3, ext4 file systems, LVM2 volume

manager.


requires NetBackup 7.5.


Same as RHEL 5.

RHEL 6 requires NetBackup 7.5.


Same as RHEL 4.SUSE 10 (32bit*/64bit)

Same as RHEL 5.

Support for ext4 starts at SUSE 11 and

requires NetBackup 7.5.


* NetBackup 7.x no longer includes Linux 32-bit clients. Consequently, file-level

restore directly to the Linux 32-bit virtual machine is not possible. As an alternative,

you can perform a file-level restore to network shared storage. Recovery of the

entire virtual machine is supported for both 32-bit and 64-bit Linux virtual machines.

Hyper-V online backups require proper version of Hyper-V integrationservices in the VM

To allow online backups of Hyper-V virtual machines, the proper version of the

Hyper-V integration services must be installed in the virtual machines. Without the

proper version, online backup may not succeed (NetBackup status 4201). The

following may appear in the job's detailed status log:

2/17/2014 1:39:17 PM - Critical bpbrm(pid=7492) from client RHEL_60_GP

FTL - snapshot processing failed, status 4201

2/17/2014 1:39:17 PM - Critical bpbrm(pid=7492) from client RHEL_60_GP

FTL - snapshot creation failed, status 4201

Table 25describes the required versions of the integration services.



42/46

Table 25 Hyper-V integration services required in the VM

Notes and requirements on the integration services in the VMGuest OS

Required minimum versions of integration services:

Hyper-V server 2012 R2: Integration services 6.3.9600.16384.

Hyper-V server 2012: The integration services built in to the Windows 2012 guest OS.

For other guest operating systems, see "Software requirements (for supported guest

operating systems)" in the following Microsoft TechNet article:

http://technet.microsoft.com/library/hh831531

Hyper-V server 2008 R2: Integration services 6.1.7600.16385

Hyper-V server 2008: Integration services 6.0.6001.18016.

To upgrade the integration services, see the TechNet article "Install the Hyper-V Role and

Configure a Virtual Machine:"

http://technet.microsoft.com/en-US/library/hh846766

Windows 2008, 2008R2, 2012, 2012 R2

Required minimum version of Linux integration services:

Hyper-V server 2012 R2: Linux integration services 3.5.

Hyper-V server 2012: Microsoft does not support online backup of Linux VMs on Windows

2012 Hyper-V hosts.

Hyper-V server 2008 / 2008 R2: 2008 and 2008 R2 do not support Linux integration services

in the VM.

Note:Linux integration services is not built in to the RHEL VM. You may have to download

and install the services in the VM.

For assistance downloading and installing Linux integration services, see the TechNet "Linux

Integration Services 3.5 Announcement:"

http://blogs.technet.com/b/virtualization/archive/2014/01/02/linux-integration-services-3-5-announcement.aspx

For further information on Linux 3.5 integration services, see the TechNet article "Linux

Integration Services Version 3.5 for Hyper-V:"

http://www.microsoft.com/en-us/download/details.aspx?id=41554

RHEL, SUSE

http://technet.microsoft.com/library/hh831531http://technet.microsoft.com/en-US/library/hh846766http://blogs.technet.com/b/virtualization/archive/2014/01/02/linux-integration-services-3-5-announcement.aspxhttp://www.microsoft.com/en-us/download/details.aspx?id=41554http://www.microsoft.com/en-us/download/details.aspx?id=41554http://blogs.technet.com/b/virtualization/archive/2014/01/02/linux-integration-services-3-5-announcement.aspxhttp://technet.microsoft.com/en-US/library/hh846766http://technet.microsoft.com/library/hh831531


43/46


44/46

To determine the current integration services version in a Linux VM

In the VM, enter the following:

/sbin/modinfo hv_vmbus

Example output:

filename: /lib/modules/2.6.32-71.el6.x86_64/extra/microsoft-

hyper-v/hv_vmbus.ko

version: 3.5

license: GPL

srcversion: ACE0AA64B58744D00E54C12

alias: acpi*:VMBus:*

alias: acpi*:VMBUS:*

depends:

vermagic: 2.6.32-71.el6.x86_64 SMP mod_unload modversions

For assistance with downloading and installing the service, see the following

Microsoft article:

Linux Integration Services 3.5 Announcement

Support for Hyper-V pass-through disks

To back up Hyper-V pass through disks, you must install NetBackup client software

in the virtual machine. You can perform the backup with or without the features of

Snapshot Client.

Any device that NetBackup supports in a physical (non hypervisor) environment is

supported for pass through disks, provided that the device vendor supports the

device in a virtual environment. For a hardware snapshot of an array configured as

a pass-through device, only off-host alternate client backup is supported (requires

Snapshot Client).

Note: NetBackup does not support point in time rollback for arrays that are configured

as pass-through devices.

For more information on using NetBackup to back up Hyper-V pass through disks,

refer to the Hyper-V pass-through disks appendix of theNetBackup for Hyper-V


Use of a volume GUID path requires NetBackup 7.0.1 or later

NetBackup 7.0.1 adds support for volume GUID paths. The following is an example

of a volume GUID path:

http://blogs.technet.com/b/virtualization/archive/2014/01/02/linux-integration-services-3-5-announcement.aspxhttp://blogs.technet.com/b/virtualization/archive/2014/01/02/linux-integration-services-3-5-announcement.aspx


45/46


46/46

netbackup 7x in virtual environments october 2 2014 update

Documents