Greetings,
I have this schedule
Schedule {
Name = "WeeklyCycle"
# Week Number A
Run = Level=Full Pool=File-Full-A-Pool oct 1st sun at 23:05
Run = Level=Differential Pool=File-Dif-A-Pool oct 1st wed at 23:05
Run = Level=Incremental Pool=File-Inc-A-Pool oct 1st mon-tue at 23:05
Run = Level=Incremental Pool=File-Inc-A-Pool oct 1st thu-sat at 23:05
# Week Number B
Run = Level=Full Pool=File-Full-B-Pool oct 2nd sun at 23:05
Run = Level=Differential Pool=File-Dif-B-Pool oct 2nd wed at 23:05
Run = Level=Incremental Pool=File-Inc-B-Pool oct 2nd mon-tue at 23:05
# Migrate the A pools to tape
Run = Level=Incremental Pool=File-Inc-B-Pool oct 2nd thu-sat at 23:05
# Week Number A
Run = Level=Full Pool=File-Full-A-Pool oct 3rd sun at 23:05
Run = Level=Differential Pool=File-Dif-A-Pool oct 3rd wed at 23:05
Run = Level=Incremental Pool=File-Inc-A-Pool oct 3rd mon-tue at 23:05
# Migrate the B pools to tape
Run = Level=Incremental Pool=File-Inc-A-Pool oct 3rd thu-sat at 23:05
# Week Number B
Run = Level=Full Pool=File-Full-B-Pool oct 4th sun at 23:05
Run = Level=Differential Pool=File-Dif-B-Pool oct 4th wed at 23:05
Run = Level=Incremental Pool=File-Inc-B-Pool oct 4th mon-tue at 23:05
# Migrate the A pools to tape
Run = Level=Incremental Pool=File-Inc-B-Pool oct 4th thu-sat at 23:05
}
I also have 2 migrate jobs that run opposite weeks.
Schedule {
Name = "MigrateA-Schedule"
Run = oct 2nd thu at 9:30 # to empty the prior volume set and move
Run = oct 4th thu at 9:30 # it to tape ready for the following week.
}
Schedule {
Name = "MigrateB-Schedule"
Run = oct 3rd thu at 9:30
}
(I have a monthly rotation already written but I'm using the weekly
rotation for testing)
the pools are auto labeling disk volumes of 2GBs each.
(will provide conf files if needed.)
so, the first week progresses filling the "A" pool set and the second
week starts filling the "B" pool set. as the volumes are created and
filled, they are marked full, and will be elegible for migration.
so at the end of any given week there will be one volume (the last one
in that week to have data stored into it) that needs to have its volume
status marked either as used or full so the migration job will pick it
up.
that last job will be an incremental and will only be a couple of days
old. (theoretically)
the way I understand it, Bacula would prefer creating new volumes if it
can before recycling the old ones.
so, my question is 2 fold. 1.) is there a way to programatically mark
that last volume as used/full so it gets migrated.
and how do I make it so that bacula will reuse the old volumes first
before making new ones. (I know I can use the "Maximum Volumes"
directive but I'm not sure how it will act if I get a dramatic rise in
the amount of data being backed up and it runs out of eligible volumes.
Thanks for any insight.
Fred
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
