Sure. Here's a sample for Win2K servers; customize it to be appropriate to
your environment; I'm no Windows expert!
define cloptset win2kserver description="Backup options for TSM Win2K
Servers"
define clientopt win2kserver compression oFF
define clientopt win2kserver maxcmdretries 99
def
ED]
Dist Stor cc
Manager"
<[EMAIL PROTECTED] Subject
.EDU> Re: Client Option Sets vs. Option
hi, how many client are you handlig ?
thanks,
goran
- Original Message -
From: "Prather, Wanda" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 13, 2004 11:35 PM
Subject: Re: Client Option Sets vs. Option Files
> We use about 5 different clopt
We use about 5 different cloptsets.
One for macs, one for Win2K, one for Win2K3 servers, one for Windows
desktops, one for AIX servers, etc.
We put in the cloptset things that apply to all Win2K servers, (or macs, or
AIX, etc.)
and put in dsm.opt anything that only applies to that particular clien
Hello all,
We are debating switching our TSM environment from the use of option
files to client option sets and a few questions have been raised:
1) Can we use just one large option set that encompasses all possible
excludes and includes (since our includes are usually directory
specific)?
