expire log backup info

[Former Member]

Looking at m_backup_catalog* views for a monitoring solution for backups I realized that there is no way to expire backup information from the catalog.

After approx 6 months of use I see 60K entries in m_backup_catalog, most of course log backups. With a scale out solution this would be multiplied with amount of hosts AFAIR, and could reach a million+ log backups a year.

Is there truly no expiration command for backup history, or a parameter? Reading through sql guide, backup guide, admin guide and monitoring views guide among others I see nothing on that subject. Perhaps I'm just missing something obvious and there is a way to expire backup info.

[lbreddemann]

Hi Robert,

nice to see you're active in the HANA field 🙂

Right now (that is SPS4) there is no supported way to shorten the backup history/catalog.

But afaik there will likelyl be an official feature for that in later versions.

For now, this doesn't pose any problem and should this turn out to become one with larger scale-out systems running OLTP traffic, then this will of course be changed.

BTW: you reported roughly 10K catalog entries per month and node.

For a 5 node cluster - that means it'll take 20 months to reach the million lines.

And if it does - so what?

cheers,

Lars