R: SVM DR in 8.3.1 - AGAIN

Not sure about this workaround. You write:

first create snapmirror with identity-preserve true; then delete (without breaking) and create again with identity-preserve false

If I start snapmirror destination volumes will be read-only, so, also if I will have the destination SVM started I will not able to write into…or do I loose some step?

In the meantime we’ve decided to use the SVM DR with 8.3.1 only for the CIFS SVM that contains a lot of complex configurations to replicate (users, domain joins and sec, groups, shares..).

The other SVM, mostly NFS, for the purpose of DR testing with up and running SVM (our goal as in my first mail) we will have an SVM DR to break and start for DR testing purposes, and of course, identity preserved. At the same time the source SVM will be replicated on a second destination SVM and, work in progress, with WFA its volumes will ben cloned and exported with old names and exports replicated.

Bye

Da: Borzenkov, Andrei [mailto:andrei.borzenkov@ts.fujitsu.com] Inviato: lunedì 20 luglio 2015 07:57 A: Moore, Doug Doug.Moore@netapp.com Cc: Milazzo Giacomo G.Milazzo@sinergy.it; Parisi, Justin Justin.Parisi@netapp.com; Toasters toasters@teaparty.net Oggetto: RE: SVM DR in 8.3.1 - AGAIN

Original question was - is it possible to start DR SVM with identity-preserve without stopping SnapMirror. It looks like it is possible.

Regarding “future snap mirror updates” - I mentioned that if I switch back from identity-preserve=false to identity-preserve=true changes made in the past (during identiry-preserve=false relationship) are replicated. They are even applied to a running DR SVM, and e.g. LIF gets configured while DR SVM is running.

I do not promote or endorse it - as I said “I am not sure if it works as intended”. But I can see use cases for it.

From: Moore, Doug [mailto:Doug.Moore@netapp.com] Sent: Sunday, July 19, 2015 7:44 AM To: Borzenkov, Andrei Cc: NGC-g.milazzo-sinergy.it; Parisi, Justin; Toasters Subject: Re: SVM DR in 8.3.1 - AGAIN

What are you trying to accomplish? The setup you have below is clearly not a use case that we advise. Anything that is sent in the initial ID preserve that is not then sent in the id discard will not be replicated in future snap mirror updates. So why would you do it that way? Doug Moore Technical Marketing Engineer Clustered Data ONTAP/Multi-Tenancy

NetApp 303.349.4851tel:303.349.4851 Direct / Mobile doug.moore@netapp.commailto:doug.moore@netapp.com www.netapp.comhttp://www.netapp.com/

On Jul 18, 2015, at 13:36, Borzenkov, Andrei <andrei.borzenkov@ts.fujitsu.commailto:andrei.borzenkov@ts.fujitsu.com> wrote: Not sure if it works as intended, but - first create snapmirror with identity-preserve true; then delete (without breaking) and create again with identity-preserve false. Now you have SVM that contains original configuration but can be started without breaking SnapMirror. To continue just resync.

OTOH it is logical. In case of identity-preserve is false, network configuration of DR SVM is not changed at all and where it came from originally does not matter.

If you delete snapmirror and recreate with identity preserve again, changes made in between on source are propagated to DR.

Of course, it does not have ability to select arbitrary snapshot as starting point (and as most part of SVM configuration is not kept in volume, it would not help anyway). I do not know if RDB even has anything similar to snapshots that could be employed here.

From: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Milazzo Giacomo Sent: Wednesday, July 08, 2015 9:06 PM To: Parisi, Justin; Toasters Cc: Moore, Doug Subject: R: SVM DR in 8.3.1 - AGAIN

We’re still experiencing a lot of issues with customer where first few days ago we’ve attempted to set up this SVM DR. As reported it seems that it does the work that someone could expect as…basic way. But at this customer the world is a little bit more complicated (does it is the only one using that DR way with 7Mode? I don’t think so!)

We need to understand how to proceed to set up this DR. Or we (better NetApp!) must officially communicate to customers that they can wast their –perfectly working for test and troubles- DR approach for it’s not possible in cDOT!

Let me resume the issue. This customer, since years, doesn’t use the vFiler DR direct approach but, at the snapmirrored destination flexclone volumes are created and on this run vfiler with –d option that start from the root volume of the vfiler.

I.e. (the green stands for running, the red for stopped/offlined/mirrored) ✓ ✓ X ✓ ✓ Production ----sm---> DR ---flexclone---> DR_clone –vfilercreate --> vfiler in dr

This permit to have a point in time instance with all the initial configurations (share/exports/MSAD domain join, users, security ecc). This also let have the choice to choose the snapshot used as starting point and, overall, this let to maintain the source-destination replicas active and updated.

All of those is automated using WFA, so it’s enough a click and everything go!

We’ve seen that SVM DR more ore less work as vfiler dr worked. ✓ ✓ X Production ----sm---> DR < break of mirror relationship – a MUST > X X ✓ Produzione ----sm---> DR

We’ve also seen with some trick and maintaining the production and test network separated in different IP spaces (and ports, switches, vlan…) that we can have both running the source and the destination, but we must also break the sm relationship!

✓ X ✓ Production ----sm---> DR

These releationships unfortunately are essential prerequisites for this customer. Let me say vols (in SVMs) must continue to replicate for the DR test SVM could be up also for 10 and more days! And customer cannot permit the risk to loose its replicated/updated copies…

The questions are: is there something like vfiler create –d? (documentation does not report anything else than “normal” usage) Something that let us create an SVM with all configurations inside but starting from cloned vols at destination snapmirrored site?

We’re really in trouble for customer is starting to suspect that this cDot could be a boomerang and, except for VSAN and VVOL support for VMware 6, the things they’ve loosed are more than the one they’ve gained!

Any help will be appreciated!

Da: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] Per conto di Milazzo Giacomo Inviato: lunedì 6 luglio 2015 17:33 A: Parisi, Justin Cc: Toasters; Moore, Doug Oggetto: R: SVM DR in 8.3.1

We need identity true. a lot of cifs configuration are not brought if false. Think to vfiler Dr of 7mode...

Bye

- Sent by mobile -

-------- Messaggio originale -------- Da: "Parisi, Justin" <Justin.Parisi@netapp.commailto:Justin.Parisi@netapp.com> Data: 06/07/2015 17:24 (GMT+01:00) A: Milazzo Giacomo <G.Milazzo@sinergy.itmailto:G.Milazzo@sinergy.it> Cc: "Borzenkov, Andrei" <andrei.borzenkov@ts.fujitsu.commailto:andrei.borzenkov@ts.fujitsu.com>, Toasters <toasters@teaparty.netmailto:toasters@teaparty.net>, "Moore, Doug" <Doug.Moore@netapp.commailto:Doug.Moore@netapp.com> Oggetto: RE: SVM DR in 8.3.1 You can always run the destination in the “Identity discard” mode to avoid IP clashes. That should allow you to test.

I’ve added the SVM DR TME to this thread so he can address your questions/be aware of the questions we have out there.

From: Milazzo Giacomo [mailto:G.Milazzo@sinergy.it] Sent: Monday, July 06, 2015 11:10 AM To: Parisi, Justin Cc: Borzenkov, Andrei; Toasters Subject: R: SVM DR in 8.3.1

Again, interesting for it summarize the two official docs. We’ve just created a test and it seems to work: unfortunately up to now we don’t have yet the physical network correctly cabled to the right switch.

We’re concerned about the statement “source SVM must be stopped” to run in DR…this because we’ve an isolated network environment and when we run DR test the source still continue to work…fortunately we’ve test the “force” option to the start SVM command…

A doubt. We’ve noted that when the SVM DR has been created automatically has been created its LIF for data communication (our test contained a CIFS server with a shared vol). This LIF has been created using the VLAN that was assigned to the ipspace we’ve created to the test network, and the same IP of source has been assigned. That’s what we expect, and it’s good.

But, what happen if I’ve a lot of source SVM, each with its subnet and broadcast domain that must converge in the same test ipspace? How the lifs and their IP addresses are choosen?

Regards,

Da: Parisi, Justin [mailto:Justin.Parisi@netapp.com] Inviato: lunedì 6 luglio 2015 16:08 A: Borzenkov, Andrei; Milazzo Giacomo; Toasters Oggetto: RE: SVM DR in 8.3.1

I wrote a blog on SVM DR, if you are interested:

https://whyistheinternetbroken.wordpress.com/2015/06/25/techstorage-virtual-...

From: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Borzenkov, Andrei Sent: Wednesday, July 01, 2015 10:05 AM To: NGC-g.milazzo-sinergy.ithttp://NGC-g.milazzo-sinergy.it; Toasters Subject: RE: SVM DR in 8.3.1

You are right, you need to create destination SVM in advance with right attributes.

According to documentation “For remote data access or data distribution, you can provide read-only access to the NFS clients and SAN hosts from the destination SVM, if you chose to set the identity-preserve option to false.”. Also “SVM Disaster Recovery Preparation Express Guide” gives examples that indicate that you can (actually, must) configure network on destination SVM and access it.

From: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Milazzo Giacomo Sent: Wednesday, July 01, 2015 4:33 PM To: Toasters Subject: SVM DR in 8.3.1

Hi all,

I know is still RC1 but prior to upgrade a running 8.3 I would try to have more info on a new 8.3.1 feature: the SVM DR.

I’ve a customer that on 7Mode ran the DR of CIFS vfiler (joined to a domain) using snapmirror of the vfiler vols, including the root one, and at the DR test/run the source vfiler was stopped and a vfiler create –d command, with the mirrored root specified, let the destination vfiler start with all domain infos, shares on the vole and ip addresses on the DR site with minimal effort.

I’ve read the docs that come with 8.3.1 but is not clear.

I don’t think that there’s something in SVM DR that permit to recreate the SVM on the destinanation: this must exist in advance, in stopped mode, right? What’s about the maintenance of the IPs? Should I have two identical subnets in both clusters? What if I cannot have two different subnets? Do I have a way to let the replicated SVM being in standby with the data lif with preregistered IPs?

Regards