Finally solved the problems
1 - The amanda host had a secondary IP alias on the LAN NIC, and Amanda was
swapping between the two IPs for its source address. Thats fine for clients
on the LAN, but the firewall didnt like that much...
2 - Once that had been fixed, I found a nasty `bug` in my
amrecover will in my setup make a completely wrong guess about what disk
to consider at startup in most cases. The example output included below
should illustrate the problem; /usr/freeware/apache is not on the /u
filesystem, and it has a separate disklist entry. Any ideas what is going
on?
Hi Gene
In this script there is no wait timer, just a repeated look at the tape
status, which is better.
The resolution after a few hours trial and error was to add 'sleep' commands
between the tape movement and/or echo commands in the chg-zd-mtx script. It
looks like the next command is issued
Greetings,
(I sent a mail about this a few days ago, so if I am duplicating info
please forgive)
I still cannot get one of my disks to dump correctly. It is reporting the
error can't switch to incremental dump. I have unforced the dump w/
amadmin just in case. I have a tape with more then
It is really that service amanda in '/etc/xinetd.d/amanda' was
disabled.
/etc/xinetd.d/amanda (should be)
# default: off
# description: The client for the Amanda backup system.\
# This must be on for systems being backed up\
# by Amanda.
service amanda
{
On Friday 20 December 2002 06:54, Peter Stokes wrote:
Hi Gene
In this script there is no wait timer, just a repeated look at the
tape status, which is better.
The resolution after a few hours trial and error was to add
'sleep' commands between the tape movement and/or echo commands
in the
Greetings. I'm attempting to recover a filesystem which is about 15-18
gigs in size. Amanda is using Tar to compress its archives... I tried to
restore the image to a filesystem large enough to handle the data,
before moving back to the original location; but I got a File size
limit exceeded. (It
On Fri, Dec 20, 2002 at 09:16:54AM -0500, [EMAIL PROTECTED] wrote:
Greetings,
(I sent a mail about this a few days ago, so if I am duplicating info
please forgive)
I still cannot get one of my disks to dump correctly. It is reporting the
error can't switch to incremental dump. I have
On Fri, 20 Dec 2002 at 11:26am, wab wrote
Greetings. I'm attempting to recover a filesystem which is about 15-18
gigs in size. Amanda is using Tar to compress its archives... I tried to
restore the image to a filesystem large enough to handle the data,
before moving back to the original
On Fri, Dec 20, 2002 at 11:26:07AM -0500, wab enlightened us:
Greetings. I'm attempting to recover a filesystem which is about 15-18
gigs in size. Amanda is using Tar to compress its archives... I tried to
restore the image to a filesystem large enough to handle the data,
before moving back to
Hello,
if you are using amrestore to grab the image from tape, then:
cd working directory
amrestore -p [and other options] | tar -xpf -
the -p option in amrestore outputs the datastream to a pipe (stdout).
this sets up the buffering correctly. the -p option in tar will restore
the files
Hello,
Am I reading you correctly that you haven't gotten a full dump yet and
amanda is displaying 'can't switch to incremental dump'?
If this is the case, read on...
Do you have the parameter reserve set in your amanda.conf file? if
not, it defaults to 100%. this means that the holding disk
Steve, I had this exact problem. The problem is that the way NAT is done is to choose
an arbitrary port number and associate it with an IP inside the NAT.
Search the archive of this list for Amanda through translated addresses where Pedro
Caria shared with me a patch to remove the port check
On Fri, Dec 20, 2002 at 11:51:52AM -0500, Jean-Louis Martineau wrote:
On Fri, Dec 20, 2002 at 09:16:54AM -0500, [EMAIL PROTECTED] wrote:
Greetings,
(I sent a mail about this a few days ago, so if I am duplicating info
please forgive)
I still cannot get one of my disks to dump
On Fri, Dec 20, 2002 at 03:52:03PM -0500, KEVIN ZEMBOWER wrote:
Steve, I had this exact problem. The problem is that the way NAT is done is to
choose an arbitrary port number and associate it with an IP inside the NAT.
Search the archive of this list for Amanda through translated addresses
Hi Jean-Louis,
Version is Amanda 2.4.3 running on 2.4.19-r6 Gentoo linux, ppc.
(there's no Amanda ebuild script available for Gentoo, btw, if anyone
more capable than I is interested in hacking one up:o))
To be more descriptive, these errors appear after I initiate a dump then
call
16 matches
Mail list logo
