Displaying SnapVault snapshots

Why to display SnapVault snapshots and qtrees

You can use the snap list command to display a list of snapshots to confirm what versions of your primary qtree data have been backed up, or to locate by date or time a particular version of a qtree to retrieve. Using the snap list -q command, you can see the following:

A list of all snapshots on the secondary storage system (not just SnapVault snapshots)
The qtrees in the snapshots
The primary storage system sources of those qtrees
The timestamp of the primary storage system snapshot that was the source for the data in the secondary storage system snapshot

Using the snap list -o command, you can also list the snapshot timestamps, primary qtree origin (if applicable), and snapshot names stored for an individual qtree.

Note
The descriptions and procedures in this section pertain to SnapVault backup of NetApp filers only. For descriptions and procedures pertaining to SnapVault backup of Open Systems drives and directories, see Setting up SnapVault backup on Open Systems platforms and Managing SnapVault backup of Open Systems platforms.

How to display SnapVault snapshots on volumes

To see a list of the snapshots and qtrees on your filer volumes, complete the following step.

Step	Action
1	On the filer for which you want to see the information, enter the following command: *snap list -q [volume_name]* volume_name is the name of the volume for which you want to list the snapshots. If no volume name is given, the snapshots on all this filer's volumes are displayed.

Sample snap list -q output

Primary storage output example

If you specify the primary volume name, the command lists the information for each snapshot in the volume. This output is from a volume used as a SnapVault primary storage system.

filerA> snap list -q vol2

working...

Volume vol2

    qtree                 contents       timestamp     source

    -----                 --------       ---------     ------

sv_hourly.0  (Jan 22 20:00)

    qtree1                Original       Jan 22 20:00  -

    qtree2                Original       Jan 22 20:00  -

    qtreeZ                Original       Jan 22 20:00  -

sv_hourly.1  (Jan 22 16:00)

    qtree1                Original       Jan 22 16:00  -

    qtree2                Original       Jan 22 16:00  -

    qtreeZ                Original       Jan 22 16:00  -

sv_hourly.2  (Jan 22 12:00)

    qtree1                Original       Jan 22 12:00  -

    qtree2                Original       Jan 22 12:00  -

    qtreeZ                Original       Jan 22 12:00  -

sv_hourly.3  (Jan 22 08:00)

    qtree1                Original       Jan 22 08:00  -

    qtree2                Original       Jan 22 08:00  -

    qtreeZ                Original       Jan 22 08:00  -

sv_nightly.0  (Jan 22 00:00)

    qtree1                Original       Jan 22 00:00  -

    qtree2                Original       Jan 22 00:00  -

    qtreeZ                Original       Jan 22 00:00  -

sv_hourly.4  (Jan 21 20:00)

    qtree1                Original       Jan 21 20:00  -

    qtree2                Original       Jan 21 20:00  - 
    qtreeZ                Original       Jan 21 20:00  -

sv_hourly.5  (Jan 21 16:00)

    qtree1                Original       Jan 21 16:00  -

    qtree2                Original       Jan 21 16:00  -

    qtreeZ                Original       Jan 21 16:00  -

sv_nightly.1  (Jan 21 00:00)

    qtree1                Original       Jan 21 00:00  -

    qtree2                Original       Jan 21 00:00  -

    qtreeZ                Original       Jan 21 00:00  -

This output shows which qtrees were writable and therefore have original content (the timestamp in these cases is the same as for the snapshot as a whole). It also shows whether any qtrees were transitioning and are therefore neither a faithful replica nor original content. Transitioning qtrees are shown with a dash (-) instead of a timestamp.

Secondary storage output example

If you specify the volume name (in this example, sv_vol) and are running the command from a filer used as a SnapVault secondary storage system, you see a list of all the SnapVault snapshots retained on volume sv_vol and the details of the qtrees contained in those snapshots.

filerB> snap list -q sv_vol

Volume sv_vol

working...

   qtree       contents    date           source

   --------    ---------   --------       -------

sv_hourly.0 (Jan 31 20:00)

   qtree1      Replica     Jan 22 20:40   filerA:/vol/vol2/qtree1

   qtree2      Replica     Jan 22 20:40   filerA:/vol/vol2/qtree2

   qtreeZ      Replica     Jan 22 20:40   filerA:/vol/vol2/qtreeZ

sv_hourly.1  (Jan 22 16:00)

   qtree1      Replica     Jan 22 16:00   filerA:/vol/vol2/qtree1

   qtree2      Replica     Jan 22 16:00   filerA:/vol/vol2/qtree2

   qtreeZ      Replica     Jan 22 16:00   filerA:/vol/vol2/qtreeZ

sv_hourly.2  (Jan 22 12:00)

   qtree1      Replica     Jan 22 12:00   filerA:/vol/vol2/qtree1

   qtree2      Replica     Jan 22 12:00   filerA:/vol/vol2/qtree2

   qtreeZ      Replica     Jan 22 12:00   filerA:/vol/vol2/qtreeZ

.....

This output shows which qtrees are replicas of another qtree, and the timestamp of the source snapshot.

Note
Qtrees that are transitioning appear with a dash (-) instead of a timestamp. In general, you should not attempt to restore snapshot versions of qtrees that are transitioning.

If you specify no arguments, the output shows the information for each snapshot in each volume.

How to list snapshots for qtrees

To see a list of snapshots associated with a qtree and, if applicable, the snapshots' primary qtree origins, complete the following step.

Step	Action
1	On the filer for which you want to see the information, enter the following command: *snap list -o [qtree_path]* qtree_path displays one qtree. If no qtree name is given, information for all the qtree names on the volume are displayed.

Sample snap list -o output

If you specify the -o parameter with a qtree path, the snap list output includes the dates, sources (if any), and names of associated SnapVault snapshots that are retained on the system, for example:

filerB> snap list -o /vol/sv_vol/qtree3

working...

Qtree /vol/sv_vol/qtree3

date          source                       name

------------  --------                     --------

Jan 31 18:00  filerA:/vol/vol2/qtree3      hourly.0

Jan 31 17:00  filerA:/vol/vol2/qtree3      hourly.1

Jan 31 16:00  filerA:/vol/vol2/qtree3      hourly.2

Jan 31 15:00  filerA:/vol/vol2/qtree3      hourly.3

Jan 30 14:00  filerA:/vol/vol2/qtree3      hourly.4

Jan 30 13:00  filerA:/vol/vol2/qtree3      hourly.5

Jan 30 12:00  filerA:/vol/vol2/qtree3      hourly.6

Jan 30 11:00  filerA:/vol/vol2/qtree3      hourly.7

Jan 31 10:00  filerA:/vol/vol2/qtree3      hourly.8

Jan 31 9:00   filerA:/vol/vol2/qtree3      hourly.9

Jan 31 8:00   filerA:/vol/vol2/qtree3      hourly.10

Jan 30 20:00  filerA:/vol/vol2/qtree3      nightly.0

Jan 29 20:00  filerA:/vol/vol2/qtree3      nightly.1

Jan 26 16:00  filerA:/vol/vol2/qtree3      weekly.0