Hi Karsten!
That's not how TDP backups should be handled. TDP for SAP backups (which are
indeed archives) should expire only when the archive file is deleted by the TDP
client. The client should be in control.
Kind regards,
Eric van Loon
AF/KLM Storage Engineering
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Karsten Pilz
Sent: vrijdag 22 mei 2015 22:20
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Removing obsolete TDP for MySAP files from TSM
Hello Eric,
Normally such a tool should not be required for TDP MySAP.
TDP Oracle stores files as backup which will not become inactive since every
filename is unique. TDP MySAP is doing archive, so files should expire
corresponding to the policy you defined.
Cheers,
Karsten
Am 22.05.2015 um 10:54 schrieb Loon, EJ van (ITOPT3) - KLM:
> 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
> ********************************************************
********************************************************
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
********************************************************
|
