Lynn,

I think the problem here is the exclude list.
Excluded files are not eligible for backup, hence the expiration.
The file retention characteristics, number of versions etc, applies to actions
on the client,
so if you delete a file on the client it becomes inactive, and any expiration on
the TSM server will follow according to the the management  class retention for
inactive files.
What do you mean by full incremental, just the normal backup, if file attributes
changed or are you saying that the upgrade itself forces a new backup of every
file not specifically excluded.
This is not something I would not  expect although I am not yet at 4.1.

John






LYNN HAMILTON <LYNN.HAMILTON AT SELECTIVE DOT COM> on 03/23/2001 02:08:00 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: John Naylor/HAV/SSE)
Subject:  Expiration Problem - Upgrade to TSM v.4.1.2.0



--- Received from SIG.HAMILTL LYNN HAMILTON                  03/23/01  908a
Our ADSM server is running on an MVS OS/390 mainframe.  Our ADSM clients
Our ADSM server is running on an MVS OS/390 mainframe.  Our ADSM clients
are Novell file servers (Netware OS v.4.11 and 4.2).  We are upgrading our
ADSM server from ADSM v.3.1.2.50 to TSM v.4.1.2.0 and we are upgrading our
Novell clients from ADSM v.3.1.0.6 to TSM v.4.1.2.0.

Most of our Novell clients are located at remote locations.  Because the
upgrade involves a full incremental we have to find a way to minimize the
upgrade time, otherwise a full incremental over the WAN could take several
weeks.  We thought that we would exclude (in the dsm.opt file) a large
population of directories and files during the upgrade.

During the first test upgrade, we saw massive expiration of objects on our
Novell clients.  We noticed that the files that were expiring were bound to
a management class backup copy group that is defined to keep all versions
of active files forever (no limit) and to keep only the last 2 versions on
deleted files.  So, we updated the management class backup copy group to
keep all versions of active and deleted files forever (no limit).
We re-ran the upgrade and still the files continue to expire.

Any helpful hints on this would be most appreciated.

Thanks,
Lynn Hamilton
Selective Insurance
lynn.hamilton AT selective DOT com

---- 03/23/01  908a ---- Sent to       ------------------------------------
  -> ADSM-L AT VM.MARIST DOT EDU
  -> ADSM-L AT VM.MARIST DOT EDU






**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric and Southern Electric are trading names of
Scottish and Southern Energy Group.
**********************************************************************