Hi, we are running snapmirror here to move a 350GB volume from our F630
to our new F760. Since we set it up last week, I have noticed a 'bug'
in the snapmirror procedure:
We set up the 2 volumes with the same amount of raw space. However, the
source volume had a snap reserve of 5%, so we changed to target volume
to snap reserve of 5% before taking it offline. We started the
snapmirror, and the volume filled up to 103%. I checked, and the snap
reserve had been reset to 20%, thus reducing the free space on the
target volume, and preventing the mirror from completing. I made the
volume writable, and tried to reset the snap reserve to 5%, but the same
thing happened. I only succeeded in completing the mirror by adding a
disk to the target volume, thus allowing enough space, even with a snap
reserve of 20%. This sounds like a bug - why should snap reserve be
reset on the target volume? Has anyone heard of this before?
Thanks,
Moshe