I know this is old, but I was experimenting converting a windows file server to a netapp CIFS share and performing the data migration with Snapvault.

Here is what I have done that so far seems to have work gret though I am still testing...and it was arguably easier than the procedure in KB1010906.

I am interested to hear any comments or know if anyone has tried a similar procedure.

Assuming you already have a snapvault that you no longer want to update and want to make writable.

1. Create a flexclone of the snapvault destination. (not really necessary, but who wouldn't rather test on a copy) snapvault status will now show the flexclone is also a snapvault destination of the same source as the parent volume. 2. The qtree status still shows as "snapvaulted" and will not be writable. Perform a snapvault stop on the flexcone. This will delete formerly snapvaulted qtree. 3. perform a snap restore to the original snap shot you flex cloned.

All the data is there and qtree status shows normal. Create a CIFS share and create a new file/folder. Works!

--Jordan

-----Original Message----- From: Jordan Slingerland Sent: Wednesday, February 05, 2014 9:15 AM To: 'Sebastian Goetze'; Ray Van Dolson Cc: toasters@teaparty.net Subject: RE: OSSV / SnapVault Newbie - Scheduling an automatic update.

I have migrated windows file servers to cifs shares on the netapp using the method (or at least very similar to) the method in that kb. (1010906) It worked great for me though the snapmirror convert took a little while on a 1TB volume. (maybe 30m seemed longer with my fingers crossed and a r/o cifs share) I might suggest trying it in a sim or with a test volume first. You may even be able to flexclone the snapvaulted volume and perform the work on the flexclone for added safety. I have not tested that, just an idea.

--JMS

-----Original Message----- From: Sebastian Goetze [mailto:spgoetze@gmail.com] Sent: Wednesday, February 05, 2014 4:07 AM To: Ray Van Dolson; Jordan Slingerland Cc: toasters@teaparty.net Subject: Re: OSSV / SnapVault Newbie - Scheduling an automatic update.

Actually the base name *IS* important, but mostly for SV (not *OS*SV):

if you do

dest> snapvault snap sched -x napc2_p2_EFT1 eft_sched dest> 1@mon-sun@0,6,12,18

the -x will make it go to the source and pull the "eft_sched.0" snapshot (the latest one with the given base name) to the destination. In case of *OS*SV it will just start the (incremental) transfer, but afterwards - of course - the snapshot will be named according to the given base name.

HTH

Sebastian

On 2/4/2014 10:45 PM, Ray Van Dolson wrote:

Thanks. I actually ended up running:

dest> snapvault snap sched -x napc2_p2_EFT1 eft_sched 1@mon-sun@0,6,12,18

Am I correct in assuming that the "sv_hourly" name isn't significant? I couldn't find any indication in the man pages that it was, but may have missed something.

I now have the following snaps:

dest> snap list napc2_p2_EFT1 Volume napc2_p2_EFT1 working...

 %/used       %/total  date          name

---

 0% ( 0%)    0% ( 0%)  Feb 04 13:03  eft_sched.0
 1% ( 1%)    0% ( 0%)  Feb 04 12:49  red-str-napc2-p2(1574798766)_napc2_p2_EFT1-base.0 (busy,snapvault)
25% (25%)    9% ( 9%)  Feb 02 08:34  schedule_02022014_074939.0

The "schedule_02022014_074939.0" may be one I attempted to schedule from System Manager and then removed. Presumably this snapshot is safe to delete.

My intent is to ultimately convert this volume/qtree into writeable mode via NetApp KB 1010906. I haven't tried this with anything but the "base" snapshot present. I'm hopeful this won't cause any issues or confusion, but guess I can give it a test run.

Ray

On Tue, Feb 04, 2014 at 09:31:24PM +0000, Jordan Slingerland wrote:

...

So...it looks like yours will work except change hourly to sv_hourly

-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Jordan Slingerland Sent: Tuesday, February 04, 2014 2:34 PM To: Ray Van Dolson; toasters@teaparty.net Subject: RE: OSSV / SnapVault Newbie - Scheduling an automatic update.

Yeah, a separate one for hourly, nightly and weekly. Like this:

snapvault snap sched -x vol1 sv_weekly 5@sat@21

snapvault snap sched -x vol1 sv_nightly 5@mon-fri@20

snapvault snap sched -x vol1 sv_hourly 4@mon-fri@8-19

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-625460D9-A96 D-440E-BD8E-4D887FB36553.html

-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Ray Van Dolson Sent: Monday, February 03, 2014 12:01 AM To: toasters@teaparty.net Subject: OSSV / SnapVault Newbie - Scheduling an automatic update.

7-Mode ONTAP 7.1.2P4 as a secondary system and OSSV on Windows as a primary. I have a relationship established and have been doing manual, periodic "snapvault update"s to bring across changes.

I want to schedule this, but I'm not sure that snapvault snap sched is what I'm after or not. It seems to be about retaining snapshots of data and really I just want to keep one copy -- as up to date as possible (once an hour or so). We're preparing for a migration.

Maybe I do something like:

 snapvault snap sched -x <vol_name> hourly 1@mon-fri@0-23

?

Thanks, Ray

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters