On 2006-05-12 13:40, Anne Wilson wrote:

On Thursday 11 May 2006 19:16, Jean-Louis Martineau wrote:

Show us that you made the change, what is the output of :
   amadmin CONFIG disklist borg /home

amadmin Daily  disklist borg /home
line 8:
    host borg:
        interface default
    disk /home:
        program "GNUTAR"
        exclude list "amanda.exclude"
        priority 1
        dumpcycle 7
        maxdumps 4
        maxpromoteday 10000
        bumpsize 10240
        bumpdays 1
        bumpmult 2.000000
        strategy STANDARD
        estimate CLIENT
        compress CLIENT BEST
        comprate 0.50 0.50
        encrypt NONE
        auth BSD
        kencrypt NO
        holdingdisk YES
        record YES
        index YES
        fallback_splitsize 10Mb
        skip-incr NO
        skip-full NO

Did the exclude have the value you want?

Hard to tell. I still don't know where it will look for the exclude-list file. Should it be in the amanda Daily directory, or the path from where the backup starts? Also, I can't find the sendbackupXXXX.exclude files that I found before, which is a bit worrying.

When all else fails, read the manual:  (man amanda.conf, "exclude"...)

  For exclude list, if the file name is relative, the  disk  name
  being backed up is prepended. So if this is entered:

      exclude list ".amanda.excludes"

  the  actual  file  used  would  be  /var/.amanda.excludes for a
  backup of /var, /usr/local/.amanda.excludes  for  a  backup  of
  /usr/local, and so on.

Where did you put that file? give the complete path? It is on borg?

On borg - in two places, /home/amanda.exclude and /usr/local/etc/amanda/Daily/amanda.exclude

The first one is correct.  At least, if that is /home of the
client!

What are its permission 'ls -l'

-rw-r--r--  1 amanda disk 35 May 10 17:23 /home/amanda.exclude

good.

-rw-r--r-- 1 amanda disk 35 May 11 14:08 /usr/local/etc/amanda/Daily/amanda.exclude

Remove the 'optional' keyword of your exclude list.

If you mean in amanda.conf, I don't have the 'optional' keyword.

The 'optional' keyword that was suggested by someone to be added
to the exclude line.  That 'optional' keyword suppresses error
messages when that file cannot be found or accessed.

Try 'amcheck -c borg /home'

amcheck -c Daily /home

Amanda Backup Client Hosts Check
--------------------------------
Client check: 1 host checked in 0.000 seconds, 0 problems found

Ok.  Now what are the contents of that file?

$cat /home/amanda.exclude
./anne/Photos
./anne/recordings


Now the weird stuff, just to check/verify.
The file must be a text file (not e.g. an MSWord file).
It must have unix line endings (\n) and not DOS (\r\n).
Spaces in the file (at the end) are significant.  Make sure there
are no unwanted spaces or tabs or carriage returns (hexdump -C).
The names of the files are case sensitive too.


Different solution using excludes is also possible.
Instead of storing the patterns in a file on the client, you can
put them in the disklist file on the server too. Use this syntax
for the disklist:

  borg  /home {
        program "GNUTAR"
        compress CLIENT BEST
        index yes
        exclude file "./anne/Photos" "./anne/recordings"
        } 1

--
Paul Bijnens, xplanation Technology Services        Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
***********************************************************************