What kind of conditions can cause snapmirror show command to display "Last Transfer Size: -"?
Applies to
ONTAP
Answer
- Condition 1)
Last Transfer Type
cannot be identified successfully.
Example:
::> snapmirror show voldest
Source Path: SVM1:volsrc
Destination Path: SVM1:voldest
Relationship Type: DP
Relationship Group Type: none
SnapMirror Schedule: -
SnapMirror Policy Type: async-mirror
SnapMirror Policy: DPDefault
Tries Limit: -
Throttle (KB/sec): unlimited
Mirror State: Snapmirrored
Relationship Status: Quiesced
File Restore File Count: -
File Restore File List: -
Transfer Snapshot: -
Snapshot Progress: -
Total Progress: -
Network Compression Ratio: -
Snapshot Checkpoint: -
Newest Snapshot: snapmirror.ca05c9c9-9530-11e8-8ac2-005056a07220_2153244767.2020-03-08_040544
Newest Snapshot Timestamp: 03/08 04:05:51
Exported Snapshot: snapmirror.ca05c9c9-9530-11e8-8ac2-005056a07220_2153244767.2020-03-08_040544
Exported Snapshot Timestamp: 03/08 04:05:51
Healthy: true
Unhealthy Reason: -
Constituent Relationship: false
Destination Volume Node: node1
Relationship ID: 8c3c6e0e-562e-11ea-9cbd-005056a07220
Current Operation ID: -
Transfer Type: -
Transfer Error: -
Current Throttle: -
Current Transfer Priority: -
Last Transfer Type: -
Last Transfer Error: -
Last Transfer Size: -
Last Transfer Network Compression Ratio: -
Last Transfer Duration: -
Last Transfer From: -
Last Transfer End Timestamp: -
Progress Last Updated: -
Relationship Capability: 8.2 and above
Lag Time: 1051:52:13
Identity Preserve Vserver DR: -
Volume MSIDs Preserved: -
Is Auto Expand Enabled: -
Number of Successful Updates: 0
Number of Failed Updates: 0
Number of Successful Resyncs: 0
Number of Failed Resyncs: 0
Number of Successful Breaks: 0
Number of Failed Breaks: 0
Total Transfer Bytes: 0
Total Transfer Time in Seconds: 0
- Condition 2)
Last Transfer Error
indicates that the SnapMirror transfer failed to start.
Example:
::> snapmirror show voldest2
Source Path: SVM2:volsrc2
Destination Path: SVM2:voldest2
Relationship Type: DP
Relationship Group Type: none
SnapMirror Schedule: mirror2
SnapMirror Policy Type: async-mirror
SnapMirror Policy: DPDefault
Tries Limit: -
Throttle (KB/sec): unlimited
Mirror State: Snapmirrored
Relationship Status: Transferring
File Restore File Count: -
File Restore File List: -
Transfer Snapshot: snapmirror.ca05c9c9-9530-11e8-8ac2-005056a07220_2153244784.2020-04-08_084807
Snapshot Progress: 1.97TB
Total Progress: 1.97TB
Network Compression Ratio: 1:1
Snapshot Checkpoint: 1.97TB
Newest Snapshot: snapmirror.ca05c9c9-9530-11e8-8ac2-005056a07220_2153244784.2020-03-07_090000
Newest Snapshot Timestamp: 03/07 20:01:29
Exported Snapshot: snapmirror.ca05c9c9-9530-11e8-8ac2-005056a07220_2153244784.2020-03-07_090000
Exported Snapshot Timestamp: 03/07 20:01:29
Healthy: false
Unhealthy Reason: Scheduled update failed to start. (Scheduled update was delayed because another SnapMirror operation for the relationship is in progress.)
Constituent Relationship: false
Destination Volume Node: BEATOMNODE06
Relationship ID: abf2ff7c-64a1-11e9-b4af-005056a07220
Current Operation ID: 3b00000a-792a-11ea-b342-00a01234567f
Transfer Type: update
Transfer Error: -
Current Throttle: unlimited
Current Transfer Priority: normal
Last Transfer Type: update
Last Transfer Error: Transfer did not start. The relationship is quiesced, or Vserver peering between source and destination Vservers has been suspended or removed.
Last Transfer Size: -
Last Transfer Network Compression Ratio: -
Last Transfer Duration: -
Last Transfer From: SVM2:volsrc2
Last Transfer End Timestamp: 03/14 17:05:08
Progress Last Updated: 04/20 23:58:04
Relationship Capability: 8.2 and above
Lag Time: 1059:56:46
Identity Preserve Vserver DR: -
Volume MSIDs Preserved: -
Is Auto Expand Enabled: -
Number of Successful Updates: 55
Number of Failed Updates: 0
Number of Successful Resyncs: 0
Number of Failed Resyncs: 0
Number of Successful Breaks: 0
Number of Failed Breaks: 0
Total Transfer Bytes: 20172269412352
Total Transfer Time in Seconds: 6214749
Additional Information