Not sure about the security on the volumes, but the NTFS perms should follow, as long as its in the same AD domain, but the shares won’t follow; you will have
to recreate the shares. I would update the disk/shelf firmware prior personally.
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net]
On Behalf Of Jeff Cleverley
Sent: Friday, March 27, 2015 12:55 PM
To: <Toasters@teaparty.net>
Subject: Snapmirror relationships
Greetings,
We have to split a cluster and one shelf will go to one site, and the rest go to another site. The single shelf (DS4243, 2 TB SATA) comprising 2 aggregates and 11 volumes will get moved to a different NetApp. The shelf will end up on
a system with new names and no aliases can be used. There are some variable moving parts so I need a sanity check.
FilerA 7.3.7 - owner of the one shelf
FilerB 8.1.2P4 - soon to be owner of the one shelf
I've setup a snapmirror with a daily cron update that goes from FilerA to FilerB. This seems OK. If we can get the shelf owners to split the same day the other moves, I'm just going to move the shelf, change ownership, import the aggregate/volumes,
create cifs shares, and update the snapvault relationship.
If they insist on moving before that, I have to break the mirrors after a final sync, rename the current snapmirror destination volumes, update snapvault relationships and create cifs shares. This seems OK.
Now the questions :-)
1. Are there any issues associated with this process with the OS differences or snapmirror not keeping filesystem security type, share, permissions, etc?
2. If I have to split the shelf later, I want to add it to FilerB and make that shelf the production shelf. This is a short term solution and the heads and shelves are not supported. Is there a graceful way to sync back to the DS4243
shelf? I don't want to disrupt the CIFS users very much.
3. Any other glaring issues that stand out?
Thanks,
Jeff
--
Jeff Cleverley
IT Engineer
4380 Ziegler Road
Fort Collins, Colorado 80525
970-288-4611