On Wed, Aug 29, 2018 at 18:38:11 +, Ryan, Lyle (US) wrote:
> I have now cut the dumpcycle down to 10, and the tapecycle down to 20, and
> was hoping Amanda could recover.
> But I'm still getting "out of holding space in degraded mode" in the logs,
> and Amanda seems t
Hi Lyle,
> under tapetype: length=5000GB and part-size=1GB
did you really define 5000GB (= 5TB) per tape?
If you instructed amanda to create vtapes on the fly and you really use
the above tape length then you'll run out of disc space quite quickly...
BRs,
Jens
Hello Lyle,
> Using Amanda 3.4.5 on Centos 7.4 to backup Linux
> clients onto 11TB of local disk. Holding area and vtapes > are all in the
> same 11TB filesystem, which is now entirely > full!
I remember that the documentation contained a warning about that. Holding disk
should be an
ot = 30
> under tapetype: length=5000GB and part-size=1GB
>
> I have now cut the dumpcycle down to 10, and the tapecycle down to 20, and
> was hoping Amanda could recover.
> But I'm still getting "out of holding space in degraded mode" in the logs,
> and Amanda seems total
-size=1GB
I have now cut the dumpcycle down to 10, and the tapecycle down to 20, and was
hoping Amanda could recover.
But I'm still getting "out of holding space in degraded mode" in the logs, and
Amanda seems totally stuck.
How would I start over, throw away all the backups made so far,
Am 29.03.2013 06:30, schrieb Kamil Jońca:
As far I know amanda does not do full dump when no tape (vtape in my
case) is not available.
Is there any way to force it?
If not what is the rationale for this?
(I would prefer keep disk with vtapes as short as possible turned on)
KJ
Hm,
what about
C.Scheeder christ...@scheeder.de writes:
Am 29.03.2013 06:30, schrieb Kamil Jońca:
As far I know amanda does not do full dump when no tape (vtape in my
case) is not available.
Is there any way to force it?
If not what is the rationale for this?
(I would prefer keep disk with vtapes as
Hello again!
mail.tarkvarastuudio.ee / lev 1 FAILED [can't dump in degraded mode]
I can't understand why Amanda goes to degraded mode.
OK, this is another of these cases where you can't find the answer on
Google until 1 minute *after* you post to the list. Turns out this is
a known
:
mail.tarkvarastuudio.ee / lev 1 FAILED [can't dump in degraded mode]
I can't understand why Amanda goes to degraded mode. The disk
containing vtapes is definitely available. I can successfully run this
command:
su backup -c touch /backup/slot2/testfile
Also, amcheck shows
Jean-Louis There is a bug if the taper crash early, the attached
Jean-Louis patch fix, the dump should go to holding disk.
Doug Thanks. I'll try it tonight.
That patch to driver.c fixes the problem of no dumps happening when in
degraded mode.
Thanks.
) {
log_add(L_WARNING,
_(going into degraded mode because of taper component error.));
@@ -1925,6 +1926,7 @@ handle_taper_result(
}
} while(areads_dataready(taper_fd));
+start_some_dumps(runq);
startaflush();
}
I'm using Amanda 3.2.1 on FreeBSD 8.1 and last night I did a stoopid
thing with my tape changer which caused Amanda to fall into degraded
mode. I found a nit and then a problem where none of my backups were
done.
First the nit. From amreport:
The next 2 tapes Amanda expects to use are: daily
Adriana Liendo schrieb:
Hello,
Do you have any idea why amanda gives the following error..
FAILURE AND STRANGE DUMP SUMMARY:
sunblade /seisan/seismo lev 4 FAILED [can't dump no-hold disk in
degraded mode]
sunblade / lev 2 FAILED [can't dump no-hold disk in degraded mode]
Yes, we
On 2007-04-26 14:04, Adriana Liendo wrote:
Hello,
Do you have any idea why amanda gives the following error..
FAILURE AND STRANGE DUMP SUMMARY:
sunblade /seisan/seismo lev 4 FAILED [can't dump no-hold disk in
degraded mode]
sunblade / lev 2 FAILED [can't dump no-hold disk
me should be able to bypass the holding disk during
normal operation while keeping the fallback feature it provides in degraded
mode.
That's why I think Amanda should use the holding disk
in degraded mode even if the dumptype has the option holdingdisk
no.
What do you think? Maybe I could patch one
holding disk. Well,
there's one
defined actually but none of my DLE use it.
...
However, I have enough place to store a few degraded
backups should it
be
needed. And I would like to take advantage of the degraded
mode while
keeping my holdingdisk no option
dumptype
define
dumptype usual-local {
global
comment Usual dumptype
holdingdisk no
}
The problem is that Amanda doesn't write
incremental-only backups on the holding disk when in degraded mode:
*** A TAPE ERROR
OCCURRED: [cannot overwrite active tape daily-backup06
to take advantage of the degraded mode while
keeping my holdingdisk no option
Is there something else I have to configure or is this an intended
behaviour of Amanda?
holdingdisk yes
reserve 100 # the default
--
Jon H. LaBadie [EMAIL PROTECTED]
JG
to store a few degraded backups
should it be
needed. And I would like to take advantage of the degraded mode
while
keeping my holdingdisk no option
Is there something else I have to configure or is this an intended
behaviour of Amanda?
holdingdisk yes
Yes, but I don't want
of my DLE use it.
...
However, I have enough place to store a few degraded backups should it
be
needed. And I would like to take advantage of the degraded mode while
keeping my holdingdisk no option
Is there something else I have to configure or is this an intended
On Fri, Jan 20, 2006 at 08:51:34AM -0500, Jean-Louis Martineau wrote:
What was your version?
2.4.5
If you upgraded from 2.4.4p2 or earlier to a 2.4.5 then could you try
the untested attached patch.
The patch seems to help. Thanks! Is this a new problem or is it already
fixed in CVS?
Hello!
Since I have re-installed amanda, I get no more incrementals when it runs
into degraded mode. From the logfiles I can't find any hint why it always
does full-backups. All DLEs are affected by this problem. But in the
description below, I list only one DLE.
Here is what amadmin info
Josef Wolf wrote:
Hello!
Since I have re-installed amanda, I get no more incrementals when it runs
into degraded mode. From the logfiles I can't find any hint why it always
does full-backups. All DLEs are affected by this problem. But in the
description below, I list only one DLE.
OK, you
-installed amanda, I get no more incrementals when it runs
into degraded mode. From the logfiles I can't find any hint why it always
does full-backups. All DLEs are affected by this problem. But in the
description below, I list only one DLE.
Index: server-src/driver.c
On Fri, Jan 20, 2006 at 02:25:41PM +0100, Paul Bijnens wrote:
Since I have re-installed amanda, I get no more incrementals when it runs
into degraded mode. From the logfiles I can't find any hint why it always
does full-backups. All DLEs are affected by this problem. But in the
description
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
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
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
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
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
on device
taper: retrying lore:/local/home/moshkow.0 on new tape: [writing
file: No space left on device]
driver: going into degraded mode because of tape error.
...
I had similar problems under 2.4.4p2 and hoped they were resolved in
this version, but now i'm not sure what the real problem
On Sat, Dec 18, 2004 at 09:35:04PM +0100, Kai Zimmer wrote:
Hi,
i'm using amanda 2.4.4p4 on linux/solaris. Today my backup stopped (or
better slowed down) and the taper didn't work anymore. At least that's
what it looked like when i used amstatus. After some hours i killed all
amanda
208.603 file
mark 1.524}]
...
FATAL taper syncpipe_put: Broken pipe
WARNING driver going into degraded mode because of tape error.
snap
Could this Broken pipe have come from me killing the taper process
after it got stuck? What a pity
when called from
amdump. When called from amflush the changer behaves as usual. The
idea here is to have full backups once in a week (I know I need _not_ to
error out once in a week, but this is a different story) and let degraded
mode collect incrementals.
The problem now is that when
On Tue, Apr 13, 2004 at 08:35:34PM +0200, Josef Wolf wrote:
Hello.
...
So what am I doing wrong? Is degraded mode in conjunction with a changer
meant to work at all?
I don't think degraded mode has anything to do with changer.
Degraded mode is a much misused term.
No tape DOES NOT mean
Hi Group !
This smorning we got the problem, that many servers were backuped in
degraded mode (host /disk lev 1 FAILED). I think this means, the
defined hdd-tapes became too small, right ?
1) We have 17 tapes defined each one with 75000 MB.
Can I expand this to 10 MB without loosing
Hi, Oliver,
on Dienstag, 27. Jänner 2004 at 12:32 you wrote to amanda-users:
OS This smorning we got the problem, that many servers were backuped in
OS degraded mode (host /disk lev 1 FAILED). I think this means, the
OS defined hdd-tapes became too small, right ?
Degraded means
On Tue, Jan 27, 2004 at 12:32:06PM +0100, Oliver Simon wrote:
Hi Group !
This smorning we got the problem, that many servers were backuped in
degraded mode (host /disk lev 1 FAILED). I think this means, the
defined hdd-tapes became too small, right ?
1) We have 17 tapes defined each one
Hi again ...
Am Di, 2004-01-27 um 16.43 schrieb Jon LaBadie:
On Tue, Jan 27, 2004 at 12:32:06PM +0100, Oliver Simon wrote:
Hi Group !
This smorning we got the problem, that many servers were backuped in
degraded mode (host /disk lev 1 FAILED). I think this means, the
defined hdd
On Tue, Jan 27, 2004 at 05:52:25PM +0100, Oliver Simon wrote:
Hi again ...
Am Di, 2004-01-27 um 16.43 schrieb Jon LaBadie:
On Tue, Jan 27, 2004 at 12:32:06PM +0100, Oliver Simon wrote:
Hi Group !
This smorning we got the problem, that many servers were backuped in
degraded
Hello amanda users,
We seem to have run out of spool area on this system last night
(this is the system we recently upgraded from DLT7000 to SDLT220).
I'd have expected either a delay in processing or use of degraded
mode rather than a failure to backup the partition (degraded is
direct to tape
On Fri, 12 Dec 2003 at 8:55am, Brian Cuttler wrote
We seem to have run out of spool area on this system last night
That's only one of your problems...
I'd have expected either a delay in processing or use of degraded
mode rather than a failure to backup the partition (degraded is
direct
a delay in processing or use of degraded
mode rather than a failure to backup the partition (degraded is
direct to tape, right ?)
No -- degraded is when there's no tape and dumps go to the holding disk.
*** A TAPE ERROR OCCURRED: [not an amanda tape].
This is your problem. Amanda didn't
On Fri, 12 Dec 2003 at 9:23am, Brian Cuttler wrote
I know this is a loaded question... but why do I have it in my
head that if there is no spool area dumps will run anyway (although
rather slowly) dumping directly to tape.
Did I just make that up or is/was there some truth to it ?
You
Joshua,
If the holding disk fills during a run, will amanda switch to
no-holding disk mode or will it fail partitions that haven't
yet dumped ?
ie: situation I wrote about a couple of days ago. Two amanda
servers running concurrently, one for local disk used what it
wanted of the /amanda/work
On Fri, 12 Dec 2003 at 9:57am, Brian Cuttler wrote
If the holding disk fills during a run, will amanda switch to
no-holding disk mode or will it fail partitions that haven't
yet dumped ?
It should flush the stuff on disk to tape before it starts any dumps that
won't fit in the available
On Fri, Dec 12, 2003 at 10:11:51AM -0500, Joshua Baker-LePain wrote:
In your situation, I would setup the config that backs up the server
itself to not use the holding disk. On a local only config, it doesn't
really buy you much speed, so why bother?
A holding disk still buys you
I am getting the following error when backing up multiple
disks on a sun box
FAIL driver hostname /dev/rdsk/c0t1d0s7 2003112 2
[cant dump no-hold disk in degraded mode]
This error occurs on all backups while all other file
systems are being backed up fine
What is degraded mode
On Tue, Nov 18, 2003 at 12:52:04PM +1100, Barry Haycock wrote:
FAIL driver hostname /dev/rdsk/c0t1d0s7 2003112 2 [can't dump no-hold
disk in degraded mode]
[...]
What is degraded mode?
It's what happens when there's no tape in the drive, or no more
room on the tape, or for whatever other
On Mon, Nov 17, 2003 at 10:35:28PM -0500, Eric Siegerman wrote:
On Tue, Nov 18, 2003 at 12:52:04PM +1100, Barry Haycock wrote:
FAIL driver hostname /dev/rdsk/c0t1d0s7 2003112 2 [can't dump no-hold
disk in degraded mode]
[...]
What is degraded mode?
It's what happens when there's
Hi!
Since this left /amanda/work as unavailable I'd have expected amanda
to have run in degraded mode writing directly to the tape drive,
however amanda reported that there was no more room in the work area
and exited without performing any dumps at all.
Isn't the term 'degraded mode' used
,
Brian
Hi!
Since this left /amanda/work as unavailable I'd have expected amanda
to have run in degraded mode writing directly to the tape drive,
however amanda reported that there was no more room in the work area
and exited without performing any dumps at all.
Isn't
as unavailable I'd have expected amanda
to have run in degraded mode writing directly to the tape drive,
however amanda reported that there was no more room in the work area
and exited without performing any dumps at all.
It was a stupid mistake on my part, now corrected. I was just
surprised
, to tell amanda don't go into
degraded mode when dumping to disk after a tape error?
Carl Soderstrom.
--
Systems Administrator
Real-Time Enterprises
www.real-time.com
can run amflush the next morning
when I come in.
(we don't have a tape changer, and backups need to be automated, so
chg-manual isn't an option as I understand its usage).
is there some setting that I'm missing, to tell amanda don't go into
degraded mode when dumping to disk after a tape error
You've got it backwards, the 10% you reserved is used for fulls, the other
90% is used for incrementals.
hmmm, the comments read completely the opposite of that, but I'll give it a
try.
thanks much!
Carl Soderstrom.
--
Systems Administrator
Real-Time Enterprises
www.real-time.com
From: Carl Wilhelm Soderstrom [EMAIL PROTECTED]
however, when the dump runs, I get the ever-popular:
lev 0 FAILED [dumps too big, but cannot incremental dump skip-incr disk]
I don't think Amanda is telling you that the level 0 won't fit on the
holding disk. It is telling you that it won't fit
I don't think Amanda is telling you that the level 0 won't fit on the
holding disk. It is telling you that it won't fit on the tape.
no, in that case it usually gives the 'dumps too big for tape' error
message.
If you want to have Amanda backup more than will fit on the tape and
--On Thursday, October 31, 2002 16:14:28 -0600 Carl Wilhelm Soderstrom [EMAIL PROTECTED] wrote:
I don't think Amanda is telling you that the level 0 won't fit on the
holding disk. It is telling you that it won't fit on the tape.
no, in that case it usually gives the 'dumps too big for
If you have enough holding disk, don't configure a changer and specify an
absurdly large tapetype.
tried that. 40GB should be enough to hold everything, but I'll turn
it up to 70GB (size of the holding disk).
Then Amanda will do all the backups required and
give you an EOT error in
:-).
If you'll send me that amdump.NN file (I think that's all I need),
I'll see if the fix is within reason. It might just be that amstatus
doesn't understand degraded mode. More likely, though, is that some
key message it needed was corrupted and there isn't much it can do.
I have a TODO item to see
Hi, I'm trying to figure out why I still get level 0 dumps when in
degraded mode (no tape available).
I took the default of 100% for the reserve parameter first being that
the result, as I understand it to be, is as I desire. When Amanda
would still run level 0's on some machines in degraded
promote: moving sabre:/biff up, total_lev0 3390062, total_size 3574492
That would not affect degraded mode.
reserving 8335017 out of 8335017 for degraded-mode dumps
cass150amgetconf hea_daily reserve
100
OK, that all fits and says no level 0's should be done in degraded mode.
Shows
Whoops. I noticed retroactively that the level stated for sabre:/biff
in the after start degraded mode schedule is level 7. There is a 0
in that row and looking too quickly I mistook that for the dump level
column. I noticed this after discovering that the file created on the
holding disk
detection for a tape and degraded mode.
Look for reserving ... for degraded-mode dumps in your amdump file.
How much did it reserve? What does amgetconf config reserve say
(just to confirm your grep).
reserving 8335017 out of 8335017 for degraded-mode dumps
cass150amgetconf hea_daily reserve
Hi, I'm trying to figure out why I still get level 0 dumps when in
degraded mode (no tape available).
Look for reserving ... for degraded-mode dumps in your amdump file.
How much did it reserve? What does amgetconf config reserve say
(just to confirm your grep).
Look for result ... from taper
66 matches
Mail list logo
