Sap Se

Sap Ag

Henrik Hempelmann

Martin Brunzema

Torsten Strahl

Anne Roessiger

Stefan Voss

Andre Schefe

Robin Wissbrock

Bernd Vorsprach

Benedikt Klus

Uwe H O Hahn

Paul Beck

Kathrin Mao

Florian Geckeler

Daniel Kirmse

Martin Kittel

Uwe Hahn

Gerald Arnold

Christoph Bautz

Uwe HO Hahn

Techniques and solutions are provided to facilitate logging of computing processes. A computing process generates multiple log entries. A first portion of the multiple log entries are written to a first log. A second portion of the multiple log entries are written to the first log and to a second log, where the second portion is less than the first portion, such as being a proper subset of the first portion. Log entries can be determined to be written to the second log by scanning all or a portion of a log, by evaluating log entries as they are generated, or through computer code that causes log entries to be written to the second log. Typically, the second log is maintained for a longer period of time than the first log.

Differential logging of computing processes

A system to manage database management system backup objects may include an external storage component storing a first database management system backup object. A database management system node (e.g., associated with a database as a service cluster of a hyper-scalar infrastructure) may be configured to write information to and read information from the external storage component without being able to delete information in the external storage component. A backup housekeeping component, independent of the database management system node, may trigger a request to retrieve backup requirement information (e.g., associated with a maximum backup age, a latest backup identifier, an indication of a newest backup to be deleted, etc.) from the database management system node. The backup housekeeping component may then delete all database management system backup objects in the external storage component that are no longer required, including the first database management object, based on the retrieved backup requirement information.

Backup housekeeping operations between database management systems and external storage

A system and method providing monitoring of services hosted by a hyperscaler environment. The method including receiving an indication of at least one metric related to a backup storage process for each of a plurality of hyperscaler hosted database service instances; determining at least one value for each of the plurality of database service instances; storing a record of the determined at least one value for each of the plurality of database service instances in a persistent data storage device that is distinct and separate from the database service instances; receiving a request from a third-party entity for the stored at least one value for at least one of the plurality of database service instances; and transmitting the requested one or more of the at least one value for the database service instances specified in the request.

Current monitoring in hyperscaler environment

Some embodiments include a system, method, and non-transitory medium, with the system including a plurality of database services; and a stateless backup operator to perform a first mode for each database service to reconfigure a current backup state of each database service with an associated desired backup state information for the respective database service and the stateless backup operator to switch to and perform a second mode for a specific one of the plurality of database services in response to a request execute a first backup operation for the specific database service.

Multiple operation modes in backup operator

A system and method to create a plurality of hyperscaler accounts having predefined access rights to an object store of a database service in a cloud environment; store hyperscaler credentials specifying access rights to the object store corresponding to the predefined access rights of the hyperscaler accounts in a secure credential store, the hyperscaler credentials providing access to the object store for a specified backup function; map each of a plurality of different backup service component processes to one of the hyperscaler credentials, each of the plurality of backup service component processes operative independent of each other and having a specific backup service functionality; receive a request to execute one of the plurality of different backup service component processes; and authenticate access rights of the backup service component process included in the request based on the mapping.

Security by default in a cloud environment

According to some embodiments, a system to manage database management system backups may include a plurality of database services. For each database service, a database backup resource (e.g., a human-readable structured document) may specify desired backup state information (e.g., a buffer size, a schedule, an amount of memory, etc.). A stateless backup operator component may then compare a present backup state of each database service with the associated desired backup state information. When a mismatch is identified between the present backup state of a database service and the associated desired backup state information, that database service may be automatically reconfigured (e.g., in connection with a recover job, backup job, backup configuration job, keystore backup job, etc.) in accordance with the desired backup state information.

Database management system backup and recovery management

A system and method to receive, by a backup service layer of a database service instance, a request to create a data backup; create, in response to the request and internally of the backup service, a backup having a filename including a version identifier; and transmit the created backup to a hyperscaler to be stored in a cloud object storage of the hyperscaler, the filename of the backup being a key for the storage of the backup in the cloud object storage.

Hyperscaler independent versioning of cloud storage objects

A system and method to receive, from a database service executing on a cloud infrastructure, information indicating metrics regarding backups for the database service, the information including at least an indication of an age of a last complete backup for the database service, an indication of a size of changed data since the last complete backup, and an indication of a number of data units changed since the last complete backup; determine a type of backup strategy to instruct the database service to perform based on the received information, the type of backup strategy being one of a complete backup of the database service, a delta backup of the database service, and no backup of the database service; and issue, in response to the determination, an instruction to the database service to execute the determined type of backup.

Automatic backup strategy selection

A system and method to receive, by a database service from an encryption service of a database provider in a cloud environment, an encryption key passphrase stored in a secure storage separate and distinct from a database persistence and object store of the database service, the encryption key passphrase used as a key to encrypt and decrypt a key storage of the database service that stores one or more keys used by the database service; and to use the encryption key passphrase by a recovery service of the database provider in the cloud environment to recover the database service and its associated key storage.

Secure storage of anchor passphrase for DBMS

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 and method to receive, by a cloud infrastructure database service provider, a request for a new database service from an entity external to the cloud infrastructure, the request including an indication the requested database service is to be created using a master copy of a database service; create, in response to the request, a partially initialized database service and a recovery job to access a resource external to the cloud infrastructure; receive, by the partially initialized database service, a master copy of the requested database service from the external resource, the master copy including data content; and fully initialize the database service using at least some of the data content included in the master copy of the requested database service.

Database setup using a master 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, 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.

Growing community of inventors

Havelberg, Germany

Henrik Hempelmann