My attempt to restore files with amrecover keep failing since I upgraded
to 2.4.5. The output in amidxtaped.debug looks like:
amidxtaped: debug 1 pid 14962 ruid 250 euid 250: start at Mon Feb 20
20:33:06 2006
amidxtaped: version 2.4.5
amidxtaped: time 0.000: SECURITY USER root
amidxtaped:
On 2006-02-21 09:25, Stephen Carville wrote:
My attempt to restore files with amrecover keep failing since I upgraded
to 2.4.5. The output in amidxtaped.debug looks like:
amidxtaped: debug 1 pid 14962 ruid 250 euid 250: start at Mon Feb 20
[...]
amrestore: could not open /dev/ait2:
hello list,
i made a fresh install of Amanda 2.5.0b2 on a debian 3.1 system. then
i set up amanda for a hourly backup.
i did some test backups that worked ok. then i mentioned an error in
the amanda.conf and aborted the dump
manually. stopped all amanda processes on the client manually and
Hi List
This morning I got my AMANDA MAIL REPORT and server had failed.
Thus I have less /tmp/amanda/amandad.20060220210110.debug
Here is the output from the server client debug I have since changed the
Estimate timeout parameter from 300 to etimeout 380 on my ~tape
server/amanda.conf Thus
Paul Bijnens wrote:
On 2006-02-21 09:25, Stephen Carville wrote:
My attempt to restore files with amrecover keep failing since I
upgraded to 2.4.5. The output in amidxtaped.debug looks like:
amidxtaped: debug 1 pid 14962 ruid 250 euid 250: start at Mon Feb 20
[...]
amrestore: could not
Title: Self check failing
I'm getting an amanda self-check failure from amcheck daily:
I suppose this was due to the mysterious disconnect of one server (m248)...
another one (nept) is running, but after removing a duplicate uid for
amanda in the NIS maps, it stopped working.
Amanda Backup
Hi
Have you had a look at your amanda tape server amanda.conf file
and amending the etimeout parameter default is usually 300 seconds.
I run less command on /tmp/amanda/amanda-date-.debug and my client was
timing out on 180.33 seconds So I had read a good possibility is that
udp which is
On 2006-02-21 11:02, Chuck Amadi Systems Administrator wrote:
Here is the output from the server client debug I have since changed the
Estimate timeout parameter from 300 to etimeout 380 on my ~tape
server/amanda.conf Thus doubled the amandad: time 180.183: dgram_recv in
debug report.
On Tue, Feb 21, 2006 at 09:45:32AM +0100, Stefan Herrmann wrote:
hello list,
i made a fresh install of Amanda 2.5.0b2 on a debian 3.1 system. then
i set up amanda for a hourly backup.
i did some test backups that worked ok. then i mentioned an error in
the amanda.conf and aborted the dump
I'm using 2.4.5p1 on NetBSD with Kerberos encryption and
authentication.
I tried to verify some tapes and found that 'gzip -t' failed on the
restored files. On investigation, after adding some better
diagnostics to gzip (NetBSD's own), I found that the problem was that
the last 32K block was
Hello everyone,
please advice...
I have two servers. One for production
and second as backup.
Both have streamers that read LTO tapes.
On these servers I have installed Suse
9.0 and amanda from rpm package.
When I do backup with amanda on production
server , then I can restore it on the same
What do the log files say? They are usually in /tmp/amanda/ on the server.
Thanks
tk
Radek Cisz wrote:
Hello everyone,
please advice...
I have two servers. One for production and second as backup.
Both have streamers that read LTO tapes.
On these servers I have installed Suse 9.0 and
Greg Troxel wrote:
I'm using 2.4.5p1 on NetBSD with Kerberos encryption and
authentication.
I tried to verify some tapes and found that 'gzip -t' failed on the
restored files. On investigation, after adding some better
diagnostics to gzip (NetBSD's own), I found that the problem was that
the
Lengyel, Florian wrote:
I'm getting an amanda self-check failure from amcheck daily:
I suppose this was due to the mysterious disconnect of one server (m248)...
another one (nept) is running, but after removing a duplicate uid for
amanda in the NIS maps, it stopped working.
Amanda Backup Client
Hi,
Maybe this is some issue with encryption?
not likely. Data encryption is new to Amanda 2.5.0.2.
amrestore sends all warnings/error to stderr.
Try amrestore -f 0 ... and send us the stderr output.
Maybe rpm package was compiled with it? I dont know how to check it .
amadmin
I'v got a brand spanking new Ultra 40, just for running Amanda! I',
trhilled.
But, I seem to be having a problem geting either the stable version, or the
latest 2.5 bersion to build coreclty. here's a logfile from the stable
build.
Script started on Tue Feb 21 18:57:19 2006
[EMAIL PROTECTED] #
On Tue, Feb 21, 2006 at 07:18:37PM -0500, stan wrote:
I'v got a brand spanking new Ultra 40, just for running Amanda! I',
trhilled.
But, I seem to be having a problem geting either the stable version, or the
latest 2.5 bersion to build coreclty. here's a logfile from the stable
build.
On Thu, Jan 19, 2006 at 07:31:08PM -0500, Jean-Louis Martineau wrote:
The Amanda core team is pleased to announce the release of Amanda
2.5.0b2. It is stable and we hope to release 2.5.0 soon. test it and
report it if you find a bug in this release.
The mail reports that are mailed by amdump
18 matches
Mail list logo
