>I am trying to use the changer option with the MRU software from >Compaq. This software has an entry point via the `robot` command and >has syntax such these examples: > > > robot load slot 0 drive 0 > > robot unload drive 0 slot 0
Then it should be reasonably simple to write the wrapper code Amanda needs to drive this. >Does anyone have any more information about configuring Amanda for >use with an MRU changer utility? Is it true that the "changerfile" >and "changerdev" variables are unnecessary? (as shown below) The "changerfile" and "changerdev" amanda.conf parameters are there to provide general purpose information to the changer script. Amanda does not use them at all. The script can use them for whatever it wants. In the letter you quoted, Nick says: (the script we use, chg-mru, can pull the changer[dev|file] options via libexec/getconf but I hardcoded them during testing). In other words, the script could have been generalized to use the values, but the programmer didn't feel like dealing with that during testing (as is often the case). The key point is this line: tpchanger "chg-mru" and Nick's comment that they use a script called "chg-mru". Reading between the lines, this says he wrote his own changer script (chg-mru) to interface between Amanda and the MRU (robot) command. That's the way it's normally done. Amanda defines an API for how it expects to manipulate a robot (docs/TAPE.CHANGERS). People write (simple) scripts that translate the Amanda requests into the appropriate commands. So what you need to do is con :-) Nick into giving you a copy of the chg-mru script he wrote. That's what you'll put in libexec. While you're at it, see if he'll send a copy to me and I'll put it in the Amanda release. If none of this works out (Nick may not be able to help for any number of reasons), let me know offline and I can probably put something together pretty easily. It looks like your "robot" command will be simple to use. >JF John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
