US 11,917,003 B2
Container runtime image management across the cloud
Richard Spillane, Palo Alto, CA (US); Yunshan Luke Lu, San Jose, CA (US); Wenguang Wang, Palo Alto, CA (US); Maxime Austruy, Lausanne (CH); Christos Karamanolis, Los Gatos, CA (US); and Rawlinson Rivera, Van Nuys, CA (US)
Assigned to VMware, Inc., Palo Alto, CA (US)
Filed by VMware LLC, Palo Alto, CA (US)
Filed on Oct. 2, 2020, as Appl. No. 17/062,411.
Application 17/062,411 is a continuation of application No. 15/191,228, filed on Jun. 23, 2016, granted, now 10,812,582.
Claims priority of provisional application 62/306,416, filed on Mar. 10, 2016.
Prior Publication US 2021/0075855 A1, Mar. 11, 2021
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 16/00 (2019.01); H04L 67/1095 (2022.01); G06F 9/455 (2018.01); G06F 16/11 (2019.01); G06F 16/178 (2019.01)
CPC H04L 67/1095 (2013.01) [G06F 9/45558 (2013.01); G06F 16/128 (2019.01); G06F 16/178 (2019.01); G06F 2009/4557 (2013.01); G06F 2009/45562 (2013.01); G06F 2009/45595 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computerized method for migrating changes to an application to a secondary cluster from a primary cluster, said method comprising:
sending, from the secondary cluster to the primary cluster, a list of files, wherein the list of files is for use in deduplication, wherein the primary cluster and the secondary cluster respectively operate volumes associated with the application on different file systems;
receiving, on the secondary cluster from the primary cluster, a deduplicated file that is generated on the primary cluster against the list of files received from the secondary cluster, the deduplicated file including data blocks that have changed in a volume on the primary cluster, a parent universally unique identifier (UUID) of the changed data blocks, and dedup UUIDs that identify data in other deduplicated files available in the secondary cluster, the parent UUID identifying a parent storage device that is hosting the changed data blocks;
identifying, on the secondary cluster, the parent UUID and the changed data blocks in the received deduplicated file;
determining, based on the identified parent UUID, that the changed data blocks have not been applied to a volume stored on the secondary cluster;
creating a clone volume of the volume stored on the secondary cluster;
applying the changed data blocks to the clone volume of the volume stored on the secondary cluster;
verifying whether the other deduplicated files identified by the dedup UUIDs are available in the secondary cluster; and
upon verification that the other deduplicated files identified by the dedup UUIDs are available in the secondary cluster, mounting the deduplicated file on the clone volume of the volume stored on the secondary cluster.