Re: Editing disklist
2004-01-23 11:33:00
In a message dated: Thu, 22 Jan 2004 18:42:54 +0100
"Stefan G. Weichinger" said:
>example/disklist
I looked at this and got a little confused. It shows as an example:
hosta /diskA/all /diskA {
# all directories except the one that start with [a-u]
high-tar
exclude "./[a-u]*"
} 1
hosta /diskA/ag /diskA {
# all directories that start with [a-g] except big1 and big2
high-tar
include "./[a-g]*"
exclude "./big1" "./big2"
} 1
hosta /diskA/big /diskA {
# directories big1 and big2
high-tar
include "./big1" "./big2"
} 1
Do the directories '/diskA/all', '/diskA/ag', and '/diskA/big'
actually exist, or are they simply labels being used to keep things
organized?
I have the following directory structure:
/u1/backup/act-of-god
/u1/backup/archive
/u1/backup/bad-for-business
/u1/backup/build
/u1/backup/cvs-repos
/u1/backup/rt
/u1/backup/sw
I'd like each of these subdirs of /u1/backup to be separate backup
volumes. To accomplish that, do I do something like this:
jpt /u1/backup/all /u1/backup {
# Exclude everything that's explicitly named
# if we add a directory later, but forget to add it here
# it will be picked up automagically
non-user-high-tar
exclude "./act-of-god"
exclude append "./archive"
exclude append "./bad-for-business"
exclude append "./cvs-repos"
exclude append "./rta"
exclude append "./software"
exclude append "./build"
} 1
jpt /u1/backup/act-of-god /u1/backup {
# only the act-of-god subdir
non-user-high-tar
include "./act-of-god"
exclude "./*"
} 1
jpt /u1/backup/archive /u1/backup {
# only the archive subdir
non-user-high-tar
include "./archive"
exclude "./*"
} 1
etc.?
Thanks
--
Seeya,
Paul
GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE
If you're not having fun, you're not doing it right!
|
|
|