TSM can be configured to keep a different # of versions for certain files.
A separate mgmt class can be created with the # of versions and files are
bound to it via the include/exclude list.  See the TSM doc.

-----Original Message-----
From: Randy Kreuziger [mailto:KREUZRSK AT DFW.WA DOT GOV]
Sent: August 8, 2003 9:59 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Large file backup strategies

We resently purchased a couple of sql server boxes for use in storing ESRI
GIS layers. This includes the storing of orthophotography images covering
our entire state. The orthos are stored in SQL Server with the initial load
creating a backup file 55 GBs in size. As we load more TIFs this backup file
will only grow.

According to the administrator of our  backups the policy governing this
machine is set to maintain 60 versions of a file. I thought this was over
kill before but with SQL Server backups that will approach 100GBs our backup
server will probably drown in orthophoto backups.

My administrator states that the system can not be configured to retain x
number of versions of one file type and y number of versions for all others
. Are there any work arounds so that I don't have 60 versions of .bak files
while retaining that number for all other files?

Thank you,
Randy Kreuziger
ArcSDE Administrator