Version 4.0 Time Navigator SnapBackup

10 Time Navigator SnapBackup
Configuration
NetApp SnapVault Technology Prerequisites
If you are using NetApp SnapVault technology, you must have the appropriate primary and
secondary SnapVault licences, and you must configure your filers prior to configuring
Time Navigator SnapBackup.
The volume to snapshot (source ) is located on the primary filer. The data, once snapshotted
is copied on the secondary filer (destination). When a snapshot job is launched, the source
volume on the primary filer is snapshotted and a copy is sent to the destination volume on
the secondary filer.
The server configuration consists in:
■ Defining a qtree on the primary server.
■ Defining a manual schedule on both primary and secondary servers.
The schedule provide such information as the snapsetname, which must be the
same on both servers and the retention, i.e., the maximum number of snapshots kept
on the servers. The retention need not be the same on both servers.
Note Although you must set the retention when you define the manual schedule,
Time Navigator actually manages the retention using the
TINA_APP_MAX_SNAP variable. See “Variable Common to all
Applications”, page 14 for details.
■ Defining the relationship between the servers.
The relationship establishes the primary qtree and server and the secondary qtree and
server. The relationship definition must take place on the secondary server.
Note The qtree definition and the relationship definition have to be performed again
if the qtree is physically destroyed. See “SnapVault Restore”, page 27 for details.
For instance:
1. Define the qtree spr on vol1 on the primary server:
qtree create /vol/vol1/spr
2. Define a manual schedule on the primary server:
snapvault snap sched vol1 edith_sv 3@0@-