Hyperscaler independent versioning of cloud storage objects
AssigneeSap SE
InventorsMartin Brunzema, Henrik Hempelmann, Benedikt Klus, Anne Roessiger, Stefan Voss
Life of this patent
Estimating the term…
Abstract
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.
Claims18
A system comprising:
- a memory storing processor-executable program code;
- and
- a processor to execute the processor-executable code in order to cause the system 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 by the backup service, a versioned backup having a filename including a version identifier;
- transmit the versioned backup created by the backup service to multiple different hyperscalers, each having a respective cloud object storage, each of the multiple different hyperscalers:
- storing the transmitted versioned backup in its respective cloud object storage;
- using the filename of the versioned backup as an object key for the storage of the versioned backup created by the backup service in its respective cloud object storage;
- and
- being configured to provide a respective versioning for the versioned backup, each respective versioning of each of the multiple different hyperscalers being independent of the respective versionings of the remainder of the multiple different hyperscalers.
A computer-implemented method, the method comprising:
- receiving, by a backup service layer of a database service instance, a request to create a data backup;
- creating, in response to the request and by the backup service, a versioned backup having a filename including a version identifier;
- and
- transmitting the versioned backup created by the backup service to multiple different hyperscalers, each having a respective cloud object storage, each of the multiple different hyperscalers:
- storing the transmitted versioned backup in its respective cloud object storage;
- using the filename of the versioned backup as an object key for the storage of the versioned backup created by the backup service in its respective cloud object storage;
- and
- being configured to provide a respective versioning for the versioned backup, each respective versioning of each of the multiple different hyperscalers being independent of the respective versionings of the remainder of the multiple different hyperscalers.
A non-transitory, computer readable medium storing instructions, which when executed by at least one processor cause a computer to perform a method comprising:
- receiving, by a backup service layer of a database service instance, a request to create a data backup;
- creating, in response to the request and created by the backup service, a versioned backup having a filename including a version identifier;
- and
- transmitting the versioned backup created by the backup service to multiple different hyperscalers, each having a respective cloud object storage, each of the multiple different hyperscalers:
- storing the transmitted versioned backup in its respective cloud object storage;
- using the filename of the versioned backup as an object key for the storage of the versioned backup created by the backup service in its respective cloud object storage;
- and
- being configured to provide a respective versioning for the versioned backup, each respective versioning of each of the multiple different hyperscalers being independent of the respective versionings of the remainder of the multiple different hyperscalers.
Dependencies are inferred from the claim text.