Your INCLUDE statement doesn't do anything except maybe bind the c:\adsm.sys *directories* (not files, which are not backed up) to SPECIAL.
To bind system object or system state to a different management class, see the INCLUDE.SYSTEMOBJECT or INCLUDE.SYSTEMSTATE options. You are otherwise correct, including and excluding the exact same pattern isn't a good idea. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.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 2005-11-30 07:58:35: > Hi, we use > > "include c:\adsm.sys\...* special" to assign a managent class to system > objects. Is this (still) correct? > > I think include and exclude to the same directory isn't a good idea. > > Regards > Stefan Holzwarth > > _____ > > From: ADSM: Dist Stor Manager on behalf of Andrew Raibeck > Sent: Tue 29.11.2005 19:46 > To: [email protected] > Subject: Re: WMI backup failure - return code 3029 > > > > > Is it safe to say that the C:\adsm.sys directory can be safely excluded > > from all Windows backups? > > Yes. What the exclude does is exclude it from the backup of your C: drive. > But C:\adsm.sys is still backed up as a part of the system object or > system state backup. > > Note that in version 5.3, TSM automatically excludes this directory. > > I believe that the 5.2.4 client uses exclude c:\adsm.sys\...\*, so the > failures you see are probably on subdirectories of adsm.sys, not files. In > 5.3, this has been changed to exclude.dir c:\adsm.sys. > > Run the "dsmc query inclexcl" command to see how the adsm.sys dir is > currently excluded. > > Regards, > > Andy > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Development > Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] > Internet e-mail: [EMAIL PROTECTED] > > IBM Tivoli Storage Manager support web page: > http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan > ager.html > <http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMa > nager.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 2005-11-29 > 11:17:20: > > > Question regarding this proposed solution: > > > > Is it safe to say that the C:\adsm.sys directory can be safely excluded > > from all Windows backups? > > > > I've had many repetitive failures of that directory in various clients > > (mainly Win2K3), but the directory exists in other windows versions. I > > just went ahead and added the exclusion to my windows cloptset and the > > failures have stopped. > > > > Thanks for your help. > > > > Sergio > > > > U. of Maryland > > Office of Information Technology > > > > Andrew Raibeck wrote: > > > Hmmmm.... > > > > > > Try doing the following: > > > > > > 1) Delete the existing c:\adsm.sys directory structure. > > > > > > 2) Add the following to the client options: > > > > > > exclude.dir c:\adsm.sys > > > > > > 3) Retry the system object backup. > > > > > > Regards, > > > > > > Andy > > > > > > Andy Raibeck > > > IBM Software Group > > > Tivoli Storage Manager Client Development > > > Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] > > > Internet e-mail: [EMAIL PROTECTED] > > > > > > IBM Tivoli Storage Manager support web page: > > > http://www-306.ibm <http://www-306.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 2005-11-29 > > > 07:09:04: > > > > > > > > >>Hi *SMers, > > >> > > >>Client - TSM 5.2.4.4 on a W2K SP4 server. > > >>Server - TSM 5.2.4.5 on a W2K SP4 server. > > >> > > >>I'm experiencing a regular backup failure of the system objects and > the > > >>information returned to me from TSM is not really directing me towards > a > > >>cause. > > >> > > >>Dsmerror.log contains: > > >>11/29/2005 13:34:08 ANS1487E Backing up WMI repository failed. No > files > > >>will be backed up. > > >>11/29/2005 13:34:14 Return code 3029 unknown > > >>11/29/2005 13:34:14 Unknown system error > > >>Please check the TSM Error Log for any additional information > > >> > > >>Dsmsched.log has less.. > > >> > > >>Is there any documentation anywhere which brings some kind of meaning > to > > >>"Return code 3029 unknown". > > >> > > >>Any assistance greatly appreciated. > > >> > > >>Regards > > >>Matthew > > >> > > >>TSM Consultant > > >>ADMIN ITI > > >>Rabobank International > > >>1 Queenhithe, London > > >>EC4V 3RL > > >> > > >> > > >>_____________________________________________________________ > > >> > > >>This email (including any attachments to it) is confidential, > > >>legally privileged, subject to copyright and is sent for the > > >>personal attention of the intended recipient only. If you have > > >>received this email in error, please advise us immediately and > > >>delete it. You are notified that disclosing, copying, distributing > > >>or taking any action in reliance on the contents of this information > > >>is strictly prohibited. Although we have taken reasonable > > >>precautions to ensure no viruses are present in this email, we > > >>cannot accept responsibility for any loss or damage arising from the > > >>viruses in this email or attachments. We exclude any liability for > > >>the content of this email, or for the consequences of any actions > > >>taken on the basis of the information provided in this email or its > > >>attachments, unless that information is subsequently confirmed in > > >>writing. If this email contains an offer, that should be considered > > >>as an invitation to treat. > > >>_____________________________________________________________
