Destination volume is too small.... for volume1 lag time is 44 days
Destination in use as source of snappvault for netabackup, dump, vol copy or snapmirror. for volume 2 on source - On destionation, snapmirror section reports destination reject lag time is 103 days.
sis status show disabled for volume1 > sis on tells me sis logical limit reached
In system manager, if I try to resize volume 1 snapmirror volume , the new size show in the wizard but not as total space!?!?
I have seen various threads where there are mentions of quesceing the volume, change fs sizee fixed to off - I get Volume 'Backup_sm' is a snapmirrored volume
We recently upgraded our domain and we now only have 2012R2 DC's but cifs domaininfo still show Type: Windows 2003 - perhaps this is of no concern, but for the sake of completion, rebooted the destionation controller and run cifs setup - Peraphs overkill but no harm really... no luck.
All other snapmirrors and snapvaults are fine, it is just there 2 vols that are giving us grief.
I am at a loss really because we are so far behind, it is rather concerning, we have room left on the aggregate, all volumes are thick.
PAR-NETAPP01> vol size backup_sm Warning: Volume 'backup_sm' has fs_size_fixed option set. The file system size may differ from the volume size.
See 'vol status -b' for more detail. vol size: Flexible volume 'backup_sm' has size 10t.
Volume 2 is called filetrans
SoSource: CAK0951A:filetrans Destination: PAR-NETAPP01:filetrans_sm Status: Idle Progress: - State: Snapmirrored Lag: 02:37:49 Mirror Timestamp: Tue Jul 14 09:30:04 BST 2015 Base Snapshot: PAR-NETAPP01(1892145899)_filetrans_sm.345 Current Transfer Type: - Current Transfer Error: - Contents: Replica Last Transfer Type: Scheduled Last Transfer Size: 13082056 KB Last Transfer Duration: 00:02:35 Last Transfer From: CAK0951A:filetrans