US 12,117,907 B2
Data replication using an extended file replication protocol
Nitin Madan, Cupertino, CA (US); Bhimsen Bhanjois, Fremont, CA (US); Kalyan C. Gunda, Bangalore (IN); Srisailendra Yallapragada, Cupertino, CA (US); Alok Katiyar, Santa Clara, CA (US); Salil Dangi, Mission Viejo, CA (US); and Sanjay Vedanthan, Santa Clara, CA (US)
Assigned to DELL PRODUCTS L.P., Round Rock, TX (US)
Filed by Dell Products L.P., Round Rock, TX (US)
Filed on Apr. 29, 2022, as Appl. No. 17/733,550.
Prior Publication US 2023/0350765 A1, Nov. 2, 2023
Int. Cl. G06F 16/182 (2019.01); G06F 11/14 (2006.01)
CPC G06F 11/1464 (2013.01) [G06F 11/1451 (2013.01); G06F 11/1469 (2013.01); G06F 16/184 (2019.01); G06F 2201/80 (2013.01)] 15 Claims
OG exemplary drawing
 
1. A computer-implemented method of replicating synthetic data backup across namespaces, the method comprising:
in response to receiving a file replication request, cloning by a processor, one or more source files from a first namespace to a second namespace, as one or more destination files;
creating, by the processor, a first attribute indicating that the one or more source files have been cloned to the second namespace as the one or more destination files;
cloning, by the processor, one or more source synthetic files from the first namespace to the second namespace, as one or more destination synthetic files, wherein each source synthetic file of the one or more source synthetic files includes at least one data segment from a source file and incremental data associated with the source file, and respective synthetic information of the one or more destination synthetic files respectively point to the one or more source files as one or more base files on the first namespace;
creating, by the processor, a second attribute indicating that the one or more source synthetic files have been cloned to the second namespace as the one or more destination synthetic files; and
based on the first and second attributes, updating by the processor, the respective synthetic information of the one or more destination synthetic files to respectively point to the one or more destination files as one or more base files on the second namespace, wherein each destination synthetic file of the one or more destination synthetic files includes at least one data segment from a destination file and incremental data associated with the destination file;
wherein the updating the respective synthetic information of the one or more destination synthetic files comprises changing one or more base file parameters in the respective synthetic information of the one or more destination synthetic files to respectively point to the one or more destination files.