2016-12-13 03:33 AM - edited 2016-12-13 03:45 AM
Short description of my environment: Data ONTAP 8.3.1, two clusters: clus1, clus2 (different physical locations)
In my environment I've got couple SVMs serving CIFS-only or CIFS/NFS data. Each primary_SVM (clus1) has it's secondary_SVM created on clus2 (different location) to which all volumes are replicating (via snapmirror). No customer access to secondary_SVMs. Both SVM subtypes are default. This configuration was created while those clusters were on ONTAP 8.2 (No "SVM_DR" available at that time). All volumes are being replicated, however secondary_SVM has no replication of CIFS shares or NFS export-policies. Please correct me if I'm wrong, but I understand such configuration as volume-level disaster recovery setup.
Lately a new SVM has been created, and since ONTAP version (8.3.1) gives us the possibility to create SVM DR relationship, the new_SVM (SVM subtype: default) in clus1 has it's new_SVM_DR (SVM subtype:dp-destination) on clus2. In this configuration all CIFS share information is also replicated to my DR site (clus2).
Now time for main main questions:
1. Is there any way I can transition/modify my old_secondary_SVMs (subtype: default) to DR_secondary_SVMs (subtype:dp-destination)? I would like to replicate CIFS shares information, and hopefully export policies for volumes and qtrees. What I would love is to avoid a need for data baseline transfers.
If there only way is a need to destory SVM_secondary and create a new one as subtype:dp-destination, but I can still keep the volumes on clus2 - I'll be able to resync volumes snapmirror without going through baseline again - that would be great!
2. My DR plan assumes: SVM_DR has a seperate CIFS server with seperate objet / different name joined to the same domain. During DR we would only create a DNS alias SVM_name (-alias->) SVM_DR_name. In such configuration we should set Identity-preserve to false - correct? How can I secure my NFS shares / export-policy information to DR site then? According to what I read, export-policy is only replicated if identity-preserve=true is set, but that would affect my CIFS config during DR.
Thanks in advance.
2016-12-13 03:50 AM
It sounds like you need ONTAP 9 that supports both converting regular snapmirror to disaster recovery snapmirror and identity preserve excluding LIF configuration.
2016-12-13 04:11 AM
thanks for a quick response! Does that mean that with ONTAP 8.3.x it's literally not possible to convert regular SM to disaster recovery SM, right?
I cannot find any good document that describes those functions in ONTAP 9, is there any 'data protection guide' or 'storage admin guide' for ontap 9, or not yet released?
2016-12-13 05:40 AM
There are thousands of pages of documentation plus TR. Download the ontap 9.x docs and you can go from there.
Also, i'm not sure why you wouldn't want to keep the CIFS server name in DR if its an active DR.
2016-12-14 01:31 AM
Does that mean that with ONTAP 8.3.x it's literally not possible to convert regular SM to disaster recovery SM, right?
That's something only NetApp internal can answer. I can only say that this feature is listed as new in ONTAP 9 release notes and is not documented in 8.3.x manuals.
2016-12-14 01:44 AM - edited 2016-12-14 01:50 AM
@JGPSHNTAPthanks! You have a good point! It's my lack of understanding the subject I guess.
If I decide to keep the same CIFS server name on my DR - how does that work during the potential disaster?
My primary site is not available, then I start SVM on my secondary_site.. Should I join the CIFS server to domain under same name as it was on source, or is CIFS server will automatically start as a member of domain, since it was somehow replicated from source?
I'm also confused about LIF replication. If I keep identity-preserve=true it wil also replicate my data/NAS LIFs.. I guess it's not only the LIF name, but also the IP configuration. In such cases both source and destination must configured wit the same VLAN, so they can keep same IP addresses, right ?
2016-12-14 04:16 AM
I would always recommend using identity preserve b/c of the CIFS server. You want the same cifs server name in DR, and not an alias or use of SPNS. It makes life easier.
If your primary site is down you don't have to do anything different, you bring up the DR site and flip your DNS (we use 3DNS GTM) so its auto for us, but that is how we do it.
In 9.0, we use identity preserve and discard network configs b/c our VLAN is different in the DR site.
There is tons of documentation on SVM DR, but for the old timers like us, this is pretty common from the 7-mode days. It was called vfiler-dr and works amazing
2017-11-20 07:32 PM
we have the similar issues after the 7 to C transition.
even i am in 9.2P1 , this one still not working
Converting volume-level SnapMirror relationships to an SVM disaster recovery relationship
From Data Protection Using SnapMirror®and SnapVault® Technology