TSMers, Thanks to all who responded to my domain backup issues. Andy, thanks for bringing this setting to my attention.
Todd -----Original Message----- From: Andrew Raibeck [mailto:[EMAIL PROTECTED]] Sent: Monday, April 08, 2002 10:21 AM To: [EMAIL PROTECTED] Subject: Re: dsm.opt domains not working Todd, Here is your trouble, from the client options set information (I've "squeezed" some of the blank spaces out to avoid line wrapping): Option Sequence Override Option Value number --------------- -------- -------- ------------ CHANGINGRETRIES 0 No 4 COMPRESSALWAYS 0 Yes no COMPRESSION 0 No off DIRMC 0 Yes dir ==> DOMAIN 0 No all-local <== DOMAIN statements are "cumulative". That is, one DOMAIN statement does not replace another; it adds items to the current domain. For example, if you have these two lines in DSM.OPT: DOMAIN C: DOMAIN D: Then the domain is C: and D:. The above two lines are equivalent to: DOMAIN C: D: In your case, you are getting the equivalent of: DOMAIN C: F: ALL-LOCAL You can delete the client option for DOMAIN ALL-LOCAL from the client options set, unless you have other clients using this client options set, and they rely on this setting. If that is the case, then you might consider creating a new client options set for the one client where you only want C: and F:. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Pucky, Todd M." <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/08/2002 04:33 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: dsm.opt domains not working Andy, Attached are the files that you requested... Thanks for all of your help. Todd -----Original Message----- From: Andrew Raibeck [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 04, 2002 11:36 AM To: [EMAIL PROTECTED] Subject: Re: dsm.opt domains not working Can you paste in the output from QUERY CLOPTSET for the cloptset you are using? Also, can you paste in the output from Q SCH domainname schedname F=D? Be sure to specify just the domainname and schedname you are using for this client in particular to keep the output to a minimum. Thanks, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Pucky, Todd M." <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/04/2002 09:16 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: dsm.opt domains not working Andy, The scheduler service was restarted and it is using the newly modified dsm.opt file. The CLOPTSET has no listing of includes for domains. The schedule definition also makes no references to domains. Can you exclude drives by putting these lines in the dsm.opt?... EXCLUDE D:* EXCLUDE E:* EXCLUDE H:* Thanks for your help! Todd -----Original Message----- From: Andrew Raibeck [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 04, 2002 10:37 AM To: [EMAIL PROTECTED] Subject: Re: dsm.opt domains not working I am not aware of any problems in this area. A few things that come to mind: 1) After modifying dsm.opt, did you restart the scheduler? 2) Did you verify that the scheduler is using the same options file that you modified? 3) Did the TSM administrator define a client options set for this node that includes the additional domains? 4) Did the TSM administrator include any domain specifications in the schedule definition? Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Pucky, Todd M." <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/04/2002 08:08 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: dsm.opt domains not working TSMers, I am having a problem with an NT4 sp6 client running TSM 4.1.3 client software. The dsm.opt file entries are as follows: TCPSERVERADDRESS xxxxxxxxx PASSWORDACCESS GENERATE NODENAME xxxxxxxxxxx RESOURCEUTILIZATION 6 ERRORLOGRETENTION 7 SCHEDLOGRETENTION 7 COMPRESSION YES BACKUPREGISTRY YES DOMAIN C: F: Exclude.Dir F:\MSSQL7\Data By using DOMAIN C: F:, only these 2 local drives should get backed up, correct? When I open the TSM GUI and click edit>preferences>backup the "Backup all local file systems" is unchecked and it appears that only C: and F: will be backed up. But that is not the case. Here is an entry from the dsmsched.log: Incremental backup of volume '\\xxxxx\C$' 04/04/2002 00:09:13 Incremental backup of volume '\\xxxxx\F$' 04/04/2002 00:09:13 Incremental backup of volume '\\xxxxx\D$' 04/04/2002 00:09:13 Incremental backup of volume '\\xxxxx\E$' 04/04/2002 00:09:13 Incremental backup of volume '\\xxxxx\G$' 04/04/2002 00:09:13 Incremental backup of volume '\\xxxxx\H$' All of the local drives get backed up. Has anyone else experienced probelms with only using the DOMAIN phrase in the dsm.opt file instead of exclude statements? Any help would be greatly appreciated. Thanks Todd M. Pucky The Timken Company Global Information Systems Programmer/Analyst 330.471.4583 [EMAIL PROTECTED] ********************************************************************** This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company ********************************************************************** #### CLOPTSET_WIN.TXT has been removed from this note on April 08 2002 by Andrew Raibeck #### SCHEDINFO.TXT has been removed from this note on April 08 2002 by Andrew Raibeck #### dsm.opt has been removed from this note on April 08 2002 by Andrew Raibeck