[prev in list] [next in list] [prev in thread] [next in thread] 

List:       adsm-l
Subject:    Re: Removing obsolete TDP for MySAP files from TSM
From:       "Loon, EJ van (ITOPT3) - KLM" <Eric-van.Loon () KLM ! COM>
Date:       2015-05-27 12:59:12
Message-ID: EA6C033452BF5F4A842F51A0D404E5F62D94C25C () KL126R4B ! cs ! ad ! klmcorp ! net
[Download RAW message or body]

Hi Karsten!
That's not how TDP backups should be handled. TDP for SAP backups (which ar=
e indeed archives) should expire only when the archive file is deleted by t=
he 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@VM.MARIST.EDU] On Behalf Of Ka=
rsten Pilz
Sent: vrijdag 22 mei 2015 22:20
To: ADSM-L@VM.MARIST.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 ever=
y filename is unique. TDP MySAP is doing archive, so files should expire co=
rresponding 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 clie=
nts I see that files are left behind in TSM which no longer exist in the SA=
P repository.
> When you backup Oracle by using TDP for Oracle you have a tool called tdp=
osync 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://w=
ww.klm.com. This e-mail and any attachment may contain confidential and pri=
vileged material intended for the addressee only. If you are not the addres=
see, you are notified that no part of the e-mail or any attachment may be d=
isclosed, copied or distributed, and that any other action related to this =
e-mail or attachment is strictly prohibited, and may be unlawful. If you ha=
ve received this e-mail by error, please notify the sender immediately by r=
eturn 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 receip=
t.
> 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 privi=
leged material intended for the addressee only. If you are not the addresse=
e, you are notified that no part of the e-mail or any attachment may be dis=
closed, 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 ret=
urn e-mail, and delete this message. =


Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its e=
mployees shall not be liable for the incorrect or incomplete transmission o=
f this e-mail or any attachments, nor responsible for any delay in receipt. =

Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Air=
lines) is registered in Amstelveen, The Netherlands, with registered number=
 33014286
********************************************************
		=09
[prev in list] [next in list] [prev in thread] [next in thread]