Note: FORCE=YES actually has no effect on include-exclude statements in client option sets. The server settings always are processed before whatever is in the local include-exclude list. So if you do something like this in the client option set:
def cliento mycloptset inclexcl "exclude *.mp3" Users cannot override it from the client side. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <[email protected]> wrote on 03/22/2008 11:54:49 PM: > That's right, the beauty of CLOPTSETs is in the fact that they are > "propagated" to the clients and picked up automatically at the next > time client communicates with the server. You might also consider > using "f=y" if you suspect that some smart-a$$ed students with > root/admin privileges on their workstations decide to play around you > restrictions by utilizing "include /.../*.mp3" statement. > > On Fri, Mar 21, 2008 at 4:39 PM, Howard Coles > <[EMAIL PROTECTED]> wrote: > > I'm not sure my messages are actually getting through, but I'll try. > > > > From what I understand about CLOPSETs the clients should re-read it each > > time they start a backup, so you should not have to restart the > > scheduler for them to pickup changes. I never have anyway. > > > > See Ya' > > Howard > > > > > -- > Warm regards, > Michael Green
