Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+SQL\s+mgmtclass\s+rules\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+SQL\s+mgmtclass\s+rules\s*$/: 2 ]

Total 2 documents matching your query.

1. [ADSM-L] SQL mgmtclass rules (score: 1): Author: "Schaub, Steve" <steve_schaub AT BCBST DOT COM>; Date: Tue, 9 Nov 2010 14:01:03 -0500; Tsm server 5.4.3.2 Tsm client 5.5.1.0 Tdp client 5.5.3.0 My mgmt classes for SQL tdp backups are: Verexist=nolimit Verdelete=nolimit Retextra=30 Retonly=90 I had thought that these settings would rol; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2010-11/msg00084.html (11,151 bytes)
2. Re: [ADSM-L] SQL mgmtclass rules (score: 1): Author: David McClelland <tsm AT NETWORKC.CO DOT UK>; Date: Tue, 09 Nov 2010 14:11:40 -0500; If your DBAs have gone ahead and deleted a database from the SQL Server end, TSM/TDP will never get a chance to inactivate the object and it will hang around forever as an 'active' object on the TSM; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2010-11/msg00085.html (12,252 bytes)

Current List: 1 - 2
Page: [1]