Library Table of Contents Index Previous Next Comments

Checking SnapVault transfers

Why to check data replication status  Top

You check transfer status, using the snapvault status command, to make sure SnapVault transfers are taking place as they should.

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.

Checking the status  Top

To check the status of a data transfer and see how recently a qtree has been updated, complete the following step.

Step

Action

1

Enter the following command:

snapvault status [-l] [[[filer_name:]qtree_path] ...] 
[-s] [-c]

Options can be one or more of the following:

  • -l displays the long format of the output, which contains more detailed information.
  • -s displays the SnapVault snapshot basename, status, and schedule for each volume.
  • -c displays the configuration parameters of all SnapVault qtrees on the filer. This option can be run only from the secondary storage system.

filer_name is the name of the filer for which you want to see the status of SnapVault operations.

qtree_path is the path of the qtree or qtrees for which you want to see the status of SnapVault operations. You can specify more than one qtree path.

Result

The filer displays a message showing whether a transfer is in progress, how much data has been transferred, the state of the destination, and how long ago the last successful transfer took place.

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.

filerA> snapvault status
Snapvault client is ON.
Source                   Destination                    State         Lag       Status
filerB:/vol/vol2/qtree3  filerA:/vol/sv_vol/qtree3      Snapvaulted  00:48:24  Idle
Example 2:

The snapvault status -l command and option displays more detailed information on the most recent SnapVault transfer and snapshot activity.

filerA> snapvault status -l 
SnapVault client is ON.
Source:                     filerA:/vol/vol2/qtree3 
Destination                 filerB:/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:              filerB(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 and option lists all the snapshots scheduled on the primary or secondary storage system. Information includes volume, snapshot basename, current status, and snapshot schedule.

filerA> snapvault status -s

Snapvault server 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 and option 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.

filerA> snapvault status -c 
/vol/sv_vol/db_qtree1 source=filerB:/vol/db1/s1 kbs=unlimited 
tries=20 
/vol/sv_vol/db_qtree2 source=filerC:/vol/db2/s2 kbs=unlimited 
tries=20 
/vol/sv_vol/qtree1 source=filerC:/vol/users/qtree1 kbs=10000 
tries=10 
/vol/sv_vol/qtree2 source=filerC:/vol/users/qtree2 kbs=10000 
tries=10 
/vol/sv_vol/qtree3 source=filerD:/vol/users/qtree1 kbs=10000 
tries=10 
/vol/sv_vol/qtree4 source=filerD:/vol/db/db_1 kbs=7000 tries=10 

 
filerA> snapvault status -c /vol/sv_vol/qtree3 
/vol/sv_vol/qtree3 source=filerA:/vol/vol2/qtree3 kbs=10000 
tries=10

What the status fields mean  Top

Information fields that SnapVault can display for the snapvault status and snapvault status -l commands are as follows.

Field

Possible values displayed include:

Source

filer:qtree_path--The source is the primary storage system filer and qtree path listed.

A dash (-) in this field means that the SnapVault secondary storage destination qtree is not yet initialized through the snapvault start -x command.

Destination

filer:qtree_path--The destination is the secondary storage system filer and qtree path listed.

State

Uninitialized--The destination SnapVault secondary storage qtree is not yet initialized through the snapvault start command.

Snapvaulted--The qtree is a SnapVault secondary destination.

Unknown--It is not known what state the secondary system qtree is in; the volume that contains the secondary system qtree could be offline or restricted.

Source--This state is reported when the snapvault status command is run on the primary storage system. It also appears if snapvault status is run on secondary storage systems after the snapvault restore command was run on an associated primary storage system.

Lag

hh:mm:ss indicates the time difference between the data currently on the primary system and the latest data stored on the secondary system; that is, the difference between the current time and the timestamp of the snapshot last successfully transferred to the secondary storage system.

A dash (-) in this field means that the secondary storage system is not initialized.

Status

idle--No data is being transferred.

Transferring--Transfer has been initiated, but has not yet started, or is just finishing.

Pending--The secondary storage system cannot be updated because of a resource issue; the transfer is retried automatically.

Aborting--A transfer is being aborted and cleaned up.

Resyncing--The specified qtree is resynchronizing.

Progress

Shows the number of KB transferred by the current transfer or the restart check point if the status is Idle or Pending.

SnapVault Timestamp

The timestamp of the last snapshot successfully transferred from the primary storage system to the secondary storage system.

Note
A resynchronization (snapvault start -r) may change the base snapshot to a snapshot with a timestamp older than the original base.

Base Snapshot

The name of the base snapshot for the corresponding qtree on the secondary storage system.

For qtrees in a SnapVault relationship, the secondary storage side lists the name of the exported snapshot for that qtree on the storage side. A resynchronization (snapvault start -r) may change the name of the base snapshot.

Current Transfer Type

Indicates the type of the current transfer: scheduled, retry, resync, update, initialize, store, or retrieve. This field applies only to the destination side.

Current Transfer Error

Displays an error message if the latest transfer attempt failed.

Contents

Indicates whether the contents of the destination volume or qtree in the active file system are up-to-date replicas or are in transition. The field applies only to the destination side. Since a destination is read-only, its contents are always a replica.

Last Transfer Type

Indicates the type of the previous transfer: scheduled, retry, resync, update, initialize, store, or retrieve. This field applies only to the secondary storage side.

Last Transfer Size

Shows the number of KB transferred in the last successful transfer.

Last Transfer Duration

Shows the elapsed time for the last successful transfer. If the transfer failed and restarted, the time includes time waiting to restart the transfer. If a transfer aborted and was retried from the beginning, it includes only the time required for the final successful attempt.

Last Transfer From

This field applies only to the secondary storage side and shows the name of the primary filer and volume or qtree (where the content is transferred from).

Library Table of Contents Index Previous Next Comments