SCENARIO 1
ADSM SERVER V3.1.2.40 and TSM CLIENT 3.7

BACKUP COPY GROUP PARAMETERS:
      Policy Domain Name: NWSMPD
         Policy Set Name: ACTIVE
         Mgmt Class Name: NWSMMC
         Copy Group Name: STANDARD
         Copy Group Type: Backup
    Versions Data Exists: 3
   Versions Data Deleted: 1
   Retain Extra Versions: 30
     Retain Only Version: 60
               Copy Mode: Modified
      Copy Serialization: Shared Dynamic
          Copy Frequency: 0

I ran selective backups on a file and accumulated 5 copies. I ran the
expire inventory process with the assumption that
the first two copies of the file would be expired off the server. I then
used a select statement to query the number of versions
left on the server:
select node_name,ll_name,state,backup_date from adsm.backups where
node_name='PARAK' and ll_name='IRIDIUM.EXE'
The ouput looked like this:

NODE_NAME      LL_NAME                          STATE
           BACKUP_DATE
------------------        ------------------           
--------------------------------
   -----------------------------------------
   -----------------------------------------
PARAK               IRIDIUM.EXE           ACTIVE_VERSION
2000-03-16 10:22:49.000000
PARAK               IRIDIUM.EXE           INACTIVE_VERSION      2000-03-16
10:19:11.000000
PARAK               IRIDIUM.EXE           INACTIVE_VERSION      2000-03-16
10:19:53.000000
PARAK               IRIDIUM.EXE           INACTIVE_VERSION      2000-03-16
10:20:32.000000
PARAK               IRIDIUM.EXE           INACTIVE_VERSION      2000-03-16
10:22:28.000000

This tells me that ADSM will only expire the first inactive copy of the
file once it has reached the 30 day retention period,
irrespective of the Number of versions that can be stored on the server;
which in this case is 3. In other words; "Retain extra
versions" takes precedence over "Versions data exists". Is this right or
wrong?????????

SCENARIO 2
TSM SERVER 3.7 and TSM CLIENT 3.7

BACKUP COPY GROUP PARAMETERS:
      Policy Domain Name: NWSMPD
         Policy Set Name: ACTIVE
         Mgmt Class Name: NWSMMC
         Copy Group Name: STANDARD
         Copy Group Type: Backup
    Versions Data Exists: 3
   Versions Data Deleted: 1
   Retain Extra Versions: 30
     Retain Only Version: 60
               Copy Mode: Modified
      Copy Serialization: Shared Dynamic
          Copy Frequency: 0

I ran selective backups on a file and accumulated 5 copies. I then used a
select statement to query the number of versions
left on the server:
select node_name,ll_name,state,backup_date from adsm.backups where
node_name='PARAK' and ll_name='IRIDIUM.EXE'
The ouput looked like this:

NODE_NAME      LL_NAME                          STATE
           BACKUP_DATE
------------------        ------------------           
--------------------------------
   -----------------------------------------
   -----------------------------------------
PARAK               IRIDIUM.EXE           ACTIVE_VERSION
2000-03-16 10:22:49.000000
PARAK               IRIDIUM.EXE           INACTIVE_VERSION      2000-03-16
10:19:11.000000
PARAK               IRIDIUM.EXE           INACTIVE_VERSION      2000-03-16
10:19:53.000000
PARAK               IRIDIUM.EXE           INACTIVE_VERSION      2000-03-16
10:20:32.000000
PARAK               IRIDIUM.EXE           INACTIVE_VERSION      2000-03-16
10:22:28.000000

 I ran the expire inventory process with the SAME  assumption that the
first two copies of the file would be expired off the server.
RESULT OF SELECT STATEMENT:

NODE_NAME      LL_NAME                          STATE
           BACKUP_DATE
------------------        ------------------           
--------------------------------
   -----------------------------------------
   -----------------------------------------
PARAK               IRIDIUM.EXE           ACTIVE_VERSION
2000-03-16 10:20:26.000000
PARAK               IRIDIUM.EXE           INACTIVE_VERSION      2000-03-16
10:10:06.000000
PARAK               IRIDIUM.EXE           INACTIVE_VERSION      2000-03-16
10:19:53.000000

The first two inactive copies of the file was expired off the TSM server;
meaning that "Versions data exists" takes precedence
over "Retain extra versions". An inactive copy of a file will be kept for
30 days, unless the "Versions data exists" threshold(3)
has been reached, in which case the inactive copy will be expired off the
server.
Once again, is this right or wrong?????
I've come to the assumption that ADSM V3 and TSM V3.7 "COPY CONTROL
ALGORITHMS" works differently. If this is the case:
WHAT HAPPENS WHEN YOU UPGRADE FROM ADSM V3 to TSM V3?????

Can someone please agree or disagree(why?)!!!!!!!













  GOD Bless
   Clarence Beukes
   IT Specialist (ADSM/TSM)
   IBM Intergrated Technology Services
   Tel : +2711 302 5333   Fax : +2711 302 8209
   Mobile : +2782 573 5665

"A computer is almost human - except that it does not blame its mistakes on
another computer. "