Replication Manager Reports > SnapVault Relationship Summary
  
Version 10.1.01
SnapVault Relationship Summary
Explore your data center using APTARE customizable report templates or by using parts of your IT infrastructure as entry points. Use Search to find reports, templates and dashboards across the portal.
Use the Reports tab to examine the StorageConsole catalog of templates, dashboards and reports - organized by products along with user-created, and system folders. This report is located here:
List status for source-destination pairs for SnapVault transactions. Choose to report by volume or QTree and select the mirror states to examine. For additional details about a Failed transaction, mouse over the Summary Status to view the message.
 
Source Location
The source location will be displayed in one of the following formats: NetApp Storage System: Volume Name or NetApp Storage System: Volume Name/QTree Name
Destination Location
The destination location will be displayed in one of the following formats: NetApp Storage System: Volume Name or NetApp Storage System: Volume Name/QTree Name
Mirror Timestamp
Date and time of last SnapMirror transaction, including unsuccessful mirrors
Contents
The active filesystem state of the destination: replica, transitioning, or original.
Last Transfer Size (KB)
Amount of data in the last mirror transfer.
Last Transfer Duration (Secs)
Length of time for the last mirror data transfer.
Transfer KB/Secs
Rate of mirror data transfer.
Base Snapshot
The name of the last snapshot transferred from source to destination
State
uninitialized, snapmirrored, broken-off, quiesced, source, unknown.
Status
Transfer completion status for the source-destination pair: idle, transferring, pending, aborting, migrating, quiescing, resyncing, waiting, syncing, in-sync, or paused.
Summary Status
Success, Failed - Mouse over the Failed status to view the error message that contains the details of why the transfer failed.
Lag Time
The length of time since the last SnapVault transfer.
Last Updated
The last time the Data Collector updated the Portal database.