US 11,947,809 B2
Data management system
Arvind Jain, Los Altos, CA (US); Arvind Nithrakashyap, San Francisco, CA (US); Bipul Sinha, Foster City, CA (US); Soham Mazumdar, San Francisco, CA (US); Adam Gee, San Francisco, CA (US); Kenny To, Santa Clara, CA (US); and Jonathan Derryberry, San Jose, CA (US)
Assigned to Rubrik, Inc., Palo Alto, CA (US)
Filed by Rubrik, Inc., Palo Alto, CA (US)
Filed on Apr. 14, 2022, as Appl. No. 17/721,240.
Application 17/721,240 is a continuation of application No. 16/813,020, filed on Mar. 9, 2020, granted, now 11,354,046.
Application 16/813,020 is a continuation of application No. 16/270,586, filed on Feb. 7, 2019, granted, now 11,079,941, issued on Aug. 3, 2021.
Application 16/270,586 is a continuation of application No. 15/804,382, filed on Nov. 6, 2017, granted, now 10,678,448, issued on Jun. 9, 2020.
Application 15/804,382 is a continuation of application No. 14/628,001, filed on Feb. 20, 2015, granted, now 10,241,691, issued on Mar. 26, 2019.
Application 16/270,586 is a continuation of application No. 14/628,001, filed on Feb. 20, 2015, granted, now 10,241,691, issued on Mar. 26, 2019.
Claims priority of provisional application 62/075,112, filed on Nov. 4, 2014.
Prior Publication US 2022/0244864 A1, Aug. 4, 2022
Int. Cl. G06F 16/00 (2019.01); G06F 3/06 (2006.01); G06F 9/455 (2018.01); G06F 9/50 (2006.01); G06F 11/14 (2006.01); G06F 16/11 (2019.01); G06F 16/13 (2019.01); G06F 16/14 (2019.01); G06F 16/27 (2019.01); G06F 16/84 (2019.01); H04L 9/32 (2006.01); H04L 43/0817 (2022.01); H04L 61/5007 (2022.01); H04L 61/5061 (2022.01); H04L 67/10 (2022.01); G06F 11/20 (2006.01)
CPC G06F 3/0619 (2013.01) [G06F 3/0641 (2013.01); G06F 3/065 (2013.01); G06F 3/0665 (2013.01); G06F 3/067 (2013.01); G06F 3/0685 (2013.01); G06F 9/45558 (2013.01); G06F 9/5077 (2013.01); G06F 11/1435 (2013.01); G06F 11/1446 (2013.01); G06F 11/1448 (2013.01); G06F 11/1451 (2013.01); G06F 11/1458 (2013.01); G06F 16/113 (2019.01); G06F 16/128 (2019.01); G06F 16/13 (2019.01); G06F 16/148 (2019.01); G06F 16/27 (2019.01); G06F 16/84 (2019.01); H04L 9/3242 (2013.01); H04L 9/3247 (2013.01); H04L 43/0817 (2013.01); H04L 61/5007 (2022.05); H04L 61/5061 (2022.05); H04L 67/10 (2013.01); G06F 2009/45562 (2013.01); G06F 2009/4557 (2013.01); G06F 2009/45579 (2013.01); G06F 2009/45583 (2013.01); G06F 11/1453 (2013.01); G06F 11/1461 (2013.01); G06F 11/1464 (2013.01); G06F 11/1484 (2013.01); G06F 11/202 (2013.01); G06F 2201/80 (2013.01); G06F 2201/815 (2013.01); G06F 2201/84 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method for operating a data management system, comprising:
acquiring, from a primary system, a full snapshot of a virtual machine of the primary system, the full snapshot corresponding with a first state of the virtual machine at a first point in time;
acquiring, from the primary system, one or more incremental snapshots of the virtual machine, the one or more incremental snapshots corresponding with one or more states of the virtual machine at one or more points in time different from the first point in time;
generating, at the data management system, a directly mountable version of the virtual machine corresponding to a point in time associated with at least one of the full snapshot or one of the one or more incremental snapshots;
receiving, at the data management system, a request to mount the directly mountable version of the virtual machine; and
causing the primary system to directly mount the directly mountable version of the virtual machine from the data management system to allow the primary system to read, from the data management system, data associated with the directly mountable version of the virtual machine maintained at the data management system, modify, at the data management system, the data associated with the directly mountable version of the virtual machine maintained at the data management system, or both.