2011-04-18 08:46 AM
I was creating a relationship that did the local backups, then used the backup and mirror policy. When I added the protection policy to the dataset, the backup volume created was the size I expected, but the mirror reported being the same size as the aggregate when the volume should have been much smaller. Once we created everything, the volume was actully the size of the original volume. Is this a known bug that it reports this way or has anyone seen this before?
2011-04-18 10:06 AM
No, this is expected behavior. The "size" of a volume gets a little tricky when SnapMirror is involved. When a volume is a VSM destination, it actually has two sizes: the size it was created with and the size reported by the "df" command. "df" will report the size of the source volume as of the time the last VSM update started (IOW, the destination volume looks like it's the size of the source volume). If the source volume grows, the next update will make the destination grow too.
This works to a point but if the source volume grows larger than the destination volume at the time the destination was created (that's the other size), the next VSM update will fail.
To avoid this situation, ProtMgr generally creates VSM destination volumes to be the size of the destination aggregate. It's actually a bit more complicated than that but the idea is to keep mirror updates from failing because we guessed wrong when creating the volume in the first place.
2011-04-18 08:42 PM
If the volumes are empty volumes, its better to size the Mirror destination volumes to smaller size, as most of the resources are spent in scanning.
Its better to size it appropriately if the volume used size is little or 1/10 of the Aggr size.