I would simplify the discussion. With what you have set up, you can
guarantee to your users that you will be able to get any file back up to
seven days. That is, if a file changes everyday, you can get the most
recent seven changes. If the file stops changing, you might be able to get
a file back that was 30 days old if the original file is still on the system
and 60 days if it was deleted.
I think this is too complicated for most folks to understand (not us
brilliant TSMers, mind you, but the huddled masses yearning to be free). So
I would rather set my policy to something like 30, 30, 30, 30. That way,
with daily incrementals, I can say that I can get back any file for 30 days.
Period. I might change the retain only to some larger number but really, if
a file is deleted, how often does someone want it back after 30 days anyway.
This approach works up to 90, 90, 90, 90, but I think starts getting a bit
space hungry after that. If you have the need to retain data for longer,
consider doing an archive instead. And, no, you don't need to archive
everything. Get your people to understand what an archive is and what
should be archived. Then get that and only that!
BTW, overall, your statements are correct. However, I'm thinking your
end-user's eyes are going to glaze over when you try to tell them. Also,
there are some open files that TSM will not backup no matter the
serialization parameter so beware of that.
Thanks,
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (240) 539-7175
Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com
www.storserver.com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Mahesh Babbar
Sent: Wednesday, April 04, 2001 7:29 AM
To: [EMAIL PROTECTED]
Subject: Backup Policies - Kind of FAQs
Hi Gurus,
Just because I wanted to put all the queries on backup verions and
deletion at rest, I have drafted following Statements.
Would appreciate all yours commnents.
I have a Backup Copy Group parameters with the following values.
COPYGROUP_NAME: STANDARD
VEREXISTS: 7
VERDELETED: 7
RETEXTRA: 30
RETONLY: 60
MODE: MODIFIED
SERIALIZATION: DYNAMIC
FREQUENCY: 0
DESTINATION: DISKPOOL1
CHG_TIME: 2001-02-15 12:01:52.000000
CHG_ADMIN: ADMIN
PROFILE:
The backup is scheduled and performed daily incrementally. The
EXPIRE INVENTORY runs daily.
For the easy understanding of the new users, who daily bug me for
the status of their data, ( and even the admins) can I state
following with the Capital letters. It would clear some of my
doubts also.
1. No. of Versions of a file kept in the backup system = 7.
The oldest version shall expire on the arrival of the 8th version.
2. No. of Versions to be kept in the backup system after the file is
deleted from the client and then incremental backup is performed on
the filesystem containing that particular file = 7
3. A file backed up and not changed is called an ACTTIVE version and
remain there in the backup system FOREVER.
4. A file backed up, changed and then backed up again, in this case,
the previous version becomes INACTIVE and the latest version becomes
ACTIVE.
5. The day a file becomes INACTIVE, it gets deleted from backup
system after 30 Days.
6. A file backed up, deleted from the Client, and then incremental
backup is performed on the directory / filesystems containing that
file, this file would remain on the system for 60 Days.
7. If a filesystem is removed from the "Object List" of the schdule,
the filesystems remain doesn't get expired and always remain active.
8. Always INCRMENTAL backup shall be performed. ( Can any body point
out if the whole file goes to the backup system or only the DELTA).
9. A file shall be backed up even if it's open. CONSISTENCY of the
file is not guranteed in that case.
Please comment if I have missed something as far as users' perpective
is concerned.
Thanks & Regards
Mahesh
