I'm learning about doing backups using the Grandfathers, Fathers, and Sons
backup process which at the end should result in about 19 volumes (GFS19).
I have three directories which contain volumes from three different pools for
the particular client I am backing up:
./<client-name>/daily - Differential Backup
(depends on either weekly or monthly to restore depending on when
backup was made)
./<client-name>/weekly - Full Backup
./<client-name>/monthly - Full Backup
I have tried running it, but I'm having trouble getting it started without an
issue with the weekly pool.
I decided to test out the backup functionality in a VM by starting with a
weekly-pool backup on the last Friday of the previous year (2016-12-30).
The dailys and the monthlys seem to be working as expected, but the weekly-pool
never seems to iron itself out to work correctly. This is important because the
first week of differential backups will depend upon that first weekly full
backup for restoration during the week of backups that follows.
To try and remedy the issue with the weekly pool volumes I tried initially
labeling a volume in the weekly pool, which would be numbered as the last in
the sequence of 4 weekly volumes (volumes 0-3):
*label storage=webserver-weekly-fileStorage slot=?(none)
pool=webserver-weekly-pool volume=webserver-weekly-volnum-3
And it appears in the attached backup plan.
The first backup / weekly backup is in the previous year (for testing purposes)
(note that the fathers / weeklys in red do not exist, they're only put there
for reference; The first backup weekly and of all is the 7 volume which as a
file would be called webserver-weekly-volnum-3 the last in a sequence of 4
labeled as [0-3])
The weekly volumes have the following VolumeUseDuration and VolumeRetention:
Pool {
Name = "webserver-weekly-pool"
PoolType = Backup
LabelFormat = "webserver-weekly-volnum-${NumVols}"
LabelType = "bareos"
ActionOnPurge = Truncate
MaximumVolumes = 10
MaximumVolumeJobs = 100
MaximumVolumeBytes = 10 g
VolumeRetention = 4 weeks
VolumeUseDuration = 2 days 22 hours
Storage = "webserver-weekly-fileStorage"
}
I expected that since I labeled the first weekly volume
webserver-weekly-volnum-3 (the last label in the sequence of [0-3]), running
subsequent weekly backups would result in the next volume being labeled
webserver-weekly-volnum-0, but instead it resulted in a volume labeled
webserver-weekly-volnum-1, and even after subsequent weekly backups run as they
would be in normal usage, only the weekly volumes [1-3] exist (I should have 4
not 3 weekly volumes).
The reason I thought this would happen is because in the other pools when the
first volume is written with similar labeling, it is written starting with a 0
volume; for example the webserver-daily-pool ends up with two volumes
webserver-daily-volnum-0 and webserver-daily-volnum-1 (however these are not
seeded as I have done with the weekly volume).
The only other solution I can see to thus would be to create all four volumes
and then set their volume status to some particular value (thought I'm not sure
which to use)...also it seems that something might need to be changed about
their statistics as well, like changing their VolumeUseDuration or
VolumeRetention counters to the proper values to ensure that
webserver-weekly-volnum-0 is used on the next weekly backup (and that the
others are set to Used recycled and written to in order).
So in summary, why do I end up with 3 weekly volumes instead of 4, and why
doesn't the webserver-weekly-volnum-0 appear as a volume if I pre-seed
webserver-weekly-volnum-3?
Thank you,
Andrew J. Leer
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
