You're on the right track... 1. VE/VD/RE/RO parms would be */*/42/42 -- that gives you point-in-time restore for any file over the past 6 weeks; do the math, and monitor the actual usage -- most shops experience less than 10% turnover per work-day, we did our sizing based on 5% (even that was abit on the high side). Using these parameters gives you exactly what you have today, without re-sending files that don't change (using the "standard" progressive incremental backup in TSM)... and you'll save over 90% of tape real estate in the process!
2. Monthly backup sets, with two year retention; this gives you the monthly snapshot of all "active" versions -- again, exactly matches your current situation -- and, again, without sending the data over the network. Hope this helps. Don France Technical Architect - Tivoli Storage Manager Professional Association of Contract Employees (P.A.C.E.) San Jose, CA mailto:[EMAIL PROTECTED] ----- Original Message ----- From: "Ken Long" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, March 17, 2002 5:21 PM Subject: versioning for user's files > Hello all... > > We're migrating our NetWare servers, currently backed up with ArcServe, to > W2K servers which will be backed up with TSM. These NetWare servers > contain programs, users' home directories, and shared directories. > > The existing NetWare server backup is a full backup every day, all to one > DLT tape. The number of tapes in rotation provides for going about six > weeks, or 30 backups, before a tape is reused. Also, at the end of each > month the tape is removed from the rotation and held for two years. > > My challenge is to provide a reasonable level of backup availability with > TSM. All I've backed up with TSM thus far are application servers where > users (other than administrators) don't have access. We keep 7 versions on > those servers. > > Our NetWare users sometimes ask for restores of files more than a year old, > and their requests have been fulfilled. I'm struggling to come up with a > version scheme which will provide a similar level of service. > > It seems a bit extreme, but my first thought is to keep 30 versions and do > a monthly backupset of the W2K file server. But that 30 versions is having > a nasty effect on calculations of the resulting TSM database size. > > What kind of versioning do you set for user files, shared documents, etc., > which are, in my mind, more volatile than application server files because > users are involved? Any examples of the model you use would be > appreciated. > > Thanks... Ken
