At 10:56 AM 10/14/2002 +0200, Toralf Lund wrote:
With tar, and some sort of a guarantee that no individual file will
exceed the tape capacity, this can be done by breaking the disklist
entries up into subdirs,
Yes, that's what I'm doing. The problem with this is that something
easily gets left out as new directories are created.
I'm late to this conversation, but I don't think it is possible to
leave out any new directories with a scheme like this:
define dumptype diskA-TheRest {
comp-user-tar #or other local globally defined TAR dumptype
exclude list /diskA/diskA.exclude
}
on client,/diskA/diskA.exclude contains:
fred
sally
sam
tom
on server, disklist:
client.fqdn /diskA diskA-TheRest #excludes fred,sally,sam,tom
client.fqdn /diskA/fred comp-user-tar
client.fqdn /diskA/sally comp-user-tar
client.fqdn /diskA/sam comp-user-tar
client.fqdn /diskA/tom comp-user-tar
(a) when remembered, add a new directory by editting disklist
(explicitly add deb and client:/diskA/diskA.exclude explicitly
exclude deb
(b) when forgotten, new directory is already included in the
diskA-TheRest because you haven't explicitly excluded it.
Yes. I think you are right.
The fact that two separate files have to be maintained is a drawback,
though, but I understand that with Amanda 2.4.3, that won't be necessary
as multiple exclusions can be listed in the dumptype (which could be
inlined in the disklist file.)
I still think a way to automate the split process would be useful,
though...
- Toralf
