Hi,
I'm curious about your standards and strategies for schedules/schedules policies names (I'm not using plans). I saw this topic: What is your naming convention for schedule policies? | Community but maybe someone has fresh idea.
We have VMs, DBs, FS and more. We have about 80 schedules. For a long time we were using something like:
-
DC1-VM-I_I_I_I_I_F_N-21:00which means: Location, VMs, Mon-Fri Incremental, Saturday Full, Sunday none, 9 PM
another example:
-
MSSQL-N_SF_N_SF_N_F_N-21:00-LOGS_4H- I think it's clear (SF - Synthetic Fulls, makes no sense here but it’s just example)
But in reality, including DC name doesn't make much sense. There was also no good way to include the incremental backup time if it was different from the full backup time. And it turned out to be better to keep logs in separate schedule policy because it's easier to resue.
Now I'm thinking about something like:
-
VM / Inc Daily / Full Sat 21:00 -
MSSQL / SFull Tue, Thu / Full Sat 21:00 -
MSSQL / Logs 4h
I think it's much easier to read. The Downside is that you can't easily include information like "no backup on Sunday" without hurting readability.
Another thing: it would be nice to have these schedules numbered somehow, because when associating a schedule policy with a subclient, they appear in alphabetical order. Ideally, I'd like all full backups to be grouped by time order instead.
Share your ideas. It's not the most important thing, but I like when everything is intuitive and easy to use.
