2012-03-10 11:34 AM
Trying to find a solution to an issue I'm having with a client and vFiler DR configurations.
Is it possible to use the nifty "/-" wildcard when setting up the SnapMirror relationships between the two sites for the DR vFiler?
Reason being - primary site utilizes a 64-bit aggregate, destination utilizes a 32-bit aggregate. I know that you can use the /- wildcard to do QSM when no qtree exists (thus how you are able to replicate from one aggregate type to another as is in this case).
It seems that vfiler dr config does not like trying to utilize SnapMirror in this way. Tried it a couple of times and unless I'm doing something wrong, it's not working at all.
I've presented options to the client:
So, situation is quite tricky. Reaching out to all NetApp geniuses for assistance / advice.
2012-03-10 01:23 PM
i think putting /etc for vfiler root (qtree path) is the way to go an utilise qsm until the other boxes are upgraded and then change them to vsm afterwards, not sure which replication technology the vfiler dr commands use qsm or vsm but you can alyways initialise them manually, I dont think it will be block replication for qsm paths
2012-03-10 07:13 PM
Are you trying to setup permanent DR relationship or just one off migration?
For a single migration run I guess it could be possible to use volume-to-qtree QSM (/- => dest:/vol/new/qtree) and then use “vfiler create -r /vol/new/qtree” to recreate vFiler on destination. Keep in mind, that you may not have any qtree inside this source volume – it will not be replicated.