Amanda-Users

RE: Avoiding incremental backups (how?)

2002-11-07 08:29:33
Subject: RE: Avoiding incremental backups (how?)
From: "Martinez, Michael - CSREES/ISTM" <MMARTINEZ AT intranet.reeusda DOT gov>
To: "'Cory Visi'" <visi AT jones-mgt DOT com>, amanda-users AT amanda DOT org
Date: Thu, 7 Nov 2002 07:43:38 -0500
I do an archival run once a month. I have a separate config called "Archive." It's identical to my DailySet config, except it gets run once a month. What I do to make it run full backup is just issue an "amadmin" command using the force option to make each client do a full backup.
 
I issue the amadmin command by hand, but it would be easy to put it into a cron script. In fact it would be easy to put the amadmin followed by the amdump, and include error checking, into a cron script.
 
Example amadmin command:
 
amadmin Archives force <amanda client hostname>

Michael Martinez
-----Original Message-----
From: Cory Visi [mailto:visi AT jones-mgt DOT com]
Sent: Thursday, November 07, 2002 3:38 AM
To: amanda-users AT amanda DOT org
Subject: Re: Avoiding incremental backups (how?)


None of these suggestions made a difference. The archival backup continues to do level 1 and 2 backups. Any other suggestions?

Thanks,
Cory


Jay Lessert <jayl AT accelerant DOT net>

10/31/2002 11:57 AM

       
        To:        Cory Visi <visi AT jones-mgt DOT com>
        cc:        
        Subject:        Re: Avoiding incremental backups (how?)



On Thu, Oct 31, 2002 at 04:13:11AM -0500, Cory Visi wrote:
> I have been trying to make an archival tape configuration for some time
> now. I have tried numerous suggestions, but nothing seems to be effective
> in stopping Amanda from doing incremental backups. I am using Amanda
> 2.4.3b4.
> The point of this configuration is to run once every 4 weeks and always do
> a full backup to tape. There are two tapes in the rotation and one is
> aways off-site.
>
> My amanda.conf:
>
> dumpcycle 0
> runspercycle 2

That doesn't make sense, use 'runspercycle 1'  I think this is
what is confusing amanda.

> tapecycle 2 tapes
>
> define dumptype comp-root-full {
>         record no
>         index yes
>         comment "Root partitions with compression"
>         compress client fast
>         priority low
>         skip-incr yes

That's not what you want.  Set 'strategy noinc'

Here's the setup that works for me.  (I run the tape once and keep
it offsite forever, but I don't see why your 'tapecycle 2' shouldn't
work.)

dumpcycle       0 days
runspercycle    1
tapecycle       1 tapes

define dumptype always-full {
   comment "Full dump always, no compression, no record"
   program "DUMP"
   maxdumps 2
   compress none
   index yes
   record no
   strategy noinc
}


> If you reply to this, please reply to me directly in addition to the list,
> as I am no longer subscribed.

Please send a summary back to the list when you fix the problem.

<Prev in Thread] Current Thread [Next in Thread>