Hi Geert,
thanks!
that solved my problem!
Gr./Br.
Dennis
> -Oorspronkelijk bericht-
> Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Verzonden: donderdag 6 december 2007 08:27
> Aan: Dennis Ortsen
> CC: amanda-users@amanda.org
> Onderwerp: Re: /usr/lib/amanda/chg-disk:: tape_rdla
On Wed, 5 Dec 2007, Dennis Ortsen wrote:
> I've just hit a 100% full root filesystem (as in / )(ouch). I managed
> to get it a bit larger (using LVM on RHEL5). After the root file
> system had space left again, I thought I could check the upcoming
> backup with AMANDA again. So I ran a "amcheck jo
[EMAIL PROTECTED] schrieb:
I get a brand new LTO4 tape and I wonder about the tape definition
to use.
You can use amtapetype to generate your own one:
http://wiki.zmanda.com/index.php/Amtapetype
And if you have done, you can add it to the wiki
http://wiki.zmanda.com/index.php/Tapetype_definit
Paul Bijnens schrieb:
>amrmtape theconfig FULLBACK-10
> ...
If you omit this, then amanda will e.g. plan a level 2,
> based on the level 1 DLE that did not had errors, but
> was stored on that tape.
Yes, you're right. This is better to do first. I just thought, this won't
happen in his "du
you can use the tapetype program to generate your own.
--On December 6, 2007 12:33:31 AM +0100 [EMAIL PROTECTED] wrote:
Hello,
I get a brand new LTO4 tape and I wonder about the tape definition
to use.
Regards
JPP
--
"Genius might be described as a supreme capacity for getting its poss
Hello,
I get a brand new LTO4 tape and I wonder about the tape definition
to use.
Regards
JPP
I have a couple of disk list entries for a samba client which seem to be
causing the disks to be backed up with a full dump nearly every time. I
am suspecting it's a regular expression problem since the DLEs are
almost identical.
The DLEs look like so:
# Design Resources Mac
moi//coralie/de
Marc Muehlfeld wrote:
Yogesh Hasabnis schrieb:
I would like to use the same tape again. What do I need to do to
get this done (ie to use the same tape again)?
Did I understand you right: You backuped your clients and one DLE failed.
And now you want to rerun the complete set on the same tap
On Wed, 5 Dec 2007 13:18:37 -0500
Jon LaBadie <[EMAIL PROTECTED]> wrote:
> On Sun, Dec 02, 2007 at 01:36:15PM +0100, Charles Stroom wrote:
> > Greeting,
> >
> > since a number of days Amanda reports:
> > "
> > FAILURE AND STRANGE DUMP SUMMARY:
> > fiume.localnet / lev 0 STRANGE
> > "
> >
>
Yogesh Hasabnis schrieb:
> The most recent monthly full backup failed for some reason. The error
> reported in the amanda email is as follows:
>
> FAILURE AND STRANGE DUMP SUMMARY:
> /vol/vol1/home lev 0 FAILED [data timeout]
> /vol/vol1/home lev 0 FAILED [dump to tape
> failed]
Have y
zuki (a.k.a. fedora?) wrote:
hoogendyk wrote:
There are a number of issues here that are hard to answer without
more information about your setup, volume of data and budget. These
are things that every backup administrator has to answer, and there
is no particular "right" answer.
So, you
Hi all,
I've just hit a 100% full root filesystem (as in / )(ouch). I managed
to get it a bit larger (using LVM on RHEL5). After the root file
system had space left again, I thought I could check the upcoming
backup with AMANDA again. So I ran a "amcheck jobname -a" and got the
following result m
On Sun, Dec 02, 2007 at 01:36:15PM +0100, Charles Stroom wrote:
> Greeting,
>
> since a number of days Amanda reports:
> "
> FAILURE AND STRANGE DUMP SUMMARY:
> fiume.localnet / lev 0 STRANGE
> "
>
> The details given below in the backup report are:
> "
> FAILED AND STRANGE DUMP DETAILS:
>
Greeting,
since a number of days Amanda reports:
"
FAILURE AND STRANGE DUMP SUMMARY:
fiume.localnet / lev 0 STRANGE
"
The details given below in the backup report are:
"
FAILED AND STRANGE DUMP DETAILS:
/-- fiume.localnet / lev 0 STRANGE
sendbackup: start [fiume.localnet:/ level 0]
sendba
Hi All,
I have two different amanda configurations - one for daily incremental backups
and the second for monthly full backup. The most recent monthly full backup
failed for some reason. The error reported in the amanda email is as follows:
FAILURE AND STRANGE DUMP SUMMARY:
/vol/vol1/ho
fedora wrote:
> (hoogendyk wrote:)
yup. I would say you are a bit confused.
The 26th is the last full backup (the 0 in the column after the date),
and the 29th is the most recent incremental based on that full (the 1 in
the column after the date). Anything else is older, out of date,
r
zuki wrote:
There are a number of issues here that are hard to answer without
more information about your setup, volume of data and budget. These
are things that every backup administrator has to answer, and there
is no particular "right" answer.
One issue is how and when to do archives with Am
There are a number of issues here that are hard to answer without more
information about your setup, volume of data and budget. These are
things that every backup administrator has to answer, and there is no
particular "right" answer.
One issue is how and when to do archives with Amanda. It'
Thomas Ginestet wrote:
Sorry for the delay, we just changed the backup server and it does the
same thing on the new one (i suppose there is a mistake in my amanda
configuraiton).
Like before, the full dump should have been made on 2007-11-30 instead
of the incremental level 4.
I expected:
Jean-Louis Martineau a écrit :
The problem is in the way amanda compute time between different run,
it use the time the backup for a DLE is terminated, not the time the
amdump started.
You should get this problem if a run take more than 12 hours. How much
time took the 23th of November amdum
There are a number of issues here that are hard to answer without more
information about your setup, volume of data and budget. These are
things that every backup administrator has to answer, and there is no
particular "right" answer.
One issue is how and when to do archives with Amanda. It's ne
21 matches
Mail list logo