I would have told you the same thing about the reboot! My experience with V6 clients on Win2K3 it's not necessary; and even if it asks for a reboot, usually any issues only affect the GUI (because of DLLs), not the scheduler/cmd line. So I'm just flailing here.
Another thing I'd look for is look in Windows task manager, see if there are extra dsm* proceses running, other than the scheduler service, and kill them if you don't know what they are, on the off chance somebody left a backup or restore session open/running that got disconnected. I've seen bizarre behavior due to that before. So no need to thank me, I haven't helped you! I'm just giving up and resorting to the last ditch "stuff on Win2K3 that cannot be explained any other way is usually fixed with a reboot" solution. And if you got 100 Windows machines upgraded without incident and just this one is goofy, I'd say that's a great result! :>) Wanda Prather TSM Consultant ICF International Enterprise and Cybersecurity Systems Division -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Kinder, Kevin P Sent: Friday, February 06, 2015 3:37 PM To: [email protected] Subject: Re: [ADSM-L] Duplicate include/exclude option error Thanks again Wanda. That will be my next step. As a bit of background, this was all part of a process to move from our TSM installation on z/OS to a new one on an AIX server. Hated to do that, but since IBM dropped development and upgrades in the z/OS arena, we had no choice. So, in going from TSM 5.5 to 7, we had client upgrades to do as well. In going to these new clients, we did have the additional software that was installed as part of the process, but our TSM consultant sad the reboot didn't have to be performed, even though it asked for one. As a TSM vet but a newbie to the AIX version, I took that at face value, and in moving some 100 clients didn't have to reboot any of them - they all worked with the new client and connecting to the new server. (Until this one, apparently.) We probably should have hired you instead! - - - - - - - - - - Kevin Kinder State of WV -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Prather, Wanda Sent: Friday, February 06, 2015 3:30 PM To: [email protected] Subject: Re: [ADSM-L] Duplicate include/exclude option error Oh, that is weird. If they only show up once in q inclexcl, you shouldn't be getting that error. Perchance is there a reboot pending since you did the upgrade? (she asked, grasping for straws...) Wanda Prather TSM Consultant ICF International Enterprise and Cybersecurity Systems Division -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Kinder, Kevin P Sent: Friday, February 06, 2015 3:22 PM To: [email protected] Subject: Re: [ADSM-L] Duplicate include/exclude option error Thanks for the reply Wanda. We don't use option sets, but I checked to make sure, it is blank. No apparent conflicts when running q inclecxl, which I had done. This dsm.opt worked in the past on this server, and the problem only started when I upgraded the client version. I am guessing something else changed as a result of that, but there were no changes made to the dsm.opt file, so it must be something in the way the 6.3.2.2 client reacts to this version of Win2k3. I have similar excludes running on other Win2k3 servers with the same client, so I'm comparing the results on those with these to see if there are any differences. I may have to dive into the registry? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Prather, Wanda Sent: Friday, February 06, 2015 2:22 PM To: [email protected] Subject: Re: [ADSM-L] Duplicate include/exclude option error Perhaps someone put these into a client option set? Q NODE nodename F=D Look for "optionset:" If it's non=blank, then you need to investigate the contents of the optionset, that's where your conflict is coming from. If that is not revealing, from the client machine: start the command line version of the client enter: q inclexcl The output shows you all the excludes, including any that come from the server and any that come from the Microsoft settings in the registry, as well as the ones in your opt file. Wanda Prather TSM Consultant ICF International Enterprise and Cybersecurity Systems Division -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Kinder, Kevin P Sent: Friday, February 06, 2015 2:10 PM To: [email protected] Subject: [ADSM-L] Duplicate include/exclude option error TSM Client 6.3.2.2 Windows Server 2003 R2 64bit I have the following include\exclude statements: EXCLUDE "E:\Interfaces\NLXjobs\WV_NLXjobs.xml" EXCLUDE "E:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\*.mdf" EXCLUDE "E:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\*.ldf" EXCLUDE "E:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\*.ndf" EXCLUDE "F:\MACCWV\MACCWV_log.ldf" EXCLUDE "F:\Workspace\Workspace_log.ldf" EXCLUDE "F:\Migration2\Migration2_log.ldf" EXCLUDE "G:\MACCWV\MACCWV_data.mdf" EXCLUDE "G:\MACCWV\MACCWV_indexes.ndf" EXCLUDE "G:\Workspace\Workspace_data.mdf" EXCLUDE "G:\Migration2\Migration2_data.mdf" EXCLUDE.DIR "*:\RECYCLER" EXCLUDE.DIR "G:\TestRestore" I am getting the following errors: 02/05/2015 03:12:56 ANS1496W Duplicate include/exclude option 'EXCLUDE F:\MACCWV\MACCWV_log.ldf' found while processing the client options file. This might produce unexpected results. 02/05/2015 03:12:56 ANS1496W Duplicate include/exclude option 'EXCLUDE F:\Migration2\Migration2_log.ldf' found while processing the client options file. This might produce unexpected results. 02/05/2015 03:12:56 ANS1496W Duplicate include/exclude option 'EXCLUDE F:\Workspace\Workspace_log.ldf' found while processing the client options file. This might produce unexpected results. 02/05/2015 03:12:56 ANS1496W Duplicate include/exclude option 'EXCLUDE G:\MACCWV\MACCWV_data.mdf' found while processing the client options file. This might produce unexpected results. 02/05/2015 03:12:56 ANS1496W Duplicate include/exclude option 'EXCLUDE G:\MACCWV\MACCWV_indexes.ndf' found while processing the client options file. This might produce unexpected results. 02/05/2015 03:12:56 ANS1496W Duplicate include/exclude option 'EXCLUDE G:\Migration2\Migration2_data.mdf' found while processing the client options file. This might produce unexpected results. 02/05/2015 03:12:56 ANS1496W Duplicate include/exclude option 'EXCLUDE G:\Workspace\Workspace_data.mdf' found while processing the client options file. This might produce unexpected results. I can't see where the errors are in my dsm.opt file. This is on a two-server cluster, but I don't think that has anything to do with the issue. I have resaved the options file and stopped and started the TSM Scheduler service via the Cluster Administrator, but it still produces the same errors. Any ideas? - - - - - - - - - - Kevin Kinder State of WV
