Uhmmm, Lawrie, I don't think you will get what you want...
Look at TSM as a big file cabinet with copies of files from other servers.
A file in TSM is "ACTIVE" if it is the way it looked on the client during
the last incremental (or selective)
A file in TSM in "INACTIVE" if it isn't the way it looked on the client
during the last incr/sel (which includes having been deleted from the
client)
Now, Versions Data Exists says how many copies of that file is kept in the
TSM file cabinet as long as it still exists on the client.
Versions Data Deleted says how many copies to immediately reduce down to as
soon as the file is found to have been deleted from the client.
Retain Extra says how long to keep INACTIVE copies (from the time they go
inactive)
Retain Only says how long to keep the LAST copy of a file that has been
deleted from a client
If you want to keep no more than 7 days you will need
A) Versions Data Exists of 7 so if a file changes daily, you will have 7
on the 8th day the 1st day's copy will expire due to VDE 7
B) Retain Extra 7 so if a file only changes weekly,
VDE won't expire because on day 8 you will only have 2 copies
BUT the old copy will be 8 days old and will go away due to RE 7
C) Versions Data Deleted 7, to always have at least 7 copies/days
D) Retain Only 30 to keep the last copy of a deleted file for 30 days (past
its deletion)
Personally I always make my Versions Data Deleted greater than one BECAUSE
what if a disk is going bad and nobody notices.
Say on night one is hoses up some of a file that is viewed as a change to
that file ??? So TSM backs it up resulting in the active copy being bad...
Now more errors on the disk make the file totally go away, a backup runs,
and the file is marked deleted and during expiration TSM cuts down to the
last copy, that BAD one made the night before ! ! ! YIKES !!!
Personally I use VDE-7, VDD-3, RE-35, RO-95 which has kept the user
community pretty happy over the years
Dwight
-----Original Message-----
From: Lawrie Scott - Persetel Q Vector
[mailto:LawrieS AT COMPAREXAFRICA.CO DOT ZA]
Sent: Wednesday, December 18, 2002 4:22 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Expiring Data / Versioning
Hi All
Thanx in advance, new to this and not sure I've set this up correctly.
I originally wanted to keep 7 versions and delete after 30 days any deleted
files.
I run TSM Server 5.1 and I'm trying to expire all my data down to only one
copy of the data. My versions were set to 7 and the rest as shown, I changed
it down to 3 and ran an inventory expire this made no changes. Have I setup
my copy group incorrectly. I wish to finally setup the copy group to have
seven days(not versions) backups and to only keep deleted files for a max of
30 days.
Copy Group Name STANDARD
Versions Data Exists 3
Versions Data Deleted 1
Retain Extra Versions 0
Retain Only Version 30
Copy Mode MODIFIED
Copy Serialization DYNAMIC
Copy Frequency 0
Kind Regards
LAWRIE SCOTT
For:
Persetel/Q Vector KZN
Company Registration Number: 1993/003683/07
Tel: +27 (0) 31 5609222
Fax: +27 (0) 31 5609495
Cell: +27 (0) 835568488
E-mail: lawries AT comparexafrica.co DOT za
Notice: This message and any attachments are confidential and intended
solely for the addressee. If any have received this message in error, please
notify Lawrie Scott at Comparex Africa (Pty) Ltd immediately, telephone
number +27 (0) 31 5609222. Any unauthorised use, alteration or dissemination
is prohibited. Comparex Africa (Pty) Ltd accepts no liability whatsoever for
any loss whether it be direct, indirect or consequential, arising from
information made available and actions resulting there from.
|
