Re: [Amanda-users] Amanda+Samba : "exclude" setting
On Fri, Dec 14, 2001 at 07:01:36PM -, Philip Cooper wrote: > It seems to work fine, once I realised you had to enable the ide-scsi kernel > module and use /dev/nst0 instead of /dev/nht0... (this would be a good > addition to the FAQ). why would this matter, aren't they both block devices? msg08937/pgp0.pgp Description: PGP signature
Re: [Amanda-users] Win32 client portrange...
On Wed, Dec 12, 2001 at 08:46:28AM +1100, Jason Thomas wrote: > no you just want the udp port that it listens on. and maybe the tcp > port. try: > start amandad -udp=10800 -no-exit sorry wrong port: 10080 msg08936/pgp0.pgp Description: PGP signature
timeout and etimeout
Hi, I have a set up where the backup server is backing up a linux box. the first backup went fine, however, since then this linux client has been generating timeout error msgs. I tried to adjust the etimeout on the backup server to 900, 1,800, and 3,000 (the last one seems to be too big, as nothing happens in hours). I am not sure how to interpret from the log file on that client to get a better idea of what value i should have set for the etimeout. Any advice would be highly appreciated! best regards, --Walter here is some system info: backup server: rh 7.1-2.4.9-6smp amanda-server-2.4.2p2-1 client: same, except with amanda-client-2.4.2p2-1 email notification: FAILURE AND STRANGE DUMP SUMMARY: wald.calte /ssel lev 0 FAILED [Request to wald.caltech.edu timed out.] wald.calte /home2 lev 0 FAILED [Request to wald.caltech.edu timed out.] wald.calte /home1 lev 0 FAILED [Request to wald.caltech.edu timed out.] wald.calte /home lev 0 FAILED [Request to wald.caltech.edu timed out.] wald.calte /var lev 0 FAILED [Request to wald.caltech.edu timed out.] wald.calte / lev 0 FAILED [Request to wald.caltech.edu timed out.] STATISTICS: Total Full Daily ... DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - eagles.calte /home 1 10265 1472 14.3 0:04 408.3 0:04 385.5 mill / 11120 1120 --0:05 209.8 0:06 192.2 mill /holddisk 0 289 32 11.1 0:15 2.1 0:15 4.1 mill /home 28416 8416 --0:12 699.6 0:09 896.4 mill /usr/local 11696 1696 --0:03 600.0 0:03 566.4 mill /var1 105856 105856 --0:244428.2 1:201317.8 wald.caltech / 0 FAILED --- wald.caltech /home 0 FAILED --- wald.caltech /home1 0 FAILED --- wald.caltech /home2 0 FAILED --- wald.caltech /ssel 0 FAILED --- wald.caltech /var0 FAILED --- the end of the email --- amandad log on the client (wald): amandad: debug 1 pid 30393 ruid 33 euid 33 start time Wed Dec 12 01:45:01 2001 amandad: version 2.4.2p2 amandad: build: VERSION="Amanda-2.4.2p2" amandad:BUILT_DATE="Thu Apr 5 09:18:00 EDT 2001" amandad:BUILT_MACH="Linux porky.devel.redhat.com 2.2.17-8smp #1 SMP Fri Nov 17 16:12:17 EST 2000 i686 unknown" amandad:CC="gcc" amandad: paths: bindir="/usr/bin" sbindir="/usr/sbin" amandad:libexecdir="/usr/lib/amanda" mandir="/usr/share/man" amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" amandad:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/" amandad:RDEV_PREFIX="/dev/" DUMP="/sbin/dump" amandad:RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient" amandad:GNUTAR="/bin/tar" COMPRESS_PATH="/usr/bin/gzip" amandad:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail" amandad:listed_incr_dir="/var/lib/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="localhost" amandad:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" got packet: Amanda 2.4 REQ HANDLE 001-184F0608 SEQ 1008146701 SECURITY USER amanda SERVICE sendsize OPTIONS maxdumps=1;hostname=wald.caltech.edu; DUMP /ssel 0 1970:1:1:0:0:0 0 DUMP /ssel 1 2001:12:11:9:55:44 0 DUMP /home2 0 1970:1:1:0:0:0 0 DUMP /home2 1 2001:12:11:10:24:4 0 DUMP /home1 0 1970:1:1:0:0:0 0 DUMP /home1 1 2001:12:11:10:45:40 0 DUMP /home 0 1970:1:1:0:0:0 0 DUMP /home 1 2001:12:11:10:6:38 0 DUMP /var 0 1970:1:1:0:0:0 0 DUMP /var 1 2001:12:11:10:0:33 0 DUMP / 0 1970:1:1:0:0:0 0 DUMP / 1 2001:12:11:1:15:27 0 sending ack: Amanda 2.4 ACK HANDLE 001-184F0608 SEQ 1008146701 bsd security: remote host mill.sslab.caltech.edu user amanda local user amanda amandahosts security check passed amandad: running service "/usr/lib/amanda/sendsize" amandad: sending REP packet: Amanda 2.4 REP HANDLE 001-184F0608 SEQ 1008146701 OPTIONS maxdumps=1; / 0 SIZE 235658 / 1 SIZE 410 /var 0 SIZE 797218 /var 1 SIZE 65901 /home 0 SIZE 1386515 /home 1 SIZE 25550 /home1 0 SIZE 1825473 /home1 1 SIZE 5513 /home2 0 SIZE 1705275 /home2 1 SIZE 201 /ssel 0 SIZE 3858
Re: Weird amdump problem on Linux machine: Unable to get an size estimate
Please ignore my previous post, i found what the problem was: the /etc/amandates was a directoy, not a file! (i made a mistake during one of the amcheck messages). I solved the problem checking the /tmp/amanda losg on the client side, they were very helpfull :) JV. --- José Vicente Núñez Zuleta <[EMAIL PROTECTED]> escribió: > Greetings, > > I'm backing up now my development network using > Amanda > and appears to run fine on almost all the machines; > I > running the tape server on a Linux machine, taping > to > hardisk (no tape unit) and have several Linux and > Solaris clients. > > I'm unable to get a backup size estimate with one of > the Linux clients but i'm successfull with the > others > (they have exactly the same configuration) and even > i'm able to run amcheck on the server and amrecover > on > that particular box without a problem!!! > > Here is the output of the last amstatus run: > > > [amanda@linux0107 amanda]$ amstatus NEWBREAK --file > NEWBREAK/logs/amdump.1 > Using /home/amanda/NEWBREAK/logs/amdump.1 from Fri > Dec > 14 01:00:03 EST 2001 > > arbitrage.dev.newbreak.bogus:/dev/dsk/c0t0d0s0 0 > 1378144k dump done (3:56:25), wait for writing to > tape > arbitrage.dev.newbreak.bogus:/dev/dsk/c0t0d0s5 0 > 818528k dump done (1:24:44), wait for writing to > tape > linux0001.dev.newbreak.bogus:/apps/ACE 0 [missing > result for /apps/ACE in linux0001.dev.newbreak.bogus > response] > linux0001.dev.newbreak.bogus:/apps/crypto 0 [missing > result for /apps/crypto in > linux0001.dev.newbreak.bogus response] > linux0001.dev.newbreak.bogus:/apps/espiel 0 [missing > result for /apps/espiel in > linux0001.dev.newbreak.bogus response] > linux0001.dev.newbreak.bogus:/apps/expat 0 [missing > result for /apps/expat in > linux0001.dev.newbreak.bogus > response] > linux0001.dev.newbreak.bogus:/apps/intex 0 [missing > result for /apps/intex in > linux0001.dev.newbreak.bogus > response] > linux0001.dev.newbreak.bogus:/apps/javapkgs 0 > [missing > result for /apps/javapkgs in > linux0001.dev.newbreak.bogus response] > linux0001.dev.newbreak.bogus:/apps/lib 0 [missing > result for /apps/lib in linux0001.dev.newbreak.bogus > response] > linux0001.dev.newbreak.bogus:/apps/roguewave 0 > [missing result for /apps/roguewave in > linux0001.dev.newbreak.bogus response] > linux0001.dev.newbreak.bogus:/apps/scripts 0 > [missing > result for /apps/scripts in > linux0001.dev.newbreak.bogus response] > linux0001.dev.newbreak.bogus:/apps/tars 0 [missing > result for /apps/tars in > linux0001.dev.newbreak.bogus > response] > linux0001.dev.newbreak.bogus:/apps/xemacs 0 [missing > result for /apps/xemacs in > linux0001.dev.newbreak.bogus response] > linux0001.dev.newbreak.bogus:/apps/xerces 0 [missing > result for /apps/xerces in > linux0001.dev.newbreak.bogus response] > linux0001.dev.newbreak.bogus:/data 0 [missing > result for /data in linux0001.dev.newbreak.bogus > response] > linux0001.dev.newbreak.bogus:/usr/atria 0 [missing > result for /usr/atria in > linux0001.dev.newbreak.bogus > response] > linux0001.dev.newbreak.bogus:/usr/java 0 [missing > result for /usr/java in linux0001.dev.newbreak.bogus > response] > linux0102.dev.newbreak.bogus:/opt0 204180k > dump done (1:06:23), wait for writing to tape > lnxdev0001.dev.newbreak.bogus:/etc 08280k > dump done (1:00:48), wait for writing to tape > lnxdev0001.dev.newbreak.bogus:/export/home 0 > 6155020k > dump done (3:26:05), wait for writing to tape > lnxdev0001.dev.newbreak.bogus:/home 0 10k > dump done (1:00:37), wait for writing to tape > lnxdev0001.dev.newbreak.bogus:/var 0 75290k > dump done (1:02:18), wait for writing to tape > > SUMMARY part real estimated > size size > partition : 22 > estimated : 0 0k > failed : 15 0k > ( > 0.00%) > wait for dumping: 0 0k > ( > 0.00%) > dumping to tape : 0 0k > ( > 0.00%) > dumping : 00k0k ( 0.00%) > ( > 0.00%) > dumped : 7 8639452k 8639495k (100.00%) > ( > 0.00%) > wait for writing: 7 8639452k 8639495k (100.00%) > ( > 0.00%) > writing to tape : 00k0k ( 0.00%) > ( > 0.00%) > failed to tape : 00k0k ( 0.00%) > ( > 0.00%) > taped : 00k0k ( 0.00%) > ( > 0.00%) > 4 dumpers idle : not-idle > taper idle > network free kps: 2000 > holding space : 1048576k (100.00%) > dumper0 busy : 2:55:47 (100.00%) >taper busy : 2:55:47 (100.00%) > 0 dumpers busy : 0:00:00 ( 0.00%) > 1 dumper busy : 2:55:47 (100.00%) > not-idle: 2:55:47 (100.00%) > [amanda@linux0107 amanda]$ > > Can anyone give me a pointer for troubleshoot this > issue? > > Thanks in advance, > > PD: The "bogus" domain is not a typo, is our > internal > DNS domain :) > > JV. > > > = > System
Amanda+Samba : "exclude" setting
I've just set up 2.4-2 & Samba 2.2.2 on RH7.1 with STT2A IDE 10Gb Travan
tape.
It seems to work fine, once I realised you had to enable the ide-scsi kernel
module and use /dev/nst0 instead of /dev/nht0... (this would be a good
addition to the FAQ).
I have a few problems, all relating to the Samba end. The most pressing
follows:
I would like to exclude a list of file types, indicated by extension. My
"exclude.lst" file for the Linux disks looks like:
core
*.o
*.odb
*.res
*.stt
*.fil
It seems to work well.
The "exclude list" feature is not available through Samba, but I wondered if
I could specify a list of file types, something like:
exclude "core,*.o,*,odb,*,res,*.stt,*.fil"
My current setting for samba shares is:
exclude "*.stt"
aimed at excluding a single, particularly profligate, file type.
I've tried to test this by running the smbclient command as issued by
amdump, and found that my current setting has no affect whatsoever, since
this type of globbing requires the "-r" swith in smbclinet:
Without -r:
[root@wayne /usr]# smbclient GULF\\Projects -U amanda -E -W
KWUK -d0 -TXqcg - *.stt > /tmp/test.tar
added interface ip=192.168.0.10 bcast=192.168.0.255 nmask=255.255.255.0
Password: tar: dumped 132 files and directories
Total bytes written: 17424896
[root@wayne /usr]# tar tvf /tmp/test.tar|grep stt
-rw-r--r-- 0/0 184320 2001-12-12 19:47:12 ./FRF/utbsf01.stt
-rw-r--r-- 0/0 184320 2001-12-12 20:39:53 ./FRF/utbsf02.stt
-rw-r--r-- 0/0 167936 2001-12-13 09:05:19 ./FRF/utbsf03.stt
-rw-r--r-- 0/0 167936 2001-12-13 10:34:38 ./FRF/utbsf04.stt
-rw-r--r-- 0/0 167936 2001-12-13 10:09:57 ./FRF/utbsf04v.stt
-rw-r--r-- 0/0 167936 2001-12-13 10:46:30 ./FRF/utbsf05.stt
-rw-r--r-- 0/0 167936 2001-12-14 17:36:38 ./FRF/utbsf08lb.stt
-rw-r--r-- 0/0 671744 2001-12-07 18:01:12 ./Pipe31/model14.stt
-rw-r--r-- 0/0 688128 2001-12-07 17:10:26 ./Pipe31/model14b.stt
With -r:
[root@wayne /usr]# smbclient GULF\\Projects -U amanda -E -W
KWUK -d0 -TXqcgr - *.stt > /tmp/test.tar
added interface ip=192.168.0.10 bcast=192.168.0.255 nmask=255.255.255.0
tar_re_search set
Password: tar: dumped 123 files and directories
Total bytes written: 14852096
[root@wayne /usr]# tar tvf /tmp/test.tar|grep stt
{no files found by grep - i.e. it worked)
Could someome tell be if this type of exclude directive is possible, and if
so how.
Thanks
Phil
Philip Cooper
K W Ltd.
Fetcham Park House
Lower road
Fetcham, Leatherhead
Surrey KT22 9HD
http://www.kwltd.com
mailto:[EMAIL PROTECTED]
Tel. +44 (0) 1372 371122
Mob. +44 (0) 7850 140538
Fax. +44 (0) 1372 371123
Re: Amanda wants to dump(8) 'sd2e' instead of '/dev/sd2e'?
On Fri, 14 Dec 2001 at 12:47pm, Hauke Fath wrote > after upgrading from amanda-2.4.2 to amanda-2.4.2p2 on an NetBSD/i386 > 1.5+ machine, I see the following in the nightly log: > > > FAILURE AND STRANGE DUMP SUMMARY: > heap sd2e lev 0 FAILED [disk sd2e offline on heap?] Try applying the advfs.patch from the patches page at www.amanda.org. It fixes problems similar to this on Linux, and may on BSD as well. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Smbclient Question
I want to thnak everyone for the samba tips. Everything works fine now. I did have some problems with the white spaces under the Windows naming convention; you know, like //MACHINE/Documents and Settings/user name/My Documents Anyway, I made a share named "amanda" diretly under the W2K root, and it worked fine when I ran amcheck. How do you guys address the white space problem? I assume most users want "My Documents" saved. Do you make a short cut without any white spaces? Thanks, Brad
samba backups "offline"
I'm backing up a single W2K machine to my tape server. There are 4 partitions on the windows box. Some nights al 4 partitions are processed normally. Most nights 1 or more of the partitions fail with the query "host offline?" which obviously it is not as the other partitions are backing up. I've increased the 3 timeout settings in amand.conf to no avail. I'm not seeing the problem in the /tmp/amanda debug files, probably because I'm not sure what to look for. Ideas? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing [EMAIL PROTECTED] 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: [Amanda-users] Win32 client portrange...
On Tue, Dec 11, 2001 at 10:53:40AM -0500, Chris Noon wrote: > Hello all, > I'm trying to get the win32 client up and running. I followed Kurt Yoder's > instructions (below), but amcheck is still timing out. I'm almost certain > that it has to do with the tcp/ip ports amanda is using. My server was > compiled with the following: > --with-portrange=5,50100 --with-udpportrange=850,860 > > I'm running the win32 client with the following command: > start amandad -tcp=5,50100 -udp=850,860 -no-exit no you just want the udp port that it listens on. and maybe the tcp port. try: start amandad -udp=10800 -no-exit have a look at the code for the win32 client the server is trying to connect to the amanda port which is from memory 10800. so you need the win32 client to listen on that port. tcp/udp don't take a range they specify the port to bind to. but only for debugging purposes. you also need to define the ROOT_DRV variable, I did it in my autoexec.bat: set ROOT_DRV=c: this is a pw32 environment variable. you may want to rebuild the win32 client and specify the port range to configure. the amanda win32 to client is built using pw32 not cygwin. http://pw32.sf.net I think. its almost the same as cygwin but free with no gui installer. zip files! good luck. > I've tried many permutations of that command, but with no luck. Any one > have some insight on how to correctly specify tcp/udp ports to the win32 > client? > > Many thanks in advance, > > Chris Noon > [EMAIL PROTECTED] msg08929/pgp0.pgp Description: PGP signature
Re: Redundancy in Amanda
Stephen Carville <[EMAIL PROTECTED]> wrote: >My boss just asked me about redundancy in amanda. I explainmed to him (...) >dumpcycle 7 days >tapecycle 15 >runspercycle 5 >runtapes 2 What is the value of 'bumpdays' in your setup. If it's 1 you might increase to 2 to have more redundancy. Just my .02 Lipo -- "They that can give up essential liberty | Roland E. Lipovits to obtain a little temporary safety | Vienna, Austria deserve neither liberty nor safety." | DSA-KeyID: 0xDA153FAB - Benjamin Franklin, 1759 | RSA-KeyID: 0xBC39A5CD
RE: Problem with windows 2000 Professional
> > I use Amanda 2.2.4p2 on a Linux Red Hat 7.1 and > > without any tape for the test. > > The backup works fine on linux. > > > > I use samba 2.2.2 for the windows clients : > > that works with NT and 98, but on windows 2000, > the > > amdump starts and > > finally freeze. After a complete and clean reinstallation of samba, works fine. Might be a conflict between old and new version of samba. = Christophe Condomines [EMAIL PROTECTED] ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Courrier : http://courrier.yahoo.fr
Amrecover is not working with Gnu Tar: help needed
Greetings, I'm using Amrecover to try to recover some file; I did a full dump (forced using amadmin) and i here is the output of a failed recover procedure: amrecover> setdate ---08 200 Working date set to 2001-12-08. amrecover> sethost lnxsrv0001 200 Dump host set to lnxsrv0001. amrecover> setdisk / Scanning /export/data06/amanda-hold-disk-temp... Scanning /home/amanda/holding-disk... 200 Disk set to /. amrecover> cd /etc /etc amrecover> ls 2001-12-08 . 2001-12-08 .pwd.lock 2001-12-08 CORBA/ amrecover> add HOSTNAME Added /etc/HOSTNAME amrecover> lcd /tmp amrecover> extract Extracting files using tape drive /dev/rmt/1bn on host lenbkx0001. The following tapes are needed: NEWBREAK_05 Restoring files into directory /tmp Continue? [Y/n]: y Load tape NEWBREAK_05 now Continue? [Y/n]: y tar: ./etc/HOSTNAME: Not found in archive tar: Error exit delayed from previous errors extract_list - child returned non-zero status: 2 Continue? [Y/n]: n amrecover> The file must be there because i did a full dump but amrecover is saying that the file is not in the tape!. The backup runs perfectly (without errors), amverify says that everythinbg is good with the tape. Any helkp with will be really apreciated, JV. = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com
RE: Full dump not running in dumpcycle days (FIXED and a question)
Check out the "RESERVE" parameter in amanda.conf. It specifies how much of the holding disk can be used for "degraded mode" (no tape) dumps to the holding disk. IIRC, it defaults to 30%. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 10, 2001 9:54 AM > To: [EMAIL PROTECTED] > Subject: Full dump not running in dumpcycle days (FIXED and a > question) > > > Hello all, > > I figured out what my issue was late last week so please > forgive in the > delay in reporting my findings. What I am doing is not > putting a tape in > the drive, so that forces amanda to write my incrementals to > disk. What > appears to be happening is amanda will not run a full dump if > there is no > tape in the drive. It will fall back on an incremental though. > > > Is this the desired behavior? My fulls only require about 15G's > currently. My holding disk is 35G. Why will amanda not > write a level 0 > if the holding disk has enough space? > > As always thanks for any insight. > > Andrew >
Re: changing the /tape/dev
On Fri, Dec 07, 2001 at 09:04:48AM -0500, Joshua Baker-LePain wrote: > On Thu, 6 Dec 2001 at 7:38pm, BRINER Cedric wrote > > > One of the problems that I see is : > > Imagine that the dump0 was happenning when we were doing a software > > compression and > > that the dump1 with a hard compression...So when we will recover the > > data, amrecover > > will use the amanda.conf which contain the hard-compression...so the > > system will be able > > to only read one of them... amrecover (amrestore) read the compression state from the dump image, the setting in the configuration file is not use. Jean-Louis > > You can specify the tape device to use when you start amrecover. Of > course, you'll need to keep track of which tapes were done with hardware > vs. software compression. > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: taper tunning to achieve tape streaming
> "Mitch" == Mitch Collinsworth <[EMAIL PROTECTED]> writes: Yes, I'am using 20G for holding disk. I had two files produced by amdump each one 9G. The taper doesn't achieve streaming when write them to the tape (and the rate is around 4MB/s instead of 5.9MB/s which is nominal). I tried to write them manually with tar on the tape (aside from amanda). Tar behaves the same unless I increase the bloking factor to 128/256 when it reaches full streaming and the rate gets to 5.6MB/s. I also tried to increase the number of tapebufs (more than 20) (altough I realized that it doesn't buffer the communication between taper and tape device drive) and I got an error. I believe that it comes from shared memory allocation that has reached its per process limit (640K - which I think it's enough). Thanks for any help, Mihai. <<>> Does anyone know how to modify the buffering ot the taper so that I can achive <<>> tape streaming. I'm using an dlt8000 tape on an enterprise e250 sun server. When <> Are you using a holding disk? Or backing up direct to tape? <> -Mitch
Amanda wants to dump(8) 'sd2e' instead of '/dev/sd2e'?
Hi list, after upgrading from amanda-2.4.2 to amanda-2.4.2p2 on an NetBSD/i386 1.5+ machine, I see the following in the nightly log: FAILURE AND STRANGE DUMP SUMMARY: heap sd2e lev 0 FAILED [disk sd2e offline on heap?] /tmp/amanda/sendsize.20011213224502.debug then shows me: calculating for amname 'sd0e', dirname '/var' sendsize: getting size via dump for sd0e level 0 sendsize: running "/sbin/dump 0Shsf 0 1048576 - /dev/rsd0e" running /usr/pkg/libexec/killpgrp DUMP: Date of this level 0 dump: Thu Dec 13 22:45:07 2001 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rsd0e (/var) to standard output DUMP: Label: none DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 29 tape blocks. . ...skipping... calculating for amname 'sd2e', dirname 'sd2e' sendsize: getting size via dump for sd2e level 0 sendsize: running "/sbin/dump 0Shsf 0 1048576 - sd2e" <<=== running /usr/pkg/libexec/killpgrp DUMP: Cannot lstat sd2e: No such file or directory . (no size line match in above dump output) . asking killpgrp to terminate sendsize: getting size via dump for sd2e level 1 sendsize: running "/sbin/dump 1Shsf 0 1048576 - sd2e" running /usr/pkg/libexec/killpgrp DUMP: Cannot lstat sd2e: No such file or directory . (no size line match in above dump output) Note that the call to dump sd0e (and any other partition besides 'rsd2e') refers to '/dev/rsd0e', whereas with 'sd2e', the prefix '/dev/' is missing. All other partitions on this machine (which runs the Amanda server) and the client machines were dumped just fine. What am I missing here? hauke -- Hauke Fath /~\The ASCII tangro software components GmbH \ / Ribbon Campaign D-69115 Heidelberg X Against Ruf +49-6221-13336-0, Fax -21 / \ HTML Email!
Re: Newbie: Can't get amanda user to work
Try changing .amandahosts on the client (which appears to be the same as the server in this case) to: admin amanda On Mon, 10 Dec 2001, KEVIN ZEMBOWER wrote: - I'm trying to get my first setup of amanda working. Running amcheck - gives me: - admin:/home/amanda # su amanda -c "/usr/local/sbin/amcheck DailySet1" - Amanda Tape Server Host Check - - - Holding disk /var/amanda: 5807968 KB disk space available, that's - plenty - NOTE: skipping tape-writable test - Tape DailySet101 label ok - NOTE: info dir /var/log/amanda/DailySet1/curinfo/admin/sdb1: does not - exist - NOTE: info dir /var/log/amanda/DailySet1/curinfo/admin/sda1: does not - exist - NOTE: info dir /var/log/amanda/DailySet1/curinfo/admin/sda3: does not - exist - Server check took 16.516 seconds - - Amanda Backup Client Hosts Check - - ERROR: admin: [access as amanda not allowed from - [EMAIL PROTECTED]] amandahostsauth failed - Client check: 1 host checked in 0.029 seconds, 1 problem found - - (brought to you by Amanda 2.4.3b1) - admin:/home/amanda # - - Yet, I have a .amandahosts file with what I think are the proper - contents and permissions: - admin:/home/amanda # ll /home/amanda/.amandahosts - -rw-r--r--1 amanda disk 30 Dec 10 16:36 - /home/amanda/.amandahosts - admin:/home/amanda # cat /home/amanda/.amandahosts - admin [EMAIL PROTECTED] - admin:/home/amanda # - - I'm stumped. I've tried or checked all the suggestions in the - FAQ-a-matic for this topic. It's probably something simple, that I don't - see because I'm new to amanda. Any suggestions? - - Thanks for your help. - - -Kevin Zembower - - - - E. Kevin Zembower - Unix Administrator - Johns Hopkins University/Center for Communications Programs - 111 Market Place, Suite 310 - Baltimore, MD 21202 - 410-659-6139 - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: taper tunning to achieve tape streaming
On Wed, 12 Dec 2001, Mihai Lozoveanu wrote: > Does anyone know how to modify the buffering ot the taper so that I can achive > tape streaming. I'm using an dlt8000 tape on an enterprise e250 sun server. When Are you using a holding disk? Or backing up direct to tape? -Mitch
RE: replacing full tapes?
Michael, I think you will want 'dumpcycle 1 week' instead of 2 weeks. This means that every 1 week, you will have a level 0 backup of every partition, which is what I think you mean by 'a 2 week latency of backups.' With 8 tapes, you will be creating the current week's backups, and have the previous week's backups to use if something goes wrong this week. For comparison, I'm using an Exabyte changer that holds 10 tapes at a time. I have three magazines for it, so my amanda.conf is set up like this: dumpcycle 1 week runspercycle 5 tapecycle 30 tapes This way every magazine has two complete backup sets on it (in case of tape failure.) > -Original Message- > From: Michael Perry [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 12, 2001 12:20 PM > To: [EMAIL PROTECTED] > Subject: Re: replacing full tapes? > > > Quoting Bort, Paul on Wed, Dec 12, 2001 at 10:49:31AM -0500: > > You probably don't want to overwrite BUP2. IIRC, "active > tape" means that > > the most recent combination of a specific disk and level > exists on that > > tape. The amoverview command can show what levels were > backed up on which > > days, for starters. > > > > You might also want to look at your tapecycle, dumpcycle, > and runspercycle > > parameters. I usually try to keep dumpcycle at half (or > less) of tapecycle, > > so that I always have a complete set of tapes to restore > from, and the set > > I'm currently overwriting. > > > > > Hi- > > Thanks for the pointer. I had neglected to take into account a few > factors about using the settings like dumpcycle, tapecycle, > runspercycle. My basic need I think is to backup 5 systems 3 > times per > week and have a 2 week latency of backups. This is not a huge network > :) but I really enjoy the way amanda does the scheduling, > planning, etc. > Best I have ever found in some years of Linux work. What I am > considering is how to build the correct settings for this and not > have to buy a lot of very expensive ecrix tapes (almost $100 > per tape). > I have sufficient tapes to handle up to a 14 tape tapecycle > but some of > them are rather old I think and many are new so I am unsure about the > relative health of the tapes. > > If I set the following variables, does this look close to my > goal? BTW, > the goal is to backup systems 3 times per week (Mon, Wed, > Fri) and have > two weeks of backups: > > dumpcycle 2 weeks > tapecycle 8 tapes > runspercycle 3 > > I am assuming with this setup that amanda will backup 3 times per week > according to my crontab and check 3 times per week a bit > earlier for the > right tape. If I want 2 weeks of backups this would equal 6 tapes and > then I would toss in a few extra to take care of any issues like > failures, etc. > > I am backing up 5 systems here at home including a bsd firewall box > which is exceedingly important to my sanity. Perhaps the > other question > is how other smaller LAN users schedule weekly backups or two week > backups when doing dumps not every day but perhaps every other day and > excluding weekends. > > Thanks for the answers to the questions everyone has sent. I should > have provided all the information on my goals and approaches using > amanda first time around. > > -- > Michael Perry | "Do or do not; there is no try" Master Yoda > [EMAIL PROTECTED] | http://www.lnxpowered.org >
Re: SOLVED: Newbie: Can't get amanda user to work
Hi Kevin: > It's still puzzling to me why the .amandahosts file, with the two > additional hosts, was being recognized in /home/amanda, but still giving > me the error with the tapeserver host. Oh, well, I'm not going to spend > too much time pondering it. > The .amandahosts file that is used during backing up is the one located in the client´s amanda´s home directory. That means that the other two clients were working fine, because their .amandahosts files were OK. You will need the entries for each client in the server´s .amandahosts file, allowing root to access the server, when you try to recover, not before. Cheers...Ana Maria
Re: Is this correct?
On Thu, 13 Dec 2001 at 12:40pm, Adolfo Manuel Pachón Rodríguez wrote > I have 5 tapes for one HP24DAT SCSI unit. I want to use one tape per day, > not including saturday/monday. > > Is this the correct configuration? > > dumpcycle 7 days > runspercycle 5 days > tapecycle 5 tapes Yep. Except, as I mentioned, a couple of spare tapes in your tapecycle would be a really good idea. What if, say, the drive eats on of your tapes (or there's some write error). Whatever was on that tape is gone, and it may very well be your only level 0 of a particular filesystem. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Full dump not running in dumpcycle days (FIXED and a question)
On Mon, 10 Dec 2001 at 9:53am, [EMAIL PROTECTED] wrote > I figured out what my issue was late last week so please forgive in the > delay in reporting my findings. What I am doing is not putting a tape in > the drive, so that forces amanda to write my incrementals to disk. What > appears to be happening is amanda will not run a full dump if there is no > tape in the drive. It will fall back on an incremental though. > > Is this the desired behavior? My fulls only require about 15G's > currently. My holding disk is 35G. Why will amanda not write a level 0 > if the holding disk has enough space? Look for a parameter in amanda.conf called 'reserve'. The default is 100. That is the percentage of holding disk space that amanda reserves for incremental backups when running in degraded mode (i.e. no tape in the drive). If you want to get full backups in degraded mode, you need to set the reserve to something < 100 (enough less than 100, obviously, to fit your full backups). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: dump fails with bread and lseek trouble
In a message dated: Fri, 14 Dec 2001 09:29:54 GMT "Thomas Robinson" said: >Hi, > >Has anyone seen or hear of this problem. Ayup, I get it all the time. I have no idea what the problem is though. It seems to come and go sporatically. >I've run e2fsck -c /dev/sda5 to no avail. I also upgraded the dump utility tha >t came with the standard Red Hat 7.1 install to dump-04b21 to dump-04b22. Any >ideas what can cause this and how I might fix it? No, but if anyone has any ideas, please post them to the list, I'll try anything :) Thanks, -- Seeya, Paul God Bless America! ...we don't need to be perfect to be the best around, and we never stop trying to be better. Tom Clancy, The Bear and The Dragon
Re: I don't understand this
amadmin config-name no-reuse tape-name that'll put a specific tape on hold until you release it and allow you to resequence the tapes without editing any of the amanda files. > Adolfo Manuel Pachón Rodríguez wrote: > > > Hi all: > > > > I have an HP24DAT SCSI over Linux RH 7.1. I want to backup the weekdays > > only, using 5+1 tapes. > > > > I've this in the amanda.conf: > > > > dumpcycle 7 > > runspercycle 5 > > tapecycle 6 > > > > The tapes are labeled: > > > > Daily-000 (monday) > > Daily-001 (tuesday) > > Daily-002 (wednesday) > > Daily-003 (thursday) > > Daily-004 (friday) > > Daily-005 (extra) > > > > What I want is this: > > > > For each day, use the Daily-00X tape. > > > > Today, thursday, I use the Daily-003 tape. With amdump Daily, I do the > > backup. But the report says this: > > > > These dumps were to tape Daily-003. > > The next tape Amanda expects to use is: Daily-006. > > > > This is my question. Why Daily-006? Why not the next tape is Daily-004? > > > > Thanks > > > > I don't think amanda works as you're expecting. You can only give amanda > a sequence of tapes, but not say "I want x tape on x day and y tape on y > day". Amanda will simply go through each tape in its list and use them > as needed. So your 000 tape will end up being used any day of the week. > > Of course, if you give amanda 10 tapes and do 5 backups in a week, > you'll always be using 0 and 6 on a Monday, 1 and 7 on a Tuesday. > > Also, in order to use them in sequence and not skip from 3 to 6, you > have to label them all in order. So if you labeled 0 through 5, let > amanda use 0 and 1, then labeled 6, amanda will expect the sequence to > be 0 1 6 2 3 4 5. > > I'm not sure how to change which tape amanda expects next, short of > removing the tapes using amrmtape and relabeling them. Edit the tapelist > file? Anyone else on the list have any answers? >
Re: Smbclient Question
On Fri, 14 Dec 2001 at 8:52am, Richard B. Tilley (Brad) wrote > My question is this: what do I do now? How can I make amanda automate the > mounts and perform the backups? If this info is on the Net somewhere, > please forgive my question and simply point me to it. > from docs/SAMBA: === Example === The Amanda client software and patched Samba is installed on host 'pcserver'. A share to be backed up called 'backupc' is on PC 'thepc'. The share will be accessed via PC user 'bozo' and password 'f00bar' and does not require a workgroup. The entry in the disklist file is: pcserver//thepc/backupc nocomp-user-gnutar ^ samba installed unix host ^ pc host and share name ^ dumptype must include the tar option In /etc/amandapass on the machine 'pcserver': //thepc/backupc bozo%f00bar If smbclient requires a workgroup specification (-W), you may add it as a third argument in /etc/amandapass line: //thepc/backupc bozo%f00bar NTGROUP This will cause smbclient to be invoked with -W NTGROUP. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: I don't understand this (the Response)
Adolfo Manuel Pachón Rodríguez wrote: > > This is my FIRST tapelist file: > > 0 Diaria-000 reuse > 0 Diaria-001 reuse > 0 Diaria-002 reuse > 0 Diaria-003 reuse > 0 Diaria-004 reuse > 0 Diaria-005 reuse > 0 Diaria-006 reuse > > I do ?amdump Diaria? today, and the tapelist file is now: > > 20011214 Diaria-004 reuse - (*-*-*) > 0 Diaria-000 reuse > 0 Diaria-001 reuse > 0 Diaria-002 reuse > 0 Diaria-003 reuse > 0 Diaria-005 reuse > 0 Diaria-006 reuse so you just start today... you can reorganize the end of the tapeline from (*-*-*) like that 20011214 Diaria-004 reuse 0 Diaria-006 reuse 0 Diaria-000 reuse 0 Diaria-001 reuse 0 Diaria-002 reuse 0 Diaria-003 reuse 0 Diaria-005 reuse because, amanda doesn't care about the name of the tape for determining which will be the next tape...it only care about the date's field "20011214"->(14th december 2001)but when it comes about ading new tapes...it just take the last non-used one in the tapelist... > The report says: > > these dumps were to tape Diaria-004. > The next tape Amanda expects to use is: Diaria-006. > Why not the Diaria-005? got itbecause at that time the last non-used tape in the tapelist was 006 > > > > > > dumpcycle 7 > > > runspercycle 5 > > > tapecycle 6 > > > > > > The tapes are labeled: > > > > > > Daily-000 (monday) > > > Daily-001 (tuesday) > > > Daily-002 (wednesday) > > > Daily-003 (thursday) > > > Daily-004 (friday) > > > Daily-005 (extra) You, can't expect with this configuration to use the Daily-000 only in monday... because you have a tapecycle of 6...so amanda will forces you to use the extra. This because you have only six tapes in your tapelist... But you should keep this configuration...and stop thinking that you will use the Daily-000 on monday...anyway, amanda keeps trace of what it is doing...so at the time you will recover information it will tell you which tape to use... Finally if you want to keep the idea of using the Daily-000 each monday... change your config as follow dumpcycle 7 runspercycle 5 tapecycle 5 it's up to you... Hope it will help > > > > > > What I want is this: > > > > > > For each day, use the Daily-00X tape. > > > > > > Today, thursday, I use the Daily-003 tape. With amdump Daily, I do the > > > backup. But the report says this: > > > > > > These dumps were to tape Daily-003. > > > The next tape Amanda expects to use is: Daily-006. > > > > > > This is my question. Why Daily-006? Why not the next tape is Daily-004? > > > > > > Thanks > > > Check the tapelist file in /etc/amanda/Daily, or wherever the directory > is > > that you have it in. Amanda uses this file to determine what tape to use > > next. You may have inserted an extra tape into the tapelist by accident. > If > > you did, you can use amrmtape to remove it from the tapelist. > > > -- > > > Chris Dahn, SERG Code Ninja > > 3141 Chestnut St. > > Attn: MCS Department > > Philadephia, PA 19104 > > Office: 215.895.0203 > > Fax: 215.895.1582 > > > <->Software Engineering Research Group<-> > > Feel the SERG! > > http://serg.mcs.drexel.edu/ > > CAT 186, The Microwave > > http://pgp.mit.edu:11371/pks/lookup?search=Christopher+Dahn&op=index
Weird amdump problem on Linux machine: Unable to get an size estimate
Greetings, I'm backing up now my development network using Amanda and appears to run fine on almost all the machines; I running the tape server on a Linux machine, taping to hardisk (no tape unit) and have several Linux and Solaris clients. I'm unable to get a backup size estimate with one of the Linux clients but i'm successfull with the others (they have exactly the same configuration) and even i'm able to run amcheck on the server and amrecover on that particular box without a problem!!! Here is the output of the last amstatus run: [amanda@linux0107 amanda]$ amstatus NEWBREAK --file NEWBREAK/logs/amdump.1 Using /home/amanda/NEWBREAK/logs/amdump.1 from Fri Dec 14 01:00:03 EST 2001 arbitrage.dev.newbreak.bogus:/dev/dsk/c0t0d0s0 0 1378144k dump done (3:56:25), wait for writing to tape arbitrage.dev.newbreak.bogus:/dev/dsk/c0t0d0s5 0 818528k dump done (1:24:44), wait for writing to tape linux0001.dev.newbreak.bogus:/apps/ACE 0 [missing result for /apps/ACE in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/apps/crypto 0 [missing result for /apps/crypto in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/apps/espiel 0 [missing result for /apps/espiel in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/apps/expat 0 [missing result for /apps/expat in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/apps/intex 0 [missing result for /apps/intex in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/apps/javapkgs 0 [missing result for /apps/javapkgs in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/apps/lib 0 [missing result for /apps/lib in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/apps/roguewave 0 [missing result for /apps/roguewave in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/apps/scripts 0 [missing result for /apps/scripts in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/apps/tars 0 [missing result for /apps/tars in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/apps/xemacs 0 [missing result for /apps/xemacs in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/apps/xerces 0 [missing result for /apps/xerces in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/data 0 [missing result for /data in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/usr/atria 0 [missing result for /usr/atria in linux0001.dev.newbreak.bogus response] linux0001.dev.newbreak.bogus:/usr/java 0 [missing result for /usr/java in linux0001.dev.newbreak.bogus response] linux0102.dev.newbreak.bogus:/opt0 204180k dump done (1:06:23), wait for writing to tape lnxdev0001.dev.newbreak.bogus:/etc 08280k dump done (1:00:48), wait for writing to tape lnxdev0001.dev.newbreak.bogus:/export/home 0 6155020k dump done (3:26:05), wait for writing to tape lnxdev0001.dev.newbreak.bogus:/home 0 10k dump done (1:00:37), wait for writing to tape lnxdev0001.dev.newbreak.bogus:/var 0 75290k dump done (1:02:18), wait for writing to tape SUMMARY part real estimated size size partition : 22 estimated : 0 0k failed : 15 0k ( 0.00%) wait for dumping: 0 0k ( 0.00%) dumping to tape : 0 0k ( 0.00%) dumping : 00k0k ( 0.00%) ( 0.00%) dumped : 7 8639452k 8639495k (100.00%) ( 0.00%) wait for writing: 7 8639452k 8639495k (100.00%) ( 0.00%) writing to tape : 00k0k ( 0.00%) ( 0.00%) failed to tape : 00k0k ( 0.00%) ( 0.00%) taped : 00k0k ( 0.00%) ( 0.00%) 4 dumpers idle : not-idle taper idle network free kps: 2000 holding space : 1048576k (100.00%) dumper0 busy : 2:55:47 (100.00%) taper busy : 2:55:47 (100.00%) 0 dumpers busy : 0:00:00 ( 0.00%) 1 dumper busy : 2:55:47 (100.00%) not-idle: 2:55:47 (100.00%) [amanda@linux0107 amanda]$ Can anyone give me a pointer for troubleshoot this issue? Thanks in advance, PD: The "bogus" domain is not a typo, is our internal DNS domain :) JV. = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com
Re: I don't understand this
On Thursday 13 December 2001 12:58 pm, Adolfo Manuel Pachón Rodríguez wrote: > Hi all: > > I have an HP24DAT SCSI over Linux RH 7.1. I want to backup the weekdays > only, using 5+1 tapes. > > I've this in the amanda.conf: > > dumpcycle 7 > runspercycle 5 > tapecycle 6 > > The tapes are labeled: > > Daily-000 (monday) > Daily-001 (tuesday) > Daily-002 (wednesday) > Daily-003 (thursday) > Daily-004 (friday) > Daily-005 (extra) > > What I want is this: > > For each day, use the Daily-00X tape. > > Today, thursday, I use the Daily-003 tape. With amdump Daily, I do the > backup. But the report says this: > > These dumps were to tape Daily-003. > The next tape Amanda expects to use is: Daily-006. > > This is my question. Why Daily-006? Why not the next tape is Daily-004? > > Thanks Check the tapelist file in /etc/amanda/Daily, or wherever the directory is that you have it in. Amanda uses this file to determine what tape to use next. You may have inserted an extra tape into the tapelist by accident. If you did, you can use amrmtape to remove it from the tapelist. -- Chris Dahn, SERG Code Ninja 3141 Chestnut St. Attn: MCS Department Philadephia, PA 19104 Office: 215.895.0203 Fax: 215.895.1582 <->Software Engineering Research Group<-> Feel the SERG! http://serg.mcs.drexel.edu/ CAT 186, The Microwave http://pgp.mit.edu:11371/pks/lookup?search=Christopher+Dahn&op=index
Re: No such file or directory
On Fri, Dec 14, 2001 at 10:28:57AM +0100, Tom Beer wrote: > Is $IFS being changed somewhere from the default? > > Sorry, but what is $IFS? > > "Internal Field Separator". See "man bash" -- - Dan Wilder <[EMAIL PROTECTED]> Technical Manager & Editor SSC, Inc. P.O. Box 55549 Phone: 206-782-8808 Seattle, WA 98155-0549URL http://embedded.linuxjournal.com/ -
Re: Is this correct?
On Fri, 14 Dec 2001 at 9:17am, Kurt Yoder wrote > You probably want at least one more tape in "tapecycle", so at least 6. > Everyone is always saying you want extras in case there's a bad run. > > (Not that I understand this; after all, if there's a bad run, why not > just increment "tapecycle" then?) Because that bad run may clobber the only level 0 of a particular filesystem that you have on tape. Upping tapecycle at that point is closing the barn door after the horses are gone... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: I don't understand this
On Friday 14 December 2001 06:51 am, Adolfo Manuel Pachón Rodríguez wrote: > This is my FIRST tapelist file: > > 0 Diaria-000 reuse > 0 Diaria-001 reuse > 0 Diaria-002 reuse > 0 Diaria-003 reuse > 0 Diaria-004 reuse > 0 Diaria-005 reuse > 0 Diaria-006 reuse > > I do amdump Diaria today, and the tapelist file is now: > > 20011214 Diaria-004 reuse > 0 Diaria-000 reuse > 0 Diaria-001 reuse > 0 Diaria-002 reuse > 0 Diaria-003 reuse > 0 Diaria-005 reuse > 0 Diaria-006 reuse > > The report says: > > These dumps were to tape Diaria-004. > The next tape Amanda expects to use is: Diaria-006. > > Why not the Diaria-005? Right. So, on the second listing there, you'll see that the last entry in the tapelist file is "0 Diaria-006 reuse". This means it's the next tape to be used. The most recently used tape is the 1st line in the file. The second line is the tape you would have used yesterday and so forth. Amanda "expects" the next tape to be the last one in the tapelist file, then it moves that tape entry to the top of the file after amdump runs. So, if you don't want Diaria-006 (I think you said you only had 6 tapes previously, so you should have Diaria-000 through Diaria-005), then you need to run "amrmtape Diaria-006" to remove it from the tapelist file. After that, the next tape it will expect is Diaria-005. -- Chris Dahn, SERG Code Ninja 3141 Chestnut St. Attn: MCS Department Philadephia, PA 19104 Office: 215.895.0203 Fax: 215.895.1582 <->Software Engineering Research Group<-> Feel the SERG! http://serg.mcs.drexel.edu/ CAT 186, The Microwave http://pgp.mit.edu:11371/pks/lookup?search=Christopher+Dahn&op=index
Re: I don't understand this
On Fri, Dec 14, 2001 at 10:15:05AM -0500, Chris Dahn wrote: > On Friday 14 December 2001 06:51 am, Adolfo Manuel Pachón Rodríguez wrote: > > This is my FIRST tapelist file: > > > > 0 Diaria-000 reuse > > 0 Diaria-001 reuse > > 0 Diaria-002 reuse > > 0 Diaria-003 reuse > > 0 Diaria-004 reuse > > 0 Diaria-005 reuse > > 0 Diaria-006 reuse > > > > I do amdump Diaria today, and the tapelist file is now: > > > > 20011214 Diaria-004 reuse > > 0 Diaria-000 reuse > > 0 Diaria-001 reuse > > 0 Diaria-002 reuse > > 0 Diaria-003 reuse > > 0 Diaria-005 reuse > > 0 Diaria-006 reuse > > > > The report says: > > > > These dumps were to tape Diaria-004. > > The next tape Amanda expects to use is: Diaria-006. > > > > Why not the Diaria-005? > > Right. So, on the second listing there, you'll see that the last entry in > the tapelist file is "0 Diaria-006 reuse". This means it's the next tape to > be used. The most recently used tape is the 1st line in the file. The second > line is the tape you would have used yesterday and so forth. Amanda "expects" > the next tape to be the last one in the tapelist file, then it moves that > tape entry to the top of the file after amdump runs. > > So, if you don't want Diaria-006 (I think you said you only had 6 tapes > previously, so you should have Diaria-000 through Diaria-005), then you need > to run "amrmtape Diaria-006" to remove it from the tapelist file. After that, > the next tape it will expect is Diaria-005. > >>> End of included message <<< As these are all "unused" tapes, if tape 5 is the only one available, would amanda use it? Also, as these are the first use, a little editor rearrangement of the tapelist file should not upset anything like indicies ... So could the file be hand edited to: 20011214 Diaria-004 reuse 0 Diaria-003 reuse 0 Diaria-002 reuse 0 Diaria-001 reuse 0 Diaria-000 reuse 0 Diaria-006 reuse 0 Diaria-005 reuse -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing [EMAIL PROTECTED] 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Linux dump
I was using dump to backup my linux clients; Apparently the previopus Sysadmin got no problems with dump on linux until one day dump got stuck dumping a huge backup (more than 12GB of data). I replaced the dump version for a new one, but then i got more weird status errors from amanda. I gived up, followed the advice i received here and swithed to Gnu Tar. Now the prod. backups are running fine :) The Solaris dump works greath and i'm still using it. JV. --- Chris Marble <[EMAIL PROTECTED]> escribió: > =?iso-8859-1?q?Jos=E9=20Vicente=20N=FA=F1ez=20Zuleta?= > wrote: > > > > Also another of my problems was using Linux dump. > Is > > simply useless with amanda, stick with tar (not > very > > usefull if you have to backup time sensitive files > as > > Rational Clearcase VOB's). > > I'm doing my backups with Linux dump, Solaris > ufsdump, HP-UX dump > and IRIX xfsdump. No problems. I did update the > Linux dump to > 0.4b23 from sourceforge.net. What problems was > Linux dump causing > for you? > -- > [EMAIL PROTECTED] - HMC UNIX Systems Manager > My opinions are my own and probably don't > represent anything anyway. = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com
Re: Smbclient Question
On Fri, 14 Dec 2001, Richard B. Tilley (Brad) wrote: > My question is this: what do I do now? How can I make amanda automate the > mounts and perform the backups? If this info is on the Net somewhere, > please forgive my question and simply point me to it. See docs/SAMBA in your amanda distribution directory. -Mitch
Re: I don't understand this
Adolfo Manuel Pachón Rodríguez wrote: > Hi all: > > I have an HP24DAT SCSI over Linux RH 7.1. I want to backup the weekdays > only, using 5+1 tapes. > > I've this in the amanda.conf: > > dumpcycle 7 > runspercycle 5 > tapecycle 6 > > The tapes are labeled: > > Daily-000 (monday) > Daily-001 (tuesday) > Daily-002 (wednesday) > Daily-003 (thursday) > Daily-004 (friday) > Daily-005 (extra) > > What I want is this: > > For each day, use the Daily-00X tape. > > Today, thursday, I use the Daily-003 tape. With amdump Daily, I do the > backup. But the report says this: > > These dumps were to tape Daily-003. > The next tape Amanda expects to use is: Daily-006. > > This is my question. Why Daily-006? Why not the next tape is Daily-004? > > Thanks > I don't think amanda works as you're expecting. You can only give amanda a sequence of tapes, but not say "I want x tape on x day and y tape on y day". Amanda will simply go through each tape in its list and use them as needed. So your 000 tape will end up being used any day of the week. Of course, if you give amanda 10 tapes and do 5 backups in a week, you'll always be using 0 and 6 on a Monday, 1 and 7 on a Tuesday. Also, in order to use them in sequence and not skip from 3 to 6, you have to label them all in order. So if you labeled 0 through 5, let amanda use 0 and 1, then labeled 6, amanda will expect the sequence to be 0 1 6 2 3 4 5. I'm not sure how to change which tape amanda expects next, short of removing the tapes using amrmtape and relabeling them. Edit the tapelist file? Anyone else on the list have any answers?
Re: Is this correct?
Adolfo Manuel Pachón Rodríguez wrote: > Hi all: > > I have 5 tapes for one HP24DAT SCSI unit. I want to use one tape per day, > not including saturday/monday. > > Is this the correct configuration? > > dumpcycle 7 days > runspercycle 5 days > tapecycle 5 tapes > > thanks > You probably want at least one more tape in "tapecycle", so at least 6. Everyone is always saying you want extras in case there's a bad run. (Not that I understand this; after all, if there's a bad run, why not just increment "tapecycle" then?)
Smbclient Question
Hello All, I have successfully been using amanda now for a week on all my Linux servers, and it works beautifully. Now I would like to try it on a few NT4 and W2K machines. I have created a NT4 domain user that can mount all the windows shares that I would like to backup. I have tested that this user can indeed mount the shares by manually running "smbclient //server/share -U user_name" from the amanda server and it works. I have also created a amandapass in /etc on the amanda server with entries for the Windows machines. My question is this: what do I do now? How can I make amanda automate the mounts and perform the backups? If this info is on the Net somewhere, please forgive my question and simply point me to it. Thank you, Brad
Probs with configure & readline
Hello, I have a bit of a problem with getting ./configure to recognize the readline library. >From its log file, it looks as though configure tries to #include , but that is installed in /usr/include/readline/readline.h Is that a problem with configure, or am I missing something? -- Ansgar --- Ansgar Esztermann Institut fuer theoretische Physik II| Heinrich-Heine-Universitaet Duesseldorf | +49-211-8113703 (phone) Geb. 25.32.02 | Universitaetsstr. 1 | +49-211-8112262 (fax) D-40225 Duesseldorf, Germany| [EMAIL PROTECTED] http://www2.thphy.uni-duesseldorf.de/~ansgar ---
Re: I don't understand this
This is my FIRST tapelist file: 0 Diaria-000 reuse 0 Diaria-001 reuse 0 Diaria-002 reuse 0 Diaria-003 reuse 0 Diaria-004 reuse 0 Diaria-005 reuse 0 Diaria-006 reuse I do amdump Diaria today, and the tapelist file is now: 20011214 Diaria-004 reuse 0 Diaria-000 reuse 0 Diaria-001 reuse 0 Diaria-002 reuse 0 Diaria-003 reuse 0 Diaria-005 reuse 0 Diaria-006 reuse The report says: These dumps were to tape Diaria-004. The next tape Amanda expects to use is: Diaria-006. Why not the Diaria-005? I don't understand it. Please, help Thanks >>>>>>>>>>>>>>>>>> Mensaje original <<<<<<<<<<<<<<<<<< El 13/12/2001, 22:32:45, Chris Dahn <[EMAIL PROTECTED]> escribió sobre el tema Re: I don't understand this: > On Thursday 13 December 2001 12:58 pm, Adolfo Manuel Pachón Rodríguez wrote: > > Hi all: > > > > I have an HP24DAT SCSI over Linux RH 7.1. I want to backup the weekdays > > only, using 5+1 tapes. > > > > I've this in the amanda.conf: > > > > dumpcycle 7 > > runspercycle 5 > > tapecycle 6 > > > > The tapes are labeled: > > > > Daily-000 (monday) > > Daily-001 (tuesday) > > Daily-002 (wednesday) > > Daily-003 (thursday) > > Daily-004 (friday) > > Daily-005 (extra) > > > > What I want is this: > > > > For each day, use the Daily-00X tape. > > > > Today, thursday, I use the Daily-003 tape. With amdump Daily, I do the > > backup. But the report says this: > > > > These dumps were to tape Daily-003. > > The next tape Amanda expects to use is: Daily-006. > > > > This is my question. Why Daily-006? Why not the next tape is Daily-004? > > > > Thanks > Check the tapelist file in /etc/amanda/Daily, or wherever the directory is > that you have it in. Amanda uses this file to determine what tape to use > next. You may have inserted an extra tape into the tapelist by accident. If > you did, you can use amrmtape to remove it from the tapelist. > -- > Chris Dahn, SERG Code Ninja > 3141 Chestnut St. > Attn: MCS Department > Philadephia, PA 19104 > Office: 215.895.0203 > Fax: 215.895.1582 > <->Software Engineering Research Group<-> > Feel the SERG! > http://serg.mcs.drexel.edu/ > CAT 186, The Microwave > http://pgp.mit.edu:11371/pks/lookup?search=Christopher+Dahn&op=index
Re: Dumper hangs
Thanks. The latest release note (0.4b25) says: Found a workaroung for the dump deadlock problem (3 childs stuck in pause(), father in read()). The workaround seems to work for me and several beta-testers. If it doesn't work for you, please report back. I didn't try it yet, but this looks like my problem. Vincent - Original Message - From: "Joshua Baker-LePain" <[EMAIL PROTECTED]> To: "Vincent GRENET" <[EMAIL PROTECTED]> Cc: "Amanda Users" <[EMAIL PROTECTED]> Sent: Thursday, December 13, 2001 1:30 PM Subject: Re: Dumper hangs > On Thu, 13 Dec 2001 at 10:33am, Vincent GRENET wrote > > > Amanda dumper hangs sometimes; and backup fails with data timeout: > > > > I set dtimeout to 3600s; it hangs whether I use a holding disk or not. > > When the dump succeeds, it runs for 46 minutes. > > > > My configuration is a RHS 7.1 (amanda 2.4.2p2). > > Many people (myself included) have hit this issue with Linux dump (or > perhaps the combo of Linux dump and 2.4 kernels). You have two options. > You can upgrade to the latest dump/restore versions from > dump.sourceforge.net, and that may or may not fix the problem. It didn't > for me. Or you can switch to using GNUtar for your backups. This is what > I did, and haven't looked back. > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University > >
Re: No such file or directory
Is $IFS being changed somewhere from the default? Sorry, but what is $IFS?
dump fails with bread and lseek trouble
Hi, Has anyone seen or hear of this problem. --8<--snip*--- /-- geko60.ehb /usr lev 0 FAILED [/sbin/dump returned 3] sendbackup: start [geko60.ehbas.com:/usr level 0] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/bin/gzip -dc |/sbin/restore -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | DUMP: Date of this level 0 dump: Fri Dec 14 04:10:47 2001 | DUMP: Dumping /dev/sda5 (/usr) to standard output | DUMP: Label: /usr | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 1521017 tape blocks. | DUMP: Volume 1 started with block 1 at: Fri Dec 14 04:11:00 2001 | DUMP: dumping (Pass III) [directories] | DUMP: dumping (Pass IV) [regular files] ? DUMP: bread: lseek fails ? DUMP: short read error from /dev/sda5: [block -680431872]: count=4096, got=0 ? DUMP: bread: lseek2 fails! ? DUMP: short read error from /dev/sda5: [sector -680431872]: count=512, got=0 ? DUMP: bread: lseek2 fails! ? DUMP: short read error from /dev/sda5: [sector -680431871]: count=512, got=0 ? DUMP: bread: lseek2 fails! ? DUMP: short read error from /dev/sda5: [sector -680431870]: count=512, got=0 ? DUMP: bread: lseek2 fails! ? DUMP: short read error from /dev/sda5: [sector -680431869]: count=512, got=0 ? DUMP: bread: lseek2 fails! more of the samethen... ? DUMP: short read error from /dev/sda5: [block -580422152]: count=4096, got=0 ? DUMP: More than 32 block read errors from 135093768 ? DUMP: This is an unrecoverable error. ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: fopen on /dev/tty fails: No such device or address | DUMP: The ENTIRE dump is aborted. sendbackup: error [/sbin/dump returned 3] I've run e2fsck -c /dev/sda5 to no avail. I also upgraded the dump utility that came with the standard Red Hat 7.1 install to dump-04b21 to dump-04b22. Any ideas what can cause this and how I might fix it? Regards, Tom Robinson This e-mail may contain confidential information and/or copyright material and is intended for the use of the addressee only. Disclosure, distribution or copying of this message is strictly prohibited by law. If you have received this communication in error, please notify the sender immediately by telephone on (01273) 234665 and delete the e-mail. The contents of this message may contain personal views that are not the opinions of EHBAS Ltd, unless specifically stated.
