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 dump is aborted. running /usr/local/amanda/libexec/killgrp . ???
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
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/null and would perform backups differently? Absolutely correct. Do **not** set tapedev to /dev/null unless you really want Amanda to throw all your data away. That feature is meant for debugging, performance test, etc. At 2.4.3 this changes to null: and /dev/null goes back to an older behavior of throwing an error (since you cannot rewind it :-). But I would still strongly recommend the /no/such/device technique -- you know for certain what's going on with that. Frank John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] and... what about changing /dev/sg0 and /dev/nst0 and /dev/st0 (which are my devices) permissions? c-1 root tape 9, 128 Aug 8 2001 /dev/nst0 c-1 backup root 21, 0 Aug 8 2001 /dev/sg0 c-1 root tape 9, 0 Aug 8 2001 /dev/st0 Would this work? Or better to touch /dev/nosuchdevice and then? Point to it the changer-device or the tape-device? Thanks
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 the -info switch comes back. Thanks in advance.
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 cause seems that amanda balances the backup on her own, but I cannot spend expensive DLT40/80 tapes with 2 gigs of incrementals only. Also, with amflush, will indexes be maintained without any trouble? So index server finds stuff as if they were on separated tapes. On the other hand, is there any irc channel for amanda? It's a nice way of sharing problems and stuff real-time. If there isnt any, what about #amanda at irc.openprojects.org? Regards...
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 correct? In amdump.log seems its everything ok.
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 (without tape device) and shurely this will become my new backup suite. My questions are: What tape changers do you un/recommend me? What should I know about this kind of devices? Thanks!
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, shouldnt it? And send there the disks that didnt fit on that prior tape. How? Here I paste a piece of amdump.log: - - --- got result for host srvc disk /data1: 0 - 32149300K, -1 - -1K, -1 - -1K got result for host srvc disk /data0: 0 - 20482410K, -1 - -1K, -1 - -1K got result for host srvb disk /data1: 0 - 35674680K, -1 - -1K, -1 - -1K got result for host srvb disk /data0: 0 - 21510210K, -1 - -1K, -1 - -1K getting estimates took 266.671 secs FAILED QUEUE: empty DONE QUEUE: 0: srva /data1 1: srva /data0 2: srvc /data1 3: srvc /data0 4: srvb /data1 5: srvb /data0 ANALYZING ESTIMATES... pondering srva:/data1... next_level0 -11737 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 27650 total size 27770 total_lev0 27650 balanced-lev0size 4608 pondering srva:/data0... next_level0 -11737 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 423860 total size 451670 total_lev0 451510 balanced-lev0size 75251 pondering srvc:/data1... next_level0 -11737 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 32149300 total size 32601010 total_lev0 32600810 balanced-lev0size 5433467 pondering srvc:/data0... next_level0 -11737 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 20482410 total size 53083460 total_lev0 53083220 balanced-lev0size 8847202 pondering srvb:/data1... next_level0 -11737 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 35674680 total size 88758180 total_lev0 88757900 balanced-lev0size 14792982 pondering srvb:/data0... next_level0 -11737 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 21510210 total size 110268430 total_lev0 110268110 balanced-lev0size 18378017 INITIAL SCHEDULE (size 110268430): srvb /data1 pri 11738 lev 0 size 35674680 srvc /data1 pri 11738 lev 0 size 32149300 srvb /data0 pri 11738 lev 0 size 21510210 srvc /data0 pri 11738 lev 0 size 20482410 srva /data0 pri 11738 lev 0 size 423860 srva /data1 pri 11738 lev 0 size 27650 DELAYING DUMPS IF NEEDED, total_size 110268430, tape length 7168 mark 8 planner: FAILED srvc /data0 0 [dumps too big, but cannot incremental dump new disk] planner: FAILED srvb /data0 0 [dumps too big, but cannot incremental dump new disk] delay: Total size now 68275730. PROMOTING DUMPS IF NEEDED, total_lev0 68275490, balanced_size 18378017... analysis took 0.000 secs GENERATING SCHEDULE: srvb /data1 11738 0 1970:1:1:0:0:0 35674680 1189156 srvc /data1 11738 0 1970:1:1:0:0:0 32149300 1071643 srva /data0 11738 0 1970:1:1:0:0:0 423860 14128 srva /data1 11738 0 1970:1:1:0:0:0 27650 921 - - --- Tape size is DLT1 40/80 btw. Thanks.
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, shouldnt it? And send there the disks that didnt fit on that prior tape. How? Here I paste a piece of amdump.log: - got result for host srvc disk /data1: 0 - 32149300K, -1 - -1K, -1 - -1K got result for host srvc disk /data0: 0 - 20482410K, -1 - -1K, -1 - -1K got result for host srvb disk /data1: 0 - 35674680K, -1 - -1K, -1 - -1K got result for host srvb disk /data0: 0 - 21510210K, -1 - -1K, -1 - -1K getting estimates took 266.671 secs FAILED QUEUE: empty DONE QUEUE: 0: srva /data1 1: srva /data0 2: srvc /data1 3: srvc /data0 4: srvb /data1 5: srvb /data0 ANALYZING ESTIMATES... pondering srva:/data1... next_level0 -11737 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 27650 total size 27770 total_lev0 27650 balanced-lev0size 4608 pondering srva:/data0... next_level0 -11737 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 423860 total size 451670 total_lev0 451510 balanced-lev0size 75251 pondering srvc:/data1... next_level0 -11737 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 32149300 total size 32601010 total_lev0 32600810 balanced-lev0size 5433467 pondering srvc:/data0... next_level0 -11737 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 20482410 total size 53083460 total_lev0 53083220 balanced-lev0size 8847202 pondering srvb:/data1... next_level0 -11737 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 35674680 total size 88758180 total_lev0 88757900 balanced-lev0size 14792982 pondering srvb:/data0... next_level0 -11737 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 21510210 total size 110268430 total_lev0 110268110 balanced-lev0size 18378017 INITIAL SCHEDULE (size 110268430): srvb /data1 pri 11738 lev 0 size 35674680 srvc /data1 pri 11738 lev 0 size 32149300 srvb /data0 pri 11738 lev 0 size 21510210 srvc /data0 pri 11738 lev 0 size 20482410 srva /data0 pri 11738 lev 0 size 423860 srva /data1 pri 11738 lev 0 size 27650 DELAYING DUMPS IF NEEDED, total_size 110268430, tape length 7168 mark 8 planner: FAILED srvc /data0 0 [dumps too big, but cannot incremental dump new disk] planner: FAILED srvb /data0 0 [dumps too big, but cannot incremental dump new disk] delay: Total size now 68275730. PROMOTING DUMPS IF NEEDED, total_lev0 68275490, balanced_size 18378017... analysis took 0.000 secs GENERATING SCHEDULE: srvb /data1 11738 0 1970:1:1:0:0:0 35674680 1189156 srvc /data1 11738 0 1970:1:1:0:0:0 32149300 1071643 srva /data0 11738 0 1970:1:1:0:0:0 423860 14128 srva /data1 11738 0 1970:1:1:0:0:0 27650 921 - Tape size is DLT1 40/80 btw. Thanks.
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, what kind of dumptype should I declare in amanda.conf ?
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, and after running amcheck, next due tape is 3 still... Tnx.
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? chg-mtx? chg-multi? chg-zd-mtx? It's kinda urgent actually to get this thing up and running. Changer device is /dev/sg0 and tape device seems to be /dev/nst0 (non-rewind version) and /dev/st0. Thanks in advance for any help. Regards.
Re: HP SureStore AutoLoader
Well, I downloaded 2.4.3b2 cause got no success with Debian package which was 2.4.2p2, so I thought that newer version might have better chg scripts. Btw: I'm trying with chg-scsi (hard since it aint script) and it generated a big big file (6gig and growing up), is it normal? 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 a backup system with amanda-2.4.3b2. I hope you are aware that your are using the beta version. If you want this thing running urgent I would suggest Amanda-2.4.2p2. best, Kasper
Re: HP SureStore AutoLoader
My changer script cannot find -clean -access -status and -barcodes files, how are those generated first time? Manually?
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 on servera?] FINISH planner date 20020213 WARNING driver WARNING: got empty schedule from planner STATS driver startup time 1.047 Any hints buds? Regards.
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 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 dump is aborted. running /usr/local/amanda/libexec/killgrp . Hmmm, what filesystem are you running on that partition? If it's ext2, then you may need to talk to the dump/restore maintainer about supporting software RAID partitions. You could also try upgrading dump/restore. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University Well, what I want to backup is a directory named /data0, which is inside a reiserfs filesystem mounted on /dev/md0 which is a raid device... gathering more info I've seen DUMP failing, but how come it's trying to dump it?? I simply want backup of /data0, so tar should be the way, no? Perhaps tar is failing at some point? Regards.
