Table of ContentsView in Frames

What the status fields mean

You can see the information fields that SnapVault can display for the snapvault status and snapvault status -l commands.

Field Possible values that might be displayed
Source system:qtree_path—The source is the primary storage system and qtree path listed.
Destination system:qtree_path—The destination is the secondary storage system 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 storage system qtree is in; the volume that contains the secondary storage 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 storage system and the latest data stored on the secondary storage system; that is, the difference between the current time and the timestamp of the Snapshot copy last successfully transferred to the secondary storage system.

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

Status Aborting—A transfer is being aborted and cleaned up.

Idle—No data is being transferred.

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

Quiescing—The specified qtree is waiting for all existing transfers to complete. The destination is being brought into a stable state.

Resyncing—The specified qtree is resynchronizing.

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

Progress Shows the number of KB transferred by the current transfer, or the restart check point if the status is Idle or Pending.
Mirror Timestamp hh:mm:ss indicates the timestamp of the last Snapshot copy successfully transferred from the primary storage system to the secondary storage system.
Note: A resynchronization (snapvault start -r) might change the base Snapshot copy to a Snapshot copy with a timestamp older than the original base.
Base Snapshot copy The name of the base Snapshot copy 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 copy for that qtree on the storage side. A resynchronization (snapvault start -r) might change the name of the base Snapshot copy.

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 system and volume or qtree (where the content is transferred from).
Note: If snapvault status displays a negative lag time, it means the clock on the destination storage system is ahead of the clock on the source storage system. The solution is to synchronize the clocks on both the storage systems.