Hi Eric,

The number of versions to keep is controlled by the
MAX_VERSIONS profile parameter. A backup generation consists of
one full database backup and associated partial/incremental and
redo log backups (no matter how many this may be).

If you used the MAX_VERSIONS profile parameter for all backups
that you ran, then the deletions should happen transparently.
You can use the backfm utility to view all data that is stored
in TSM. By pressing 'F6' you can see additional information for
each backup, including the version number.

If a backup was performed without the MAX_VERSIONS profile parameter,
then this backup is considered to be under some other policy and will
NOT be deleted by the MAX_VERSIONS processing. Such a backup would be
shown by the backfm utility with version number 0.
Backups that are under TSM ERP version control will have a number > 0.

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 05/22/2015
04:54:46 AM:

> From: "Loon, EJ van (ITOPT3) - KLM" <Eric-van.Loon AT KLM DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 05/22/2015 04:56 AM
> Subject: Removing obsolete TDP for MySAP files from TSM
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Hi TSM-ers! (or should I say ISP-ers since the product will be
> renamed in the near future?)!
> We are using TDP for MySAP to back-up our SAP databases. For several
> clients I see that files are left behind in TSM which no longer
> exist in the SAP repository.
> When you backup Oracle by using TDP for Oracle you have a tool
> called tdposync which compares the RMAN catalog with TSM and it
> allows you to delete files from TSM which are not in RMAN. How does
> this work in TDP for MySAP?
> Thank you very much for any help in advance!
> Kind regards,
> Eric van Loon
> AF/KLM Storage Engineering
> ********************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee
> only. If you are not the addressee, you are notified that no part of
> the e-mail or any attachment may be disclosed, copied or
> distributed, and that any other action related to this e-mail or
> attachment is strictly prohibited, and may be unlawful. If you have
> received this e-mail by error, please notify the sender immediately
> by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/
> or its employees shall not be liable for the incorrect or incomplete
> transmission of this e-mail or any attachments, nor responsible for
> any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> Dutch Airlines) is registered in Amstelveen, The Netherlands, with
> registered number 33014286
> ********************************************************
>