On Tue, Nov 02, 2010 at 07:26:47AM -0400, Chris Hoogendyk wrote:
>
>
> On 11/1/10 10:10 PM, Jon LaBadie wrote:
> >I've started backing up my amanda files nightly
> >in a separate amdump run after my primary amdump.
> >My plan was to leave it on the holding disk and
> >let it autoflush to vtape during the next day's
> >dump. Unfortunately it does not flush. I've
> >now got about 7 dumps on the holding disk.
> >
> >Any suggestions why an "autoflush yes" might
> >not be effective?
>
> How do you achieve the separate dump? Is it the same configuration
> with command line options to stipulate what is getting done? It
> doesn't make sense that something as fundamental as autoflush would
> stop working or be removed from the options, so I'm just wondering
> how you have it set up. Details?
>
My scheme would not scale well or be suitable in a
production environment.
There is only one config, "Daily". For the amanda
server, one DLE (called Amanda) uses a disk of "/"
and "includes" each of the amanda directories.
My other server DLEs exclude these same dirs.
My crontab executes a script that does two amdumps.
The first looks like this:
/usr/sbin/amdump Daily \
.butch. Root \
.butch. Var \
<snip bunch of similar DLE lines>
.bigcow. Opt \
.bigcow. Home
Then it executes:
/usr/sbin/amdump Daily --no-taper .bigcow. Amanda
to get the amanda files.
--
Jon H. LaBadie [email protected]
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)
