Data: VMware data with deduplication on with SMVI snapshots
When considering SnapMirror for migrating data from the DS14 to DS4243 (for that matter, between disparate disk size aggregates), I have couple of questions around best practices
a) What are the dedupe recommendations/best practices - turn it on on the destination while SM is running and set it to auto? or perform dedup after SM baseline is done?
b) Since the # of drives and size of the drives are going to be different on Source and Destination, is it a best practice/recommendation to run wafl reallocate on the destination? If so, I am guessing that the dedup should be off?
c) Given the block transfer nature of VSM and b), should we use QSM instead? any preference?
Thanks for the responses. I am still a bit unconvinced about b), since I'll be moving snapmirror volumes between aggregates of different types and sizes. I've always been a fan of VSM but want to ensure that the data will be spread equally among all disks - if I need to run reallocate, I can. Will read up more and update this post.