I generally use ALL_LOCAL_DRIVES and exclude things I don't want to
backups.  This sort of covers me incase an enthusiastic admin adds some
storage and forgets to tell me about it.  That said, I have a few
policies like this, mostly backing up Oracle Archive Files (don't ask.)
If you select E: but E: doesn't exist on a client, it skips it.  Worst
case scenario you might end up with an error 71 - no files on the list
exist, but I think only if you are multistreaming.  You'll have to check
that part out, but generally speaking your method is fine and in
production here.

-Jonathan 

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Paul
Keating
Sent: Wednesday, July 12, 2006 8:24 AM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] changing backup selection in a policy

I don't have a windows client in the lab at the moment, otherwise I
would test this myself and not bother you fine folks.
I feel like I should know this, but I've been burned by
assumptions/beliefs before.

I currently have a windows policy with several clients and a "backup
selections" list of C:\, D:\ and System_State:\ One of the machines has
a new volume added mounted as E:\, so I want to add E:\ to the
list......will adding an entry for E:\ in the list trip the policy up so
as to run all incremental backups as "FULL"?
I don't mind that this one client will pick up the E:\ drive as "changed
since full" untill the next full, as it isn't too big.

I think not, as the policy name has not changed....each client should go
on as usual, knowing it previously had a good FULL with the same policy
name, search the system for the new drive letter, then move on, if it
doesn't exist....correct?

Paul