The real question is what is your business requirement? Forget what you
have done in the past for a moment and ask your customers what their
business recovery requirement is.
If they could recovery a file from forever ago and it changed once a
day there is a large cost to do that. Most customers will say they need
something for up to 3 years ago. We arbitrarily presume we can just save a
yearly or monthly tapes and get back what they want. Let's say they created
a file and worked on it for March 10th through March 25 and needed to keep a
backup of it for 3 years. Let's just say now you saved every full backup at
the beginning of every month. This file would be completely lost if it got
accidentally corrupted or deleted before April 1. So, who is the fool in
this scenario when it is discovered 3 years later.
TSM avoids all of this, you have a deleted file policy. You have
retention versions and a way to expire versions that get really old. But,
it always keeps the copy that matches the active backup on disk unless you
as an administrator delete the file space or expire directories you do not
want using an exclude.dir.
This all said. You probably are looking at time as being your
retention policy for inactive versions of a file. The only question is how
many versions of a file does a user think they need to go back to.
Remember, with TSM you can use different management classes for different
data on the same client and manage it differently.
So, to answer you more directly. Think about a very long deleted
file expiration time and a lower number of retain deleted versions. Think
about NOLIMIT (or large number)for the number of versions and a period of
time that reflects your recovery requirements. No matter what you come up
with if you use some kind of backupset type of thing you will lose a
customer's data eventually. It only saves a copy of the current active
data. You will need a copypool to send your data offsite with TSM, meaning
at least 2 tape drives and probably a lot more tapes, but the recovery
capability will be immearsurably improved.
-----Original Message-----
From: Ken Long [mailto:[EMAIL PROTECTED]]
Sent: Sunday, March 17, 2002 8:22 PM
To: [EMAIL PROTECTED]
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
