On 02/12/2015 11:05 AM, Stefan G. Weichinger wrote:
How are multiple holding disks used?
Do multiple dumpers write to separate holding disks in parallel?
yes
Is it possible to configure this?
no, it is always done.
thanks, Stefan
How are multiple holding disks used?
Do multiple dumpers write to separate holding disks in parallel?
Is it possible to configure this?
thanks, Stefan
the system with about
580 GB holding storage. The system starts with the requested 5 dumpers, but
utilizes only 3, from which the third only works once. The others work along
but never use more than about 25% of the available holding disk space. No
error messages or other complaints.
I would
, the
procedure takes almost 24 hours.
I have to backup about 700 GB uncompressed, and supply the system with about
580 GB holding storage. The system starts with the requested 5 dumpers, but
utilizes only 3, from which the third only works once. The others work along
but never use more than about 25
the system with about
580 GB holding storage. The system starts with the requested 5 dumpers, but
utilizes only 3, from which the third only works once. The others work along
but never use more than about 25% of the available holding disk space. No
error messages or other complaints.
from my
about 700 GB uncompressed, and supply the system with about
580 GB holding storage. The system starts with the requested 5 dumpers, but
utilizes only 3, from which the third only works once. The others work along
but never use more than about 25% of the available holding disk space. No
error
. The system starts with the requested 5 dumpers, but
utilizes only 3, from which the third only works once. The others work along
but never use more than about 25% of the available holding disk space. No
error messages or other complaints.
from my amanda.conf
.
.
.
inparallel 5 # maximum
I'm having more weird problems backing up the server I mentioned
yesterday (where amstatus was dying). I came in this morning, and
discovered that last night's incremental backup job is still running,
and that it seems to be because 4 dumper threads to that server are
stalled out.
amstatus
the just the
prompt. Instead this shows dumpers busy. Why is this? surely the backup should
not be busy if I've run an amflush on it and cleaned up. It should now show
nothing and sit and wait to the next nights backup run
Attached is an
output of the amstatus command once I've run the cleanup
this shows dumpers busy. Why is this?
I think amstatus just summarizes the current log, so it shows the
last state of the current backup, even after the backup is finished.
Since your backup was killed, amstatus is showing you where it was
at the time it died.
Frank
surely
the backup should
Hello David,
Thanks for your analysis of the problem.
Do you know why the write failed?
The attached patch should fix the infinite loop, could you try it and
let me know if it works.
Jean-Louis
On Thu, Jan 09, 2003 at 11:58:33PM +, David Trusty wrote:
I think I may have found the cause of
Thanks!!
I believe the errno from the write was EPIPE.
David
From: Jean-Louis Martineau [EMAIL PROTECTED]
To: David Trusty [EMAIL PROTECTED]
CC: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: dumpers exiting with signal 11 in version 2.4.3?
Date: Fri, 10 Jan 2003 08:39:15 -0500
Hello
: John R. Jackson [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: David Trusty [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: dumpers exiting with signal 11 in version 2.4.3? Date: Fri, 03
Jan 2003 18:22:19 -0500
I received these messages at the end of a backup:
driver: dumper3 exited
The start of the looping appears to have coincided with a tape
change. Note that I use chg-zd-mtx and ammt.
Any ideas?
Thanks!
David
From: John R. Jackson [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: David Trusty [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: dumpers exiting with signal 11
Hello,
* David Trusty ([EMAIL PROTECTED]) [20030105 13:25] thus spake:
I have more information on this problem.
I see these messages in the 'amdump' file:
dumper: logfile.c@202: memory allocation failed (28 bytes requested)
dumper: debug.c@345: memory allocation failed (22 bytes
My runtapes is 4.
I also think it may happen every time the tape is changed.
I still can't seem to get a core dump for analysis. I used
the 'limit' command in the shell where I did the amdump,
but it did not seem to take effect. I will try a few variants
to see if I can get a core dump to be
I received these messages at the end of a backup:
driver: dumper3 exited with signal 11
Oops. :-)
I am running version 2.4.3.
What OS?
I believe most files were written to tape, but these messages look unusual.
I did not find core files, but they may be somewhere I haven't yet
discovered.
I have a client with 4 fast processors and would like to use at least 2 or 3
of them if possible for dumps. ...
Dumps can be very I/O bound. Make sure you have enough bandwidth as well.
Is it possible to get amanda to dump more
than 1 partition on the same client at a time to the backup
to
counteract that I'd like amanda to run multiple dumpers on the same client
but not necessarily the same partition.
Thanks!
Trevor.
I have a client with 4 fast processors and would like to use at least 2 or 3
of them if possible for dumps. ...
Dumps can be very I/O bound. Make sure you have enough bandwidth as well.
Is it possible to get amanda to dump more
than 1 partition on the same client at a time to the backup
(From amstatus)
adv2.kellogg.nwu.edu://129.105.xxx.xxx/progfiles 1 1059392k wait for dumping
adv2.kellogg.nwu.edu://66.92.xxx.xx/backupdoc 05585k dumping 1472k
(26.36%) (18:21:38)
9 dumpers idle : client-constrained
Is there some way to make them dump at the same time? What's
Is there some way to make them dump at the same time? What's this client
constrainted stuff ? :)
See:
http://www.backupcentral.com/amanda-21.html
http://www.backupcentral.com/amanda-20.html
Basically, client constrained means the client is running everything
it can run at the moment
Looking at the amstatus code in 2.4.2 indicates the output you indicated
*is* displayed if you pass the --stats option.
Thanks. I used to have a mix of 2.4.1p1 and 2.4.2 and I don't think
this arg used to be needed.
However, I don't see any way to get that output using 2.4.1p1.
I don't
How do I know how many dumpers are active? I just changed my config to
allow 2 while i figure out this problem with the disk. It said both
dumpers
were active, but there were no dumper processes on the one client box
in my disklist file.
Robert
--
:wq
Date: Thu, 09 Nov 2000 18:42:16 -0500
From: "John R. Jackson" [EMAIL PROTECTED]
How do I know how many dumpers are active? ...
Amanda will start the number you tell it to.
Up to MAX_DUMPERS (which in my copy of server-src/driverio.c is 63).
The real question is,
how well are they
Up to MAX_DUMPERS (which in my copy of server-src/driverio.c is 63).
True.
amplot is handy for this, as well ...
Also true.
(What's "broken" about it...?)
It doesn't generate any of that output I posted :-(. I'm guessing it
might be because the dump was finished, so it skipped over doing
26 matches
Mail list logo
