Subscribe

snapmirror issues

Hello everyone,

 

We have 3210 as source and 2240 as destination.

Running 8.1.2

We have issues with 2 volumes

  • Volume 1 is 11.14 TB
  • Volume 2 is 210 GB

System Manager snapmirror tells me

  • 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.

 

Help much appreciated.

 

Thanks.

Re: snapmirror issues

Log into each controller and do a vol size on each for the first volume.. Make sure they are the same size

 

 

On the second one show us snamirror -l of the relationship and a snap list of the dst side.

 

Also, you are running 8.1.2, it's time to think about upgrading

Re: snapmirror issues

Hi,

Thanks.

 

This is what I get

 

Volume 1 as referred in my op is called backup and it's snapmirror is called backup_sm

 

CAK0951A> vol size backup
vol size: Flexible volume 'backup' has size 11964514316k.

 

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

 

 

 

snap list

Volume filetran_sv
working......

%/used %/total date name
---------- ---------- ------------ --------
0% ( 0%) 0% ( 0%) Jul 14 11:52 Daily.0
0% ( 0%) 0% ( 0%) Jul 13 11:06 Daily.1
0% ( 0%) 0% ( 0%) Jul 13 11:06 PAR-NETAPP01(1892145899)_filetran_sv-base.1 (busy,snapvault)
0% ( 0%) 0% ( 0%) Apr 01 00:01 Monthly.0
0% ( 0%) 0% ( 0%) Mar 31 11:06 Daily.2
0% ( 0%) 0% ( 0%) Mar 30 11:06 Daily.3
0% ( 0%) 0% ( 0%) Mar 29 11:07 Daily.4
0% ( 0%) 0% ( 0%) Mar 28 11:08 Daily.5
0% ( 0%) 0% ( 0%) Mar 27 11:07 Daily.6
0% ( 0%) 0% ( 0%) Mar 26 11:07 Daily.7
0% ( 0%) 0% ( 0%) Mar 25 11:06 Daily.8
1% ( 0%) 0% ( 0%) Mar 24 11:07 Daily.9
1% ( 0%) 0% ( 0%) Mar 23 11:07 Daily.10
1% ( 0%) 0% ( 0%) Mar 22 11:07 Daily.11
1% ( 0%) 1% ( 0%) Mar 21 11:08 Daily.12
1% ( 0%) 1% ( 0%) Mar 20 11:07 Daily.13
1% ( 0%) 1% ( 0%) Mar 19 11:07 Daily.14
1% ( 0%) 1% ( 0%) Mar 18 11:07 Daily.15
1% ( 0%) 1% ( 0%) Mar 17 11:07 Daily.16
1% ( 0%) 1% ( 0%) Mar 16 11:07 Daily.17
1% ( 0%) 1% ( 0%) Mar 15 11:07 Daily.18
1% ( 0%) 1% ( 0%) Mar 14 11:07 Daily.19
1% ( 0%) 1% ( 0%) Mar 13 11:07 Daily.20
1% ( 0%) 1% ( 0%) Mar 12 11:06 Daily.21
1% ( 0%) 1% ( 0%) Mar 11 11:06 Daily.22
1% ( 0%) 1% ( 0%) Mar 10 11:07 Daily.23
1% ( 0%) 1% ( 0%) Mar 09 11:07 Daily.24
1% ( 0%) 1% ( 0%) Mar 08 11:07 Daily.25
2% ( 0%) 1% ( 0%) Mar 07 11:07 Daily.26
2% ( 0%) 1% ( 0%) Mar 06 11:06 Daily.27
2% ( 0%) 1% ( 0%) Mar 05 11:06 Daily.28
2% ( 0%) 1% ( 0%) Mar 04 11:06 Daily.29
2% ( 0%) 1% ( 0%) Mar 03 11:07 Daily.30
2% ( 0%) 1% ( 0%) Mar 01 00:01 Monthly.1
11% ( 9%) 9% ( 7%) Feb 01 00:01 Monthly.2
11% ( 0%) 9% ( 0%) Jan 01 00:01 Yearly.0
11% ( 0%) 9% ( 0%) Jan 01 00:01 Monthly.3
11% ( 0%) 9% ( 0%) Dec 01 00:02 Monthly.4
12% ( 1%) 10% ( 1%) Nov 01 00:02 Monthly.5
14% ( 3%) 12% ( 2%) Oct 01 00:01 Monthly.6
18% ( 4%) 15% ( 3%) Sep 01 00:01 Monthly.7
20% ( 4%) 18% ( 3%) Aug 01 00:01 Monthly.8
22% ( 3%) 20% ( 2%) Jun 30 23:59 Monthly.9
24% ( 2%) 22% ( 2%) May 31 23:59 Monthly.10
24% ( 1%) 22% ( 1%) Apr 30 12:27 Monthly.11
24% ( 1%) 23% ( 1%) Mar 03 13:21 CAM0951(1892145899)_filetran_sv-base.0
27% ( 4%) 26% ( 3%) Jan 01 00:01 Yearly.1

 

 

Volume filetrans
working...

%/used %/total date name
---------- ---------- ------------ --------
0% ( 0%) 0% ( 0%) Jul 14 09:30 PAR-NETAPP01(1892145899)_filetrans_sm.345 (snapmirror)
0% ( 0%) 0% ( 0%) Jul 14 09:00 hourly.0
0% ( 0%) 0% ( 0%) Jul 14 00:01 nightly.0
21% (21%) 15% (15%) Apr 01 09:30 PAR-NETAPP01(1892145899)_filetrans_sm.344 (snapvault)
23% ( 4%) 17% ( 2%) Feb 28 22:02 CAM0951(1892145899)_filetrans_sm.165 (snapvault)

Re: snapmirror issues

The first volume prod size is larger than the DR side so this will not work.  Also, both should be in the same unit.

 

Do yourself a favor, set both sides to 12TB  vol size volname 12t   - Start with that baseline and then you will be fine.  Snapmirror should work without issue

Re: snapmirror issues

I'm not seeing an issue with vol2... Seems lag time is very small..

 

What's the issue with vol2?

Re: snapmirror issues

THanks. Great stuff, things looking a lot better now.

Not done anything with volume 2, and it looks ok now.

 

You say both should be in the same unit? Do you mean source volume and snapmirror volume - Can you please expend on that?

 

Many thanks for your help.

 

Cheers.

Re: snapmirror issues

I'm not a fan of volumes of different units.. So your one was in K and one was in T.  I like to make sure they are in the same unit, either GB, TB with volumes that size. 

 

Also, if you were on 8.2.3, 8.2 introduced autoresizing of the DR side.