You also want to look if the client has a lot of individual files to see if they are a candidate for journaling. The TSM database for the client can grow large very fast.
Bob Martoncik Lucas County Information Services 419-213-4633 >>> [EMAIL PROTECTED] 5/30/2006 10:13 AM >>> We retain all backups for 30 days by setting VEREXISTS and VERDELETED to NOLIMIT and RETONLY and RETEXTRA to 30. David >>> [EMAIL PROTECTED] 5/30/2006 9:38:40 AM >>> Has anyone heard of or every set there TSM file version retention polices to 30 days across all clients? Traditionally number of versions retained has been specific to the application, data type and the business need to be able to retain versions. We have a TSM server we are evaluating for a client and they have about 500 clients of all different applications and databases that they are setting these 30 days of version retention. I want to be able to counsel them correctly, so I'm looking for feedback. If this is a standard practice or something that isn't unusual, then I would want to approach this from the TSM server and resources, if this is a poor practice, of course I would want to point them in the right direction. My opinion is that this is a poor practice and the policies should be tailored to the business requirements of the department and application. Any opinions or recommendations would be greatly appreciated. Thanks, Ken.