Chat now with support
Chat with Support

NetVault Plug-in for SnapVault Manager 11.4.5 - User Guide

Installing the plug-in

•
Deploying the plug-in
•
Planning SnapVault backup system
•
Prerequisites
•
Installing the plug-in
•
Removing the plug-in

Deploying the plug-in

The SnapVault backup systems consist of one or more Primary Systems and one Secondary System.

Figure 1. A SnapVault environment

•
Primary System: The Primary Systems consist of Filers or Open Systems with data to be backed up to a Secondary System. When a Filer is acting as a Primary System, SnapVault backs up primary qtrees to one or more volumes on the SnapVault Secondary System. With an Open System as a Primary, SnapVault can back up directories and entire drives to volume on the Secondary System.
•
Secondary System: The Secondary System is a central, disk-based unit that receives and stores backup data from Filers and Open Systems as Snapshots. Any NetApp filer can be configured as a Secondary system.

Planning SnapVault backup system

Some initial planning should be performed before setting up a SnapVault Backup System.

To start, you must plan the Relationship between the qtrees and directories of a Filer or Open System acting as SV Primaries and the qtrees of the Filer serving as the SV Secondary. You can perform multiple SV Primary backups (for example, both the qtrees of a Filer and the directories of an Open System) to a single volume of the corresponding qtrees of the SV Secondary system.

Figure 2. A sample of a SnapVault Backup System Plan

Before beginning a SnapVault configuration, you must also plan how many snapshots are required on a per volume basis; when they are to be updated; and how many of each are to be kept. Scheduling is decided upon based on the various values.

•
Hourly: Does the data change often enough throughout the day to make it worthwhile to create a snapshot every hour, every two hours or every four hours?
•
Nightly: Do you want to create a snapshot every night or just workday nights?
•
Weekly: How many weekly snapshots is it necessary or useful to keep?
 
Table 1. Snapshots Required
SV Primary Target (qtree/directory)
SV Secondary Destination (qtree)

Filer_A

/vol/vol1/qtree_a

/vol/sv_vol/qtree_a

/vol/vol1/qtree_b

/vol/sv_vol/qtree_b

Filer_B

/vol/vol1/qtree_c

/vol/sv_vol/qtree_c

/vol/vol1/qtree_d

/vol/sv_vol/qtree_d

Server_A (Open System)

C:\accts

/vol/sv_vol/accts

Server_A:\docs\dev

/vol/sv_vol/dev

In the example represented by the preceding figure and table, there are six qtrees on the SV Secondary volume. The following schedule has been created for the backups:

•
An hourly update every hour from 8:00 a.m. to 7:00 p.m. and 120 of these Snapshots are to be kept.
•
A daily update is to be performed every Monday through Friday at 8:00 p.m in which 60 of the Snapshots are to be kept.
•
A weekly update every Saturday at 9:00 p.m. in which eight Snapshots are kept.

The result from this example is that 188 Snapshots are kept in the SV Secondary volume. The limit on snapshots per volume is 251, so the 188 snapshots scheduled in this example is well within this limit.

Prerequisites

Before installing the plug-in, you must complete the following tasks:

•
Install and Configure SnapVault: The NetApp SnapVault software must be installed and properly configured on all SV Primaries and SV Secondaries to be used. For complete details on the installation and configuration of the SnapVault software, see the relevant NetApp documentation
•
Install and Configure NetVault Backup Server Software: The Plug‑in for SnapVault Manager can only be installed on the NetVault Backup Server.
•
Enable SnapVault: The SnapVault application must first be enabled on all SV Primaries and SV Secondaries to be used.
•
SV Secondary: At the command prompt, type the following:
options snapvault.enable on
options snapvault.access <primary system>
This setting lets you specify the names of the SV Primary systems to back up and restore. A comma-separated list of SV Primaries is included in place of the “<primary systems>” value shown earlier. Eligible values include the actual name of the host (for example, “host=melzhost, budzhost”) or its IP address (for example, “10.1.213.101”).
•
SV Primary: Filer — Launch a terminal session from the filer, and run the following commands:
options snapvault.enable on
options snapvault.access <secondary>
This setting lets you specify the name of the SV Secondary that it backs up to. The SV Secondary is what is named in place of the “<secondary>” value shown earlier. Eligible values include the actual name of the host or its IP address. If multiple SV Secondaries are to be used, a comma-separated list of eligible values should be input.
•
SV Primary: Open System — On an Open System, follow these steps to enable SnapVault and configure the SV Secondary system:
a
From the Open System, access the SnapVault Configurator (svconfigurator on Linux and OSSV Configurator on Windows).
b
Select the SnapVault tab, and configure the following settings:
•
In the NDMP Host Name box, type the host name or IP address of the SV Primary system.
•
In the QSM Access List box, type the IP address or host name of the SV Secondary system. To configure multiple SV Secondary systems, specify a comma-separated list of eligible values.
c
To save the settings and close the SnapVault Configurator, click OK.
•
Install SnapVault Software Licenses: The SnapVault software installed on the SV Secondary must have the proper license keys installed. Contact NetApp for details on obtaining license keys.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating