US 12,086,116 B2
Object and sequence number management
Ananthan Subramanian, San Ramon, CA (US); Sridevi Jantli, San Jose, CA (US); Anil Paul Thoppil, Sunnyvale, CA (US); Cheryl Marie Thompson, Sunnyvale, CA (US); and Qinghua Zheng, San Jose, CA (US)
Assigned to NetApp, Inc., San Jose, CA (US)
Filed by NetApp Inc., San Jose, CA (US)
Filed on Oct. 31, 2022, as Appl. No. 17/976,946.
Application 17/976,946 is a continuation of application No. 16/751,766, filed on Jan. 24, 2020, granted, now 11,487,723.
Application 16/751,766 is a continuation of application No. 15/581,447, filed on Apr. 28, 2017, granted, now 10,552,389, issued on Feb. 4, 2020.
Prior Publication US 2023/0052732 A1, Feb. 16, 2023
Int. Cl. G06F 16/00 (2019.01); G06F 16/215 (2019.01); G06F 16/22 (2019.01); G06F 16/23 (2019.01)
CPC G06F 16/215 (2019.01) [G06F 16/22 (2019.01); G06F 16/2379 (2019.01)] 20 Claims
OG exemplary drawing
 
1. A method, comprising:
storing data of a volume into an object within a remote object store, wherein an object name is assigned to the object based upon a volume identifier of the volume stored within a storage system external to the remote object store;
for each object name within a list of object names of objects stored within the remote object store:
in response to determining that the object name of the object matches the volume identifier within a list of volume identifiers of volumes stored within the storage system external to the remote object store, designating the object as a valid object storing the data of the volume having the volume identifier; and
in response to determining that the object name does not match at least one volume identifier within the list of volume identifiers, designating the object as an orphan object that stores stale data no longer referenced by the volumes; and
deleting the orphan object from the remote object store to reclaim storage space consumed by the orphan object.