this is one of my amstatus reports:
[EMAIL PROTECTED]:~/hourly$ amstatus hourly
Using /usr/local/etc/amanda/hourly/amdump.1 from Thu Feb 23 10:20:59
CET 2006
pille.hq.imos.net:/0 driver: (aborted:[request failed: timeout
waiting for ACK])(too many dumper retry)
pille.hq.imos.net:/opt 1
Hi!
It happened again, that a disk grew over the lenght of a tape, and
so its backup got stuck on the holding disk.
And as it is all the time it happened when i was out of office
for some days...
I knew its my concern as the sysadmin to split it into smaller
pieces ...
But it would be nice
On 2006-02-23 10:45, Stefan Herrmann wrote:
this is one of my amstatus reports:
[EMAIL PROTECTED]:~/hourly$ amstatus hourly
Using /usr/local/etc/amanda/hourly/amdump.1 from Thu Feb 23 10:20:59 CET
2006
pille.hq.imos.net:/0 driver: (aborted:[request failed: timeout
waiting for ACK])(too
On 2006-02-23 11:05, Peter Mueller wrote:
It happened again, that a disk grew over the lenght of a tape, and
so its backup got stuck on the holding disk.
And as it is all the time it happened when i was out of office
for some days...
I knew its my concern as the sysadmin to split it into
Hi Paul again I received via the Amanda Report this morning that my
server client Failed.
I am still lost in the woods.
On the ipchains firewall I added ipchains -M -S tcp tcpin udp to
masqueraded and set the timeouts.
My Amanda Report output below:
server / lev 0 FAILED [Estimate timeout
On 2006-02-23 11:36, Chuck Amadi Systems Administrator wrote:
Hi Paul again I received via the Amanda Report this morning that my
server client Failed.
I am still lost in the woods.
On the ipchains firewall I added ipchains -M -S tcp tcpin udp to
masqueraded and set the timeouts.
My Amanda
Hi Here is my sendsize log.
sendsize[2481]: time 220.652: Total bytes written: 5132001280 (4.8GB,
22MB/s)
sendsize[2481]: time 220.726: .
sendsize[2481]: estimate time for / level 0: 220.672
sendsize[2481]: estimate size for / level 0: 5011720 KB
sendsize[2481]: time 220.727: waiting for
Any idea why I get the following?
fileserv:/usr/freeware/etc/openldap 1 32k dumping0k (
1.53%) (11:32:10)
This is from amstatus on a currently running dump, and the time is now
# date
Thu Feb 23 12:32:35 CET 2006
I mean, why does this dump take so long? This is (as you can
Toralf Lund wrote:
Any idea why I get the following?
fileserv:/usr/freeware/etc/openldap 1 32k dumping0k (
1.53%) (11:32:10)
This is from amstatus on a currently running dump, and the time is now
# date
Thu Feb 23 12:32:35 CET 2006
I mean, why does this dump take so long?
Any idea why I get the following?
fileserv:/usr/freeware/etc/openldap 1 32k dumping0k (
1.53%) (11:32:10)
This is from amstatus on a currently running dump, and the time is now
# date
Thu Feb 23 12:32:35 CET 2006
I mean, why does this dump take so long?
I get these
Hi again!
Did you specify taperalgo largestfit in the amanda.conf? Or any other?
I will check that, probably not, because I dont remember this parameter.
Is was missing, which means first - I changed this to smallest to
give the
2rd and 3rd level images a chance to get thru ..
I taped
Feb 23 14:19:44 2006
Does amcheck pass all tests?
yes:
[EMAIL PROTECTED]:~$ amcheck hourly
Amanda Tape Server Host Check
-
Holding disk /holding: 264416 MB disk space available, using 263392 MB
read label `hourly023', date `20060223'
read label `hourly024', date `X
On 2006-02-23 14:03, Peter Mueller wrote:
Paul Bijnens wrote:
When there is only one image to choose from, Amanda will take that one,
even if it will probably not fit. Changing that will make many other
users of Amanda unhappy, e.g. those using hardware compression because
their tape length is
On 2006-02-23 14:18, Peter Mueller wrote:
Did you specify taperalgo largestfit in the amanda.conf? Or any other?
I will check that, probably not, because I dont remember this parameter.
Is was missing, which means first - I changed this to smallest to
give the
2rd and 3rd level images a
On Thu, Feb 23, 2006 at 02:31:06PM +0100, Paul Bijnens enlightened us:
Paul Bijnens wrote:
When there is only one image to choose from, Amanda will take that one,
even if it will probably not fit. Changing that will make many other
users of Amanda unhappy, e.g. those using hardware
On 2006-02-23 14:24, Stefan Herrmann wrote:
Am 23.02.2006 um 11:17 schrieb Paul Bijnens:
I would take a look in the debug files on the client, usually in
the dir /tmp/amanda/. There you can see files amandad.datetime.debug
which contain the packet received, and the replies. If there
are no
Am 23.02.2006 um 14:43 schrieb Paul Bijnens:
On 2006-02-23 14:24, Stefan Herrmann wrote:
Am 23.02.2006 um 11:17 schrieb Paul Bijnens:
I would take a look in the debug files on the client, usually in
the dir /tmp/amanda/. There you can see files
amandad.datetime.debug
which contain the
Hi Paul!
Paul Bijnens wrote:
On 2006-02-23 14:18, Peter Mueller wrote:
Did you specify taperalgo largestfit in the amanda.conf? Or any
other?
I will check that, probably not, because I dont remember this
parameter.
Is was missing, which means first - I changed this to smallest to
On 2006-02-23 15:54, Stefan Herrmann wrote:
i think there was no useful information in the leftout part, but look
for yourself:
Yes indeed. No REQ packet at all.
Are you sure this debug file is the result from a amdump request,
and not one of those that were generated by all different
Hi Paul!
Paul Bijnens wrote:
...
The problem here is that when you had a real tape error, and then try
to flush o a new tape, then amanda refuses to put that one tape, because
it got an error last time? Not good. So how you do see if you got
a real error or just EOT. Explain me, because I
When I run amrestore like this
amrestore -f 0 -p /dev/nst0 localhost
sda2 | restore -ivb2 -f -
I got message:
Verify tape and initialize maps
Input is from a local file/pipe
amrestore: 0: skipping start
of tape: date 20060223 label EPIP2
amrestore: 1: restoring localhost.sda2.20060223.0
Dear group,
i´am trying to install the amanda client from the
current version.
I´ve configured it with user=amanda group=disk and
client installation only
The prefix is /usr/amanda.
The problem is, that the amandad can´t be started.
I execute $Prefix/libexec/amandad, this takes a
this
amrestore -f 0 -p /dev/nst0 localhost sda2 | restore -ivb2 -f -
I got message:
Verify tape and initialize maps
Input is from a local file/pipe
amrestore: 0: skipping start of tape: date 20060223 label EPIP2
amrestore: 1: restoring localhost.sda2.20060223.0
restore: Tape is not a dump
On 2006-02-23 16:30, Radek Cisz wrote:
Its dump archive.
please see my first letter below
OK.
Then maybe you have some difference in blocksize between
the two machines. Some implemenations (HPUX in my experience)
read a block, and if the tapeblocksize is greater than the
readblocksize, then
On Thu, Feb 23, 2006 at 02:24:59PM +0100, Stefan Herrmann wrote:
Does amcheck pass all tests?
yes:
[EMAIL PROTECTED]:~$ amcheck hourly
Amanda Tape Server Host Check
A config named hourly. Do you actually run amdump each hour?
If so, might there be some extraneous, old, stuck, ???
Radek Cisz wrote:
When I run amrestore like this
amrestore -f 0 -p /dev/nst0 localhost sda2 | restore -ivb2 -f -
I got message:
Verify tape and initialize maps
Input is from a local file/pipe
amrestore: 0: skipping start of tape: date 20060223 label EPIP2
amrestore: 1: restoring
On Wed, Feb 22, 2006 at 03:34:44PM -0800, Kevin Till wrote:
- What is the point to uuencode and encrypt (with gpg) random data to
generate the key? Since the passphrase is stored on the same host,
protecting the key with the passprase is not of much use (IMHO).
It illustrates the method
On Thu, Feb 23, 2006 at 04:34:19PM +0100, Patrick Mania wrote:
Dear group,
The problem is, that the amandad canŽt be started.
I execute $Prefix/libexec/amandad, this takes a while (30 secs) and breaks.
amandad is not intended to run continually nor to be run from the command line.
Jon LaBadie wrote:
On Thu, Feb 23, 2006 at 04:34:19PM +0100, Patrick Mania wrote:
Dear group,
The problem is, that the amandad canŽt be started.
I execute $Prefix/libexec/amandad, this takes a while (30 secs) and breaks.
amandad is not intended to run continually nor to be run
nner Adding new disk localhost:/itrn1.START taper datestamp 20060223 label [fake-label] tape 0WARNING taper tapedev is null:, dumps will be thrown awayERROR planner Request to localhost timed out.FINISH planner date 20060223WARNING driver WARNING: got empty schedule from plannerSTATS driver startup t
.20060223.0
START driver date 20060223
DISK planner localhost /itrn1
START planner date 20060223
INFO planner Adding new disk localhost:/itrn1.
START taper datestamp 20060223 label [fake-label] tape 0
WARNING taper tapedev is null:, dumps will be thrown away
ERROR planner Request to localhost
Josef Wolf wrote:
On Wed, Feb 22, 2006 at 03:34:44PM -0800, Kevin Till wrote:
- What is the point to uuencode and encrypt (with gpg) random data to
generate the key? Since the passphrase is stored on the same host,
protecting the key with the passprase is not of much use (IMHO).
It
On Thu, Feb 23, 2006 at 03:50:11PM -0800, Kevin Till wrote:
Josef Wolf wrote:
On Wed, Feb 22, 2006 at 03:34:44PM -0800, Kevin Till wrote:
Amanda users have used aespipe in the past, so it's there.
Hmmm, AFAIK is aespipe part of loop-aes and loop-aes is deprecated
because the kernel
Jon LaBadie wrote:
On Thu, Feb 23, 2006 at 03:50:11PM -0800, Kevin Till wrote:
Josef Wolf wrote:
On Wed, Feb 22, 2006 at 03:34:44PM -0800, Kevin Till wrote:
Amanda users have used aespipe in the past, so it's there.
Hmmm, AFAIK is aespipe part of loop-aes and loop-aes is deprecated
I'm trying to compile 2.5 beta 2 on Solaris 10 X86. The build is failing in
the man subdirectory. It's complaining about this line in the generated
Makefile:
$(man_MANS): %: $(MANPAGEDIR)/%.proc.xml xslt/man.xsl
$(XSLTPROC) --path xslt/ --output $@ man.xsl $
Now, it's been a while since
in the /etc/hosts file,
or an alias that is also listed in that file.
__
My log file reads:
[host] /usr/adm/amanda/ProtoLocal more log.20060223.0
START driver date 20060223
DISK planner localhost /itrn1
START planner date 20060223
INFO planner
On Thu, Feb 23, 2006 at 07:24:34PM -0500, stan wrote:
I'm trying to compile 2.5 beta 2 on Solaris 10 X86. The build is failing in
the man subdirectory. It's complaining about this line in the generated
Makefile:
The actual complaint is often a big help to those answering.
$(man_MANS): %:
On Thursday 23 February 2006 22:38, Jon LaBadie wrote:
The actual complaint is often a big help to those answering.
$(man_MANS): %: $(MANPAGEDIR)/%.proc.xml xslt/man.xsl
$(XSLTPROC) --path xslt/ --output $@ man.xsl $
Now, it's been a while since I wrote Makefiles, but I must
38 matches
Mail list logo
