BUT tdp/r3 doesn't use the backup copy group of the management class, it
uses the "archive" copy group.
the reason for 4 (or more) is so if you go straight to a tape drive... like
this...
Storage      Device       Estimated    Pct    Pct  High  Low  Next Stora-
Pool Name    Class Name    Capacity   Util   Migr   Mig  Mig  ge Pool
                               (MB)                 Pct  Pct
-----------  ----------  ----------  -----  -----  ----  ---  -----------
PR3590A      3590B1A            0.0    0.0    0.0    90   70
PR3590B      3590B1A            0.0    0.0    0.0    90   70
PR3590C      3590B1A            0.0    0.0    0.0    90   70
PR3590D      3590B1A            0.0    0.0    0.0    90   70

Policy        Policy        Mgmt          Copy            Retain
Domain        Set Name      Class         Group          Version
Name                        Name          Name
---------     ---------     ---------     ---------     --------
SAP           ACTIVE        B7.3_R35-     STANDARD            10
                             .95_A10-
                             _PR_A
SAP           ACTIVE        B7.3_R35-     STANDARD            10
                             .95_A10-
                             _PR_B
SAP           ACTIVE        B7.3_R35-     STANDARD            10
                             .95_A10-
                             _PR_C
SAP           ACTIVE        B7.3_R35-     STANDARD            10
                             .95_A10-
                             _PR_D

then the copy destinations for each of the above mentioned management
classes goes to the corresponding storage pool listed above.
This is a test server, which is why there is no data in the storage pools
(in case anyone catches that)
Make as many different management class ~sets~ as you might ever want to
keep data for,
that is, I have a set for 10 days, one for 35 days, one for 185 days, 370
days, etc....

Dwight E. Cook
Software Application Engineer III
Science Applications International Corporation
509 S. Boston Ave.  Suite 220
Tulsa, Oklahoma 74103-4606
Office (918) 732-7109



-----Original Message-----
From: brian welsh [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 11, 2002 2:06 PM
To: [EMAIL PROTECTED]
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/

Reply via email to