[no subject]
auth 160941f7 subscribe amanda-users [EMAIL PROTECTED] Thanks Clint ~~ Clinton Dilks Ph: (09) 8154200 Ext 7171 Computer Services Team Email: [EMAIL PROTECTED] - HORTRESEARCH - __ The contents of this e-mail are privileged and/or confidential to the named recipient and are not to be used by any other person and/or organisation. If you have received this e-mail in error, please notify the sender and delete all material pertaining to this e-mail. __
problems with with Amanda-2.4.3b1
Hi I'm currently evaluating the first beta of the 2.4.3beta1 version and i have the following problems with the tape changer. Im under solaris and i use the stc driver with the associate changer script. It works quite well on the 2.4.2p2 version but with the 2.4.3b1 version i got the following error on the amdump file driver: hdisk-state time 22984.326 hdisk 0: free 5480521 dumpers 3 taper: writing end marker. [MCI16 ERR kb 35984768 fm 271] changer: opening pipe to: /usr/local/libexec/stc-changer -info changer: got exit: 0 str: 4 10 1 changer_query: changer return was 10 1 changer_query: searchable = 0 changer_find: looking for MCI17 changer is searchable = 0 changer: opening pipe to: /usr/local/libexec/stc-changer -slot current changer: got exit: 0 str: 4 /dev/rmt/0n taper: slot 4: date 20011214 label MCI16 (active tape) changer: opening pipe to: /usr/local/libexec/stc-changer -slot next changer: got exit: 0 str: 5 /dev/rmt/0n taper: slot 5: date Xlabel MCI17 (exact label match) taper: read label `MCI17' date `X' taper: wrote label `MCI17' date `20011214' driver: result time 23208.351 from taper: QUITTING 00-00549 [writing file: short write] driver: driver received unexpected token (2) from taper taper: DONE [idle wait: 7082.735 secs] taper: writing end marker. [MCI17 OK kb 0 fm 0] amdump: end at Sat Dec 15 03:25:50 MET 2001 dumper: error [bad command after RQ-MORE-DISK: 1] error [bad command after RQ-MORE-DISK: 1] dumper: pid 1093 finish time Sat Dec 15 03:37:24 2001 Has someone already seen this problem between driver and taper? The output of taper seems ok but not for driver Neverthless i will go investigate in the source code Thanks in advance for any help -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
No such device or address
Dear Members, I tried to restore to a remote host by giving the following command but the system replied as follows: amanda:~# /usr/sbin/amrestore -p /dev/nst0 debian | rsh debian -l root /sbin/restore ivf - /sbin/restore: cannot open /dev/tty: No such device or address amrestore: 0: skipping start of tape: date 20011128 label DCS01 amrestore: 1: restoring debian.cs.ruh.ac.lk._var_backups_testdebian.20011128.0Level 0 dump of /var (dir /backups/testdebian) on debian:/dev/sda6 Label: none /sbin/restore Verify tape and initialize maps Dump date: Wed Nov 28 12:10:22 2001 Dumped from: the epoch Extract directories from tape Initialize symbol table. Have you any idea please help me! Bye! cdamith Technical Officer Department of Computer Science/Computer Unit Wellamadama, MATARA SRI LANKA http://www.ruh.ac.lk
Re: problems with with Amanda-2.4.3b1
Hello Eric, Could you try the latest snapshot available from http://www.iro.umontreal.ca/~martinea/amanda It should fix this problem. Jean-Louis On Tue, Dec 18, 2001 at 09:21:43AM +0100, Eric Doutreleau wrote: Hi I'm currently evaluating the first beta of the 2.4.3beta1 version and i have the following problems with the tape changer. Im under solaris and i use the stc driver with the associate changer script. It works quite well on the 2.4.2p2 version but with the 2.4.3b1 version i got the following error on the amdump file driver: hdisk-state time 22984.326 hdisk 0: free 5480521 dumpers 3 taper: writing end marker. [MCI16 ERR kb 35984768 fm 271] changer: opening pipe to: /usr/local/libexec/stc-changer -info changer: got exit: 0 str: 4 10 1 changer_query: changer return was 10 1 changer_query: searchable = 0 changer_find: looking for MCI17 changer is searchable = 0 changer: opening pipe to: /usr/local/libexec/stc-changer -slot current changer: got exit: 0 str: 4 /dev/rmt/0n taper: slot 4: date 20011214 label MCI16 (active tape) changer: opening pipe to: /usr/local/libexec/stc-changer -slot next changer: got exit: 0 str: 5 /dev/rmt/0n taper: slot 5: date Xlabel MCI17 (exact label match) taper: read label `MCI17' date `X' taper: wrote label `MCI17' date `20011214' driver: result time 23208.351 from taper: QUITTING 00-00549 [writing file: short write] driver: driver received unexpected token (2) from taper taper: DONE [idle wait: 7082.735 secs] taper: writing end marker. [MCI17 OK kb 0 fm 0] amdump: end at Sat Dec 15 03:25:50 MET 2001 dumper: error [bad command after RQ-MORE-DISK: 1] error [bad command after RQ-MORE-DISK: 1] dumper: pid 1093 finish time Sat Dec 15 03:37:24 2001 Has someone already seen this problem between driver and taper? The output of taper seems ok but not for driver Neverthless i will go investigate in the source code Thanks in advance for any help -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED] -- 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: backup failed and nothing in holding disk
On Tue, 18 Dec 2001 at 9:17am, Hery Zo RAKOTONDRAMANANA wrote I often have this problem: amdump reports that backup failed due to input/output error, somehow nothing has been written to holding disk. Has anyone any idea on it. I'm using Amanda 2.4.1p1-12 on a Linux debian potato 2.2r3 with a STT 2000N (travan tr5) tape. We really need more info here. What exactly is in the post-backup email from amanda (just cut-n-paste it)? Are there any error messages in the system logs? I/O errors are the fault of the OS, not amanda -- amanda is just telling you what the OS told it. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: problems with with Amanda-2.4.3b1
On Tue, 18 Dec 2001, Jean-Louis Martineau wrote: Hi I will tonight I got the amanda-2.4.3b1-20011214 snapshot Thanks for your quick answer Hello Eric, Could you try the latest snapshot available from http://www.iro.umontreal.ca/~martinea/amanda It should fix this problem. Jean-Louis On Tue, Dec 18, 2001 at 09:21:43AM +0100, Eric Doutreleau wrote: Hi I'm currently evaluating the first beta of the 2.4.3beta1 version and i have the following problems with the tape changer. Im under solaris and i use the stc driver with the associate changer script. It works quite well on the 2.4.2p2 version but with the 2.4.3b1 version i got the following error on the amdump file driver: hdisk-state time 22984.326 hdisk 0: free 5480521 dumpers 3 taper: writing end marker. [MCI16 ERR kb 35984768 fm 271] changer: opening pipe to: /usr/local/libexec/stc-changer -info changer: got exit: 0 str: 4 10 1 changer_query: changer return was 10 1 changer_query: searchable = 0 changer_find: looking for MCI17 changer is searchable = 0 changer: opening pipe to: /usr/local/libexec/stc-changer -slot current changer: got exit: 0 str: 4 /dev/rmt/0n taper: slot 4: date 20011214 label MCI16 (active tape) changer: opening pipe to: /usr/local/libexec/stc-changer -slot next changer: got exit: 0 str: 5 /dev/rmt/0n taper: slot 5: date Xlabel MCI17 (exact label match) taper: read label `MCI17' date `X' taper: wrote label `MCI17' date `20011214' driver: result time 23208.351 from taper: QUITTING 00-00549 [writing file: short write] driver: driver received unexpected token (2) from taper taper: DONE [idle wait: 7082.735 secs] taper: writing end marker. [MCI17 OK kb 0 fm 0] amdump: end at Sat Dec 15 03:25:50 MET 2001 dumper: error [bad command after RQ-MORE-DISK: 1] error [bad command after RQ-MORE-DISK: 1] dumper: pid 1093 finish time Sat Dec 15 03:37:24 2001 Has someone already seen this problem between driver and taper? The output of taper seems ok but not for driver Neverthless i will go investigate in the source code Thanks in advance for any help -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED] -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
timeout waiting for ack
I'm having problems backing up one particular host on my network. amandad.debug reports: amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, giving up! amandad: pid 32317 finish time Tue Dec 18 10:57:51 2001 There is another host (theoretically) identically configured which backs up fine. The 2 hosts in question are on my DMZ, protected by a firewall. The rule sets for the 2 hosts are identical (I've been over them with the networking guy 3 times). Yet one host backs up fine, the other does not. Can someone point me in the right direction of what to look at? 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: timeout waiting for ack
In a message dated: Tue, 18 Dec 2001 11:17:17 EST Paul Lussier said: I'm having problems backing up one particular host on my network. amandad.debug reports: amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, giving up! amandad: pid 32317 finish time Tue Dec 18 10:57:51 2001 It appears that problem is that there are simply too many file systems on this particular client. I'm guessing the problem is that there's too much information to cram into a UDP packet, and that's why it's failing. Anyone have any ideas as to how to work around this? I kind of have to back up the entire system all together, but I'd be interested in some creative ways to get all my data on the same tape set. 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
sdt 5000
Hi All I am trying to setup amanda with a sdt 5000 scsi tape unit. Does anybody have the exact setting for amanda.conf for this unit. Hope to hear from yuo soon. Joseph
Re: timeout waiting for ack
Paul Lussier wrote: I'm having problems backing up one particular host on my network. amandad.debug reports: amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, giving up! amandad: pid 32317 finish time Tue Dec 18 10:57:51 2001 There is another host (theoretically) identically configured which backs up fine. The 2 hosts in question are on my DMZ, protected by a firewall. The rule sets for the 2 hosts are identical (I've been over them with the networking guy 3 times). Yet one host backs up fine, the other does not. Can someone point me in the right direction of what to look at? Actually, that one: http://amanda.sourceforge.net/cgi-bin/fom?_highlightWords=firewallfile=139 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 -- Yuri Pismerov, TUCOWS.COM INC. (416) 535-0123 ext. 1352
Re: timeout waiting for ack
Paul Lussier wrote: I'm having problems backing up one particular host on my network. amandad.debug reports: amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, giving up! amandad: pid 32317 finish time Tue Dec 18 10:57:51 2001 There is another host (theoretically) identically configured which backs up fine. The 2 hosts in question are on my DMZ, protected by a firewall. The rule sets for the 2 hosts are identical (I've been over them with the networking guy 3 times). Yet one host backs up fine, the other does not. Can someone point me in the right direction of what to look at? http://amanda.sourceforge.net/cgi-bin/fom?_highlightWords=firewallfile=16 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 -- Yuri Pismerov, TUCOWS.COM INC. (416) 535-0123 ext. 1352
Re: timeout waiting for ack
In a message dated: Tue, 18 Dec 2001 13:38:58 EST Yura Pismerov said: http://amanda.sourceforge.net/cgi-bin/fom?_highlightWords=firewallfile=16 Thanks, except it's not a firewall problem, nor was amcheck reporting errors. As I pointed out in a subsequent post/followup, the problem appears to be simply too many file systems on that one client. Thanks anyway. -- 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
Need exact settings for firewall with amanda
I've been successful so far setting up Amanda to back up my hosts inside my firewall, where my tapeserver is also located. Now, I'm trying to set it up to also backup the hosts outside the firewall. Unfortunately, I don't control the firewall, I have to just tell the folks who do exactly what I need. So far, I've told them I need the following ports opened: 10080/udp 10082/tcp 10083/tcp I just noticed that, while these are the ports listed in the INSTALL document, the patch-system actually put these lines in my /etc/services (client only; no tape server): www:/tmp/amanda # grep amanda /etc/services amanda 10080/udp amanda 10080/tcp kamanda 10081/udp amandaidx 10082/tcp Is there a misprint in the INSTALL document? Should I also asked the firewall group to open port 10080/tcp? If anyone's ever done this (specify the firewall settings needed by amanda), could you let me know what you requested? 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
debug file overwrite
My /tmp/amanda debug files seem to get overwritten during each entry in the disklist so only one entry remains the next after an amdump run. sendsize.debug is the only file showing the results for each entry. Where is the control of whether these get opened for append or truncate? -- 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] sdt 5000
nope but if you have tape problems try using a block size of 4096 On Wed, Dec 19, 2001 at 05:28:57AM +1100, Joseph Sirucka wrote: Hi All I am trying to setup amanda with a sdt 5000 scsi tape unit. Does anybody have the exact setting for amanda.conf for this unit. Hope to hear from yuo soon. Joseph ___ Amanda-users mailing list [EMAIL PROTECTED] http://mail.topic.com.au/cgi-bin/mailman/listinfo/amanda-users -- Jason Thomas Phone: +61 2 6257 7111 System Administrator - UID 0 Fax:+61 2 6257 7311 tSA Consulting Group Pty. Ltd. Mobile: 0418 29 66 81 1 Hall Street Lyneham ACT 2602 http://www.topic.com.au/ msg08977/pgp0.pgp Description: PGP signature
Re: [Amanda-users] debug file overwrite
you probably want to upgrade newer versions of amanda store the files with a data stamp as part of the name! On Tue, Dec 18, 2001 at 04:29:51PM -0500, Jon LaBadie wrote: My /tmp/amanda debug files seem to get overwritten during each entry in the disklist so only one entry remains the next after an amdump run. sendsize.debug is the only file showing the results for each entry. Where is the control of whether these get opened for append or truncate? msg08978/pgp0.pgp Description: PGP signature
Problems with chio tape changer under NetBSD
This may affect other versions of *BSD which also use chio to manage the tape changer, I don't know ... I seem to be having problems with the chg-chio script to manage my tape changer (an ExaByte Mammoth 10-tape unit) - chg-chio appears to want to change tapes that aren't present, even when chio has told it so ... Does anyone else have these problems with it? I am thinking of rewriting it from scratch, but I want to make sure someone hasn't already done so ... -- Malcolm HerbertThis brain intentionally [EMAIL PROTECTED]left blank
problems with Amanda-2.4.3b1
Hi I'm currently evaluating the first beta of the 2.4.3beta1 version and i have the following problems with the tape changer. Im under solaris and i use the stc driver with the associate changer script. It works quite well on the 2.4.2p2 version but with the 2.4.3b1 version i got the following error on the amdump file driver: hdisk-state time 22984.326 hdisk 0: free 5480521 dumpers 3 taper: writing end marker. [MCI16 ERR kb 35984768 fm 271] changer: opening pipe to: /usr/local/libexec/stc-changer -info changer: got exit: 0 str: 4 10 1 changer_query: changer return was 10 1 changer_query: searchable = 0 changer_find: looking for MCI17 changer is searchable = 0 changer: opening pipe to: /usr/local/libexec/stc-changer -slot current changer: got exit: 0 str: 4 /dev/rmt/0n taper: slot 4: date 20011214 label MCI16 (active tape) changer: opening pipe to: /usr/local/libexec/stc-changer -slot next changer: got exit: 0 str: 5 /dev/rmt/0n taper: slot 5: date Xlabel MCI17 (exact label match) taper: read label `MCI17' date `X' taper: wrote label `MCI17' date `20011214' driver: result time 23208.351 from taper: QUITTING 00-00549 [writing file: short write] driver: driver received unexpected token (2) from taper taper: DONE [idle wait: 7082.735 secs] taper: writing end marker. [MCI17 OK kb 0 fm 0] amdump: end at Sat Dec 15 03:25:50 MET 2001 dumper: error [bad command after RQ-MORE-DISK: 1] error [bad command after RQ-MORE-DISK: 1] dumper: pid 1093 finish time Sat Dec 15 03:37:24 2001 Has someone already seen this problem between driver and taper? The output of taper seems ok but not for driver Neverthless i will go investigate in the source code Thanks in advance for any help -- Eric Doutreleau [EMAIL PROTECTED] Les signatures les plus courtes sont les signatures les meilleures
Re: backup failed and nothing in holding disk
En réponse à Joshua Baker-LePain [EMAIL PROTECTED]: On Tue, 18 Dec 2001 at 9:17am, Hery Zo RAKOTONDRAMANANA wrote I often have this problem: amdump reports that backup failed due to input/output error, somehow nothing has been written to holding disk. Has anyone any idea on it. I'm using Amanda 2.4.1p1-12 on a Linux debian potato 2.2r3 with a STT 2000N (travan tr5) tape. We really need more info here. What exactly is in the post-backup email from amanda (just cut-n-paste it)? Are there any error messages in the system logs? I/O errors are the fault of the OS, not amanda -- amanda is just telling you what the OS told it. I think it seems like my tape is out of service. This we can replace. Somehow, I just thought that when amanda encounters problems during backup, it just performs it into holding disk, so I was expecting having something written in my holding disk. Am I wrong? Or can you tell me where can I check for error messages ? Here is the e-mail report for this matter. Hery Zo *** THE DUMPS DID NOT FINISH PROPERLY! *** A TAPE ERROR OCCURRED: [rewinding tape: Input/output error]. *** PERFORMED ALL DUMPS TO HOLDING DISK. THESE DUMPS WERE TO DISK. Flush them onto tape jeudi1 or a new tape. Tonight's dumps should go onto 1 tape: a new tape. FAILURE AND STRANGE DUMP SUMMARY: localhost /etc lev 0 FAILED [can't switch to incremental dump] localhost /usr/local/bin lev 0 FAILED [can't switch to incremental dump] localhost /root lev 0 FAILED [can't switch to incremental dump] localhost /var/backups lev 0 FAILED [can't switch to incremental dump] localhost /home/simicro lev 0 FAILED [can't switch to incremental dump] localhost /var/courrier/vmail lev 0 FAILED [can't switch to incremental dump] STATISTICS: Total Full Daily Dump Time (hrs:min) 0:00 0:00 0:00 (0:00 start) Output Size (meg) 0.0 0.0 0.0 Original Size (meg) 0.0 0.0 0.0 Avg Compressed Size (%) -- -- -- Tape Used (%) 0.0 0.0 0.0 Filesystems Dumped 0 0 0 Avg Dump Rate (k/s) -- -- -- Avg Tp Write Rate (k/s) -- -- -- DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- -- -- localhost /etc 0 FAILED localhost /home/simicro 0 FAILED localhost /root 0 FAILED localhost /usr/local/bin 0 FAILED localhost /var/backups 0 FAILED localhost -ourrier/vmail 0 FAILED (brought to you by Amanda version 2.4.1p1) -- Joshua Baker-LePain Department of Biomedical Engineering Duke University Hery Zo RAKOTONDRAMANANA Simicro Internet Tél: (261) 20 22 648 83 Fax: (261) 20 22 661 83 --
Re: problems with with Amanda-2.4.3b1
Hi I just tried it and it solve my problem Thank you very much P.S the autoflush feature is really a cool feature Hello Eric, Could you try the latest snapshot available from http://www.iro.umontreal.ca/~martinea/amanda It should fix this problem. Jean-Louis On Tue, Dec 18, 2001 at 09:21:43AM +0100, Eric Doutreleau wrote: Hi I'm currently evaluating the first beta of the 2.4.3beta1 version and i have the following problems with the tape changer. Im under solaris and i use the stc driver with the associate changer script. It works quite well on the 2.4.2p2 version but with the 2.4.3b1 version i got the following error on the amdump file driver: hdisk-state time 22984.326 hdisk 0: free 5480521 dumpers 3 taper: writing end marker. [MCI16 ERR kb 35984768 fm 271] changer: opening pipe to: /usr/local/libexec/stc-changer -info changer: got exit: 0 str: 4 10 1 changer_query: changer return was 10 1 changer_query: searchable = 0 changer_find: looking for MCI17 changer is searchable = 0 changer: opening pipe to: /usr/local/libexec/stc-changer -slot current changer: got exit: 0 str: 4 /dev/rmt/0n taper: slot 4: date 20011214 label MCI16 (active tape) changer: opening pipe to: /usr/local/libexec/stc-changer -slot next changer: got exit: 0 str: 5 /dev/rmt/0n taper: slot 5: date Xlabel MCI17 (exact label match) taper: read label `MCI17' date `X' taper: wrote label `MCI17' date `20011214' driver: result time 23208.351 from taper: QUITTING 00-00549 [writing file: short write] driver: driver received unexpected token (2) from taper taper: DONE [idle wait: 7082.735 secs] taper: writing end marker. [MCI17 OK kb 0 fm 0] amdump: end at Sat Dec 15 03:25:50 MET 2001 dumper: error [bad command after RQ-MORE-DISK: 1] error [bad command after RQ-MORE-DISK: 1] dumper: pid 1093 finish time Sat Dec 15 03:37:24 2001 Has someone already seen this problem between driver and taper? The output of taper seems ok but not for driver Neverthless i will go investigate in the source code
Re: Problems with chio tape changer under NetBSD
Malcolm Herbert writes: - This may affect other versions of *BSD which also use chio to manage - the tape changer, I don't know ... Why not use chg-scsi? It knows how to use the chio ioctl(2) interfaces to manipulate the robots. I use it to run my Exabyte EXB-480 robot, my HP/Compaq SureStore DLT robot, and my Archive 4586NP loader. I run on NetBSD 1.5.*, on an AlphaPC64. (previously on NetBSD 1.3 on i386) I wrote the predecessor of chg-scsi on the NetBSD 1.3 system. -- Eric Schnoebelen[EMAIL PROTECTED] http://www.cirr.com Man seeking truth: Were we created like this, or did we evolve from apes? Guru: We were bought on credit and never paid for, and are being repossessed one by one.
