Sap Se

Andre Schefe

Robin Wissbrock

Torsten Strahl

Henrik Hempelmann

Martin Brunzema

Bernd Vorsprach

Hans-Georg Bumes

Mihnea Andrei

Norman May

Yong Sik Kwon

Jaeyoung Choi

Werner Thesing

Hyunjun Kim

Eunsang Kim

Stefan Voss

Ruediger Karl

Patrick Voelker

Jian Luo

Uwe Hahn

Urs Klingsporn

Systems and methods include reception of an instruction to recover a first database tenant of a first database instance to a first point in time, the first database tenant associated with first database artifacts of the first database instance, and the first database instance including two or more database tenants and, in response to the instruction, creation of a second database instance, selection of backup data of the first database instance based on the first point in time, execution of a recovery of the backup data on the second database instance, export of second database artifacts of the first database tenant from the second database instance to a storage, truncation of the first database artifacts from the first database instance, import of the second database artifacts from the storage to the first database instance, and deletion of the second database instance.

Tenant-level database recovery

The disclosure generally describes methods, software, and systems for performing automatic backups to the cloud. Application code in a database system updates rows and columns in the database for an updated object, and automatically performs a backup of database information to the cloud. Performing the backup includes directly executing a REST call to the cloud storage solution to which the backup of the database information is performed. Performing the backup includes: sending a request, using a REST call, to create a new object in the cloud storage solution; in response to receiving an acknowledgement of a successful creation of the new object, sending, to the cloud storage solution, REST PUT calls that include contents of the object for the cloud storage solution to store into the created new object; receiving, from the cloud storage solution, a specific key identifying the backup; and locally storing the specific key.

Object store for database backups

A system includes reception, at a target database system, of a request to recover a backup created by a source database system into the target database system, where the request comprises a system identifier of the source database system, determination of a backup tool configuration file associated with the source database system based on the system identifier of the source database system, request of a recovery of the backup into the target database system using the backup tool configuration file, copying of a backup catalog of the source database system into a storage location associated with the target database system, and appending of a system change marker to the copied backup catalog, wherein the system change marker comprises the system identifier of the source database system.

Database recovery after system copy

A system includes reception, at a target database system, of a request to recover a backup created by a source database system into the target database system, determination of a backup tool configuration file associated with the source database system, determination of a filepath of the backup, determination of a backup filepath associated with the target database system, and request of a recovery of the backup using the backup tool configuration file, wherein the request using the backup tool configuration file includes the filepath of the backup and the backup filepath associated with the target database system.

Database recovery using foreign backups

A system includes reception of a command to recover a database to a point in time, determining a log backup which covers the point in time, determination of a sequence identifier associated with the log backup, collection of log backups which are older than the determined log backup and associated with the sequence identifier, and a data backup associated with the sequence identifier, and execution of a recovery of the database based on the determined log backup and the collected log backups and data backup.

Recovery strategy with dynamic number of volumes

A method, medium, and system to receive a request to remove a service of an instance of a distributed database system; redistribute data of the service to be removed to at least one remaining service of the distributed database system; save unsaved log segments of the service to be removed in a log backup; register removal of the service to be removed with the distributed database system; delete an entry of the service to be removed from a startup configuration of the distributed database system; halt operation of the service to be removed; and remove the halted service from internal topology information of the distributed database system.

Method and system to remove a service from a distributed database system

A system includes obtaining of a backup of the source database system comprising N hosts and a first plurality of servers, where N is an integer greater than one, access of a target database system comprising M hosts, where M is an integer less than N, configuration of the target database system to include the first plurality of servers, and performance of a database recovery of the target database system using the backup of the source database system.

N to M host system copy

A method, medium, and system to receive a request to perform a log recovery to restore multiple database services; determine log backup entries corresponding to a target log position for a first database service of the multiple database services; read from a sequential stream device, by the first database service, the log backup entries corresponding to the target log position for the first database service; inform a second database service of the multiple database services that the first database service has concluded executing the log backup entries corresponding to the target log position for the first database service from the sequential stream device; assuring that no resources of the streaming device are blocked by the first database service; and read log backup entries of the second database service corresponding to a target log position for the second database service from the sequential stream device.

Growing community of inventors

Berlin, Germany

Andre Schefe