Hi!
Recently had a drive fail on a RAID I am backing up. Since replacing
the drive and re-building the RAID, amanda has been failing on all of
the partitions on this computer.
The error I see in the amanda report is the following:
hostname /dev/da0s1f lev 0 FAILED [disk
I have Sun Storage C1537A L706 under RH6.2 Sparc
I tried to run tapetype -f /dev/nst0 from amanda 3 times and get the same
error:
[root@host]# tapetype -f /dev/nst0
wrote 375069 32Kb blocks in 1147 files in 11803 seconds (short write)
st0: Error 2603 (sugg. bt 0x20, driver bt 0x26, host bt
I'm using a daily config named DailySet1 on a HP DDS3. Six days a
week. Works nicely.
DailySet1:
dumpcycle 2 weeks
runspercycle 12
tapecycle 16 tapes
...
define dumptype global {
index yes
maxdumps 2
}
I'm also experimenting with a weekly archive config named Archive. It uses
the same
Hi,
I have been struggling to get amanda to work with my tape changer. And
going over the documentation does not help me. I have read it over and
over again. I have tried to use the chg-zd-mtx and (just now) chg-multi
changer scripts, but I can't get either of them to work. Please, please,
When changing to bigger tapes, label the new tapes with different
values. If you have FOO_000 to FOO_019 now, use something like
FOO_020 to FOO_039. Making 2 tapes with the same label just causes
trouble, and there is no reason to do it. Once you have new tapes,
just swap them in. Make sure
On Mon, 20 May 2002 at 9:26am, Brian Jonnes wrote
What are the current feelings of the group re the following? Should I switch
to TAR?
*Careful* -- this one can erupt quickly! The canonical answer is use what
works in your testing and what makes you comfortable. Some people have
noticed
Okay, I just grabbed the chg-zd-mtx script from the CVS... appears to
have solved the problems so far... holding my breath and issuing a
'amdump...' :-)
Peter Normann
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Peter Normann
Sent: 20. maj 2002
--
On Mon, 20 May 2002, Brian Jonnes wrote:
What are the current feelings of the group re the following? Should I switch
to TAR?
dump reads on a lower level than tar, and is more sensitive when dumping
an active file system. Dumps may be rendered useless due to a file
changing underneath
We're converting from Alexandria to Amanda. The differences are rather,
well, stark.
I've been reading a lot of various online Amanda resources, but what I
really need to determine is holding disk requirements. I'm sure this
info is concisely covered somewhere, but I'm slogging through tons of
I user it successfully. The weird variable is need reject. Here's my
changer.conf.
firstslot 1
endslot 22
cleanslot 0
cleancycle 0
autocleancount 99
chgtapedev 0
havereader 0
offlinestatus 0
OFFLINE_BEFORE_UNLOAD 1
needeject 1
Peter Normann wrote:
Hi there,
Is anybody using this
On 20 May 2002 at 10:02am, Brad Felmey wrote
I've been reading a lot of various online Amanda resources, but what I
really need to determine is holding disk requirements. I'm sure this
info is concisely covered somewhere, but I'm slogging through tons of
the same stuff over and over looking
Hello again,
When I run amdump and then amstatus, some of the 'backup jobs' issue the
following error/warning (which is it):
localhost:/backup/dump27/. 0 [dumps too big, but cannot
incremental dump new disk]
The size of dump27/. is way smaller than other 'backup jobs' and can
As with most things, it all depends on what you want to accomplish.
You could get by without any holding disk, forcing all your backups to
go directly to tape, but this would take longer since whenever the tape
drive caught up with the data stream it would have to stop and reposition
itself. Any
... Filemarks seperate files on tape, and because amanda stores
each disk in the disklist in a seperate file on tape, it must account
for any loss of capacity due to filemarks when estimating. ...
Right.
IIRC though
this value is not currently used by or necessary for amanda so it's
perfectly
I have broken my previously working configuration...
Well, that was a pretty silly thing to do! :-)
So, why would amcheck be saying: WARNING: tapedev is /dev/null?
I see the man page says the amcheck uses /dev/null as the default ...
There are a couple of interactions going on here.
Why then does my tapelist have reuse at the end of every single tape's
entry ?
Presumably (i.e., I'm guessing here) because the tape will, eventually,
be reused. ...
Correct. Or, possibly more accurately, because the tape may be
eventually reused.
The amadmin command allows you to mark
When I run amdump and then amstatus, some of the 'backup jobs' issue the
following error/warning (which is it):
localhost:/backup/dump27/. 0 [dumps too big, but cannot
incremental dump new disk]
That's an error, as in, that file system is not going to be backed up.
Amanda is
I'm running Amanda lastest stable version in one Red Hat with Postfix, but
after I run amdump the summary mail sent to me is blank.
Anyone was had the same problem ?
Have another way to I see the tapelist required for next dump ?
Have another site to I learn more about amanda ? (not
18 matches
Mail list logo
