Just make "non-default" management classes with the archive retentions you
need... then have the user archive to a management class that fits their
needs for long term storage... Below are the management classes I've
defined for one of my domains, each management class directs the data to a
specific storage pool and/or keeps it for a unique period of time (based on
how the data is stored, backup or archive)
example
tsm: TSMSRV03>q mgmt sap active
Policy Policy Mgmt Default Description
Domain Set Name Class Mgmt
Name Name Class ?
--------- --------- --------- --------- ------------------------
SAP ACTIVE 10YRARCH No 10 year archive, two
copies
SAP ACTIVE AMOCO_DE- Yes Sap default mgmtclass
FAULT
SAP ACTIVE ARCHLOG10 No DB redo log 10 day
retention
SAP ACTIVE ARCHLOG1- No DB redo log 185 day
85 retention
SAP ACTIVE ARCHLOG35 No DB redo log 35 day
retention
SAP ACTIVE ARCHLOG95 No DB redo log 95 day
retention
SAP ACTIVE B7.3_R35- No std w/ 10 day arch
.95_A10
SAP ACTIVE B7.3_R35- No Std w/ 10 day arch into
.95_A10- prpool
_PR
SAP ACTIVE B7.3_R35- No Used by SAP prod utility
.95_A185 servers
SAP ACTIVE B7.3_R35- No Used by SAP prod
.95_A18-
5_PR
SAP ACTIVE B7.3_R35- No std w/ 30 day arch
.95_A30
SAP ACTIVE B7.3_R35- No Std w/ 30 day arch into
.95_A30- prpool
_PR
SAP ACTIVE B7.3_R35- No Sap mgmt vere=7 verd=3
.95_A35 rete=35 reto=95 a=35
SAP ACTIVE B7.3_R35- No Sap mgmt vere=7 verd=3
.95_A35- rete=35 reto=95 a=35
_PR
SAP ACTIVE B7.3_R35- No Used by SAP prod utility
.95_A370 servers
SAP ACTIVE B7.3_R35- No Used by SAP prod
.95_A37-
0_PR
SAP ACTIVE B7.3_R35- No Sap mgmt vere=7 verd=3
.95_A60 rete=35 reto=95 a=60
SAP ACTIVE B7.3_R35- No Sap mgmt vere=7 verd=3
.95_A60- rete=35 reto=95 a=60
_PR
SAP ACTIVE B7.3_R35- No Used by SAP prod utility
.95_A740 servers
SAP ACTIVE B7.3_R35- No Used by SAP prod
.95_A74-
0_PR
SAP ACTIVE B7.3_R35- No 8 Day archive for PF
.95_A8_- backups
PF
SAP ACTIVE B7.3_R35- No Used by SAP prod utility
.95_A95 servers
SAP ACTIVE B7.3_R35- No Used by SAP prod
.95_A95-
_PR
-----Original Message-----
From: MC Matt Cooper (2838) [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 07, 2001 8:29 AM
To: [EMAIL PROTECTED]
Subject: Seven year retention issue
Hello all,
I have TSM 4.1 on OS390. My issue is keeping a copy of 'some data'
from an AIX platform for seven years. My difficulties arise from the fact
that the Policy that this server is on has the Archive group retention set
to 1 day. This has to be this way because the server also has DB2 which
writes journals to the archive pool, and I have no choice about it. It
appears to be the way the DB2 api works. So I am not sure what options I
really have and what would be "best practice'. I know this data will not be
the only request that I will receive for a long retention isolated request.
Any ideas are truly welcome.
Matt
