US 11,809,280 B2
Synchronizing expirations for incremental backup data stored on a cloud-based object storage
Shelesh Chopra, Bangalore (IN); Sunil Yadav, Bangalore (IN); Amarendra Behera, Bangalore (IN); Ravi Vijayakumar Chitloor, Bengaluru (IN); Tushar Dethe, Bangalore (IN); Himanshu Arora, Bangalore (IN); Prabhat Kumar Dubey, Chikkanagamangala (IN); Jigar Bhanushali, Bengaluru (IN); and Deependra Singh, Kanpur (IN)
Assigned to EMC IP Holding Company LLC, Hopkinton, MA (US)
Filed by EMC IP Holding Company LLC, Hopkinton, MA (US)
Filed on Mar. 5, 2021, as Appl. No. 17/193,919.
Prior Publication US 2022/0283904 A1, Sep. 8, 2022
Int. Cl. G06F 11/14 (2006.01)
CPC G06F 11/1451 (2013.01) [G06F 11/1461 (2013.01); G06F 11/1464 (2013.01); G06F 2201/80 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A system comprising:
one or more processors; and
a non-transitory computer-readable medium storing a plurality of instructions, which when executed, cause the one or more processors to:
perform a first backup of client data stored on a client device at a first point-in-time to a cloud-based object storage, the first backup including storing the client data within a first set of objects on the object storage and storing metadata associated with the first backup in a metadata database, the metadata including an expiration time for each object in the first set of objects and a list of objects required to perform a full recovery to the first point-in-time;
perform a second backup of the client data stored on the client device at a second point-in-time to the object storage, the client data stored on the client device at the second point-in-time including at least some of the client data already stored within the first set objects and new client data stored on the client device since the first point-in-time, the second backup including storing the new client data within a second set of objects on the object storage and storing metadata associated with the second backup in the metadata database, the metadata including an expiration time for each object in the second set of objects and a list of objects required to perform a full recovery to the second point-in-time;
identify, amongst the first set of objects, a third set of objects storing at least a portion of the client data stored on the client device at the second point-in-time by comparing the list of objects required to perform a full recovery for a first point-in-time and for a second point-in-time stored in the metadata database, in response to the performance of the second backup;
determine whether a first expiration time specified by metadata associated the objects identified in the third set of objects is prior to a second expiration time specified by metadata associated with the second set of objects; and
update the metadata associated with each of the objects identified in the third set of objects from the first expiration time to the second expiration time in the metadata database, in response to determining the first expiration time is prior to the second expiration time.