#SM Active Sync... should I be worried?

1 messages · Page 1 of 1 (latest)

pliant olive
#

Hi there,I have setup two C800 clsters with SM Active Sync on a VMWare vCenter using ONTAP Tools v10... everything seems OK... (it took a few tries) 😉
I am now having a checkup look.. and I can see that the volumes are not the same size...
SnapMirror show OK and in sync... the volumes are of cause in a consistency group, but still it bugs me...

`# ssh xx@vojstor "volume show -volume ds1"
Vserver Volume Aggregate State Type Size Available Used%

vojstor_vmware ds1 vojstor_01_SSD_CAP_1 online RW 37.40TB 7.40TB 79%

ssh xx@hadstor "volume show -volume ds1_dst"

Vserver Volume Aggregate State Type Size Available Used%

hadstor_vmware ds1_dst hadstor_01_SSD_CAP_1 online RW 34.37TB 3.79TB 88%`

Is this normal?

fathom glade
#

Just curious
What does “df -S -h” show for each of those volumes?

stark cliff
#

37.4TB - 7.4TB = 30TB used and 34.3TB - 3.79TB = 30.51TB. They are very close with regards to used size and some discrepancy is normal (snapmirror metadata overhead, SE differences, Snapshot differences, etc.).
For total size, destination volumes grow as-needed, assuming you have autosize enabled.
In other words - Yes, it's normal and no you shouldn't be worried.

pliant olive
#

But it's a snapmirror in sync.. the data is in sync.. but the volume details is not... makes no sense to me...

pliant olive
# fathom glade Just curious What does “df -S -h” show for each of those volumes?

Filesystem used total-saved %total-saved deduplicated %deduplicated compressed %compressed Vserver /vol/vol0/ 61GB 0B 0% 0 0% 0 0% vojstor-01 /vol/vol0/ 60GB 0B 0% 0 0% 0 0% vojstor-02 /vol/ds1/ 28TB 13TB 32% 14293651161088 32% - - vojstor_vmwareFilesystem used total-saved %total-saved deduplicated %deduplicated compressed %compressed Vserver /vol/vol0/ 60GB 0B 0% 0 0% 0 0% hadstor-01 /vol/vol0/ 56GB 0B 0% 0 0% 0 0% hadstor-02 /vol/ds1_dst/ 28TB 13TB 31% 14293651161088 31% - - hadstor_vmware

#

sorry for the formatting.. but it "closer" but unly because we use the "-h" option...

#

`Filesystem used total-saved %total-saved deduplicated %deduplicated compressed %compressed Vserver
/vol/vol0/ 64966544 0 0% 0 0% 0 0% vojstor-01
/vol/vol0/ 63627160 0 0% 0 0% 0 0% vojstor-02
/vol/ds1/ 30234319644 13995731508 32% 13995731508 32% - - vojstor_vmware

Filesystem used total-saved %total-saved deduplicated %deduplicated compressed %compressed Vserver
/vol/vol0/ 63581240 0 0% 0 0% 0 0% hadstor-01
/vol/vol0/ 59128780 0 0% 0 0% 0 0% hadstor-02
/vol/ds1_dst/ 31038241792 14121549376 31% 14121549376 31% - - hadstor_vmware`

#

One of the reasons I found this was that the volumes were filled over 80%, so our monitorig war triggered.. I then "fixed" the autoresize to trigger at 80%... on the primary volumes.. which they did... but they didn't on the destination.. and still haven't... and you cannot modify the destination volume because it is a snapmirror volume... so... again strange annoying issues...

#

I'm tempted to open a P3 on this...

pliant olive
#

... I was looking at the snapshots on the volumes, and they are not the same... so that can account for the difference I guess.. I just thought the snapmirror sync did all snapshots? But we have 81 on the source and 78 on the destination.. Also when running "snapshot show -volume sss -fields snapmirror-label" on the destination volume, it has no labels at all... strange...

fathom glade
#

There’s a kb to resize or make changes to a snap mirror destination

pliant olive
#

Error: command failed: Modification of the following fields is not supported on volume "ds1_dst" in Vserver "hadstor_vmware" because it is the destination of a SnapMirror active sync relationship: size, max-autosize, autosize-grow-threshold-percent, autosize-shrink-threshold-percent, autosize-mode.

#

I also just deleted some snapshots on the source... which isn't deleted on the destination... so that's just great..

slender flint
#

Just out of curiosity: Is this a flexgroup?

pliant olive
#

no, it's a consistency group...

#

pretty annoying if you ask me... or maybe I just want it to work like a MCC 😉

slender flint
#

I understand. It does work almost like a MCC. Same with snapmirro, let OnTap do its magic when updating. Volumes are never exactly the same.

slender flint
# pliant olive no, it's a consistency group...

Was curious, because I know there are some limits per volume and this seems like a pretty large volume. I tend to max 16 TB for VMware (depending on the average size of VMs). No more then 40-50 VMs per datastore

pliant olive
slender flint
#

Not sure if they are hard, but in my experience, I still keep them around max 40. And 16 TB

pliant olive
#

famous last words ;.)