Examples for checking the status

The following examples help you check the data transfer status pertaining to SnapVault backup of storage systems running Data ONTAP only.

Example 1

If you enter snapvault status with no option, you see SnapVault qtree relationships involved in the most recent transfer from a primary qtree to a secondary qtree:

systemA> snapvault status

Snapvault primary  is ON.
Source 			               Destination 		             State       Lag      Status
systemB:/vol/vol2/qtree3 systemA:/vol/sv_vol/qtree3 Snapvaulted 00:48:24 Idle

Note: If the SnapVault primary and secondary licenses are installed on the same storage system, the following message is displayed:

Snapvault is ON.

Example 2

The snapvault status -l command displays more detailed information on the most recent SnapVault transfer and Snapshot copy activity:

systemA> snapvault status -l

SnapVault primary is ON.
Source: 		              systemA:/vol/vol2/qtree3
Destination             systemB:/vol/sv_vol/qtree3
Status                  Idle
Progress:               -
State: 			              SnapVaulted
Lag: 			                2:09:58
SnapVault Timestamp:    Thu Jan 31 12:30:01 PST 2002
Base Snapshot: 		       systemB(0016778780)_sv_vol.59
Current Transfer Type
Current Transfer Error:
Contents:               Replica
Last Transfer Type: 	   Scheduled
Last Transfer Size: 	   1680 KB
Last Transfer Duration: 00:02:08-

Example 3

The snapvault status -s command lists all the Snapshot copies scheduled on the primary or secondary storage system. Information includes volume, Snapshot copy basename, current status, and Snapshot schedule:

systemA> snapvault status -s

Snapvault secondary is ON.
Volume 	Snapshot   Status  Schedule
------ 	--------   ------  --------
sv_vol 	sv_hourly  Idle    1@0-23
vol2 	  sv_weekly  Idle    8@fri

Example 4

The snapvault status -c command lists all the secondary system qtrees, their corresponding primary system qtrees, maximum speed of scheduled transfers, and maximum number of times SnapVault attempts to start a scheduled transfer before skipping that transfer:

systemA> snapvault status -c

/vol/sv_vol/db_qtree1 source=systemB:/vol/db1/s1       kbs=unlimited tries=20
/vol/sv_vol/db_qtree2 source=systemC:/vol/db2/s2       kbs=unlimited tries=20
/vol/sv_vol/qtree1    source=systemC:/vol/users/qtree1 kbs=10000     tries=10
/vol/sv_vol/qtree2    source=systemC:/vol/users/qtree2 kbs=10000     tries=10
/vol/sv_vol/qtree3    source=systemD:/vol/users/qtree1 kbs=10000     tries=10
/vol/sv_vol/qtree4    source=systemD:/vol/db/db_1      kbs=7000      tries=10

systemA> snapvault status -c /vol/sv_vol/qtree3

/vol/sv_vol/qtree3 source=systemA:/vol/vol2/qtree3     kbs=10000     tries=10

Example 5

The snapvault status -t command lists all the SnapVault relationships that have active transfers:

systemA> snapvault status -t 

Snapvault secondary is ON.
Source                    Destination                   State         Lag      Status
systemB:/vol/vol2/qtree3  systemA:/vol/sv_vol/qtree3   Snapvaulted   00:48:24  Transferring

If there are no active transfers, the following message appears:

systemA> snapvault status -t

Snapvault secondary is ON.
There are no active transfers.

Parent topic: Checking SnapVault transfers