Hi,
Kern Sibbald wrote:
On Monday 12 March 2007 04:05, Troy Daniels wrote:
Greetings Listers,
Last week I upgraded my Bacula install to 2.0.2 without any issues
during the upgrade process.
All seemed to be working well until Friday, but that was only because I
hadn't discovered this issue yet.
I run several jobs each night, with Full backups on Friday night and
incrementals every other night. Once the backups are completed I have
bacula setup to verify a few of these tape jobs against the catalog with
Volume to Catalog jobs.
These verify jobs have a higher priority, so they shouldn't start until
after the backup jobs are complete. I also schedule them to start 10
minutes after the backups at 23:15. (All backups are scheduled to start
at 23:05)
This behaviour seems to have changed in Bacula 2.0.2 however. They seem
to launch immediately and select which tape they'll use for the verify.
Here's a log excerpt from a job running under 1.38.5 (My old version)
02-Mar 01:09 backup1-dir: Verifying against JobId=6017
Job=fs1.2007-03-01_23.00.00 02-Mar 01:09 backup1-dir: Bootstrap records
written to
/export/bacula/var/backup1-dir.restore.Verify-fs1.2007-03-01_23.15.00.b
sr 02-Mar 01:09 backup1-dir:
02-Mar 01:09 backup1-dir: The job will require the following Volumes:
02-Mar 01:09 backup1-dir:
02-Mar 01:09 backup1-dir: 000009
02-Mar 01:09 backup1-dir:
Even tho it was scheduled to run at 23:15, it didn't start until 1:09
the next morning. This is the expected behaviour.
Here's a log excerpt from Friday night under 2.0.2:
09-Mar 23:15 backup1-dir: Verifying against JobId=6101
Job=fs1.2007-03-08_23.00.00 09-Mar 23:15 backup1-dir: Bootstrap records
written to /export/bacula/var/backup1-dir.restore.11.bsr 09-Mar 23:15
backup1-dir:
09-Mar 23:15 backup1-dir: The job will require the following
Volume(s) Storage(s) SD Device(s)
=======================================================================
== == 09-Mar 23:15 backup1-dir:
09-Mar 23:15 backup1-dir: 000010 Tape
OfficeAutochanger 09-Mar 23:15 backup1-dir:
10-Mar 20:57 backup1-dir: Start Verify JobId=6125 Level=VolumeToCatalog
Job=Verify-fs1.2007-03-09_23.15.00
As can be seen, the job started at 23:15, selected tape '000010' and
then waited until the next night to run (Full backups take most of a day
) Meanwhile, the full backup ran, writing to 2 other tapes.
The problem encountered by bacula is that tape 000010 had been removed
from the Autochanger on Friday morning and replaced with this weeks
incremental tape. So Bacula blocked, waiting for a tape, until I
discovered and cancelled this job this morning. Not ideal, but it did
bring this issue to light.
What I'd like to know is if this was a deliberately designed feature, or
if it classifies as a bug? If it's deliberate, is there anyway to
control when it performs it's tape selection, or even which job it
verify? I've scanned the Jobs section of the latest manual but didn't
see anything obvious.
For now I can either work around it(With a Run script running the verify
job), or even work with it (I've wanted to run the Full Backup job
verifies on Sunday for a while anyways.)
To the best of my knowledge there is no deliberate change in the way
Verify jobs are run.
You haven't supplied sufficient information, so I am not able to
understand the problem.
Doh, and I thought I'd described the problem well. Take 2.
Not sure what else to say about it. Maybe if I summarise it a bit more (My
previous attempt was a bit verbose)
When a verify job is scheduled under 2.0.2 to perform a Volume to Catalog
verify it now selects the job to be verified (and the associated tape(s))
at the scheduled start time. It then waits until all jobs of lower priority
finish before performing the actual verify. This results in it verifying
the previous nights backup instead of the current nights one.
Under 1.38.5 the job wouldn't select the job to verify until it actually
ran (Actual start time instead of scheduled start time). In my case this is
after the job I actually want to verify has finished running for the
evening.
OK, thanks. This time, the problem is crystal clear. The above describes what
I need to know/understand.
I haven't looked at the code, but I suspect that some of the startup code was
moved earlier in the process. In general this was done so that the catalog
entries are more complete if the job is subsequently cancelled before it is
actually started.
In this case, if this is what happened, I can see that this will create a
problem for you. However, it does seem to make sense that the Verify job
would select the job to be verified when Verify is scheduled rather than at
some later time when additional jobs may have run.
I'm not sure what the solution is. It seems there are two ways to resolve it:
1. Start the Verify immediately after the backup (probably with a RunScript.
2. Put the code back the way it was in 1.38.11 (assuming that is the problem).
Do you or anyone else on this list have any comments on the above two possible
solutions?
Best regards,
Kern
This is the core of the problem I wanted to highlight, and you can see in
the above quoted email log excerpts showing the different times the
job/tape selection was performed.
Maybe an example will help too.
At 23:05 every night, backups of my servers are scheduled to commence. All
servers are backed up concurrently.
At 23:15 every night, VolumeToCatalog verify jobs of certain backup jobs
are scheduled to commence. These jobs have a higher priority than the
backups so they will wait until they are finished.
Under 1.38.5, the job to be verified wouldn't be selected until the verify
job ran. This meant it picked the job that had run that night at 23:05.
Under 2.0.2 the job to be verified is chosen at 23:15. The job I want to be
verified is still running, so isn't chosen. Instead the previous nights job
is selected. The verify job then waits until all other jobs are finished
before running the verify.
Hope this is enough information, if not please advise what you need so I
can supply it.
Cheers,
Troy Daniels
iTouch Australia
Regards,
Kern
-------------------------------------------------------------------------
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 < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users
-------------------------------------------------------------------------
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 < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users
