Re: cloptset broken for Windows 4.1.2.X client
On Tue, Apr 10, 2001 at 09:02:13AM -0400, Kleynerman, Arthur wrote: > Suad, did you specify force=yes (to override the options in the dsm.opt > file)? > > For example: > > def clientopt opt_set 'Exclude ' seq=0 force=yes Aaarrggghh ... found out what the story is. When I actually demonstrated the 4.1 "daylight savings bug-fix" client install for a desktop (desktops get the "only backup the documents directory" Cloptset), I noticed a whole bunch of files in \winnt and \program files were getting backed-up. I kept quitting the incremental thinking the program ignored the exclude directives. The old 3.7 client was an obediant little surf and did what I told it to do. It didn't occur to me they were the system-files part of the "System Object". Cheers, Suad -- (off to the pub to sedate my remaining sane braincells)
Re: cloptset broken for Windows 4.1.2.X client
>My understanding from documentation is that specifying force=yes on server >side inclexcl options will process those includes/excludes *before* the >ones in the client side dsm.opt file. And force=no will process them >after. In effect, force=yes puts the server side rules at the "bottom" of >the include/exclude list and force=no puts them at the "top". Jennifer - The redbook Getting Started with Tivoli Storage Manager: Implementation Guide, SG24-5416-01 does a good job of describing Client Option Sets, in section 7.3. The server-supplied include-exclude definitions ALWAYS precede the client options file specifications, in the processing order. As the manual says: "include-exclude options in a client option set will always be seen and processed during backup first, before any options set in the client options file." And: "Include-exclude options in the client option set are additive options and will not override the include-exclude options in the client options file." As the book says: "The sequence is not obvious." There is a lot of customer confusion about this because the standard product reference, the Admin Guide, treats the topic superficially and the Client manual ignores it. Richard Sims, BU
Re: cloptset broken for Windows 4.1.2.X client
Greetings, We are running a test of Client Option Sets from an AIX server running TSM 4.1.2 and an NT 4.0 Workstation running TSM 4.1.2.12. Things *seem* to be behaving as expected with includes/excludes. One that exists only on the server side is working to exclude the entire D:drive. This is set to force=yes, and it does override an include on the client sode. Incl/excl rules that exist on both server and client are giving the expected duplicate error messages in the dsmerror.log (and the files are being excluded). My understanding from documentation is that specifying force=yes on server side inclexcl options will process those includes/excludes *before* the ones in the client side dsm.opt file. And force=no will process them after. In effect, force=yes puts the server side rules at the "bottom" of the include/exclude list and force=no puts them at the "top". We are new at this, so this may not be entirely accurate information. Just wanted to share our experiences so far. Thanks, Jennifer At 09:18 AM 4/10/2001, you wrote: >What if one has all of inclexcl statements defined in the client option set >and none in the dsm.opt file? > >-Original Message- >From: Richard Sims [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, April 10, 2001 9:16 AM >To: [EMAIL PROTECTED] >Subject: Re: cloptset broken for Windows 4.1.2.X client > > > >Suad, did you specify force=yes (to override the options in the dsm.opt > >file)? > >Note that INCLEXCL and DOMAIN are additive options such that >Force has no effect. That is, Force pertains only to >singular options. > > >--- > >The information contained in this e-mail message, and any attachment >thereto, is confidential and may not be disclosed without our express >permission. If you are not the intended recipient or an employee or agent >responsible for delivering this message to the intended recipient, you are >hereby notified that you have received this message in error and that any >review, dissemination, distribution or copying of this message, or any >attachment thereto, in whole or in part, is strictly prohibited. If you >have received this message in error, please immediately notify us by >telephone, fax or e-mail and delete the message and all of its >attachments. Thank you. > >Every effort is made to keep our network free from viruses. You should, >however, check this e-mail message, as well as any attachment thereto, for >viruses. We take no responsibility and have no liability for any computer >virus which may be transferred via this e-mail message.
Re: cloptset broken for Windows 4.1.2.X client
What if one has all of inclexcl statements defined in the client option set and none in the dsm.opt file? -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 10, 2001 9:16 AM To: [EMAIL PROTECTED] Subject: Re: cloptset broken for Windows 4.1.2.X client >Suad, did you specify force=yes (to override the options in the dsm.opt >file)? Note that INCLEXCL and DOMAIN are additive options such that Force has no effect. That is, Force pertains only to singular options. --- The information contained in this e-mail message, and any attachment thereto, is confidential and may not be disclosed without our express permission. If you are not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution or copying of this message, or any attachment thereto, in whole or in part, is strictly prohibited. If you have received this message in error, please immediately notify us by telephone, fax or e-mail and delete the message and all of its attachments. Thank you. Every effort is made to keep our network free from viruses. You should, however, check this e-mail message, as well as any attachment thereto, for viruses. We take no responsibility and have no liability for any computer virus which may be transferred via this e-mail message.
Re: cloptset broken for Windows 4.1.2.X client
Suad, did you specify force=yes (to override the options in the dsm.opt file)? For example: def clientopt opt_set 'Exclude ' seq=0 force=yes Arthur. -Original Message- From: Suad Musovich [mailto:[EMAIL PROTECTED]] Sent: Monday, April 09, 2001 11:08 PM To: [EMAIL PROTECTED] Subject: cloptset broken for Windows 4.1.2.X client I have upgraded a few Windows (2Kpro) boxes from the 3.7.2 TSM client to the 4.1.2.19 one. The new client seems to ignore the Client-Option set assigned to these clients? In our case, it ignores all the EXCLUDE options and proceeds to backup the entire hard-drive. Anyone aware of this one? Cheers, Suad -- --- The information contained in this e-mail message, and any attachment thereto, is confidential and may not be disclosed without our express permission. If you are not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution or copying of this message, or any attachment thereto, in whole or in part, is strictly prohibited. If you have received this message in error, please immediately notify us by telephone, fax or e-mail and delete the message and all of its attachments. Thank you. Every effort is made to keep our network free from viruses. You should, however, check this e-mail message, as well as any attachment thereto, for viruses. We take no responsibility and have no liability for any computer virus which may be transferred via this e-mail message.
Re: cloptset broken for Windows 4.1.2.X client
>Suad, did you specify force=yes (to override the options in the dsm.opt >file)? Note that INCLEXCL and DOMAIN are additive options such that Force has no effect. That is, Force pertains only to singular options.
cloptset broken for Windows 4.1.2.X client
I have upgraded a few Windows (2Kpro) boxes from the 3.7.2 TSM client to the 4.1.2.19 one. The new client seems to ignore the Client-Option set assigned to these clients? In our case, it ignores all the EXCLUDE options and proceeds to backup the entire hard-drive. Anyone aware of this one? Cheers, Suad --
