I am able to successfully back up Solaris and Red Hat clients. I can not
back up the Debian client. The server is running on Red Hat.
This is the error message in the log:
STRANGE dumper 0 [sec 3057.777 kb 9339610 kps 3054.4 orig-kb
9749540]
sendbackup: start [ level 0]
sendbackup: info
What exactlty means the "sleep" configuration parameter in the
changer.conf file? I notice some lag in the tape commands (it seems
the tape is doing nothing, and the amtape is just sleeping...), so
maybe the default value of 90 is too conservative for my system. How
can I safely tune it?
And BTW,
Can someone help me out on how to restore
amanda.conf from tape? I can't see any way to do it.
[EMAIL PROTECTED] wrote:
Can someone help me out on how to restore
amanda.conf from tape? I can't see any way to do it.
Basically: on the amanda server
$ cd /tmp
$ mkdir restore-tmp; cd restore-tmp
# we restore in a safe place so that we don't overwrite
# anyting useful
$ su
On Tue, Nov 15, 2005 at 08:52:24AM -0700, [EMAIL PROTECTED] wrote:
> Can someone help me out on how to restore
> amanda.conf from tape? I can't see any way to do it.
>
Sure it is possible, that is a reason I use amanda.
You can recover without having amanda.
Do you have printed reports showing
On Tue, Nov 15, 2005 at 02:50:17PM +, Rodrigo Ventura wrote:
>
> What exactlty means the "sleep" configuration parameter in the
> changer.conf file? I notice some lag in the tape commands (it seems
> the tape is doing nothing, and the amtape is just sleeping...), so
> maybe the default value o
On Tue, Nov 15, 2005 at 09:41:04AM -0500, Rodney Johnson wrote:
> I am able to successfully back up Solaris and Red Hat clients. I can not
> back up the Debian client. The server is running on Red Hat.
>
> This is the error message in the log:
>
> STRANGE dumper 0 [sec 3057.777 kb 9339610 kps
When we got our first changer I actually did some timing tests to get a
rough idea on how long "longest case" rewind-eject-load-calibrate (I'm
using DLT) took. Then I starting shaving the time down until I saw
problems and then bumped the time back up.
Jon LaBadie wrote:
On Tue, Nov 15, 2005
Thanks for the suggestion.
A wrapper (or part of the cron job) only handles part of the problem.
If the machine has a timeout, say 1 hour, then either solution will
allow the estimate to be performed, but the backup itself may fail if
it is more than 1 hour between the estimate and the backup.
M
Oops. I misread the position of the wrapper.
Since the wrapper described on
http://www.amanda.org/docs/howto-wrapper.html runs on the client, the
wrapper won't work if the client is asleep.
Kevin Dalley <[EMAIL PROTECTED]> writes:
> Thanks for the suggestion.
>
> A wrapper (or part of the cron
Jon LaBadie wrote:
>
> On Thu, Oct 27, 2005 at 10:25:43AM -0700, Chris Marble wrote:
> > Jon LaBadie wrote:
> > >
> > > On Wed, Oct 26, 2005 at 11:53:16AM -0700, Chris Marble wrote:
> > > > >
> > > > > the /dev/sdb2 is mounted on / partition
> > > > > but instead of using /dev/sdb2 it uses /dev
Stefan G. Weichinger wrote:
The metadata on my
testmachine is about 1.2 MB in size ok, other installations will
exceed this but I think it should not be much of a problem.
Correction on this:
I took the data of a small test-config, the metadata of my productive
configuration sums up t
Gene Heskett wrote:
My method simply waits till amdump is done and has returned to the
script that launched it, at which point the script then launches a
second script that tars up all this stuff and appends it to the tape. It
could be all in one script I guess, but I tend to scratch individual
As I mentioned in another thread some minutes ago, I have done some
generalization-work on a script by Gene Heskett, which he sent to me
back in 2004.
This script is intended to help generating the necessary structures for
a vtape-setup, creating the various virtual tapes and slots etc.
I
On Mon, 2005-11-14 at 15:36 -0500, James D. Freels wrote:
Hello folks ! I have been using AMANDA now for several years and find it to be a superb backup tool. I just converted one of my AMANDA backup servers (fea5) from an Alpha 64-bit machine running Debian/Sarge to a new AMD64 64-bit m
The version of tar that is installed on the debian client is 1.13.25
When I manually create and extract the tar I do not get any errors.
From: Jon LaBadie <[EMAIL PROTECTED]>
Reply-To: amanda-users@amanda.org
To: amanda-users@amanda.org
Subject: Re: can not back up client
Date: Tue, 15 Nov 200
16 matches
Mail list logo
