Very good.. Hoped to have igroup and lun mapping, but a script or wfa can handle that for us. Any reason that FSID isn't moved like 7-Mode did? Not an issue to remount at a DR site though. The qtree note is a good one to know, and hope to never see anyone mount a qtree path in the svm root namespace.

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Parisi, Justin Sent: Monday, July 6, 2015 7:08 AM To: Borzenkov, Andrei; NGC-g.milazzo-sinergy.it; Toasters Subject: 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.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

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.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

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.com Data: 06/07/2015 17:24 (GMT+01:00) A: Milazzo Giacomo G.Milazzo@sinergy.it Cc: "Borzenkov, Andrei" andrei.borzenkov@ts.fujitsu.com, Toasters toasters@teaparty.net, "Moore, Doug" 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.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