Subscribe
Accepted Solution

Snapshot and SnapVault schedule conflict

I've been monitoring my SnapVault jobs via the filers but until I installed DFM I noticed that there are conflicts regarding the jobs. Could someone pinpoint me to where the problem exactly is? Each of my volumes is snapshoted at the hour between 6 am and 8 PM with a retention schedule of 1 week,  7 days and 12 hours. Each of my snapvault schedules do not start until 00:00. There are 3 Filers in this setup. 2 in the primary DC (active/active) and 1 in the DR site. Below is an output from the filers:

DFM ERROR:

Source    XXXXXXXXXXXXX:/vol1_ESX_VM_OSD_SAS

Severity    Warning

About   Schedule Conflicts with snapvault schedules .

Condition   Both snapvault and snaphsot schedules exist on this volume. 

Triggered   04 Jun 00:05

SECONDARY FILER'S SNAPVAULT STATUS

YYYYYYYYYYYY> snapvault status

Snapvault is ON.

Source                                      Destination                                                   State          Lag        Status

XXXXXXXXXXXX:/vol/vol1_ESX_VM_OSD_SAS      YYYYYYYYYYYY:/vol/VLT_XXXXXXXXXXXX/vol1_ESX_VM_OSD_SAS      Snapvaulted    13:17:18   Idle

SECONDARY FILER'S SCHEDULES

YYYYYYYYYYYY> snapvault snap sched

xfer   VLT_XXXXXXXXXXXX sv_nightly 7@mon-sat@0 preserve=default,warn=0

xfer   VLT_XXXXXXXXXXXX sv_weekly 4@sun@0 preserve=default,warn=0

PRIMARY FILER'S STATUS (XXXXXXXXXXXX)

XXXXXXXXXXXX> snapvault status

Snapvault is ON.

Source                                    Destination                                                 State          Lag        Status

XXXXXXXXXXXX:/vol/vol1_ESX_VM_OSD_SAS    YYYYYYYYYYYY:/vol/VLT_XXXXXXXXXXXX/vol1_ESX_VM_OSD_SAS    Source         13:47:13   Idle

PRIMARY FILER'S SCHEDULE (XXXXXXXXXXXX)

XXXXXXXXXXXX> snapvault snap sched

xfer   vol1_ESX_VM_OSD_SAS sv_nightly 2@mon-sat@0 preserve=default,warn=0

xfer   vol1_ESX_VM_OSD_SAS sv_weekly 1@sun@0 preserve=default,warn=0

XXXXXXXXXXXX> snap sched

Volume vol1_ESX_VM_OSD_SAS: 1 7 12@6,7,8,9,10,11,12,13,14,15,16,17,18,19,20

Snapshot and SnapVault schedule conflict

you can make snapshots with the snap command but also with the snapvault command.

so check snap sched and snapvault snap sched.

When using snapvault it is normal to disable the snap sched schedules.

Snapshot and SnapVault schedule conflict

XXXXXXXXXXXX> snapvault snap sched

xfer   vol1_ESX_VM_OSD_SAS sv_nightly 2@mon-sat@0 preserve=default,warn=0

xfer   vol1_ESX_VM_OSD_SAS sv_weekly 1@sun@0 preserve=default,warn=0

XXXXXXXXXXXX> snap sched

Volume vol1_ESX_VM_OSD_SAS: 1 7 12@6,7,8,9,10,11,12,13,14,15,16,17,18,19,20

snap sched:

The weekly (1) in snap sched will be taken at 0 on sunday and keeps 1

The daily (7) will be taken at 0 on mon - sat and keeps 7

The hourly ... no problem

The snapvault sv_nightly happens also at 0 and keeps 2

The snapvault sv_weekly happens also at 0 and keeps 1

So snap sched can be changed to 0 0 12@6,7,8,9,10,11,12,13,14,15,16,17,18,19,20

and problem will be gone.

Snapshot and SnapVault schedule conflict

Thanks, that makes a lot of sense, I appreciate your time explaining the problem and providing examples.