Object storage for guaranteed content for backup and retention
AssigneeEMC IP Holding Company LLC
InventorsAssaf Natanzon, Jehuda Shemer, Kfir Wolfson
Life of this patent
Estimating the term…
Abstract
Systems, apparatus and methods for managing an object's lifecycle in an object store. A distributed ledger is used to record transactions between a client and an object store. The distributed ledger records the transaction and also attests to the object authenticity. Thus, the transactions can be verified and may assist in resolving issues that arise with respect to the stored objects.
Claims17
A method for protecting data stored in an object storage, the method comprising:
- performing a transaction with an object to the object storage by a client with regard to an object;
- recording a transaction in a ledger for the object by the client such that the ledger attests to the transaction and to the object, wherein the transaction includes an action performed on the object and an identifier of the object;
- receiving an acknowledgement from the object store, wherein the acknowledgement indicates that an identifier of the object generated by the object store matches the identifier of the object provided by the client;
- logging the acknowledgement from the object store in the ledger, wherein the transaction further comprises an agreement that is accepted by the object storage or by a provider of the object storage when the acknowledgement is logged and wherein the agreement specifies a penalty;
- receiving a delete request to delete the object into the ledger from the client, wherein deletions are included in the agreement;
- servicing the delete request by the object store by deleting the object, wherein the identifier in the ledger and associated with the delete request ensures that the object store understood which object to delete;
- and
- automatically performing the penalty when the agreement is broken.
A method for writing an object to a cloud object storage, the method comprising:
- writing the object to the cloud object storage by a client;
- recording a transaction in a ledger reflecting that the object was written to the cloud object storage, wherein the transaction attests that the object was written to the cloud object storage and includes an identifier of the object and is associated with an agreement that specifies an availability of the object;
- receiving an acknowledgement from the object store, wherein the acknowledgement indicates that an identifier of the object generated by the object store matches the identifier of the object provided by the client and wherein the acknowledgement constitutes acceptance of the agreement;
- receiving a delete request to delete the object into the ledger from the client, wherein deletions are included in the agreement;
- servicing the delete request by the object store by deleting the object, wherein the identifier in the ledger and associated with the delete request ensures that the object store understood which objects to delete;
- and
- enforcing the agreement by applying a penalty when determining that the agreement regarding the object is broken.
A non-transitory computer readable medium comprising instructions that, when executed by a processor, perform a method comprising:
- performing a transaction with an object to the object storage by a client with regard to an object;
- recording a transaction in a ledger for the object by the client such that the ledger attests to the transaction and to the object, wherein the transaction includes an action performed on the object and an identifier of the object;
- receiving an acknowledgement from the object store, wherein the acknowledgement indicates that an identifier of the object generated by the object store matches the identifier of the object provided by the client;
- logging the acknowledgement from the object store in the ledger, wherein the transaction further comprises an agreement that is accepted by the object storage or by a provider of the object storage when the acknowledgement is logged and wherein the agreement specifies a penalty;
- receiving a delete request to delete the object into the ledger from the client, wherein deletions are included in the agreement;
- servicing the delete request by the object store by deleting the object, wherein the identifier in the ledger and associated with the delete request ensures that the object store understood which object to delete;
- and
- automatically performing the penalty when the agreement is broken.
Dependencies are inferred from the claim text.