CN114422533B - Method and device for processing path conflict in cloud backup and electronic equipment - Google Patents
Method and device for processing path conflict in cloud backup and electronic equipment Download PDFInfo
- Publication number
- CN114422533B CN114422533B CN202111641380.3A CN202111641380A CN114422533B CN 114422533 B CN114422533 B CN 114422533B CN 202111641380 A CN202111641380 A CN 202111641380A CN 114422533 B CN114422533 B CN 114422533B
- Authority
- CN
- China
- Prior art keywords
- server
- local
- file
- change data
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012545 processing Methods 0.000 title claims abstract description 51
- 238000000034 method Methods 0.000 title claims abstract description 34
- 230000008859 change Effects 0.000 claims abstract description 143
- 238000004590 computer program Methods 0.000 claims description 15
- 230000001360 synchronised effect Effects 0.000 claims description 8
- 230000008569 process Effects 0.000 claims description 5
- 238000003672 processing method Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000002124 flame ionisation detection Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a method for processing path conflict in cloud backup, which comprises the following steps: comparing the local file with the father table to determine local variation data, and comparing the father table with the server table to determine server variation data; determining whether the file or the folder with the same path is changed by a local server or/and a server according to the local change data and the server change data, and if so, determining that the path conflict exists; and according to the change type, performing deduplication operation on the file or folder with the path conflict. The technical scheme provided by the application can ensure the safety of data.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a method and an apparatus for processing a path conflict in cloud backup, a storage medium, and an electronic device.
Background
With the popularization of networks and intelligent terminals, a file cloud backup function has been developed. And cloud backup, namely, backing up user files (such as address book, short message, pictures, documents and other data) on a network in a cloud storage mode. How to ensure data security and data accuracy is always a technical problem that cloud backup is very concerned.
Disclosure of Invention
In view of this, the present application provides a method, an apparatus, a storage medium, and an electronic device for processing a path conflict in cloud backup, which mainly aims to improve the security of cloud backup data.
According to one aspect of the present application, a method for processing a path conflict in cloud backup is provided, where after downloading latest file data from a server to a local client, the method is used for processing the data conflict at the local client, and includes: comparing the local file with the father table to determine local variation data, and comparing the father table with the server table to determine server variation data; determining whether the file or the folder with the same path is changed by a local server or/and a server according to the local change data and the server change data, and if so, determining that the path conflict exists; and according to the change type, performing deduplication operation on the file or folder with the path conflict.
According to one aspect of the present application, there is provided a processing device for path conflict in cloud backup, configured to process, after downloading latest file data from a server to a local client, the data conflict at the local client, including: the change data determining unit is used for comparing the local file with the father table to determine local change data, and comparing the father table with the server table to determine server change data; the conflict determination unit is used for determining whether the files or folders with the same paths are changed by the local and/or server according to the local change data and the server change data, and if so, determining that the paths conflict; and the conflict processing unit is used for carrying out duplication removal operation on the files or folders with the paths conflicting according to the changing type.
According to an aspect of the present application, there is provided a storage medium having a computer program stored therein, wherein the computer program is configured to execute the above-described method for processing a path conflict in cloud backup at runtime.
According to an aspect of the present application, there is provided an electronic device comprising a memory, in which a computer program is stored, and a processor arranged to run the computer program to perform the above-mentioned method of handling path conflicts in cloud backup.
By means of the technical scheme, the processing method, the device, the storage medium and the electronic equipment for path conflict in cloud backup provided by the application, comparison and judgment of local change data and server change data determine that file change types are deleted, newly built files or folders, and duplicate removal processing is conducted on files or folders of the same path aiming at file change of different types. By adopting the technical scheme provided by the application, the security of the data of the cloud backup can be ensured.
The foregoing description is only an overview of the technical solutions of the present application, and may be implemented according to the content of the specification in order to make the technical means of the present application more clearly understood, and in order to make the above-mentioned and other objects, features and advantages of the present application more clearly understood, the following detailed description of the present application will be given.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
fig. 1 is a schematic implementation scenario of a method for processing path conflicts in cloud backup according to an embodiment of the present application;
fig. 2 illustrates an example flowchart of a method for processing a path conflict in cloud backup according to an embodiment of the present application;
FIG. 3 shows a file cloud backup flowchart provided in an embodiment of the present application;
fig. 4 illustrates an example two-flowchart of a method for processing a path conflict in cloud backup according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a processing device for path conflict in cloud backup according to an embodiment of the present application.
Detailed Description
In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other.
In practical applications, there is a possibility that data collision occurs. When conflict is handled, the existing software (APP) for file cloud backup often uses a server file to cover a local file or uses a local file to cover a server file, and does not carry out targeted handling on various conflict situations of real users. For users with the same ID, backup of files may be performed on different devices, and at this time, file conflicts may occur. For example, two persons a and b (sharing the same account ID) modify the file a at the same time at two PC ends, or one user a operates the file a at the same time or substantially at the same time at two PC ends, and at this time, the files are synchronized, and there must be one end where the file data arrives at the server first, and the other end where the file data arrives at the server later. In this case, many cloud backup software is implemented by using data that arrives at the server first at both PC ends. As a result, file data later reaching the server is lost, and thus the act of losing user data is likely to result in significant time and economic loss to the user.
The embodiment of the application provides a cloud backup path conflict processing method, which is characterized in that local change data and server change data are determined at a user client, and conflicts are judged and processed according to the two change data, so that whether the data of the current PC end of a user is reserved or server data is reserved or both data are reserved is selected, and the core purpose of the cloud backup path conflict processing method is to ensure that the data of the user are lost in any situation.
Referring to fig. 1, an implementation scenario schematic diagram of a cloud backup path conflict processing method provided in an embodiment of the present application is shown. The client side includes a plurality of clients (terminals), such as a client 1, a client 2, a client 3, and a client 4, and may specifically be a terminal such as a mobile phone, a computer, or a pad, and the server side includes at least one server. And the user performs file cloud backup operation through the file cloud backup APP on the client, and the server can be a server corresponding to the APP and stores the file in the cloud by responding to a user backup request.
Referring to fig. 2, a method for processing a conflict of a cloud backup path according to an embodiment of the present application is configured to process, at a local client, a data conflict after downloading latest file data from a server to the local client, and includes the following steps:
s201: comparing the local file with the father table to determine local variation data, and comparing the father table with the server table to determine server variation data;
s202: according to the local change data and the server change data, determining whether the files with the same path are changed by the local and/or server, if so, determining that the path conflict exists;
s203: and according to the change type, performing deduplication operation on the file or folder with the path conflict.
The terms involved are described as follows:
the FID (File ID), which is a unique identifier of the File backup to the cloud, is automatically generated at the server when the user uploads the File for the first time.
Server table (Server table): server data is delivered to a locally stored database table.
Parent table (Parent table): database tables after the last synchronization of the local file is completed.
Local data (Local data): local real file data.
Server change data (Server change): the server side changes the file newly.
Local change data (Localchange): newly added changes to the local file of the user.
In this embodiment of the present application, the path conflict refers to a conflict that, for files (FID are different) with the same path, the files are changed locally or by a server, and data inconsistency may be caused. In the implementation, the local change data is determined by comparing the local file with the father table, and the server change data is determined by comparing the father table with the server table; then, determining whether a path conflict exists by comparing the local variation data with the server variation data; finally, path conflicts are handled, e.g., selecting whether to hold local change data or server change data, or to hold all.
Referring to fig. 3, a file cloud backup flowchart provided in an embodiment of the present application is shown. The purpose of the file cloud backup flow is to lead out the path conflict processing method provided by the embodiment of the application.
The file cloud backup main flow is to download the latest data of the server to a local server table. And comparing the server table with the parent table which is synchronized last time, wherein the comparison result is the data (including the new file, the modified file and the deleted file) modified by the server side after the synchronization is completed last time. The local parent list is compared with the local file, and the comparison result is the data modified by the local file (including newly added, modified and deleted files) after the last synchronization is completed.
S301: judging whether full clear synchronization is completed, if yes, executing S302, otherwise, executing S303;
s302: resetting the delta time stamp, and emptying all Databases (DB); then S305 is performed;
s303: if the full synchronization is completed, executing S304, otherwise executing S306:
s304: resetting the increment time stamp and emptying the Server table;
s305: forcing the current synchronization to be fully synchronized;
s306: requesting an up-to-date list of the server;
s307: the latest list is put into a Server list;
s308: comparing the Local file with the Parent table to obtain Local Change data (Local Change);
s309: the Server table and the Parent table are paired to obtain Server change data (SeverChange)
S310: and processing a path conflict flow.
After comparing the local variation data (S308) and the server variation data (S309), it is necessary to combine the local variation and the server variation, that is, to process the data collision (S310). The normal synchronization process is performed without conflicting changes, and the embodiment of the present application focuses on the path conflict handling case (S310).
Path conflict processing, mainly aiming at files or folders with different FIDs and identical paths, is changed by a local or server, including but not limited to the following cases:
(1) The server is a newly added file, and the paths of the locally renamed files are the same.
(2) The local is the newly added file, and the renamed file paths of the server are the same.
(3) The server newly adds files, the paths of the local newly added files are the same, and two conditions of the same or different MD5 are further distinguished.
(4) The server is a newly added folder, and the local renamed file paths are the same.
(5) The file path is the same after the server modifies the file.
Referring to fig. 4, an example two-flowchart of a method for processing a cloud backup path conflict provided in the embodiment of the present application is shown, where the example provides a logic and a processing scheme for determining a path conflict.
S401: the path conflict processing flow is started.
S402: a processing branch is determined. For the processing procedure of the path conflict, three branches are further divided, the first branch (S403-S412) is the path conflict processing for the local change data and the server change data, the second branch (S413-S417) is for the server node without synchronization, and the third branch (S418-S421) is for the local file without synchronization.
S403: a first branch.
S404: discarding server change data when the change type is determined to be the deletion of a file or a folder by the server; then, S422 is executed, ending the path conflict processing flow.
S405: it is determined that the server is a new file or folder and that the local is also a new file or folder operation.
S406: judging whether the local variation data and the server variation data MD5 have the same value or not; if so, S407 is performed, otherwise S408 is performed.
S407: if the MD5 values are the same, discarding the local change data and the server change data, and updating the father table according to the server node; then, S422 is executed, ending the path conflict processing flow.
If the MD5 values are different, S408-S411 are performed.
S408: when the server is determined to be a newly-built folder and the local is a change type of the newly-built file, the server change data is stored unchanged, and the file of the local change data is renamed; then, S422 is executed, ending the path conflict processing flow.
S409: when it is determined that both the local and the server are new files and the local new file is empty, further executing S410;
s410: it is determined whether the same file identification FID file exists in the parent table as in the server change data, and if so, S411 is executed, otherwise S412 is executed.
S411: discarding the local variation data; then, S422 is executed, ending the path conflict processing flow.
S412: the server change data is saved and the file of the local change data is renamed; then, S422 is executed, ending the path conflict processing flow.
S413: and a second branch.
S414: and obtaining all the local files, and removing the files contained in the local change data to obtain the local files which do not need to be synchronized.
S415: and traversing server change data for the local files which do not need to be synchronized.
S416: discarding server change data and updating the father table file when determining that the server and the local are both newly added files or the change types of newly added folders; then, S422 is executed, ending the path conflict processing flow.
S417: when the server and the local are not the newly added files or the newly added folders, the server change data are stored unchanged, and the files or the folders of the local change data are renamed; then, S422 is executed, ending the path conflict processing flow.
S418: and a third branch.
S419: and obtaining all the nodes of the server, and eliminating the nodes contained in the server change data to obtain the server nodes without synchronization.
S420: and traversing the local variation data aiming at the server nodes which do not need to be synchronized.
S421: when the local and the server are determined to be the change types of the newly added files or folders, discarding the local change data and updating the father table; then, S422 is executed, ending the path conflict processing flow.
S422: and ending the path conflict processing flow.
According to the method for processing path conflict in cloud backup, the type of file change is determined to be deleted, newly built or a folder through comparison and judgment of the local change data and the server change data, and duplicate removal processing is conducted on files or folders of the same path aiming at file changes of different types. By adopting the technical scheme provided by the application, the security of the data of the cloud backup can be ensured.
Referring to fig. 5, a schematic structural diagram of a processing device for path conflict in cloud backup according to an embodiment of the present application is shown. The device can be located in a local client for processing data conflicts at the local client after downloading the latest file data from the server to the local client.
The apparatus may include a change data determination unit 501, a conflict determination unit 502, and a conflict processing unit 503, wherein: a change data determining unit 501, configured to compare the local file with the parent table, determine local change data, and compare the parent table with the server table, determine server change data; a conflict determination unit 502, configured to determine, according to the local change data and the server change data, whether the file or the folder with the same path is changed by the local and/or the server, and if so, determine that a path conflict exists; the conflict processing unit 503 is configured to perform a deduplication operation on the file or folder that conflicts the path according to the modification type.
In one implementation, the conflict processing unit 503 is configured to, according to the local variation data and the server variation data, further determine whether the local variation data and the server variation data MD5 have the same value when determining that the server is a new file or folder and the local is also a new file or folder operation; if the MD5 values are the same, discarding the local change data and the server change data, and updating the father table according to the server node; if the MD5 values are different, determining the deduplication operation according to the server and the local change types.
In one implementation, the conflict processing unit 503 is configured to, according to the local change data and the server change data, request, when determining that the server is a new file and the local is a change type of the new folder, renaming the file of the server change data from the server.
In one implementation, the conflict processing unit 503 is configured to, according to the local change data and the server change data, when determining that the server is a new folder and the local is a change type of a new file, save the server change data unchanged and rename the file of the local change data.
In one implementation, the conflict processing unit 503 is configured to further determine, according to the local change data and the server change data, whether the file identification FID file that is the same as the file identification FID file in the server change data exists in the parent table when it is determined that both the local and the server are new files and the local new files are empty, discard the local change data if the file identification FID file exists in the parent table, save the server change data if the file identification FID file does not exist in the server change data, and rename the file of the local change data.
In one implementation, the conflict processing unit 503 is configured to discard the server change data when determining that the server is a change type of deleting a file or a folder according to the local change data and the server change data.
In one implementation manner, the conflict processing unit 503 is configured to obtain all local files, and reject files contained in the local variation data, so as to obtain local files that do not need to be synchronized; and obtaining all the nodes of the server, and eliminating the nodes contained in the server change data to obtain the server nodes without synchronization.
In one implementation, the conflict processing unit 503 is configured to traverse server change data for the local file that does not need synchronization; discarding server change data and updating the father table file when determining that the server and the local are both newly added files or the change types of newly added folders; when the server and the local are not the newly added files or the newly added folders, the server change data is kept unchanged, and the files or the folders of the local change data are renamed.
In one implementation, the conflict processing unit 503 is configured to traverse the local variation data for the server node that does not need synchronization; when it is determined that both the local and the server are of a change type for the newly added file or folder, the local change data is discarded and the parent table is updated.
Embodiments of the present application also provide a storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.
Alternatively, in the present embodiment, the above-described storage medium may be configured to store a computer program for performing the steps of:
(1) Comparing the local file with the father table to determine local variation data, and comparing the father table with the server table to determine server variation data;
(2) Determining whether the file or the folder with the same path is changed by a local server or/and a server according to the local change data and the server change data, and if so, determining that the path conflict exists;
(3) And according to the change type, performing deduplication operation on the file or folder with the path conflict.
Alternatively, in the present embodiment, the storage medium may include, but is not limited to: a usb disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing a computer program.
Embodiments of the present application also provide an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.
Optionally, the electronic apparatus may further include a transmission device and an input/output device, where the transmission device is connected to the processor, and the input/output device is connected to the processor.
Alternatively, in the present embodiment, the above-described processor may be configured to execute the following steps by a computer program:
(1) Comparing the local file with the father table to determine local variation data, and comparing the father table with the server table to determine server variation data;
(2) Determining whether the file or the folder with the same path is changed by a local server or/and a server according to the local change data and the server change data, and if so, determining that the path conflict exists;
(3) And according to the change type, performing deduplication operation on the file or folder with the path conflict.
Alternatively, specific examples in this embodiment may refer to examples described in the foregoing embodiments and optional implementations, and this embodiment is not described herein.
The foregoing embodiment numbers of the present application are merely for describing, and do not represent advantages or disadvantages of the embodiments.
In the foregoing embodiments of the present application, the descriptions of the embodiments are emphasized, and for a portion of this disclosure that is not described in detail in this embodiment, reference is made to the related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed technology content may be implemented in other manners. The above-described embodiments of the apparatus are merely exemplary, and the division of the units, such as the division of the units, is merely a logical function division, and may be implemented in another manner, for example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interfaces, units or modules, or may be in electrical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely a preferred embodiment of the present application and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present application and are intended to be comprehended within the scope of the present application.
Claims (10)
1. The method for processing the path conflict in the cloud backup is characterized by comprising the following steps of:
comparing the local file with the father table to determine local variation data, and comparing the father table with the server table to determine server variation data;
determining whether the file or the folder with the same path is changed by a local server or/and a server according to the local change data and the server change data, and if so, determining that the path conflict exists;
according to the change type, performing duplication removal operation on the file or folder with the path conflict;
and performing deduplication operation on the file or folder with the path conflict according to the change type, wherein the deduplication operation comprises the following steps:
according to the local change data and the server change data, when the server is determined to be a new file or folder and the local is also the operation of the new file or folder, whether the local change data and the server change data MD5 are the same is further judged; if the MD5 values are the same, discarding the local change data and the server change data, and updating the father table according to the server node; if the MD5 values are different, determining a deduplication operation according to the server and the local change types; or,
and discarding the server change data when the server is determined to be a change type of the deleted file or folder according to the local change data and the server change data.
2. The method of claim 1, wherein if the MD5 values are different, further determining a deduplication operation based on the server and the local change types comprises:
and according to the local change data and the server change data, when the server is determined to be a new file and the local change type of the new folder, requesting the server to rename the file of the server change data.
3. The method of claim 1, wherein if the MD5 values are different, further determining a deduplication operation based on the server and the local change types comprises:
and according to the local change data and the server change data, when the server is determined to be a new folder and the local is a change type of the new file, the server change data is stored unchanged, and the file of the local change data is renamed.
4. The method of claim 1, wherein if the MD5 values are different, further determining a deduplication operation based on the server and the local change types comprises:
and according to the local change data and the server change data, when the local and the server are determined to be new files and the local new files are empty, further judging whether File Identification (FID) files which are the same as those in the server change data exist in the father table, discarding the local change data if the File Identification (FID) files exist, and if the File Identification (FID) files do not exist, storing the server change data unchanged and renaming the files of the local change data.
5. The method of claim 1, further comprising, prior to said deduplicating the path conflicting file or folder according to the change type:
obtaining all local files, and removing files contained in the local change data to obtain local files which do not need to be synchronized; and obtaining all the nodes of the server, and eliminating the nodes contained in the server change data to obtain the server nodes without synchronization.
6. The method according to claim 5, wherein for the local file that does not need synchronization, the performing a deduplication operation on a file or folder that conflicts with a path according to a change type includes:
traversing server change data for the local file which does not need synchronization;
discarding server change data and updating the father table file when determining that the server and the local are both newly added files or the change types of newly added folders; when the server and the local are not the newly added files or the newly added folders, the server change data is kept unchanged, and the files or the folders of the local change data are renamed.
7. The method according to claim 5, wherein for the server node that does not need synchronization, the performing a deduplication operation on a file or folder that is in path conflict according to a change type includes:
traversing the local variation data aiming at the server node which does not need synchronization;
when it is determined that both the local and the server are of a change type for the newly added file or folder, the local change data is discarded and the parent table is updated.
8. A device for processing path conflicts in cloud backup, characterized in that the device is configured to process the path conflicts in a local client after downloading the latest file data from a server to the local client, where the device is configured to execute the method according to any one of claims 1 to 7.
9. A storage medium having a computer program stored therein, wherein the computer program is arranged to perform the method of any of claims 1 to 7 when run.
10. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to run the computer program to perform the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111641380.3A CN114422533B (en) | 2021-12-29 | 2021-12-29 | Method and device for processing path conflict in cloud backup and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111641380.3A CN114422533B (en) | 2021-12-29 | 2021-12-29 | Method and device for processing path conflict in cloud backup and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114422533A CN114422533A (en) | 2022-04-29 |
| CN114422533B true CN114422533B (en) | 2023-05-09 |
Family
ID=81269807
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111641380.3A Active CN114422533B (en) | 2021-12-29 | 2021-12-29 | Method and device for processing path conflict in cloud backup and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114422533B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104182294A (en) * | 2013-05-23 | 2014-12-03 | 华为技术有限公司 | Method and device for backing up and recovering file |
| CN108667881A (en) * | 2017-03-31 | 2018-10-16 | 中国科学院声学研究所 | A method for synchronizing business data between an intelligent terminal and a cloud server |
| CN109313634A (en) * | 2016-03-15 | 2019-02-05 | 微软技术许可有限责任公司 | File synchronization for single file is suspended |
| CN110532021A (en) * | 2018-05-25 | 2019-12-03 | 北京东土科技股份有限公司 | The processing method and processing device of the configuration file of dcs |
| CN112650618A (en) * | 2019-10-12 | 2021-04-13 | 伊姆西Ip控股有限责任公司 | Method, apparatus and computer program product for backing up data |
| CN113411404A (en) * | 2021-06-24 | 2021-09-17 | 平安普惠企业管理有限公司 | File downloading method, device, server and storage medium |
| CN113449216A (en) * | 2020-03-26 | 2021-09-28 | 腾讯科技（深圳）有限公司 | File processing method and device and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9912425B2 (en) * | 2014-12-15 | 2018-03-06 | Intel Corporation | Radio frequency transceiver with local oscillator control for multi-carrier applications |
| US10866963B2 (en) * | 2017-12-28 | 2020-12-15 | Dropbox, Inc. | File system authentication |
-
2021
- 2021-12-29 CN CN202111641380.3A patent/CN114422533B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104182294A (en) * | 2013-05-23 | 2014-12-03 | 华为技术有限公司 | Method and device for backing up and recovering file |
| CN109313634A (en) * | 2016-03-15 | 2019-02-05 | 微软技术许可有限责任公司 | File synchronization for single file is suspended |
| CN108667881A (en) * | 2017-03-31 | 2018-10-16 | 中国科学院声学研究所 | A method for synchronizing business data between an intelligent terminal and a cloud server |
| CN110532021A (en) * | 2018-05-25 | 2019-12-03 | 北京东土科技股份有限公司 | The processing method and processing device of the configuration file of dcs |
| CN112650618A (en) * | 2019-10-12 | 2021-04-13 | 伊姆西Ip控股有限责任公司 | Method, apparatus and computer program product for backing up data |
| CN113449216A (en) * | 2020-03-26 | 2021-09-28 | 腾讯科技（深圳）有限公司 | File processing method and device and storage medium |
| CN113411404A (en) * | 2021-06-24 | 2021-09-17 | 平安普惠企业管理有限公司 | File downloading method, device, server and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114422533A (en) | 2022-04-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3125501B1 (en) | File synchronization method, server, and terminal | |
| CN106325933B (en) | Batch data synchronous method and device | |
| US9336227B2 (en) | Selective synchronization in a hierarchical folder structure | |
| CN102629247B (en) | Method, device and system for data processing | |
| EP3300334A1 (en) | Network-based file cloud synchronization method | |
| US20120323847A1 (en) | Apparatus, and associated method, for synchronizing directory services | |
| CN108460041B (en) | Data processing method and device | |
| CN102882985A (en) | File sharing method based on cloud storage | |
| CN103823807B (en) | A kind of method, apparatus and system for removing repeated data | |
| CN111190962A (en) | A file synchronization method, device and local terminal | |
| CN114422533B (en) | Method and device for processing path conflict in cloud backup and electronic equipment | |
| CN109815047B (en) | Data processing method and related device | |
| US20200133919A1 (en) | Method, electronic device and computer program product for snapshot replication | |
| CN111324483B (en) | Data recovery method and device and related equipment | |
| US10534708B1 (en) | Shallow cache for content replication | |
| CN114422500B (en) | Method and device for processing file identification conflict in cloud backup and electronic equipment | |
| CN105844171B (en) | Method and device for file synchronization control | |
| CN109842482B (en) | Information synchronization method, system and terminal equipment | |
| CN111881110A (en) | Data migration method and device | |
| CN103856535B (en) | A kind of method and apparatus obtaining user data | |
| CN115687276A (en) | File processing method and device, electronic equipment and storage medium | |
| CN110677497B (en) | Network medium distribution method and device | |
| US20200296161A1 (en) | Learning client preferences to optimize event-based synchronization | |
| CN114036104A (en) | Cloud filing method, device and system for re-deleted data based on distributed storage | |
| CN115525618A (en) | Storage cluster, data storage method, system and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |