How to configure Veritas NetBackup (tm) for a SnapVault backup for NetApp Network Appliances

  • Modified Date:
  • Article ID:000030237


NetBackup 6.5.x and earlier only.

How to configure Veritas NetBackup (tm) for a SnapVault backup for NetApp Network Appliances


Installation and Configuration Requirement:
Both Veritas NetBackup (tm) for Network Data Management Protocol (NDMP) and NetBackup Advanced Client software must be installed and licensed on the NetBackup server. The NetBackup client used to perform the backup should have NetBackup Advanced Client installed. The NetBackup for NDMP license should be purchased for each NDMP host. The NetBackup server must also have a network-attached storage (NAS) SnapVault Options license.

The NAS host must support NDMP V4 and NDMP V4 snapshot extension.

Note: While the minimum version of OnTap 6.5.1 is required for NAS Snapshot (both Network Appliance filer & Network Appliance NearStore hardware), the minimum requirement for the OnTap version for a secondary filer to be used as SnapVault disk backup is 7.1

NetBackup must have access to the host where snapshots will be created. This should be configured and checked  with the tpconfig -add and tpautoconf -verify commands. Consult the Veritas NetBackup (tm) 6.0 Advanced Client System Administrator's Guide (found below, in the Related Documents section) for more details about these two commands and their usage.

Note: For SnapVault to work, the data should be common internet file system (CIFS) or network file system (NFS), mounted respectively on a Windows or UNIX system that will be used as the client in the policy. Windows (32 and 64 bits) and Solaris clients only are supported at this release.

Policy type for a Windows system where the data is CIFS mounted is MS-Windows-NT, for UNIX client where the data is NFS mounted - Standard, and for Oracle backup - Oracle. NDMP policy type is not supported in the current version of NetBackup 6.0.

Version, Licensing & Configuration options requirement for Network Appliances:

Do not put both primary and secondary licenses on the same machine. It is permissible to have both SnapMirror and SnapVault licenses on the same filer simultaneously, if it is necessary to use SnapMirror. SnapMirror is not required for SnapVault.

Below is a configuration example from a working environment with NetBackup 6.0:
In this example, test10 is the primary filer where the data resides, and test11 is the secondary filer that is used as the SnapVault disk storage unit.

A. OnTap version

host name "test10"
 os type "NetApp"
 os version "NetApp Release 6.5.3H1P4"

host name "test11"
 os type "NetApp"
 os version "NetApp Release 7.1RC3"

The OnTap version can be seen by executing the following command on the NetApp Filer:

filer1> sysconfig

The NDMP protocol version can be checked by executing the following command on the NetApp Filer:

filer1> ndmpd version

The above information is also displayed when the NetBackup command tpautoconf -verify is executed on the NetBackup server.

B. Licensing information:

On the primary filer:
SnapRestore, SnapVault_primary

Note: SnapRestore is a separately licensed feature of NetApp, and is required only if this feature is used to restore the data.


                    cifs XXXXXXX
                     nfs YYYYYYY
          snapmirror ZZZZZZZZ
  snaprestore site AAAAAAA expires 17 Jan 2006      
 sv_ontap_pri site BBBBBBB expires 10 Jan 2006 <<<<< primary license
      sv_ontap_sec not licensed

On the Secondary filer (SnapVault system)


                     cifs site ZZZZZZZZ expires 10 Jan 2006
                   iscsi site CCCCCCCC expires 10 Jan 2006
                      nfs site LLLLLLLL expires 10 Jan 2006
      sv_ontap_sec site BBBBBBB expires 10 Jan 2006 <<<<<< secondary license
                sv_unix_pri not licensed

Licenses can be added and displayed using the following commands on the NetApp Filer:

filer1>license add <code>

C. Settings / Options:

On the primary filer:

ndmpd on
snapvault.enable on
snapvault.access: host=sv_secondary


ndmpd.enable                 on        
snapmirror.enable            off        
snapvault.access             host=all   (or just all without host=)
snapvault.enable             on        

On the Secondary filer:

snapvault.enable on
snapvault.access: host=sv_primary1, sv_primary2


snapmirror.enable            off              
snapvault.access             host=all   (or just all without host=)
snapvault.enable             on    

Options parameters can be viewed by executing the following commands:

filer1>  options snapvault
filer1>  options ndmpd
or just:
filer1>  options

Options parameters can be set by using the following commands:

filer1>  options snapvault.enable on
filer1>  options snapvault.access all

Policy Configuration for NetBackup:

Note that only the required part of the policy is shown here and not the whole policy.

Example of a working policy:

Policy Type:       MS-Windows-NT (13)
Active:            yes

Mult. Data Stream: yes
Perform Snapshot Backup:   yes
Snapshot Method:           auto
Snapshot Method Arguments: (none)
Perform Offhost Backup:    yes
Backup Copy:               2
Use Data Mover:            yes
Data Mover Type:           3

Residence:         test_stu
Volume Pool:       NetBackup
Client/HW/OS/Pri:  windows01 PC WindowsNET 0 0 0 0 ?
Include:           \\filer1\qtree1

Note that the filer data is mounted on a Windows 2000 machine in the above example, and the backup selection list contains the data path as \\filername\sharename. For SnapVault, qtrees must be shared on the filer by means of NFS or CIFS.

For SnapVault, you must specify the path up to a subvolume which is qtree in NetApp term. For a UNIX system, if the data resides in /vol/vol1/qtree1 on NDMP host filer1 and is NFS mounted to /mnt/vol1/qtree1 on the UNIX client, put /mnt/vol1/qtree1 in the backup selection list. Each subvolume listed in the backup policy must be individually mounted on the client. It is not sufficient to mount only the volume containing the subvolumes.

Existing volumes can be displayed by executing the following command on the NetApp Filer:

filer1> vol status
filer1> sysconfig -r

Existing qtrees can be seen by executing the following commands on the NetApp Filer:

filer1> qtree status
filer1> qtree stats

Storage Unit Configuration for NetBackup

Label:                test_stu
Storage Unit Type:    Disk
Media Subtype:        SnapVault (3)
Host Connection:      media_server
SnapVault Server:     filer2
Concurrent Jobs:      1
On Demand Only:       yes
Path:                 "/vol/vol1"
Robot Type:           (not robotic)
Max Fragment Size:    524288
Max MPX:              1
Stage data:           no
Block Sharing:        no
Transfer Throttle:    0
High Water Mark:      98
Ok On Root:           no

Note that the disk type/media subtype use SnapVault. Do not select NearStore, as NearStore storage unit type does not support SnapVault.

Additional notes:
For restrictions on point in time rollback from a snapshot, alternate path restore and Optimized Snapshot/SnapVault restore, consult the following manual:



Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)