Unless there is a reason why you *wouldn't* want one of your clients to back
up all locally attached drives, there should be no problem.  We've used the
default of ALL-LOCAL from the start and haven't run into any problems.




ADSM-L AT vm.marist DOT edu on 07/20/99 08:33:35 AM
Please respond to ADSM-L AT vm.marist DOT edu @ INTERNET
To: ADSM-L AT vm.marist DOT edu @ INTERNET
cc:
Subject: DOMAIN statement

I have a number of clients (both NT and Netware) running on ADSM v3.1 where
the
DOMAIN statement in the client dsm.opt is coded for specific local
drives/volumes respectively (like DOMAIN C: D:) I've shot myself at times
where
a new
drive was added to an NT server and was not caught in the backup for some
time.
Does anyone know of any 'gotchas' or such using DOMAIN ALL-LOCAL in both NT
4.0
and Netware 4.11(soon to be v5.0) clients?
If all is fine, i plan to changes the OPT files soon to use DOMAIN ALL-LOCAL