ONTAP Build Process: Part 2 - Cron Schedules and Snapshot Policy

Note: As pre the previous post I'm highlighting where a naming convention might be required.

Cluster level cron schedules and snapshot policies

Firstly, we want to think about our snapshot policies.

Option 1 (standard):

• 18 x 4hourly snapshots (i.e. 3 days worth)
• 30 daily
• 3 monthly

Option 2 (Tamperproof for 3 days):

• 18 x 4hourly snapshots (these are tamperproof!)
• 30 daily
• 3 monthly

We want custom cron schedules too. Here I put "my" at the start of the cron schedule name to signify they are not default schedules.

job schedule cron create -cluster cluster1 -vserver cluster1 -name my4hourly -minute 0 -hour 0,4,8,12,16,20
job schedule cron create -cluster cluster1 -vserver cluster1 -name my4hourlytp -minute 0 -hour 0,4,8,12,16,20
job schedule cron create -cluster cluster1 -vserver cluster1 -name mydaily -minute 5 -hour 0
job schedule cron create -cluster cluster1 -vserver cluster1 -name mymonthly -minute 10 -hour 0 -day 1

We also want a schedule for 5 minutely snapmirrors that does not coincide with the snapshots.

job schedule cron create -cluster cluster1 -vserver cluster1 -name my5min03 -minute 3,8,13,18,23,28,33,38,43,48,53,58

Note: my4hourly and my4hourlytp is the same schedule, but if we want a different snapmirror label (my4hourlytp) we need to clone the schedule otherwise we get an error: Schedule "my4hourly" has prefix "my4hourly". Cannot associate another prefix "my4hourlytp" to same schedule.

Also create a 15 minute schedule for another offering (with lower RPO.)

job schedule cron create -cluster cluster1 -vserver cluster1 -name my5min03 -minute 3,18,33,48

Creating our 2 snapshot policies.

snapshot policy create
-vserver cluster1
-policy my18x4hourly30daily3monthly
-enabled true
-schedule1 my4hourly
-count1 18
-prefix1 my4hourly
-snapmirror-label1 my4hourly
-schedule2 mydaily
-count2 30
-prefix2 mydaily
-snapmirror-label2 mydaily
-schedule3 mymonthly
-count3 3
-prefix3 mymonthly
-snapmirror-label3 mymonthly

snapshot policy create -vserver cluster1 -policy my18x4hourly30daily3monthly -enabled true -schedule1 my4hourly -count1 18 -prefix1 my4hourly -snapmirror-label1 my4hourly -schedule2 mydaily -count2 30 -prefix2 mydaily -snapmirror-label2 mydaily -schedule3 mymonthly -count3 3 -prefix3 mymonthly -snapmirror-label3 mymonthly

snapshot policy create
-vserver cluster1
-policy my18x4hourlytp30daily3monthly
-enabled true
-schedule1 my4hourlytp
-count1 18
-prefix1 my4hourlytp
-snapmirror-label1 my4hourlytp
-retention-period1 3 days
-schedule2 mydaily
-count2 30
-prefix2 mydaily
-snapmirror-label2 mydaily
-schedule3 mymonthly
-count3 3
-prefix3 mymonthly
-snapmirror-label3 mymonthly

snapshot policy create -vserver cluster1 -policy my18x4hourlytp30daily3monthly  -enabled true -schedule1 my4hourlytp -count1 18 -prefix1 my4hourlytp -snapmirror-label1 my4hourlytp -retention-period1 3 days -schedule2 mydaily -count2 30 -prefix2 mydaily -snapmirror-label2 mydaily -schedule3 mymonthly -count3 3 -prefix3 mymonthly -snapmirror-label3 mymonthly

We don't need a SnapMirror policy since we'll be using the MirrorAllSnapshots default policy (with our custom 5 minute schedule.)

Repeat on the other (DR) cluster (so they have identical schedules and policies)!