Re: File-driver: degraded mode
Actually, that's not true. It goes by your tapecycle setting. You have a tapecycle of 9 tapes, and only 8 tapes are labeled for some reason (as you noted, tape 4 is missing), so amanda will not overwrite tapes until you've used 9. If you label tape 4, then amanda should start cycling through as normal. You probably will want to look into why they've all been written on the 22nd, however. Yes, that's it. I forced relabeled vtape 4. It's working again as normal. It's funny why it detect tape 4 as active but not labeled. I don't have sendmail installed in any of the server machine. Sendmail has lots of bugs and security vulnerability, is there other way to send amanda report? Log files is fine for me. For example in amflush, from what I read, it can only send reports by mail and through sendmail, unless I run it manually using -s to pipe all report to standard out/err. Thanks all for the helps. I think the amanda setup is almost complete, just keeping running first to see what other problem could occur before it's officially online. Kuas.
Holding Space Size and autoflush
-slot next changer: got exit: 0 str: 9 file:/amandatapes/daily taper: slot 9: date 20050422 label daily9 (active tape) changer: opening pipe to: /opt/utils/amanda-2.4.5/libexec/chg-disk -slot next changer: got exit: 0 str: 1 file:/amandatapes/daily taper: slot 1: date 20050425 label daily1 (active tape) changer: opening pipe to: /opt/utils/amanda-2.4.5/libexec/chg-disk -slot next changer: got exit: 0 str: 2 file:/amandatapes/daily taper: slot 2: date 20050422 label daily2 (active tape) driver: result time 0.245 from taper: TAPE-ERROR [new tape not found in rack] dump of driver schedule before start degraded mode: dump of driver schedule after start degraded mode: driver: state time 0.245 free kps: 2000 space: 296960 taper: DOWN idle-dumpers: 4 qlen tapeq: 29 runq: 0 roomq : 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 0.245 if : free 600 if LE0: free 400 if LOCAL: free 1000 driver: hdisk-state time 0.245 hdisk 0: free 296960 dumpers 0 driver: state time 0.245 free kps: 2000 space: 296960 taper: DOWN idle-dumpers: 4 qlen tapeq: 29 runq: 0 roomq : 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 0.245 if : free 600 if LE0: free 400 if LOCAL: free 1000 driver: hdisk-state time 0.245 hdisk 0: free 296960 dumpers 0 driver: QUITTING time 0.245 telling children to quit driver: send-cmd time 0.245 to taper: QUIT taper: DONE [idle wait: 0.000 secs] driver: FINISHED time 0.246 /usr/sbin/sendmail: No such file or directory [EMAIL PROTECTED] DailySet1]# taper: buffer[09] at 0xbf4c1000 taper: buffer[10] at 0xbf4c9000 taper: buffer[11] at 0xbf4d1000 taper: buffer[12] at 0xbf4d9000 taper: buffer[13] at 0xbf4e1000 taper: buffer[14] at 0xbf4e9000 taper: buffer[15] at 0xbf4f1000 taper: buffer[16] at 0xbf4f9000 taper: buffer[17] at 0xbf501000 taper: buffer[18] at 0xbf509000 taper: buffer[19] at 0xbf511000 taper: buffer structures at 0xbf519000 for 240 bytes changer: opening pipe to: /opt/utils/amanda-2.4.5/libexec/chg-disk -info changer: got exit: 0 str: 3 9 1 changer: opening pipe to: /opt/utils/amanda-2.4.5/libexec/chg-disk -slot current changer: got exit: 0 str: 3 file:/amandatapes/daily taper: slot 3: date 20050422 label daily3 (active tape) changer: opening pipe to: /opt/utils/amanda-2.4.5/libexec/chg-disk -slot next changer: got exit: 0 str: 4 file:/amandatapes/daily taper: slot 4: date 20050422 label daily1 (active tape) changer: opening pipe to: /opt/utils/amanda-2.4.5/libexec/chg-disk -slot next changer: got exit: 0 str: 5 file:/amandatapes/daily taper: slot 5: date 20050422 label daily5 (active tape) changer: opening pipe to: /opt/utils/amanda-2.4.5/libexec/chg-disk -slot next changer: got exit: 0 str: 6 file:/amandatapes/daily taper: slot 6: date 20050422 label daily6 (active tape) changer: opening pipe to: /opt/utils/amanda-2.4.5/libexec/chg-disk -slot next changer: got exit: 0 str: 7 file:/amandatapes/daily taper: slot 7: date 20050422 label daily7 (active tape) changer: opening pipe to: /opt/utils/amanda-2.4.5/libexec/chg-disk -slot next changer: got exit: 0 str: 8 file:/amandatapes/daily taper: slot 8: date 20050422 label daily8 (active tape) changer: opening pipe to: /opt/utils/amanda-2.4.5/libexec/chg-disk -slot next changer: got exit: 0 str: 9 file:/amandatapes/daily taper: slot 9: date 20050422 label daily9 (active tape) changer: opening pipe to: /opt/utils/amanda-2.4.5/libexec/chg-disk -slot next changer: got exit: 0 str: 1 file:/amandatapes/daily taper: slot 1: date 20050425 label daily1 (active tape) changer: opening pipe to: /opt/utils/amanda-2.4.5/libexec/chg-disk -slot next changer: got exit: 0 str: 2 file:/amandatapes/daily taper: slot 2: date 20050422 label daily2 (active tape) driver: result time 0.245 from taper: TAPE-ERROR [new tape not found in rack] dump of driver schedule before start degraded mode: dump of driver schedule after start degraded mode: driver: state time 0.245 free kps: 2000 space: 296960 taper: DOWN idle-dumpers: 4 qlen tapeq: 29 runq: 0 roomq : 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 0.245 if : free 600 if LE0: free 400 if LOCAL: free 1000 driver: hdisk-state time 0.245 hdisk 0: free 296960 dumpers 0 driver: state time 0.245 free kps: 2000 space: 296960 taper: DOWN idle-dumpers: 4 qlen tapeq: 29 runq: 0 roomq : 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 0.245 if : free 600 if LE0: free 400 if LOCAL: free 1000 driver: hdisk-state time 0.245 hdisk 0: free 296960 dumpers 0 driver: QUITTING time 0.245 telling children to quit driver: send-cmd time 0.245 to taper: QUIT taper: DONE [idle wait: 0.000 secs] driver: FINISHED time 0.246 /usr/sbin/sendmail: No such file or directory --- end amflush log Kuas.
File-driver: degraded mode
Hi all, I am using file-driver setup. And set all the tape to reuse, I set the tapecycle=9, dumpcycle=5 (full backup every 5 days), runspercycle=5,runtapes=1 and tapechanger=chg-disk. And in the tapelist file: 20050422 daily8 reuse 20050422 daily5 reuse 20050422 daily7 reuse 20050422 daily6 reuse 20050422 daily1 reuse 20050422 daily3 reuse 20050422 daily2 reuse 20050422 daily9 reuse But, I just realize that my holding-disk is full and some backups failed because of that. The reason is amanda is running on degraded mode. The output of amcheck verifies that: Holding disk /opt/amanda-holding: 11179172 KB disk space available, that's plenty amcheck-server: slot 7: date 20050422 label daily7 (active tape) amcheck-server: slot 8: date 20050422 label daily8 (active tape) amcheck-server: slot 9: date 20050422 label daily9 (active tape) amcheck-server: slot 1: date 20050425 label daily1 (active tape) amcheck-server: slot 2: date 20050422 label daily2 (active tape) amcheck-server: slot 3: date 20050422 label daily3 (active tape) amcheck-server: slot 4: date 20050422 label daily1 (active tape) amcheck-server: slot 5: date 20050422 label daily5 (active tape) amcheck-server: slot 6: date 20050422 label daily6 (active tape) ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test I don't understand why in slot 4 was not labeled with daily4. But back to the problem, all the tapes are supposed to be reuse, why it does not recycle the tapes after the last taped is filled? Am I missing any configuration? Thanks, Kur.
Re: File-driver: degraded mode
Frank Smith wrote: --On Tuesday, April 26, 2005 22:26:54 -0400 kuas [EMAIL PROTECTED] wrote: Hi all, I am using file-driver setup. And set all the tape to reuse, I set the tapecycle=9, dumpcycle=5 (full backup every 5 days), runspercycle=5,runtapes=1 and tapechanger=chg-disk. And in the tapelist file: 20050422 daily8 reuse 20050422 daily5 reuse 20050422 daily7 reuse 20050422 daily6 reuse 20050422 daily1 reuse 20050422 daily3 reuse 20050422 daily2 reuse 20050422 daily9 reuse But, I just realize that my holding-disk is full and some backups failed because of that. The reason is amanda is running on degraded mode. The output of amcheck verifies that: Holding disk /opt/amanda-holding: 11179172 KB disk space available, that's plenty amcheck-server: slot 7: date 20050422 label daily7 (active tape) amcheck-server: slot 8: date 20050422 label daily8 (active tape) amcheck-server: slot 9: date 20050422 label daily9 (active tape) amcheck-server: slot 1: date 20050425 label daily1 (active tape) amcheck-server: slot 2: date 20050422 label daily2 (active tape) amcheck-server: slot 3: date 20050422 label daily3 (active tape) amcheck-server: slot 4: date 20050422 label daily1 (active tape) amcheck-server: slot 5: date 20050422 label daily5 (active tape) amcheck-server: slot 6: date 20050422 label daily6 (active tape) ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test I don't understand why in slot 4 was not labeled with daily4. But back to the problem, all the tapes are supposed to be reuse, why it does not recycle the tapes after the last taped is filled? Am I missing any configuration? Your dumpcycle is 5 days, but all your tapes are less than five days old, so Amanda won't reuse them yet. Did you write all 9 tapes on the 22nd, or is your changer script not properly updating the tapelist? The date on each tape should be the day it was last written to. I see, so it will go strictly by the day to prevent full backup lost as reference. I was actually testing amanda at that time, by calling amdump straight in the command line. How can I fix this without resetting all the tapes again. Can I reset the day count? Is there anyway I can force it going to full backup and let it continue backup in the tape? Thanks. Kuas.
file-driver tape problem
Hi all, Thanks for all the helps before, exclusion list works for me now. I am using the file-driver mechanism for the tape, the configuration follows ch. 13 in the manual. I have a recurring problem, sometimes the tapes are in a strange stage. This is the output of amcheck: $ amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /tmp/amanda-holding: 1818064 KB disk space available, that's plenty amcheck-server: slot 9: date 20050422 label daily9 (active tape) amcheck-server: strange amanda header: AMANDA: amcheck-server: slot 1: not an amanda tape amcheck-server: slot 2: date 20050422 label daily2 (active tape) amcheck-server: slot 3: date 20050422 label daily3 (active tape) amcheck-server: slot 4: date 20050422 label daily1 (active tape) amcheck-server: slot 5: date 20050422 label daily5 (active tape) amcheck-server: slot 6: date 20050422 label daily6 (active tape) amcheck-server: slot 7: date 20050422 label daily7 (active tape) amcheck-server: slot 8: date 20050422 label daily8 (active tape) ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /opt/utils/amanda/amanda/var/amanda/DailySet1/curinfo/sphynx.ece.toronto.edu/_home_lionel: does not exist NOTE: index dir /opt/utils/amanda/amanda/var/amanda/DailySet1/index/sphynx.ece.toronto.edu/_home_lionel: does not exist Server check took 0.209 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 10.529 seconds, 0 problems found (brought to you by Amanda 2.4.4p4) [EMAIL PROTECTED] amanda]$ Slot 1 was labeled properly before, but somehow, it has nothing in the directory. What could have caused this? How should I fix this, the proper way? I tried to remove the tape from the tapelist by removing the entries in the tapelist and relabeled the directory slot1. That resulted in different problem. Thanks, Kuas.
Debian Compile failed
I can compile everything in FC3 and FC1 without a problem. But when I tried to compile Amanda in Debian it gave this error in configure: # ./configure --program-prefix=/opt/amanda-2.4.5 --with-user=amanda --with-group=disk : : checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking dependency style of g++... none checking how to run the C++ preprocessor... /lib/cpp configure: error: C++ preprocessor /lib/cpp fails sanity check See `config.log' for more details. When I check if gnu c++ compiler and the standard library, it is installed: # dpkg --list | grep g++ ii g++-2.95 2.95.4-22 The GNU C++ compiler # dpkg --list | grep libstdc ii libstdc++2.10- 2.95.4-22 The GNU stdc++ library (development files) ii libstdc++2.10- 2.95.4-22 The GNU stdc++ library ii libstdc++5 3.3.5-8The GNU Standard C++ Library v3 Does any one know what package or step am I missing? Thanks. Kuas
Re: Exclude list and disklist
Joshua Baker-LePain wrote: On Thu, 21 Apr 2005 at 12:39pm, Kuas wrote I setup the back-up so that all excluded list are in /var/lib/amanda/exclude.txt on each machine, so that I can use a general dump-type. But I haven't been able to get it work. For example, I backed up all the /var/spool/mail for every user (the emails are in 1 file), except: A and B. I put in the exclude.txt on that machine: /var/spool/mail/A and /var/spool/mail/B. This doesn't work, I wonder if they're absolute path. In the dumptype, I put: Exclude paths are relative. So, if your DLE is /var/spool/mail, you'd have to exclude ./A and ./B. Got it. Now, In a situation I want to give flexibility to users, that they are the one that knows if a directory needs to be excluded or backup to be more efficient in the backup process. From the howto and some trial I can specify in the dumptype, instead of the absolute path to the exclude file, but just the name of the file: exclude list exclude.list So each user needs to create this file and has full authority to change it. The effect I saw (from amcheck) is that it will try to find that the file in each of the DLE that uses that dumptype. But the problem I saw, when there is a problem like the file doesn't exist. That will stop all backup processes or at least for that DLE. Has anybody else seen this, or it's just normal behavior when there's a problem, they just stop the backup. Is the syntax of that exclude behavior is prohibited. Has anybody tried doing similiar purpose like this before? Would there be a better way to do it? Thanks, Kuas.
