What version of Amanda?
Pretty much the latest, 242p2, I think.
The netusage would not affect planner. And I don't think inparallel is
involved, either. I'm pretty sure planner ships a sendsize request to
all the clients at the same time and doesn't pay any attention to either
of
the problem?
Thanks in advance,
Carey
Carey Jung
IT Freedom
[EMAIL PROTECTED]
512.419.0070, fax 419.0080
We're running amanda 242p2 with a Linux server and Exabyte 220 tape library.
We can't seem to get amrecover to work. We have to manually load the
correct tape and then run amrecover, because if the correct tape is not in,
it's not able to access the tape device.
It appears that somewhere in the
we seem to get a lot of 'not at start of tape' errors
It's not an error, just a warning that the tape section numbers that
follow do not reflect the actual tape section numbers on tape, because
you hadn't started amrestore at the beginning of the tape. It has
absolutely nothing to do
Am I
correct, and if so how do I force amanda to do a full on the same day
every week?
Why would you want to do that?
Here's one example: You're backing up a number of customer servers over
relatively slow WAN connections. A full backup takes 18 hours, and you
don't want to choke the
When running amverify with a tape changer and runtapes set to n greater than
1, we've noticed that amverify will verify the current tape and the next
runtapes-1 tapes, even if they weren't all used during the previous amdump.
Is this a bug or a feature? It creates unnecessary usage on the unused
We have an Exabyte 220 tape library, running chg-scsi tape changer ...
What version of Amanda? What version of chg-scsi?
2.4.2 p2. I'm not sure which version of chg-scsi; whatever's with amanda
2.4.2p2.
Carey
:[EMAIL PROTECTED]]On Behalf Of Carey Jung
Sent: Tuesday, April 24, 2001 11:25 PM
To: Amanda Users
Subject: amtape advance errors
Hi,
We have an Exabyte 220 tape library, running chg-scsi tape changer, and
getting a tape 'advance' error at the end of amverify runs. It seems
inconsequential
nks,
Carey
----
----
Carey Jung
IT Freedom
[EMAIL PROTECTED]
512.419.0070, fax 419.0080
, 2001 8:04 PM
To: Carey Jung
Cc: Amanda Users
Subject: Re: Exabyte Mammoth tape type?
Hi,
The three parameters you need can be easily obtained or estimated.
For no hardware compression:-
length 2 mbytes # Raw length using 170m AME tape
# (use up to 4 mbytes
Can amanda use who tape devices to perform a single backup?
You can't use them concurrently (yet), but you can set up chg-multi to
switch between tape drives automatically. That's what we do here.
Can you elaborate on this? We are just beginning to set up an Exabyte 220
tape library
, but I'm
not sure what effect that has on indexing, amrecover, etc.
thanks in advance for any help,
Carey
Carey Jung
IT Freedom
[EMAIL PROTECTED]
512.419.0070, fax 419.0080
Did somebody yell, "Fire!"?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Daniel
Sent: Thursday, March 22, 2001 6:10 PM
To: [EMAIL PROTECTED]
Subject:
unsubscribe [EMAIL PROTECTED]
Amrecover is not the issue. The issue is why amindexd is quitting. I
assume both machines are connecting to the same amindexd server?
Everything's happening on the same machine. The problem is not amindexd
quitting, I believe, but rather amrecover not being able to connect to it.
We ran
We've gotten it working now, by going back to 2.4.2, applying the
/dev/root
fix, rebuilding, reinstalling, etc. I'll look at amrecover diffs between
2.4.2 and 2.4.2p1 and see if I can track the problem down.
I misspoke. We have it working now, running 2.4.2p1 plus the /dev/root
patch.
It was on the mailing list within the past couple weeks. I'll send it to
you directly.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Shreedeep Bhachech
Sent: Tuesday, March 20, 2001 10:51 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL
After all was said and done, it turned out that our amrecover problems had
to do with reverse dns lookup errors. We had a named db misconfigured.
Sorry for the waste of bandwidth.
Carey
.,
recompile), or do we need to modify the source. If this is a braindead
idea, I'd like to know that, too.
Thanks in advance.
Carey Jung
IT Freedom
[EMAIL PROTECTED]
512.419.0070, fax 419.0080
We just built 242p1 and are getting errors contacting the index server from
amrecover. We get the following error:
% amrecover -C DailySet1 -s localhost -t localhost -d /dev/nst0
AMRECOVER Version 2.4.2p1. Contacting server on localhost ...
amrecover: Unexpected server end of file
Here's
Are there perhaps index file incompatibilities between 242 and 242p1?
amrecover is working fine on the machine it was built on, but not on the
machine below, which has been running 242
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Carey Jung
We just ran across the same problem. It's fixed in 2.4.2p1.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Shreedeep Bhachech
Sent: Monday, March 19, 2001 3:59 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Failed backup of /
Nope. Use 2000mb. That's a little bit less than 2Gb, so it won't
bump into the limit.
Confusing, but understood. I will try that, thanks.
I think the amanda man page discusses this a bit, or else it's in the
default amanda.conf. To allow for header information on the dump file,
etc.,
We're about to dive into smbclient backups of NT servers with amanda. We're
running 2.4.2. What would the amanda developers recommend using, 2.4.2,
2.4.2p1, or latest stable patches? I recall seeing notes to the effect that
some of this code has changed/been fixed recently, so I want to get
Can somebody explain this oddity? I run amcheck and get this:
[amanda@intranet DailySet1]$ amcheck DailySet1
Amanda Tape Server Host Check
-
Holding disk /home/amanda/dumps: 2514280 KB disk space available,
using 2411880
KB
amcheck-server: slot 3: date
Slot 1 was just reported as having DailySet108. What's up?
Carey
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Carey Jung
Sent: Wednesday, March 14, 2001 10:54 AM
To: Amanda Users
Subject: tape slot anomaly
Can somebody explain this oddity? I
... What would the amanda developers recommend using, 2.4.2,
2.4.2p1, or latest stable patches? ...
Is that a rhetorical question? :-) Developers **always** recommend
you use the absolutely latest stuff so you'll test it for them :-).
That being said, I'd recommend the latest 2.4.2
2.4.2 makes it possible to define dump types directly in the
disklist. And since dump types can define the filename for an exclude
file you can have seperate exclude files for each disk entry (of
course you could also define the dump types in amanda.conf and use
different dump types for
By sheer (and extremely annoying :-) coincidence, one of my systems did
the same thing last night, but behaved "properly", i.e. all the images
smaller than 2 GBytes were flushed and removed from the holding disk.
So my best guess is this a problem that's fixed with a more recent
version of
We just ran across this error, because we hit the 2GB filesize limit on ext2
filesystems. After reading the man pages, we've cranked down the
holdingdisk chunksize to 2000MB, which should alleviate the problem in the
future.
However, the behavior after this error seems a bit odd. Amanda
I've caught some
conversation about tape libraries w/barcode readers. How are they used,
and what does amanda do with them?
Regards,
Carey
Carey
Jung
IT Freedom
[EMAIL PROTECTED]
512.419.0070, fax 419.0080
when I do amcheck and no error are reported, can I trust it 100 %
that the backup will work?
Well, there's always Murphy's law :-)
amcheck doesn't, by default, try to write to the tape. It just reads the
label. If, for example, the write-protect tab is set on today's tape,
amcheck will
Could someone please clarify the holding disk/taper semantics? It appears
that amanda deletes files from the holding disk as they are taped off,
rather than after they are ALL successfully taped off. We noticed this when
we had a tape problem. When we put a good tape in and tried to re-flush
32 matches
Mail list logo
