[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bacula-devel] Remaining dual changer problems

Another way to look at this would be to start phasing out Bacula's knowledge
of physical location entirely and deal only with volume names. Autochangers
are getting smarter, and it really isn't Bacula's business how the changer
organizes it's volumes as long as the right volume appears where it's

That approach would permit keeping the mtx-changer syntax the same, and
implementing the volume->slot mapping inside the existing script shell. That
would permit putting logic into mtx-changer to do simple mappings for
simple-minded changers, or (in the case of more sophisticated changers, hand
off to a library manager application).

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Bacula-devel mailing list

This mailing list archive is a service of Copilotco.