Overwrite of catalog during/after system copy possible?

[former_member184680]

Hi,

we use backint for the backup of our HANA databases. For a system copy, you have to use the parameter files of the source database in the target database to recover the catalog/data/logs.

Is it possible, that the target database overwrite the catalog of the source database because of using the parameter files for recovery?

If yes, is there a best practice for this behaviour?

br

Patrick

[jgleichmann · Accepted solution]

Hi Patrick,

there is no official best practice for this backup/recovery scenario with 3rd party tools. If your third party tool can't restrict write access to the backup destination, you can disable log backups via backint (they will be written to disk) or disable automatically log backups at all for the time of the recovery procedure. But normally you stop the DB directly after the successful recovery procedure and reconfig the backup destinations.

But to answer your question, yes the DB can (if not restricted by third party tool) write to the destination. On the other hand no, the backup catalog of the origin/source DB can't be overwritten, because another EBID (external backup ID) is used. What can happen is if the new DB is the last one which writes to the backup destination and a system failure takes place, the recovery procedure will use the latest backup catalog except otherwise specified. The backup catalog can be manually recreated as long as you have all backup data in access.

Regards,

Jens

[lbreddemann]

I’m not sure what you refer to with “catalog”, so I assume it’s the backup catalog.

When restoring a database backup to another system than that’s a system copy. The correct procedure, including how to handle configuration files, is described in the SAP HANA Administration Guide and the technical operations guide.