ADSM-L

Re: [ADSM-L]

2009-04-29 16:41:46
Subject: Re: [ADSM-L]
From: Dwight Cook <cookde AT COX DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 29 Apr 2009 15:40:20 -0500
Can I add a comment...
What if you have some form of file system corruption from anything and the
file appears to have changed, TSM backs up the corrupt version and purges
off the old copy???
If the files are as you say and never change, you won't have any inactive
versions as long as active versions exist and if a file is accidentally
deleted you would want some time to recover...

In looking at your current settings, from a business point of view, they are
very sound and (if the files are as you say) you will only have one copy of
the data, until something is deleted and then you will have 60 days to
figure out someone incorrectly deleted a file and recover it.

Again, if those files never change, your existing config will only have a
single copy of the data... the current/active version.

Dwight

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Bell, Charles (Chip)
Sent: Wednesday, April 29, 2009 2:55 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L]

I have a copygroup set up for a domain that is strictly a bunch of nodes for
a document imaging application, millions of files each. I am going to change
the backups from the incremental-forever to image backups. Also, I am going
to change the retention to where I would only keep the active copy of each,
and that's it. I don't want any inactive copies, and I don't want to keep
them around for ANY amount of time, only the active. Reason being, the files
in those NTFS file systems never change, and they are only archives.



Here is the current config

Versions Data Exists        2

Versions Data Deleted   1

Retain Extra Versions     30

Retain Only Version        60



Based on my comments above, would that need to be?:

Versions Data Exists        1

Versions Data Deleted   0

Retain Extra Versions     0

Retain Only Version        0



Please help...This is one of the parts I hate about TSM. I know it's
probably
simple, but I never can seem to remember what each retention parameter (as
shown above) MEANS!  J

God bless you!!!

Chip Bell
Network Engineer I
IBM Tivoli Certified Deployment Professional (ITSM)
Baptist Health System
Birmingham, AL

<Prev in Thread] Current Thread [Next in Thread>