Hi all,
I'm using AMANDA 2.4.5
I've got a configuration question. I wasn't able to find a similar
question with Google. I thought I'd try it on the list.
I've got a disklist with a few DLE's in it. At the start of an amdump,
AMANDA asks the clients for an estimate. When the server has received
Hi,
I need some clarification on the usage of the amanda.
What parameters need to be congfigured for the
partial full backup i.e.,the full backup is divided
into according to the dumpcycle and runspercycle. We
configured
dumpcycle 10 days
runspercycle 10
Suppose this is the case,
On Wed, 31 May 2006 at 1:50am, silpa kala wrote
I need some clarification on the usage of the amanda.
What parameters need to be congfigured for the
partial full backup i.e.,the full backup is divided
into according to the dumpcycle and runspercycle. We
configured
dumpcycle 10 days
On 2006-05-31 10:50, silpa kala wrote:
Hi,
I need some clarification on the usage of the amanda.
What parameters need to be congfigured for the
partial full backup i.e.,the full backup is divided
into according to the dumpcycle and runspercycle. We
configured
dumpcycle 10 days
On 2006-05-31 10:35, Dennis Ortsen wrote:
Hi all,
I'm using AMANDA 2.4.5
I've got a configuration question. I wasn't able to find a similar
question with Google. I thought I'd try it on the list.
I've got a disklist with a few DLE's in it. At the start of an amdump,
AMANDA asks the clients
From: Nicola Mauri
Sent: 31 May 2006 11:38
We are constantly encountering strange errors whith DLEs that
refer to cluster virtual addresses.
virtualA /apps/a lev 0 FAILED [data timeout]
virtualB /apps/b RESULTS MISSING
The disklist contains:
node1 /etc full
Pavel Pragin wrote:
Hello,
1. Can you please post the last log file and the amdump.1 file from the
/usr/local/amanda/log/teste directory.
2. Can you also run amadmin x version and post that as well.
3. Can you aslo explain in more detail what you are trying to acomplish
from this
On Wed, 31 May 2006 at 9:45am, Edson wrote
My intention is perfom a backup schema in 6x1 (6 incremental and 1 full
backup) using a LTO tape drive (200gb). My target system is a ext3
partition (/home) in a Suse Linux 9.3 box called alpes, with less than 50gb
of size (mailserver).
Current Im
On Tue, May 30, 2006 at 01:50:21PM -0700, Pavel Pragin wrote:
But amplot's Bandwidth Allocated graph shows the line mostly pegged at 0%
the
entire time. From glancing through the amplot scripts, I'm guessing
this should be labeled Bandwidth Free?
If you run amstatus again what is the
Paul, thanks for your suggestions.
On our machines, all network masks appear
to be consistent. We'll try to configure different client instance on xinetd.
Another frequent message error I didn't
mention in my first post is:
aborted:nak error: amandad busy
which may sometimes lead to:
On Wed, May 31, 2006 at 03:37:44PM +0200, Nicola Mauri enlightened us:
Paul, thanks for your suggestions.
On our machines, all network masks appear to be consistent. We'll try to
configure different client instance on xinetd.
Another frequent message error I didn't mention in my first
On 2006-05-31 16:05, Matt Hyclak wrote:
On Wed, May 31, 2006 at 03:37:44PM +0200, Nicola Mauri enlightened us:
Paul, thanks for your suggestions.
On our machines, all network masks appear to be consistent. We'll try to
configure different client instance on xinetd.
Another frequent message
On 2006-05-30 10:30, Paul Duncan wrote:
Hello,
One of our filesystems is failing to get backed up and I am interested
in trying to ascertain why. The report entry is:
compaqdev2 /export/home lev 0 FAILED [data timeout]
In the amdump file I see the following suspicious entries. I get a
use the interface (aka bind) option in xinetd
to run multiple
instances of the amanda client each responding
on a different address
TESTED. Configuring multiple amanda client seems to
solve this issue!
My new /etc/xinet.d/amanda file has three entries:
- The first entry binds to node
On 2006-05-31 17:00, Nicola Mauri wrote:
use the interface (aka bind) option in xinetd to run multiple
instances of the amanda client each responding on a different address
TESTED. Configuring multiple amanda client seems to solve this issue!
My new /etc/xinet.d/amanda file has three
Hi,
Thanks for this information. I gone through the all
the threads related to the Partial Full backup
configuration for amanda.
Partial full backup is happening based on the DLE
entries instead of memory occupied for all DLEs.That
means If one DLE happens to contain 50% of all data,
then one
On Wed, May 31, 2006 at 09:48:07AM -0700, silpa kala wrote:
Hi,
Thanks for this information. I gone through the all
the threads related to the Partial Full backup
configuration for amanda.
Partial full backup is happening based on the DLE
entries instead of memory occupied for all
17 matches
Mail list logo
