Amanda-Users

Re: GNUTAR include/exclude questions

2003-05-23 10:24:11
Subject: Re: GNUTAR include/exclude questions
From: Jon LaBadie <jon AT jgcomp DOT com>
To: amanda-users AT amanda DOT org
Date: Fri, 23 May 2003 10:21:36 -0400
On Fri, May 23, 2003 at 09:19:50PM +0800, Mathias Körber wrote:
> Hi friends of AMANDA!
> 
> after years I am coming back to Amanda and am overjoyed at the progress
> the package has made. I especially like the GNUTAR support (or which I
> was the first glimpses just before I stopped using ...).
> 
> Anyway, I now have some questions/problems regarding defining backup sets
> for GNUTAR backups.
> 
> I want to create a single backup of
>       /var/imap/*
> and   /var/spool/imap/*
> 
> I tried this:
> 
> localhost var-imap /var {
>       comp-user-tar
>       include "./imap*"
>       include "./spool/imap/*"
>       } 1
> 
> to no avail. The ./spool/imap/*
> and its subdirs never made it to the archive.
> 
> on looking back at the manual, it says:
>       All include expression are expanded by amanda and concatenated in
>       one file  and passed to gnutar as a --files-from argument.  They
>       must start with "./" and containing no other "/".
> which would explain that ./spool/imap* dis not work.
> 
> Note that I will not know of any other subdirectories of /var
> and /var/spool which I could explicitly exclude...
> 
> So here my questions regarding include/exclude:
> 
> a) Is there any way around this limitation?
> 
> b) In which sequence are include and excludes processed?
>       1. in the sequence they appear in the definition,
>          ie, does
>               exclude './[a-z]*'
>               include './big1'
>          include big1 or will the preceding exclude
>          already result in it not being seen at all?
> 
>          and/or would
>               include './big1'
>               exclude './[a-z]*'
> 
>          result in big1 being included or excluded?
> 
>       2. includes before excludes
>       3. excludes before includes
> 
> c) does using include in a definition imply a preceding 'exclude all'
>    and vice versa?
> 
> d) Is there a way to get amanda to do a dry-run to show which files
>    it would include/exclude with a given definition but not actually
>    do a backup?
> 
> any help is appreciated


Welcome back.  Good questions all.  I hope the person(s) responsible for
adding the code are still list readers and can give us the insights.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)

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