Amanda-Users

Re: Sizes don't fit?

2006-03-16 08:56:07
Subject: Re: Sizes don't fit?
From: listrcv <listrcv AT condor-werke DOT com>
To: Paul Bijnens <paul.bijnens AT xplanation DOT com>
Date: Thu, 16 Mar 2006 14:52:06 +0100
Paul Bijnens wrote:
On 2006-03-16 13:48, listrcv wrote:

prometheus:/tmp/xxx# tar -cf test.tar -T include .


When using -T you should not specify a list of things
to backup on the command line as well, i.e. omit the final dot.

Oh! :)

Maybe I just have to try it out ... :/


Yes, indeed!

I'm somewhat stuck with it. I need some doc on the format of the disklist to understand the example in the FAQ:


fatboy  /bigmama_BIGDIR  /bigmama {     # a big subdirectory
comp-user-tar
include "./bigdir"
}
fatboy  /bigmama_FILES01 /bigmama {     # all files beginning with...
nocomp-user-tar
include "./file[01]*"
}


The 'fatboy' is the server? What is bigmama_BIGDIR and bigmama_FILES01? And why is every thing called /bigmama?

Using


prometheus      /home/a*        tar-dfault-no-x
prometheus      /home/b*        tar-dfault-no-x
[...]


doesn't work, amcheck complains:


ERROR: prometheus: [could not access /home/z* (/home/z*): No such file or directory] ERROR: prometheus: [could not access /home/y* (/home/y*): No such file or directory]
[...]


Would it be something like this?


prometheus /home_a /home {
  tar-dfault-no-x
  include "/home/a*"
  exclude "/home/[!a]*"
}

prometheus /home_b /home {
  tar-dfault-no-x
  include "/home/b*"
  exclude "/home/[!b]*"
}
[...]
prometheus /home_rest /home {
  tar-dfault-no-x
  include "/home/[!a-z]*"
  exclude "/home/[a-z]*"
}


GH

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