Eric, You can bind the database backups to any management class you would like. That is described in the User's Guide. Here is an example:
INCLUDE \...\db1\...\* MC_9DAYS INCLUDE \...\db2\...\* MC_14DAYS INCLUDE \...\db3\...\* MC_28DAYS INCLUDE \...\db4\...\* MC_168DAYS Take a look at Appendix C in the User's Guide for exact details on INCLUDE/EXCLUDE statements. Thanks, Del ---------------------------------------------------- > Our SQL Server department is currently migrating to SQL Server 2000 and thus > they are going to use DP for SQL Server 5.2.1 instead of TDP for SQL Server > 1.1.2. > With 1.1.2 they were able to control retention through the ADSMAUTODELETE > command, but since 5.2.1 uses TSM policy retention management that's no > longer possible. > The problem (or challenge?) is that they have several databases on one node > with all their own retention requirements, varying from 9 days to 168 days. > Just storing all data for 168 days would be the easiest solution, but one of > the short retention databases is 20 Gb. so the impact on the TSM storage > would be significant. > Does anybody have a simple solution to use the 5.2.1 client in such an > environment?
