So, with SVM-DR, the destination volumes are never the same size as the source. It appears that they are 80 or 90% of the source, but as the source grows, the destination volumes do not autogrow. Is there some setting I need to enable on the destination SVM to prevent them from hitting 100%?
#SVM-DR and autogrow
gray meteor
gray meteor
just to clarify, autogrow is not the right answer here as the source does not want it on (and if we do a dr-failover, then update, then fail back, all my volumes now have autogrow enabled). I basicly want volume size to mirror the source. At some point in the past this is how it worked. Or at least give me an option to turn on size mirroring.
plucky flame
Hi, this is 'by design', what we do to achieve the exact same thing as you want is using 'vserver config override' commands on all destinations volumes to change their settings according to the source ( autosize mode , new-size, max-autosize, etc .....), if someone has a better/supported way i'm curious to hear it 🙂
gray meteor
Yes, well the design is wrong 😄 Or at least not without a way to override it. I am fine with needing to use config override on a read-only mirror, but as a storage admin I expect certain things to replicate that don't. Many years back when this broke (And I say broke, because it used to work and now it does not) things like percent-snapshot-space and volume size (and by extension when you resize a volume, the dest resized) used to replicate to the destination. I now have to develop complicated sync scripts for values that are part of a volume and run them hourly to update the destination. I have confirmed with Support that there is currently no other way to do this and will be submitting multiple RFE's to have this address. This will be my second time submitting it. IIRC, I sent them in about 6+ years back.