Snapshotroot
Use the snapshotroot option with the incremental, selective, or archive commands with an independent software vendor application that provides a snapshot of a logical volume, to associate the data on the local snapshot with the real file space data that is stored on the IBM Spectrum Protect server.
The snapshotroot option can be used to back up NFS mounted file systems. Both the backup specification (source) and the snapshotroot value can be an NFS mounted file specification. For example, the snapshotroot option can be used to backup an NFS file system that is hosted on a network-attached storage (NAS) that supports snapshot.
This option should be used with an incremental backup of a NAS file server volume instead of a simple incremental or incremental with snapshotroot option whenever the NAS file server is running ONTAP V7.3 for performance reasons. The snapdiff and snapshotroot options should not be used together.
The snapshotroot option can be used to back up network share mounted file systems. Both the backup specification (source) and the snapshotroot value can be a network share mounted file specification. For example, the snapshotroot option can be used to back up a network share file system hosted on a network-attached storage (NAS) that supports snapshot.
In the following example, filesystem
test495
is NFS-mounted from a NAS file server philo
and
/philo/test945/.snapshot/backupsnap
represents the snapshot that is created at the
NAS file server.
In the following example, c:\snapshots\snapshot.0
is network
share that is mounted from a NAS file server and \\florance\c$
represents the
snapshot that is created at the NAS file server.
dsmc incr \\florance\C$ -snapshotroot=c:\shapshots
\snapshot.0
You can also specify a directory with the snapshotroot option when you backup each file set as a separate file space.
The snapshotroot option does not provide any facilities to take a volume snapshot, only to manage data that is created by a volume snapshot.
/usr file system
and mounts it as /snapshot/day1
. If you
back up this data by using the following command, a unique file space that is called
/snapshot/day1
is created on the server.
dsmc incremental /snapshot/day1
/usr
file system. Using the
snapshotroot option, you can associate the data with the file space corresponding
to the /usr
file system on the IBM
Spectrum Protect server:
dsmc incremental /usr -snapshotroot=/snapshot/day1
c:
drive and mounts it as the NTFS junction point
\\florence\c$\snapshots\snapshot.0
. If you back up this data by using the following
command, a unique file space that is called \\florence\c$\snapshots\snapshot.0
is
created on the server.
dsmc incremental \\florence\c$\snapshots\snapshot.0
c:
drive (\\florence\c$)
. Using the
snapshotroot option, you can associate the data with the file space corresponding
to the c:
drive (\\florence\c$)
on the IBM
Spectrum Protect server:
dsmc incr c: -snapshotroot=\\florence\c$\snapshots\snapshot.0
-or-
dsmc incr \\florence\c$ -snapshotroot=\\florence\c$\snapshots\
snapshot.0
dsmc incremental /usr -snapshotroot=/snapshot/day2
dsmc incr c: -snapshotroot=\\florence\c$\snapshots\snapshot.1
dsmc incremental /usr/dir1/* -subdir=yes
-snapshotroot=/snapshot/day1
dsmc selective /usr/dir1/sub1/file.txt
-snapshotroot=/snapshot/day1
dsmc archive /usr/dir1/sub1/*.txt
-snapshotroot=/snapshot/day1
dsmc incr c:\dir1\* -subdir=yes -snapshotroot=\\florence\c$\
snapshots\snapshot.1
dsmc sel c:\dir1\sub1\file.txt -snapshotroot=\\florence\c$\
snapshots\snapshot.1
dsmc archive c:\mydocs\*.doc -snapshotroot=\\florence\c$\
snapshots\snapshot.1
/usr
file system), and not the name of the
target of the snapshot (/snapshot/day1)
. Doing this allows you to preserve a set of
include and exclude statements regardless of the name of the logical volume to which the snapshot is
written. The following are examples of include and exclude statements.
include /usr/dir1/*.txt 1yrmgmtclass
exclude /usr/mydocs/*.txt
c:
drive), and not the name of the target of the snapshot
(\\florence\c$\snapshots\snapshot.1)
. Doing this allows you to preserve a set of
include and exclude statements regardless of the name of the logical volume to which the snapshot is
written. The following are examples of include and exclude statements.
include c:\dir1\.../*.txt lyrmgmtclass
exclude \\florence\c$\mydocs\*.doc
include /snapshot/day1/dir1/*.txt 1yrmgmtclass
exclude /snapshot/day1/mydocs/*.txt
include \\florence\c$\snapshots\snapshot.1\dir1\...\
*.txt 1yrmgmtclass
exclude \\florence\c$\mydocs\*.doc
dsmc incremental /usr -snapshotroot=/snapshot/day1
dsmc incremental /usr/dir1/* -snapshotroot=/snapshot/day1
dsmc incr c: -snapshotroot=\\florence\c$\snapshots\snapshot.0
dsmc incr c:\dir1\* -snapshotroot=\\florence\c$\snapshots\
snapshot.0
The
following command is invalid because it contains two file specifications:
dsmc incremental /usr/dir1/* /home/dir2/*
-snapshotroot=/snapshot/day1
dsmc incr c:\dir1\* e:\dir1\* -snapshotroot=\\florence\c$\
snapshots\snapshot.0
dsmc incremental -snapshotroot=/snapshot/day1
dsmc incr -snapshotroot=\\florence\c$\snapshots\snapshot.0
- Ensure that the snapshotroot option references a snapshot of the correct volume. Ensure that snapshotroot location refers to the root of the snapshot. If these rules are not followed, unintended results, such as files that expire incorrectly, can result.
- If you specify the filelist option and the snapshotroot option, all files that are specified in the filelist option are assumed to be in the same file system. If there are entries in the filelist in a different file system, they are skipped and an error is logged. If the filelist contains files that were created in the file system after the snapshot was taken, these entries are also skipped, and an error is logged.
- You cannot use the snapshotroot option with any backup command, such as backup image, or backup systemstate, and so on.
- You cannot use the snapshotroot option with the snapdiff option.
- Use the snapshotroot option with caution if you are using the IBM Spectrum Protect journal-based backup feature. Since there is no coordination between the IBM Spectrum Protect journal and the vendor-acquired snapshot provider (VSS), unwanted behavior can occur with journal notifications received after the snapshot occurs. For example, files might not be backed up, or they might be backed up redundantly to the IBM Spectrum Protect server.
- You can use the snapshotroot option with the preschedulecmd and postschedulecmd options, or in an automated script that you run with the client scheduler.
Supported Clients
This option is valid for the following clients:- UNIX and Linux clients except Mac OS X.
- All Windows clients.
Syntax
Parameters
- snapshot_volume_name
- Specifies the root of the logical volume that is created by the independent software vendor snapshot application.
Examples
- Command line:
dsmc incremental /usr -SNAPSHOTRoot=/snapshot/day1
- Command line:
dsmc incr c: -SNAPSHOTRoot=\\florence\c$\snapshots\snapshot.0