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 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.0The "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-A96D-440E-...
-----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