Multiple schedules == different backup sets?
-
I have noted with the schedules that we can setup multiple backup schedules per backup job. The schedule also indicate that different retention levels can be set and even force full backups.
Does this mean that each schedule manages it's own "backup set" (thus different snapshots per VM)? In our case, we just want to delay the start of the backup on a Saturday (currently backups are 4am each week day but on Saturdays we want it to only start at 10am).
-
@mauzilla
No if your doing delta with 2 schedule for example they will be part of the same chain, but you can setup different times for each day with different schedule yes. -
@darkbeldin said in Multiple schedules == different backup sets?:
No if your doing delta with 2 schedule for example they will be part of the same chain, but you can setup different times for each day with different schedule yes.
I think I may have done something wrong. I have 1 backup job. The backup job has 2 scheduled (called daily and Saturdays), with the only difference being that on a Saturday it starts at 10am where the rest of the days it starts at 4am. It however appears that there is now 2 seperate snapshots for each VM in this chain. It also seems that the Saturday schedule runs a backup for the week (so saturday to saturday) based on the data that was backed up / merged.
I can functionally understand why this is happening, but is there a way for me to have a single schedule / job but only have the time that it starts different? Also, if I remove the Saturday schedule, will it automatically remove the 2nd snapshot per VM that has been created?
-
I've done so that I have two separate backup jobs
- incremental every 4 hours, with exception on weekends. Retention usually 8 days
- weekly full backups, zstd compression, every Sunday night.
This way we have a separate backup from the incremental chain. We also are able to do more maintenance jobs on the nfs server etc during the off hours on the weekend.
