--On Wednesday, September 10, 2003 15:12:15 +1000 Craig Dewick <[EMAIL PROTECTED]> wrote:
> On Tue, 9 Sep 2003, Frank Smith wrote: > >> --On Wednesday, September 10, 2003 14:31:40 +1000 Craig Dewick <[EMAIL PROTECTED]> >> wrote: >> >> > >> > I'm thinking of building and installing Amanda on my Cobalt Raq2 unit, and >> > was wondering what experience any of you may have with doing this? >> >> I built a couple of 2.4.2p2 clients on Raq2s without any problems (other >> than having to build several other packages first). Never tried making >> one an Amanda server, they seem somewhat underpowered for that. >> What problems are you having? > > I'm not planning on using the Raq2 as the server - this machine (Sun Ultra > 60) is set up for that task. The Raq2 will just be a client. I presume the > stock gcc installation provided with the Cobalt Linux distribution will > build Amanda without problems? >From the few notes I have on the build, it looks like I had to build tar, gzip, and readline. I also built flex and perl, but I don't recall if those were for Amanda or something else we needed. Definitely don't use the tar that comes with the Cobalt. > The main problem on this system at the moment appears to be that Amanda is > viewing my single DLT-7000 drive (no autoloader) as a multi-slot device. > If the tape currently loaded isn't usable, I get asked to put a tape in > slot 2 (!) and hit 'enter'.... Sounds like you have a changer defined in your config file. > That's not physically possible with a single drive that doesn't have any > autoloader built around it. 8-) If the right tape in the sequence (I've > set the config to use 20 tapes in rotation) is loaded that problem doesn't > matter since 'amcheck' says the tape is ok and doesn't complain. > > Having to manually change tapes each day is annoying at times but with DLT > autoloaders taking enough tapes to suit my application being obnoxiously > expensive on the local Australian market, the single drive is a good > compromise. > > I also get no errors from any of the client machines from 'amcheck', but > when Amanda runs in the wee hours to actual perform the backups, there are > a errors logged in the report saying that disk partitions could not be > accessed. Possibly missing the SUID bit on some binaries on the clients? > On all my systems, I have created an 'amanda' user which the various > application programs run under. On the Sun boxes running Solaris, I made > 'amanda' a member of the 'sys' group which should give automatic access to > the disk devices without having to manually 'chmod' on the device files in > /dev/dsk so they can be accessed by members of group 'sys'. > > Perhaps I'm overlooking something... Time to re-read the documentation > again. If that fails, try posting your config file and relevant /tmp/amanda/*debug files. Frank > > Craig. > > -- > Email by Craig Dewick (tm). Home page at "lios.apana.org.au/~cdewick". > "[EMAIL PROTECTED]" or "[EMAIL PROTECTED]". > Explore and enjoy my public-domain Sun Microsystems technical data archive at > "www.sunshack.org", "www.sunshack.net" or "www.sunshack.info".
