ADSM-L

Re: Management Class and TDP for R/3

2002-12-11 15:34:21
Subject: Re: Management Class and TDP for R/3
From: "Davidson, Becky" <Becky.Davidson AT SLBG DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 11 Dec 2002 14:17:14 -0600
For my SAP systems I have 4 management classes
<SID>_saplog1
<SID>_saplog2
<SID>_sapincr
<SID>_cold  <----this is for tsm cold backups and restores.  I also use the
TSM expiration but we have been thinking about using TDP versioning but it
is one of those don't fix what isn't broken.  TDP uses the archive copy
group and not the backup copy group so all you have to worry about is Retain
Version.  I group the SID's by type so I have all of my DV's going to
dv_saplog1 and same with TT (technical test), CN (consolidation), and PR
(production).  For versioning I believe it is 9999 or at least beyond what
the latest possible the versioning would expire.  We do most of our stuff
for 18 days so my retv=18 for most systems.
Becky

-----Original Message-----
From: brian welsh [mailto:brianwelsh3 AT HOTMAIL DOT COM]
Sent: Wednesday, December 11, 2002 2:06 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Management Class and TDP for R/3


Hello,

Server AIX 5.1, TSM 4.2.2.8. Client AIX 4.3, TSM 4.2.1.25, and TDP for R/3
3.2.0.11 (Oracle)

Question about TDP.

We wanted to use the Management Class on the TSM-server like this:
Versions Data Exists            NOLIMIT
Versions Data Deleted           3
Retain Extra Versions           21
Retain Only Version             30

In the Guide Tivoli Data Protection for R/3 Installation & User's Guide for
Oracle is mentioned to define 4 different Management Classes. I was
wondering how other people have defined there Management Classes. Support
told me to use 4 different Management Classes because it's in the manual so
they mention something with it (maybe for in the future), but what is the
advantage of 4 different Management Classes. We have 8 TDP-clients. The
manual is saying every client his own 4 different Management Classes. It's
not easy to manage that way.

Besides you have to define an archive-copy group. We don't want to use
Versioning in TDP, but use expiration via TSM-client/server. How many days I
have to define the archive-copy group. I think it has to be 21 days. I guess
that when using Versioning in TDP you have to set these parameter on 9999.
Am I right.

Is there somebody who want to share the definitons used for TDP for
Management Classes and Copy Groups?

Thanx,

Brian.





_________________________________________________________________
Chatten met je online vrienden via MSN Messenger. http://messenger.msn.nl/