Assuming the specified schedule, volume retention, and job
retention... is there a possibility that you can have a failed
full backup on the 1st Sunday that leaves you without any backup
for 24 hours? (Previous full one has expired in terms of
retention, which kills all incremental and differentials for the
previous month. So, doesn't it mean that there is no backup
until the next one completes?)
Should retention periods be setup so that they are 1 month + 1
day?
Any backup staggered rotation scheme (different pools & retentions) requires at least two version of the same backup level (IMHO). While the last job is resting, you run a new one. E.g. monthly backups should have at least 60 days retentions.
Btw: you can still restore expired backups, at least until they are recycled.
Also, it seems that job and volume retention should be the same
in most cases. It appears to not be useful to have one without the
other. job without volume can tell you where the file used to be,
and volume without job makes it near impossible to find a given
file... correct?
Schedule {
Name = "WeeklyCycle"
Run = Full 1st sun at 23:05
Run = Differential 2nd-5th sun at 23:05
Run = Incremental mon-sat at 23:05
}
===========================================================================
Heitor Medrado de Faria | Bacula do Brasil
============================================================================
Indicamos também as capacitações complementares:
============================================================================
