[prev in list] [next in list] [prev in thread] [next in thread] 

List:       adsm-l
Subject:    Re: TSM 5.3.2 Version Retention Policy
From:       Bob Martoncik <BMartoncik () CO ! LUCAS ! OH ! US>
Date:       2006-05-30 15:47:33
Message-ID: s47c30dc.073 () co ! lucas ! oh ! us
[Download RAW message or body]

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

>>> deehre01@LOUISVILLE.EDU 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

>>> Kenneth.Bradberry@ACS-HCS.COM 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.
[prev in list] [next in list] [prev in thread] [next in thread]