planner and sendsize

Here it goes something interesting too: sendsize.log> calculating for amname '/data0', dirname '/data0' sendsize: getting size via dump for /data0 level 0 sendsize: running "/sbin/dump 0Ssf 1048576 - /dev/md0" /dev/md0: Bad magic number in super-block while opening filesystem DUMP: The ENTIRE

every run a new tape?

Why amanda uses a new tape on every night run? Tapes are 40/80GB DLT1, and I dont understand why It dumps daily incrementals to a new tape always, most of tapes are not even at 20%. Any help? Is it any parameter I've missed out? Thanks.

Re: without tapes

>>and... what about changing /dev/sg0 and /dev/nst0 and /dev/st0 (which >>are my devices) permissions? > > As long as you're not running as root, I guess this is OK. Seems like > a lot of work and potential for messing up to me, but whatever you're > comfortable with. > > BTW, you shouldn't be us

Re: without tapes

>>> Put /dev/null in for your tape device when running the amdumps, then >>> set it to a real tape and do an amflush. >> >>Wasn't there a comment on this list before about using something non- >>existent (like /dev/nosuchdevice) instead of /dev/null because amanda >>was somehow 'aware' of /dev/nul

without tapes

Hi, Is it possible to run amanda "without-tapes" so it dumps only to holding disk? But what I mean is not to take off the tapes physically but disabling tape writing. I want to accumulate incrementals worth a week and flush them on friday to a tape... How can I do such a thing?

migrated

Hello, I have just moved my amanda setup from one server to another (the old one was already setup). But now I always get the same error message either trying to label tapes, or running amcheck: no tape online Notes: amcheck never finishes... chg-zd-mtx works... but it neither finishes, only t

amflush and irc?

Hello, Two things; On one hand, I have been thinking about running amanda once a week for totals directly to tape, and the rest of weekdays without tapes so incrementals are sent to holding disk, and then before next total on friday with tapes, I do amflush... Would that work nicely? I ask caus

amoverview

hello, After doing a start backup, of many filesystem, I run amoverview to check the state of the backup, every filesystem is 0 except two of them (the two that failed first write cause of tape space and were successful on second try) that are with EE code. Whats the meaning of that? Is that cor

every run a new tape?

Why amanda uses a new tape on every night run? Tapes are 40/80GB DLT1, and I dont understand why It dumps daily incrementals to a new tape always, most of tapes are not even at 20%. Any help? Is it any parameter I've missed out? Thanks.

Re: Changers

Well, if this can be useful: I got it running with an HP SureStore AutoLoader (9 slots)... Regards. -Original Message- From: Ignacio Dosil Lago <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date: Mon, 25 Feb 2002 15:49:53 +0100 Subject: Changers > Hi, everybody! > I´m testing Amanda (witho

amanda planner fails, dumps too big

Hello, Seems that only 4 out of 6 dumps are backed up. Two of them are skipped giving error message: dumps too big What I see is that it starts estimating sizes of every disk, therefore total size exceeds single tape size, but I'm using an autoloader, so It should jump on to a new tape, s

planner fails, dumps too big

Hello, Seems that only 4 out of 6 dumps are backed up. Two of them are skipped giving error message: dumps too big What I see is that it starts estimating sizes of every disk, therefore total size exceeds single tape size, but I'm using an autoloader, so It should jump on to a new tape, s

next tape and tapelist

After doing some checks, I'm gonna let amanda do a first backup, about 180 Gigs of data. Well, after those checks, the pointer is at tape 3, how can I tell amanda to start with tape 1? I've tried launching: amrmtape confname tapelabel but it says something about preserving original database,

Backup cycle

I have 9 slot autoloader, on slot 9 I have cleaning tape, well, my dumpcycle is one week, and tapecycle is 8. My idea was doing incrementals during weekdays and full backup on weekend. I have been reading around and seems that amanda works different. So.. in order to achieve such a configuration

Re: planner and sendsize

-Original Message- From: Joshua Baker-LePain <[EMAIL PROTECTED]> To: Juanjo <[EMAIL PROTECTED]> Date: Wed, 13 Feb 2002 13:13:12 -0500 (EST) Subject: Re: planner and sendsize > On Wed, 13 Feb 2002 at 6:23pm, Juanjo wrote > > > Here it goes s

planner and sendsize

Here it goes something interesting too: sendsize.log> calculating for amname '/data0', dirname '/data0' sendsize: getting size via dump for /data0 level 0 sendsize: running "/sbin/dump 0Ssf 1048576 - /dev/md0" /dev/md0: Bad magic number in super-block while opening filesystem DUMP: The ENTIRE

planner gives disk offline?

Hello, Finally, went back to stable release of amanda (2.4.2p2) from sources, since debian package seems to be broken. Looking at logs got this: START driver date 20020213 START planner date 20020213 INFO planner Adding new disk servera:/data0. FAIL planner servera /data0 0 [disk /data0 offline

Re: HP SureStore AutoLoader

My changer script cannot find -clean -access -status and -barcodes files, how are those generated first time? Manually?

Re: HP SureStore AutoLoader

Tnx -Original Message- From: Kasper Edwards <[EMAIL PROTECTED]> To: "Juanjo" <[EMAIL PROTECTED]> Date: Wed, 13 Feb 2002 11:07:36 +0100 Subject: Re: HP SureStore AutoLoader > At 10:37 13-02-2002 +0100, Juanjo wrote: > >Hello, > > > >I'm trying to config

HP SureStore AutoLoader

Hello, I'm trying to config a backup system with amanda-2.4.3b2. I have a HP SureStore AutoLoader with 9 slots, I've put 8 backup tapes and have a cleantape on slot 9. I can manage the changer with no problems using mtx. My problems start when running amcheck, which changerscript should I use? c