If it's easy for you to log in and set up the dsm.opt files for your
servers, that's fine.

In the case of someone whose clients are geographically scattered,
and/or they don't have administration rights on all the clients, and/or
there are 100's of clients involved, the decision to use server-side
cloptsets is much clearer!

Here I have TSM 5 domains, the clients in each domain are administered
by different people.
So I use cloptsets to set up the basic include/excludes that we use for
ALL Windows clients, and the client admins put in dsm.opt only those
things that are unique to their individual clients (which is nothing,
for most clients).

Purely an issue of convenience for you, and how things operate best at
your site.

Wanda Prather
"I/O, I/O, It's all about I/O"  -(me)



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
JR Trimark
Sent: Tuesday, March 08, 2005 10:38 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: JR- Client Option set vs dsm.opt (sys)


We are debating whether or not to use client option sets in addition to
the dsm.opt file.  A little history is needed for discussion sake:
We are backing up data only, which is typically on another drive.
Each server can have a different data drive letter depending on the
application requirements.
The include/excludes for each system will be different.
We are backing up AIX, NetWare, Linux and Windows.

I have looked through the client option set valid commands and came up
with only a handful that I would use, the remaining ones would go in the
dsm.opt (sys) file:
changing retries
dirmc
quiet
verbose
schedmode
subdir
txnbytelimit

Any thoughts are welcomed.

thanks