We typically segregate OS and basic
install backups from Application and Database backups so would never use the
ALL_LOCAL_DRIVES. For any given host we might have multiple
policies depending on how many different “environments” it is
supporting. (For example we have one server that has Oracle middle
tier for about 15 different environments – each of these would have a
separate policy [if backed up at all] and that would be separate from what we
call the “OS” policy.) It would be hard to do
that with the ALL_LOCAL_DRIVES specification.
Also for Databases we would have different
policies and each of those might have multiple streams (and in some cases in
line copies) so again ALL_LOCAL_DRIVES wouldn’t work for us.
The note about “if backed up at all”
is because many of the Test/Dev environments are not backed up.
This is on the theory that if they die rather than restoring from a Test/Dev we’d
simply refresh from a recent Prod backup instead.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Nathan Kippen
Sent: Tuesday, October 21, 2008
5:25 PM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu]
"/" + Cross All Mnt Pts Vs. ALL_LOCAL_DRIVES
I'm just looking to see what the recommendation out there is for
backing up unix-based servers.
In the past I've always backed up a unix client using
"/" in my selection list and using cross all mount points + exclude
lists. As I was browsing through the Admin guide I read that
ALL_LOCAL_DRIVES could be used on unix-based clients as well.
I'm interested to know how people out there backup their unix
clients. We use cross all mount points so to make sure that an
Admin doesn't create something on a client that needs to be backed up that he
doesn't tell us [backup admins] about.
I'm looking into using the ALL_LOCAL_DRIVES directive with "allow
multiple streams" so I can stream out my unix clients by filesystem thus
getting more i/o throughput by having the backups read from multiple physical
disks at the same time. ... This opposed to using "/" +
NEW_STREAM .. since I don't really know what directories are actual
filesystems. (I don't admin the majority of the clients I backup.)