Hi Kenneth,

Sto is right. The procedure you suggested will not work for us. This link resumes the issue: http://forums.netapp.com/conversation.asp?vid=49303&tid=1&thd=1 But I cannot get hold of Steve Waggott's document. Can anyone else help?

On Dec 9, 2007 1:12 AM, Sto Rage(c) netbacker@gmail.com wrote:

That procedure is for moving QSM and not for moving snapvault destination. Plus as the OP mentioned, you cannot SM from a trad to a flex vol so the procedure won't work in this case. -G

...

Hi

I think the procedure here could help: http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb468

It's a bit long and complex and the big downside is that you will temporarily need to have a third copy of the data as you migrate from the original trad vol destination to the new flex vol destination.

cheers Kenneth

Kenneth Heal Storage Consultant Databasement BV

---

...

Date: Sat, 8 Dec 2007 14:34:19 +0100 From: bob.doho@gmail.com To: toasters@mathworks.com Subject: traditional SnapVault destination vol to flex vol convertion

question

...

Hi guys,

We need to convert traditional SnapVault destination volume (2TB) on a R200 to flex volume. We want to keep the snapvault snapshot to avoid doing another base transfer from source located in another data center. VSM is not possible. QSM will not copy the snapshots. We have heard that there is a procedure with snapmirror –s options that do the trick. Can someone help us with that procedure? Many thanks in advance.

Thanks,

---

Express yourself instantly with MSN Messenger! MSN Messenger

Unfortunately, since it's a Snapvault destination, it will have (probably many) qtrees and very little non-qtree data.

-- Adam Fox adamfox@netapp.com

-----Original Message----- From: Miller, Michael CTR USTRANSCOM J2 [mailto:michael.miller.ctr@ustranscom.mil] Sent: Monday, December 10, 2007 2:10 PM To: Bob Doho; toasters@mathworks.com Subject: RE: traditional SnapVault destination vol to flex vol convertion question

I got the following from Bob Jenkins of NetApp some time ago. I don't know if it will work for what you are asking but it does copy traditional volumes to flex qtrees quite nicely. I have used it many times since I got it.

Filer> snapmirror initialize -S sourcefiler:/vol/vol2/- destfiler:/vol/v3/vol3 Note the - on the source spec ^ its required This copies all NON-qtree from the source to the destination. The destination qtree (i.e: vol3) must not exist but MUST be specified.

Mike Miller Site Lead HQ DIA OGW-4 General Dynamics Information Technology Michael.Miller.ctr@ustranscom.mil Michael.Miller@gdit.com Phone: 618-229-1428

-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Bob Doho Sent: Saturday, December 08, 2007 7:34 AM To: toasters@mathworks.com Subject: traditional SnapVault destination vol to flex vol convertion question

Hi guys,

We need to convert traditional SnapVault destination volume (2TB) on a R200 to flex volume. We want to keep the snapvault snapshot to avoid doing another base transfer from source located in another data center. VSM is not possible. QSM will not copy the snapshots. We have heard that there is a procedure with snapmirror -s options that do the trick. Can someone help us with that procedure? Many thanks in advance.

Thanks,

That's a bit easier. You can use vol copy/aggr copy or VSM to do that since those are block for block copies, you should be fine. The reason it's easier for you is you're staying within the same volume type (flex -> flex). Going between volume types is more complicated.

-- Adam Fox adamfox@netapp.com

-----Original Message----- From: John Stoffel [mailto:john.stoffel@taec.toshiba.com] Sent: Tuesday, December 11, 2007 3:13 PM To: Fox, Adam Cc: Miller, Michael CTR USTRANSCOM J2; Bob Doho; toasters@mathworks.com Subject: RE: traditional SnapVault destination vol to flex vol convertion question

This is an interesting thread. To ask a slightly different question, can I move a destination snapvault from one aggregate to another on a filer without having to re-sync all my data across the WAN?

I'm happy to stop SV on the source, wait til the destination is queisced, and then copy the data to a new location. But I want to re-start the snapvault without having to start all over from scratch.

Doable? The man pages I've looked at aren't quite clear on this.

Thanks, John

John> This is doable. I've moved snapvault destination volumes John> between aggregates without issue. Stop the snapvaults, vol copy John> the data, offline the old volume, rename the new volume and John> start the snapvaults again.

Duh... makes sense. I wasn't even thinking of the vol copy for some reason, mostly because I do it so infrequently.

Hmmm... the only problem is that I've got qtree based SnapVaults as well, and I'd probably prefer to move them instead if I can. But I think I need to move on a per-volume basis instead. Grr...

Thanks! eheerder, suspected terrorist