Hi Eric, SAP did not release a change needed to do this within the API so the Spectrum Protect team will handle this directly.
Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 06/21/2017 04:26:33 AM: > From: "Loon, Eric van (ITOPT3) - KLM" <eric-van.l...@klm.com> > To: ADSM-L@VM.MARIST.EDU > Date: 06/21/2017 04:28 AM > Subject: Re: SAP HANA backup expiration > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > Hi Del! > Thank you very much for your explanation. I discovered that the > delete through HANA studio works as expected. I noticed however a > large amount of files in TSM which do no longer exist in HANA, so we > are working on a script to remove them too. I do not know how these > backups get stuck in TSM... > I really hope IBM will soon support versioning again, it would make > life much easier. The fact that you say IBM has plans to support it > in a future release, does that mean that SAP has removed/fixed the > HANA BACKINT API limitation? > Kind regards, > Eric van Loon > Air France/KLM Storage Engineering > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Del Hoobler > Sent: maandag 19 juni 2017 15:48 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: SAP HANA backup expiration > > Hi Eric, > > Once the backups have been deleted in HANA Studio, then HANA will > delay the actual deletion of the objects in Spectrum Protect. It is > not known or documented by SAP how long this delay may be or on what > it depends. We have seen a delay of several minutes. If you delete a > large number of objects, HANA will delete them in chunks of 500 objects. > > The actual deletion can be checked in the 'backint.log' file. After > some time there will be entries like this: > > BKI2003I: File R26___A0HZTF1HWY_RZ_TSM_SERVER@MC_DISK#160701 00000 > /usr/sap/R26/SYS/global/hdb/backint/2016_09_20_databackup_4_1 deleted. > #DELETED "R26___A0HZTF1HWY" > "/usr/sap/R26/SYS/global/hdb/backint/2016_09_20_databackup_4_1" > BKI2003I: File R26___A0HZTF1HWY_RZ_TSM_SERVER@MC_DISK#150700 00000 > /usr/sap/R26/SYS/global/hdb/backint/2016_09_20_databackup_2_1 deleted. > #DELETED "R26___A0HZTF1HWY" > "/usr/sap/R26/SYS/global/hdb/backint/2016_09_20_databackup_2_1" > BKI2003I: File R26___A0HZTF1HWY_RZ_TSM_SERVER@MC_DISK#140699 00000 > /usr/sap/R26/SYS/global/hdb/backint/2016_09_20_databackup_3_1 deleted. > #DELETED "R26___A0HZTF1HWY" > "/usr/sap/R26/SYS/global/hdb/backint/2016_09_20_databackup_3_1" > BKI2003I: File R26___A0HZTF1HWY_RZ_TSM_SERVER@MC_DISK#130698 00000 > /usr/sap/R26/SYS/global/hdb/backint/2016_09_20_databackup_1_1 deleted. > #DELETED "R26___A0HZTF1HWY" > "/usr/sap/R26/SYS/global/hdb/backint/2016_09_20_databackup_1_1" > > > IBM does plan to add support for expiration based on version limit > in a future delivery. > > > > Del > > > "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 06/19/2017 > 05:22:33 AM: > > > From: "Loon, Eric van (ITOPT3) - KLM" <eric-van.l...@klm.com> > > To: ADSM-L@VM.MARIST.EDU > > Date: 06/19/2017 05:23 AM > > Subject: SAP HANA backup expiration > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > > > Dear Del, > > About a year ago you explained why TDP for HANA backup versioning is > > no longer working (see your mail down below), do you know if SAP has > > fixed this issue by now? > > I'm still struggling with this in our environment. The only > > documentation I can find on the IBM site about this issue is > > IT11810. It contains two options: > > > > 1) Create a new domain and use the retver option, which could > > cause all you backups to expire when no backup is made during that > > period (so not acceptable for us). > > > > 2) Remove obsolete backup manually through SAP Studio. > > When we use option 2, the backups seem to be removed from SAP, but I > > still see the archive objects in TSM... Is this circumvention maybe > > documented somewhere in more detail? > > Thank you very much for your help in advance! > > Kind regards, > > Eric van Loon > > Air France/KLM Storage Engineering > > > > > > Eric, > > This "design change" is a "change" from the Data Protection for ERP > > perspective, but not from the Data Protection for ERP for SAP HANA > > perspective, which has always worked this way. > > This design "change" is a result of a current limitation in the SAP > > HANA BACKINT API and is expected to be temporary. This backup API > streams the > > backup data to the DP for SAP HANA client via named pipes and today > > it gives no indication whether the data stream was complete or the pipe > was > > closed prematurely due to some error. > > We don't want to expire a prior/older backup version unless we know > > we have a successful new backup version so we do not currently offer > > expiration of backups based on version limit. However, we do plan > > to provide that capability once SAP implements the enhancement to the > backup > > API we have requested (to indicate whether or not all the data was > > streamed successfully). SAP did indicate they plan to provide that > > enhancement but we do not yet have a target date for that. > > Thank you, > > Del > > ******************************************************** > > 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 > ******************************************************** >
