Reset amanda
Hi! How can I reset amanda to clear all vtapes and start at zero? -- Best Regards Thomas Wegner www.tommiwe.de
Trouble with new Client
Hi! Amanda is running on my server since August 2009. I backup only one ubuntu-client. 3 weeks ago I made a completely new installation on my ubuntu-client using ubuntu karmic-koala. I installed amamda-client on this client and restored all necessary files from my amanda-server. It works very well. But now I want to backup my client like 3 weeks ago. The backup ends with an error. This is the message: Amanda Backup Client Hosts Check ERROR: NAK chef: user backup from knecht.fritz.box is not allowed to execute the service noop: Please add amdump to the line in /var/backups/.amandahosts on the client I wonder where I have to add those lines? I've added it in /var/lib/.amamdahosts, /var/backups/.amandahosts which is a symbolic link to /etc/amandahosts. The error messages are still the same. What can I do? -- Best Regards Thomas Wegner www.tommiwe.de
Re: Trouble with new Client
Am Sonntag, den 29.11.2009, 13:18 -0600 schrieb Dustin J. Mitchell: Hi Dustin! Thanks a lot. It works! :-)) On closer inspection, the error message in the original post gives enough information to reconstruct the proper amandahosts line. Amanda Backup Client Hosts Check ERROR: NAK chef: user backup from knecht.fritz.box is not allowed to execute the service noop: Please add amdump to the line in /var/backups/.amandahosts on the client So this is an amcheck run, presumably to be followed by an amdump run, from host knecht.fritz.box, and sending username backup. So, on the client (not the server!), you should add knecht.fritz.box backup amdump to /var/backups/.amandahosts That's it. Not using FQDN was my problem. -- Best Regards Thomas Wegner www.tommiwe.de
Re: amrecover
Am Samstag, den 20.12.2008, 11:57 + schrieb Nuno Dias: When I try to issue the command amrecover in the client machine, I have the message [request failed: timeout waiting for ACK] Is your client listed in /etc/hosts? Try this. -- Regards Thomas
Re: recovery question
On Wednesday 19 November 2008, Gene Heskett wrote: Hi Gene! Extracting files using tape drive chg-disk on host coyote. Load tape Dailys-17 now Continue [?/Y/n/s/d]? Volume labeled 'Dailys-17' not found. Is your tape labeld correct? -- Regards Thomas
Re: amrecover fails
Am Dienstag, den 21.10.2008, 16:49 -0400 schrieb Timothy Ball: Hi Timothy! [EMAIL PROTECTED]:~$ cat .amandahosts localhost root amindexd amidxtaped localhost amandabackup amdump localhost.localdomain root amindexd amidxtaped localhost.localdomain amandabackup amdump CLIENT-BOXroot CLIENT-BOX root amindexd amidxtaped Can you ping CLIENT-BOX? If you can't, you should add the server name to /etc/hosts. Maybe your backup server can't resolve CLIENT-BOX. -- Regards Thomas
Re: Amanda can't overwrite old tapes
Am Donnerstag, den 16.10.2008, 17:44 -0400 schrieb Jon LaBadie: Hello Jon! Assuming you have ten tapes labeled 01-10, and use tape 01 today, that tape, tape 01 can not be used again until tapes 02-10 are used. When tape 01 can be used again, amanda is willing to use it or another never used tape such as tape 11 or 12 if they are also in circulation. But it will not use tape 02, because (tapecycle -1) other tapes have not been used since tape 02 was last used. Thanks for explanation. I think I will edit my configuration. -- Regards Thomas
Re: Amanda can't overwrite old tapes
Am Donnerstag, den 16.10.2008, 17:39 -0400 schrieb Jean-Louis Martineau: Hello Jean-Louis! Look correctly at the error message: label weekly1-10 match labelstr but it not listed in the tapelist file. Why it is not in the tapelist file? You probably have only 9 tapes in the tapelist, so they are all actives and can't be reused. Thanks. I didn't recognized this error message. -- Regards Thomas
Re: exlude list
Am Donnerstag, den 09.10.2008, 12:14 -0600 schrieb Mario Silva Borrego: depending what your amanda.conf says is the way you will hold this exclude file in the client side. And the format is quite easy, you just need to list the directories or files to be exclude in each run, although it can always be modified. Thanks to all for advice. I've created an exlude list on the client and seems to work. :-) Now I'm testing to recover some files. -- Regards Thomas Homepage: www.tommiwe.de Key fingerprint = 5451 1661 23A7 0C7D CA32 48B0 F266 5D60 0436 17C4
exlude list
Hi! I'm new to this list. I don't understand the way exclude lists work. I want to exclude /var/tmp, /var/log, /var/spool and /var/cache and also /tmp. Where do I have define exclude defintions? Is /etc/amanda/exclude_file the correct path? Can anyone send me an example of this file? -- Thanks Tommi Homepage: www.tommiwe.de Key fingerprint = 5451 1661 23A7 0C7D CA32 48B0 F266 5D60 0436 17C4
Re: Connection refused by peer
Am Montag, den 31.10.2005, 08:59 -0400 schrieb Gene Heskett: Hi Gene! Thanks for that detailed answer. In /root/.amandahosts is an entry 'localhost root'. Wrong location for the .amandahosts file. It should be in the $home/$user directory whom amanda runs as. The FAQ discusses this (whats wrong with building and running amanda as root) I believe. My user is backup and he has an .amandahosts file in his home directory. If you built and installed amanda as root, then rip it all out, nuke the src dir, then do an adduser amanda and make this user a member of the group disk or backup (whatever your machine uses for those disk related tasks) then do an su amanda, untar a fresh copy of the src tree, recopy your config script into that directory and re-exec that script, which in my case finishes up with a make, all done as the user amanda. Then become root again and reinstall it. The permissions will now be correct. I've installed a debian package so that I don't know what build options were chosen at build time. Can I check this anywhere? I don't whant to build amanda from source. Greetings Thomas
Re: Connection refused by peer
Am Freitag, den 28.10.2005, 14:28 +0200 schrieb Thomas Wegner: Hello. I will answer to myself. Am Freitag, den 28.10.2005, 13:07 +0200 schrieb Alexander Jolk: Could you try without a changer, or debug your changer script? That might be the problem. I have no changer and in amanda.conf is no changer defined. -- [EMAIL PROTECTED]:~$ amtape backup_woche device amtape: no tpchanger specified in /etc/amanda/backup_woche/amanda.conf - That's an error message I believe, even though it's not evidently worded as such. You seem to have specified runtapes 1 without giving a changer. Either configure a changer if you want more than one tape per run, or just set runtapes to 1. No, I didn't configured any changer or any runtapes. This is my amanda.conf: I took a look at the FAQ on www.amanda.org and read the how to configure tape changer chapter. One suggestions is to set runtapes to 1 as you wrote and comment out tpchanger. But this won't work on my machine. The error message is the same as ever. Then I've tried 'runtapes 1000' and 'tpchanger chg-manual '. This seems to work. But I wonder about the short time amanda uses for backup my /home directory. How can I proof if backup was correct? When I start 'amrecover -C /etc/amanda/backup_woche/ -s localhost -t localhost' as user backup amanda tells me that amrecover must run as root. When I start amrecover as root the following message appears: %-- [EMAIL PROTECTED]:/home/tommi # amrecover -C /etc/amanda/backup_woche/ -s localhost -t localhost AMRECOVER Version 2.4.5. Contacting server on localhost ... 220 chef AMANDA index server (2.4.5) ready. 500 Access not allowed: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed -% In /root/.amandahosts is an entry 'localhost root'. Has anyone an idea? Thomas
Re: Connection refused by peer
Am Freitag, den 28.10.2005, 13:07 +0200 schrieb Alexander Jolk:
Could you try without a changer, or debug your changer script? That
might be the problem.
I have no changer and in amanda.conf is no changer defined.
--
[EMAIL PROTECTED]:~$ amtape backup_woche device
amtape: no tpchanger specified in /etc/amanda/backup_woche/amanda.conf
-
That's an error message I believe, even though it's not evidently worded
as such. You seem to have specified runtapes 1 without giving a
changer. Either configure a changer if you want more than one tape per
run, or just set runtapes to 1.
No, I didn't configured any changer or any runtapes. This is my
amanda.conf:
-
org Wochenbackup # your organization name for reports
mailto root tommi # space separated list of operators at your site
dumpuser backup # the user to run dumps under
#
inparallel 4# maximum dumpers that will run in parallel
netusage 600 # maximum net bandwidth for Amanda, in KB per sec
# a filesystem is due for a full backup once every dumpcycle days
#dumpcycle 7 days # the number of days in the normal dump cycle
#tapecycle 7 tapes # the number of tapes in rotation
dumpcycle 1 day
tapecycle 2 tapes
bumpsize 20 MB # minimum savings (threshold) to bump level 1 - 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * (level-1)**bumpmult
#runtapes 9 # explained in WHATS.NEW
#tpchanger no-changer # the tape-changer glue script, see
TAPE.CHANGERS
tapedev /dev/nst0 # Linux @ tuck, important: norewinding
# tapedev /dev/nrst8 # or use the (no-rewind!) tape device directly
#Eintrag von Hand vom 23.10.2005
tapetype HP-DAT-C1537A
labelstr ^Wochenbackup[0-9][0-9]*$# label constraint regex: all tapes
must match
diskdir /var/backups/amandadump/backup_woche # where the holding disk
is
disksize 500 MB # how much space can we use on it
#diskdir /dumps/amanda/work # additionaly holding disks can be
specified
#diskdir /mnt/disk4
#disksize 1000 MB # they are used round-robin
# Amanda needs a few MB of diskspace for the log and debug files,
# as well as a database. This stuff can grow large, so the conf
directory
# isn't usually appropriate.
infofile /var/lib/amanda/backup_woche/curinfo # database filename
logfile /var/log/amanda/backup_woche/log # log filename
# where the index files live
indexdir /var/lib/amanda/backup_woche/index
# tapetypes
#Eintrag von Hand - siehe amanda.org vom 23.10.2005
define tapetype HP-DAT-C1537A {
comment HP C1537A Streamer - DDS3 Tape
length 11694 mbytes
filemark 78 kbytes
speed 830 kps
}
define dumptype nocomp-user {
comment Non-root partitions on slow machines
options no-compress
priority medium
}
Thomas
Re: Connection refused by peer
Am Donnerstag, den 27.10.2005, 12:23 +0200 schrieb Alexander Jolk: Thomas Wegner wrote: But in /var/log/amanda/backup_woche/amdump.1 are these lines: [...] taper: tape changer failed with exit status -1 Could you try without a changer, or debug your changer script? That might be the problem. I have no changer and in amanda.conf is no changer defined. -- [EMAIL PROTECTED]:~$ amtape backup_woche device amtape: no tpchanger specified in /etc/amanda/backup_woche/amanda.conf -
Connection refused by peer
Hi!
I'am a newbee in using amanda. I have configured one machine als server
and client to backup this one. I followed the instructions described on
www.amanda.org.
I'm using debian ubuntu (breezy badger) with linux kernel 2.6.12-9.
amcheck runs well.
-
[EMAIL PROTECTED]:~$ amcheck backup_woche
Amanda Tape Server Host Check
-
Holding disk /var/backups/amandadump/backup_woche: 23574028 kB disk
space availa ble, that's plenty
NOTE: skipping tape-writable test
Tape Wochenbackup001 label ok
NOTE: info dir /var/lib/amanda/backup_woche/curinfo/chef: does not exist
NOTE: it will be created on the next run.
Server check took 35.892 seconds
Amanda Backup Client Hosts Check
Client check: 1 host checked in 0.133 seconds, 0 problems found
(brought to you by Amanda 2.4.5)
--
But amdump backup_woche fails. This is the message from amanda:
---
*** THE DUMPS DID NOT FINISH PROPERLY!
The next tape Amanda expects to use is: a new tape.
The next new tape already labelled is: Wochenbackup001.
FAILURE AND STRANGE DUMP SUMMARY:
driver: FATAL reading result from taper: Connection reset by peer
chef hda7 RESULTS MISSING
STATISTICS:
Total Full Incr.
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: tapecycle (1) = runspercycle (1)
planner: Adding new disk chef:hda7.
DUMP SUMMARY:
DUMPER STATSTAPER
STATS
HOSTNAME DISKL ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS
KB/s
-- -
chef hda7 MISSING
--
(brought to you by Amanda version 2.4.5)
---
Have anyone suggestions about a solution?
Greetings from Germany
Thomas
Re: Connection refused by peer
Am Mittwoch, den 26.10.2005, 13:25 -0400 schrieb Jon LaBadie: On Wed, Oct 26, 2005 at 06:56:35PM +0200, Alexander Jolk wrote: Thomas Wegner wrote: [...] NOTES: planner: tapecycle (1) = runspercycle (1) [...] Have anyone suggestions about a solution? Hmm, I sense a suggestion looming behind that line of your report... For testing I've changed my amanda.conf in: dumpcycle 1 day tapecycle 2 tapes This is the result: FAILURE AND STRANGE DUMP SUMMARY: driver: FATAL reading result from taper: Connection reset by peer chef hda7 RESULTS MISSING [...] NOTES: planner: Adding new disk chef:hda7. DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS KB/s -- - chef hda7 MISSING -- The same behaviour as bevore. :-(( Definitely should be adjusted. But, would that prevent/stop the dump from completing to holding disk? The report seemed to me to show no activity. Sounds like it is time to check the 'debug files' on the server and on the client, possibly saved under /tmp/amanda. Sorry. But in /tmp are no debug files. I can offer log-files. In example : --- DISK planner chef hda7 START planner date 20051026 INFO planner Adding new disk chef:hda7. START driver date 20051026 STATS driver startup time 0.004 FATAL driver reading result from taper: Connection reset by peer FINISH planner date 20051026 time 25.606 -- And dumpoutput: - amdump: start at Wed Oct 26 18:23:46 CEST 2005 amdump: datestamp 20051026 planner: pid 11133 executable /usr/lib/amanda/planner version 2.4.5 planner: build: VERSION=Amanda-2.4.5 planner:BUILT_DATE=Thu Jun 9 09:26:39 UTC 2005 planner:BUILT_MACH=Linux vernadsky 2.6.10 #1 SMP Fri May 13 09:24:22 UTC 2005 i686 GNU/Linux planner:CC=gcc planner:CONFIGURE_COMMAND='./configure' '--prefix=/usr' '--bindir=/usr/sbin' '--mandir=/usr/share/man' '--libexecdir=/usr/lib/amanda' '--enable-shared' '--sysconfdir=/etc' '--localstatedir=/var/lib' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' '--with-index-server=localhost' '--with-user=backup' '--with-group=backup' '--with-bsd-security' '--with-amandahosts' '--with-smbclient=/usr/bin/smbclient' '--with-tcpportrange=5,50100' '--with-udpportrange=840,860' planner: paths: bindir=/usr/sbin sbindir=/usr/sbin planner:libexecdir=/usr/lib/amanda mandir=/usr/share/man planner:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda planner:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ planner:RDEV_PREFIX=/dev/ DUMP=/sbin/dump planner:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF planner:XFSDUMP=/sbin/xfsdump XFSRESTORE=/sbin/xfsrestore planner:VXDUMP=UNDEF VXRESTORE=UNDEF planner:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar planner:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip planner:LPRCMD=/usr/bin/lpr MAILER=/usr/bin/mail planner:listed_incr_dir=/var/lib/amanda/gnutar-lists planner: defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 planner:DEFAULT_TAPE_SERVER=localhost planner:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE planner:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS planner:CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP planner:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast planner:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc planner: time 0.000: dgram_bind: socket bound to 0.0.0.0.853 READING CONF FILES... driver: pid 11134 executable /usr/lib/amanda/driver version 2.4.5 driver: tape size 11974656 driver: send-cmd time 0.002 to taper: START-TAPER 20051026 driver: adding holding disk 0 dir /var/backups/amandadump/backup_woche size 512000 chunksize 1048576 reserving 512000 out of 512000 for degraded-mode dumps driver: started dumper0 pid 11136 driver: started dumper1 pid 11137 dumper: dgram_bind: socket bound to 0.0.0.0.856 dumper: pid 11136 executable dumper0 version 2.4.5, using port 856 dumper: dgram_bind: socket bound to 0.0.0.0.857 dumper: pid 11137 executable dumper1 version 2.4.5, using port 857 driver: started dumper2 pid 11138 dumper: dgram_bind: socket bound to 0.0.0.0.859 dumper: pid 11139 executable dumper3 version 2.4.5, using port 859 driver: started dumper3 pid 11139 dumper: dgram_bind: socket bound to 0.0.0.0.858 dumper: pid 11138 executable dumper2 version 2.4.5, using port 858 planner: time 0.029: startup took 0.029 secs SENDING FLUSHES... ENDFLUSH SETTING UP FOR ESTIMATES... planner: time 0.029: setting up estimates for chef:hda5 chef:hda5 overdue
Re: Connection refused by peer
Am Mittwoch, den 26.10.2005, 18:46 -0400 schrieb Jon LaBadie: Sounds like it is time to check the 'debug files' on the server and on the client, possibly saved under /tmp/amanda. Sorry. But in /tmp are no debug files. I can offer log-files. In example : I didn't type /tmp, but /tmp/amanda. Your logs show this to be the debug directory as in the following line: planner:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda I didn't saw any directory /tmp/amandy yesterday. The server and client are still on the same machine called chef. I've started the machine this morning and there was no directory /tmp/amanda. After running amdump it was created. Clear again and run amdump. Look in the newly created files for more details on the error that causes the network problems. I can't see any hints. sendsize.debug shows: sendsize: debug 1 pid 11492 ruid 34 euid 34: start at Thu Oct 27 06:52:11 2005 sendsize: version 2.4.5 sendsize[11494]: time 0.011: calculating for amname 'hda7', dirname '/home', spindle -1 sendsize[11494]: time 0.011: getting size via dump for hda7 level 0 sendsize[11494]: time 0.011: calculating for device '/dev/hda7' with 'ext3' sendsize[11494]: time 0.011: running /sbin/dump 0Ssf 1048576 - /dev/hda7 sendsize[11494]: time 0.012: running /usr/lib/amanda/killpgrp sendsize[11492]: time 0.012: waiting for any estimate child: 1 running sendsize[11494]: time 24.833: 170489856 sendsize[11494]: time 24.872: . sendsize[11494]: estimate time for hda7 level 0: 24.860 sendsize[11494]: estimate size for hda7 level 0: 166494 KB sendsize[11494]: time 24.872: asking killpgrp to terminate sendsize[11494]: time 25.874: done with amname 'hda7', dirname '/home', spindle -1 sendsize[11492]: time 25.874: child 11494 terminated normally sendsize: time 25.874: pid 11492 finish time Thu Oct 27 06:52:37 2005 amandad.debug shows: --- amandad: debug 1 pid 11489 ruid 34 euid 34: start at Thu Oct 27 06:52:11 2005 amandad: version 2.4.5 amandad: build: VERSION=Amanda-2.4.5 amandad:BUILT_DATE=Thu Jun 9 09:26:39 UTC 2005 amandad:BUILT_MACH=Linux vernadsky 2.6.10 #1 SMP Fri May 13 09:24:22 UTC 2005 i686 GNU/Linux amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--prefix=/usr' '--bindir=/usr/sbin' '--mandir=/usr/share/man' '--libexecdir=/usr/lib/amanda' '--enable-shared' '--sysconfdir=/etc' '--localstatedir=/var/lib' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' '--with-index-server=localhost' '--with-user=backup' '--with-group=backup' '--with-bsd-security' '--with-amandahosts' '--with-smbclient=/usr/bin/smbclient' '--with-tcpportrange=5,50100' '--with-udpportrange=840,860' amandad: paths: bindir=/usr/sbin 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 VDUMP=UNDEF VRESTORE=UNDEF amandad:XFSDUMP=/sbin/xfsdump XFSRESTORE=/sbin/xfsrestore amandad:VXDUMP=UNDEF VXRESTORE=UNDEF amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip amandad:LPRCMD=/usr/bin/lpr 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=backup FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 000-70620608 SEQ 1130388731 SECURITY USER backup SERVICE noop OPTIONS features=feff9ffe7f; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 000-70620608 SEQ 1130388731 amandad: time 0.000: bsd security: remote host localhost user backup local user backup amandad: time 0.011: amandahosts security check passed amandad: time 0.011: running service noop amandad: time 0.011: sending REP packet: Amanda 2.4 REP HANDLE 000-70620608 SEQ 1130388731 OPTIONS features=feff9ffe7f; amandad: time 0.011: got packet: Amanda 2.4 ACK HANDLE 000-70620608 SEQ 1130388731 amandad: time 0.011: pid 11489 finish time Thu Oct 27 06:52:11 2005 Thomas
Re: Connection refused by peer
Am Mittwoch, den 26.10.2005, 18:46 -0400 schrieb Jon LaBadie: Hi. Here am I once again! I deletet all files in /tmp/amanda and starts amcheck and amdump once again. All output to /tmp/amanda seems ok to me. But in /var/log/amanda/backup_woche/amdump.1 are these lines: -- driver: send-cmd time 0.002 to taper: START-TAPER 20051027 driver: adding holding disk 0 dir /var/backups/amandadump/backup_woche size 512000 chunksize 1048576 reserving 512000 out of 512000 for degraded-mode dumps driver: started dumper0 pid 12211 driver: started dumper1 pid 12212 driver: started dumper2 pid 12213 driver: started dumper3 pid 12214 driver: flush size 0 driver: start time 0.005 inparallel 4 bandwidth 600 diskspace 512000 dir OBSOLETE datestamp 20051027 driver: drain-ends tapeq FIRST big-dumpers ttt dumper: dgram_bind: socket bound to 0.0.0.0.856-- could this be a problem? taper: tape changer failed with exit status -1 at /usr/lib/amanda//taperlib.pm line 112. or this ? driver: reading result from taper: Connection reset by peer -- Thomas
