On Thursday 15 March 2007 04:38, maseda < at > un... wrote:
Upon running a migration job, bacula asked me to load one of my
cleaning tapes... Then, I updated the MediaId in the Media table to
correspond with the tape that bacula should have been looking for...
This caused bacula to successfully complete the migration job...I think
bacula should have been looking for a specific VolumeName *not*
MediaId... I like bacula, but this is just wrong... Btw, this problem
occured because I changed some of my MediaIds a while back (I can't
help it sql is fun and I'm a control freak
)... But still, i think
bacula should have asked me to load tape "MSR100L3" or whatever... Ya
know?
If you modified a MediaId in the Media table and you don't understand the full
details of how the database is organized and linked together (e.g. where to
find *all* references to the MediaId), you have probably damaged your
database.
While certain fields can be modified directly via SQL, MediaIds are not one.
For the record, I discourage all users from doing similar things, and I can
assure you, it is not something that I would personally do.
To the best of my knowledge the only place Bacula ever asks for a MediaId is
when it asks you to select a particular Volume during the update command (and
possibly some other ones).
If you decide to respond to this with a bit more concrete information, please
read the Support page on the bacula web site (www.bacula.org -> Support)
first.
