We have 2 pairs of v-series filers that are in a snapmirror relationship. When they were originally set up the volumes on the source and destination were set up with no space guarantee, fractional reserve=0% and snap reserve =1%. Every other option is defaulted (nosnap=off, try_first=volume etc). There are no LUN's allocated to the volumes, all of volumes are shared out as CIFS exports. To me this seems a little dangerous unless you have good monitoring in place to keep an eye on the aggregate usage.
In the past when i have set up snapmirrors i created the source volumes with guaranteed space and aded the autosize option, if i felt i may need it. Then set the volumes on the destination to the same size as the maximum specified by the autosize option either by setting this. And as a back up make sure the autodelete oldest_snap is enabled as well. This in my mind means at worst i will take a volume offline on the source and should the need arise where we need to use the destinations as the source following a DR or something, then all the volumes are the same size.
I wonder though before i go making changes to this snapmirror configuration that has been created what the thoughts of the community would be.
Would you tend to create snapmirrors with guarantees on the volumes (both source and destination) rather than none?
Would you create the destination volumes with no guarantee and maybe several times the maximum size of the source instead?
I would be interested in getting peoples opinions or comments based on experience on this?
Message was edited by: Andrew Pilgrim
Was wondering if anyone had any thoughts on this? Thank you.