Techniques for maintaining file consistency during file system cross-region replication
Novel techniques are described for maintaining file consistency between different cloud infrastructure regions during cross-region file storage replication. The novel techniques comprise upon detecting a file deletion status (i.e., a file directory entry version marked as deletion) in a source file system during a replication cycle, retrieving file name from a valid file directory entry of a prior snapshot to construct a temporary file directory entry containing necessary information for a target file system to reconstruct a duplicate file directory entry version marked as deletion. The temporary file directory entry is transferred from the source file system to the target file system during the same replication cycle.
1 . A method, comprising:
identifying, by a computing system, a file directory entry without a file deletion status in a snapshot of a source file system being replicated to a target file system;
in accordance with identifying the file directory entry without the file deletion status in the snapshot, generating, by the computing system, a temporary file directory entry based at least in part on the identified file directory entry without the file deletion status; and
transferring, by the computing system, the temporary file directory entry from the source file system to the target file system.
2 . The method of claim 1 , wherein a source file directory entry of a first snapshot containing a first file deletion status has an encrypted file name associated with a file that is part of the replication to the target file system.
3 . The method of claim 2 , wherein the temporary file directory entry has a plain text file name associated with the file, and wherein the plain text file name is obtained by decrypting an encrypted file name in the identified file directory entry without the file deletion status in the snapshot.
4 . The method of claim 2 , further comprising creating a target file directory entry with a file deletion status by the target file system based on the temporary file directory entry.
5 . The method of claim 4 , wherein the target file directory entry is a duplicate of the source file directory entry of the first snapshot containing a file deletion status.
6 . The method of claim 4 , further comprising extending the first file deletion status in the target file directory entry with a second file deletion status in the target file system until another file directory entry without file deletion status is received by the target file system during the file replication.
7 . The method of claim 1 , wherein transferring the temporary file directory entry from the source file system to the target file system occurs during a same replication cycle.
8 . The method of claim 1 , wherein the source file system and the target file system are in different cloud infrastructure data centers.
9 . A non-transitory computer-readable medium storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:
identifying, by a computing system, a file directory entry without a file deletion status in a snapshot of a source file system being replicated to a target file system;
in accordance with identifying the file directory entry without the file deletion status in the snapshot, generating, by the computing system, a temporary file directory entry based at least in part on the identified file directory entry without the file deletion status; and
transferring, by the computing system, the temporary file directory entry from the source file system to the target file system.
10 . The non-transitory computer-readable medium of claim 9 , wherein a source file directory entry of a first snapshot containing a first file deletion status has an encrypted file name associated with a file that is part of the replication to the target file system.
11 . The non-transitory computer-readable medium of claim 10 , wherein the temporary file directory entry has a plain text file name associated with the file, and wherein the plain text file name is obtained by decrypting an encrypted file name in the identified file directory entry without the file deletion status in the snapshot.
12 . The non-transitory computer-readable medium of claim 10 , further comprising creating a target file directory entry with a file deletion status by the target file system based on the temporary file directory entry.
13 . The non-transitory computer-readable medium of claim 9 , wherein transferring the temporary file directory entry from the source file system to the target file system occurs during a same replication cycle.
14 . The non-transitory computer-readable medium of claim 9 , wherein the source file system and the target file system are in different cloud infrastructure data centers.
15 . A computing system, comprising:
one or more processors; and
one or more non-transitory computer readable media storing computer-executable instructions that, when executed by the one or more processors, cause the system to perform operations comprising:
identifying, by the computing system, a file directory entry without a file deletion status in a snapshot of a source file system being replicated to a target file system;
in accordance with identifying the file directory entry without the file deletion status in the snapshot, generating, by the computing system, a temporary file directory entry based at least in part on the identified file directory entry without the file deletion status; and
transferring, by the computing system, the temporary file directory entry from the source file system to the target file system.
16 . The system of claim 15 , wherein a source file directory entry of a first snapshot containing a first file deletion status has an encrypted file name associated with a file that is part of the replication to the target file system.
17 . The system of claim 16 , wherein the temporary file directory entry has a plain text file name associated with the file, and wherein the plain text file name is obtained by decrypting an encrypted file name in the identified file directory entry without the file deletion status in the snapshot.
18 . The system of claim 16 , further comprising creating a target file directory entry with a file deletion status by the target file system based on the temporary file directory entry.
19 . The system of claim 18 , wherein the target file directory entry is a duplicate of the source file directory entry of the first snapshot containing a file deletion status.
20 . The system of claim 15 , wherein transferring the temporary file directory entry from the source file system to the target file system occurs during a same replication cycle.