US 12,287,758 B2
Snapshot and restoration of distributed file system
Vijay Karthik, Sunnyvale, CA (US); Anshul Gupta, Mountain View, CA (US); Abhay Mitra, Santa Clara, CA (US); Vivek Sanjay Jain, Palo Alto, CA (US); and Satwant Rana, Mountain View, CA (US)
Assigned to Rubrik, Inc., Palo Alto, CA (US)
Filed by Rubrik, Inc., Palo Alto, CA (US)
Filed on Apr. 26, 2024, as Appl. No. 18/648,223.
Application 18/648,223 is a continuation of application No. 17/363,694, filed on Jun. 30, 2021, granted, now 12,001,392.
Claims priority of provisional application 63/053,146, filed on Jul. 17, 2020.
Prior Publication US 2024/0289302 A1, Aug. 29, 2024
Int. Cl. G06F 16/11 (2019.01); G06F 16/16 (2019.01); G06F 16/174 (2019.01); G06F 16/182 (2019.01)
CPC G06F 16/128 (2019.01) [G06F 16/164 (2019.01); G06F 16/1752 (2019.01); G06F 16/1844 (2019.01)] 20 Claims
OG exemplary drawing
 
1. A method comprising:
storing a file-to-chunk mapping in file system metadata, wherein the file-to-chunk mapping maps a file of a distributed file system to a first set of data chunks and a first file system generation identifier (ID) associated with a first time at which a first snapshot of the distributed file system was obtained;
detecting, after the first time, a trigger event that indicates that the first snapshot is set to expire; and
deleting, based at least in part on the trigger event, a second set of data chunks from the distributed file system based at least in part on the trigger event and further based at least in part on the second set of data chunks being associated with the first file system generation ID and being excluded from the file-to-chunk mapping in the file system metadata, wherein the first set of data chunks remain in the distributed file system after the first snapshot expires based at least in part on the first set of data chunks being included in the file-to-chunk mapping in the file system metadata.