Hi,
* Jon LaBadie <j...@jgcomp.com> [20180409 17:34]:
> On Mon, Apr 09, 2018 at 01:20:05PM -0400, Jean-Francois Malouin wrote:
> > Hi,
> >
> > It's with some shame that I must admit that through the long years of using
> > amanda I've never really played w
On Mon, Apr 09, 2018 at 01:20:05PM -0400, Jean-Francois Malouin wrote:
> Hi,
>
> It's with some shame that I must admit that through the long years of using
> amanda I've never really played with the bump* parameters for DLEs!
>
> I'm now in a situation that might benefit from
Hi,
It's with some shame that I must admit that through the long years of using
amanda I've never really played with the bump* parameters for DLEs!
I'm now in a situation that might benefit from some tuning using those
to aggressively encourage bumping the gnutar incremental levels
inherited my amanda setup from my predecessor in this job and I have never
messed with the bump settings. But we are moving from physical tapes to
virtual tapes. Here are the current values:
bumpsize 500 mb # minimum savings (threshold) to bump level 1
- 2
bumpdays 1
night.
It's not obvious to me from the docs that 'amadmin force bump' will
actually prevent amanda from concluding that it's time for a level
0. Would 'force bump' serve my purpose? (My guess = no.)
There is more than one runcycle in our tape cycle, and we won't be
over-writing
There is a planner bug with force-bump when a dle is overdue.
The attached patch should fix it.
As a workaround, you can set a large dumpcycle (eg. 1).
force-bump will prevent full, but it will also bump the level, this
might not be what you want.
Setting a large dumpcycle and a small
One day next week I want to prevent any level 0 dumps, and run only
incrementals for that one night.
It's not obvious to me from the docs that 'amadmin force bump' will
actually prevent amanda from concluding that it's time for a level
0. Would 'force bump' serve my purpose? (My guess
On Wed, Dec 21, 2011 at 10:01:36AM -0500, Bryan Hodgson wrote:
One day next week I want to prevent any level 0 dumps, and run only
incrementals for that one night.
It's not obvious to me from the docs that 'amadmin force bump' will
actually prevent amanda from concluding that it's time
bump' will
actually prevent amanda from concluding that it's time for a level
0. Would 'force bump' serve my purpose? (My guess = no.)
There is more than one runcycle in our tape cycle, and we won't be
over-writing the most recent level 0 for any dump.
I looked at the man page and I
Hi all
I think about the backup schedules as follow:
1st full backup(LV0)
2nd partial backup(LV1)
3rd partial backup(LV1)
4th partial backup(LV1)
'force', 'forcd-bump', and 'forcd-no-bump' each option of the amadmin
command had been executed specifying it before the
amdump command was executed
and
EPO bumpdays should be specified. My problem is that I don't know exactly
EPO what this bump and the associated level mean.
EPO Would someone please explain these terms to me?
I don't want repeat my new mantra too often, as it might get worn out
too early ... :
Have you read
Hi Stefan,
- Original Message -
From: Stefan G. Weichinger [EMAIL PROTECTED]
To: amanda-users@amanda.org
Subject: Re: Meaning of bump
Date: Sat, 15 Jan 2005 12:08:31 +0100
OK, it says:
The minimum savings required to trigger an automatic bump from one
incremental level to the next
Hi, Erik,
on Samstag, 15. Jänner 2005 at 13:59 you wrote to amanda-users:
EPO On Sat, 2005-01-15 at 10:03 +0100, Stefan G. Weichinger wrote:
Have you read the description of those parameters at
http://www.amanda.org/docs/amanda.8.html ?
EPO Yes, I have (and am) reading it. Description of the
to point me at those
SGW issues as it is sometimes hard to forget what you know when it comes
SGW to writing docs. Over the years one gets so used to some of the
SGW concepts that one gets a bit blind sometimes ...
One more on this: A grep for bump in the docs-tree showed that there
REALLY
Hi,
I am running Fedora Core 3 which comes with amanda installed and I have
just started to set it up. In amanda.conf bumpsize, bumpmult and
bumpdays should be specified. My problem is that I don't know exactly
what this bump and the associated level mean.
Would someone please explain
Hey Gang,
Anyone seen this before?
NOTES:
planner: Incremental of www.thepilot.com:/usr/local/apache bumped to level 2.
yet the actual summary says:
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME
Hi,
Yes, seen that message many times. What happens is following:
planner decides the savings would let the drive bump to level 2,
produces this message and goes on with planning. Later it finds
out, this drive is due for a level 0, so it skips the bump and
does a level 0 instead.
Quite normal
Friends, please ...
During amanda bkp process, I had been received the message
== planner: Preventing bump of ... ==
Always the msg is for the same directory.
Is this a problem or just an information message ?
See the report:
===
NOTES:
. . .
planner
Hello Floriano,
You did a
'amadmin conf force-no-bump prods6.hc.unicamp.br //samara/Projetos'
The command is in effect until the dump is written to tape.
Jean-Louis
On Fri, Oct 25, 2002 at 10:06:14AM +, Prods6 - AMANDA - Bkp Mannager wrote:
Friends, please ...
During amanda bkp
?
The log says: INFO planner Preventing bump of localhost://ntserver/ppidocs
as directed, INFO planner Preventing bump of
localhost://ntserver/businesswork as directed. -- Can someone please
assist?
Thanks,
Michael Blinn
People Places, Inc.
amanda.conf:
dumpuser backup # the user to run dumps
more than it has to. This simplifies what needs to be done for a restore.
In your case, you want to minimize the amount of data in the holding disk,
so may want to change the bump* parameters in amanda.conf (set them all
to zero) to encourage Amanda to go to the next level every day.
Deni
21 matches
Mail list logo
