CN111581029B - Remote backup method and system for hard link files - Google Patents
Remote backup method and system for hard link files Download PDFInfo
- Publication number
- CN111581029B CN111581029B CN202010395549.0A CN202010395549A CN111581029B CN 111581029 B CN111581029 B CN 111581029B CN 202010395549 A CN202010395549 A CN 202010395549A CN 111581029 B CN111581029 B CN 111581029B
- Authority
- CN
- China
- Prior art keywords
- file
- attribute
- map
- files
- disaster recovery
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/13—File access structures, e.g. distributed indices
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/178—Techniques for file synchronisation in file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method and a system for remote backup of hard link files, wherein the method comprises the following steps: step S1, creating a map file for a data directory to be backed up on a working machine, wherein a key value of the map file records a file index number of a file under the data directory, and a value is used for storing a path of a corresponding file; step S2, traversing the files under the data directory, acquiring the file index number of each file, respectively judging the files of different types, marking the map file according to the judging result, and sending the corresponding file information to the disaster recovery device terminal according to the processing result; and step S3, after the disaster recovery machine receives the file message of the working machine, corresponding backup processing is carried out according to different file attributes.
Description
Technical Field
The invention relates to the field of computer data backup disaster recovery, in particular to a remote backup method and system for hard link files.
Background
A hard link is a type of file that can be considered as multiple file names of a file, with the same physical index number between the hard-linked file and the linked file, and is not destroyed when the original file is moved or deleted because it references the physical data of the file rather than the location of the file in the file structure. The main function of the hard link is to realize multiple copies of one file under the same file system, and hard disk space can be saved by hard linking without copying a data space.
In the field of data disaster recovery, in the process of transmitting data of a working machine to a disaster recovery machine, if a hard link file exists, the following two methods are generally adopted: one method is to copy the hard link file directly to the disaster recovery machine, however, the hard link file at the disaster recovery machine end becomes a common file which is the same as the original file content, and the hard link file at the disaster recovery machine end occupies more space, so that the space of a disk is wasted, if one file has a plurality of hard link files, the disk is wasted greatly, and the performance of the disaster recovery data is affected; alternatively, the hard link file is not transmitted, but the hard link file is selected to be ignored, however, the data at the disaster recovery machine side is inconsistent with the data of the working machine.
Disclosure of Invention
In order to overcome the defects of the prior art, the invention aims to provide a method and a system for backing up hard link files in different places, so as to realize the rapid synchronization of hard link data to a disaster recovery machine, and enable the hard link data to be used as the hard link files at the disaster recovery machine side after being transmitted to the disaster recovery machine.
In order to achieve the above object, the present invention provides a method for remotely backing up hard-linked files, comprising the following steps:
step S1, creating a map file for a data directory to be backed up on a working machine, wherein a key value of the map file records a file index number of a file under the data directory, and the value is used for storing a path of a corresponding file;
step S2, traversing files under a data catalog to be backed up on the working machine, acquiring a file index number of each file, respectively judging different types of files, marking the map files according to a judging result, and sending corresponding file information to a disaster recovery machine end according to a processing result;
and S3, at the disaster recovery machine end, corresponding backup processing is carried out according to different file attributes after the received file information of the working machine.
Preferably, step S2 further comprises:
step S200, traversing each file under the data directory, reading a file index number nodeid of each file under the data directory, and judging different types of files;
step S201, for the current file with the file type being the directory, marking the attribute as the directory, and sending the file message containing the directory attribute to the disaster recovery device terminal;
step S202, for the current file with the file type of a general file, marking the current file as a general file, and sending a file message containing the file data and the file attribute to a disaster recovery device end;
step S203, for the current file with the file type being the hard link file, searching whether the current file has the file index number nodeid in the map file, marking the attribute of the map file as a common file according to the searching result, processing the common file or marking the attribute of the map file as the hard link file, processing the hard link file, and sending the corresponding file message to the disaster recovery device.
Preferably, in step S203, if the map file does not have the file index number nodeid of the current file, the file index number nodeid and the file path of the current file are inserted into the map file, the file attribute is marked as a common file, and the file attribute and the file data content are sent to the disaster recovery device side.
Preferably, in step S203, if the file index nodeid of the current file is found in the map file, the file attribute of the current file is marked as a hard link file, the original file path corresponding to the key value in the map file as the value of the file index nodeid is recorded, and the original file path, the file attribute of the current file and the hard link file path are sent to the disaster recovery device together as a file message.
Preferably, in step S3, at the disaster recovery device side, for the file message of the directory attribute, a subdirectory is created according to the received directory attribute message, and the directory attribute is synchronized.
Preferably, at the disaster recovery machine side, for a file message with an attribute of a common file, the data content of the file is directly written into a disk according to the received file message, and the file attribute is synchronized.
Preferably, for a file message with a hard link file attribute, the hard link file is created directly according to the path of the original file, the file attribute of the current file and the path of the link file.
In order to achieve the above object, the present invention further provides a system for remote backup of hard-linked files, comprising:
the working machine is used for creating a map file for the data directory to be backed up on the working machine, traversing the files under the data directory to be backed up on the working machine during backup, acquiring the file index number of each file, respectively judging the files of different types, marking the map file for processing, and sending the corresponding file information to the disaster recovery machine end according to the processing result;
and the disaster recovery machine is used for carrying out corresponding backup processing according to the received file message of the working machine and different file attributes thereof.
Preferably, the working machine further includes:
the Map file creating unit is used for creating a Map file for a data directory to be backed up on the working machine before backup, wherein a key value of the Map file records a file index number of a file under the data directory, and the value is used for storing a path of a corresponding file;
the traversing processing unit is used for traversing the files under the data directory to be backed up on the working machine, obtaining the file index number nodeid of each file, respectively judging the files of different types, marking the map files, and sending the corresponding file information to the disaster recovery machine end according to the processing result.
Preferably, the traversal processing unit is specifically configured to:
traversing each file under the data directory, reading a file index number nodeid of each file under the data directory, and judging files of different types;
for the current file with the file type being the directory, marking the attribute as the directory, and sending a file message containing the directory attribute to the disaster recovery device terminal;
for the current file with the file type of a common file, marking the current file with the attribute of the common file, and sending a file message containing the file data and the file attribute to a disaster recovery device end;
and for the current file with the file type of the hard link file, searching whether a file index number nodeid of the current file exists in the map file, marking the attribute of the map file as a common file to be processed as the common file or marking the attribute of the map file as the hard link file to be processed as the hard link file according to the searching result, and sending a corresponding file message to the disaster recovery device.
Compared with the prior art, the remote backup and system for the hard link files creates the map file for the files under the data directory to be backed up on the working machine before backup, then traverses the files under the data directory to be backed up on the working machine during backup, obtains the file index number of each file, respectively judges the files of different types, marks the files in the map file according to the judging result, sends the corresponding file information to the disaster recovery machine end according to the processing result, and carries out corresponding backup processing according to different file attributes after receiving the file information of the working machine at the disaster recovery machine end.
Drawings
FIG. 1 is a flowchart illustrating a method for remote backup of hard-linked files according to the present invention;
FIG. 2 is a system architecture diagram of a remote backup system for hard-linked files according to the present invention;
FIG. 3 is a flowchart of a remote backup of a hard link file according to an embodiment of the present invention.
Detailed Description
Other advantages and effects of the present invention will become readily apparent to those skilled in the art from the following disclosure, when considered in light of the accompanying drawings, by describing embodiments of the present invention with specific embodiments thereof. The invention may be practiced or carried out in other embodiments and details within the scope and range of equivalents of the various features and advantages of the invention.
FIG. 1 is a flowchart illustrating a method for remote backup of hard-linked files according to the present invention. As shown in FIG. 1, the remote backup method of the hard link file comprises the following steps:
step S1, before backup, a map file is created on a working machine for a data directory to be backed up, wherein a key value of the map file is a file index number, and a value is a path of the file.
In a specific embodiment of the present invention, it is assumed that a data directory a is data to be protected by a user on a working machine, and a map file is created, where the map file includes a key value and a value, the key value is used to store a file index number of a file under the data directory, and the value is used to store a path of a corresponding file, that is, each recorded key value in the map file records a file index number of a corresponding file under the data directory a, and the value records a path of a corresponding file. Here, in the process of building a map, the map file initially built is empty.
And S2, traversing files under the data directory to be backed up on the working machine, acquiring a file index number nodeid of each file, respectively judging different types of files, marking the map files, and sending corresponding file information to a disaster recovery machine end according to a processing result.
Specifically, step S2 further includes:
step S200, traversing each file under the data catalog A, reading the file index number nodeid of each file under the data catalog A, and judging different types of files;
step S201, for the current file with the file type being the directory, marking the attribute as the directory, and sending the file message containing the directory attribute to the disaster recovery device terminal;
step S202, for the current file with the file type of a general file, marking the current file as a general file, and sending a file message containing the file data and the file attribute to a disaster recovery device end;
step S203, for the current file with the file type being the hard link file, searching whether the current file has the file index number nodeid in the map file, marking the attribute of the current file as a common file according to the searching result, processing the current file as a common file, or marking the attribute of the current file as the hard link file, processing the current file as the hard link file, and sending the corresponding file message to the disaster recovery device. Specifically, if the map file does not have the current file index number nodeid, inserting the file index number nodeid and the file path of the current file into the map file, marking the current file attribute as a common file, and sending the corresponding file attribute and file data content to a disaster recovery device end; if the file index number nodeid of the current file is found in the map file, marking the attribute of the current file as a hard link file, recording the value corresponding to the value of the key value in the map file as the value of the file index number nodeid, namely the original file path of the hard link file, and sending the value to the disaster recovery machine together with the file attribute of the current file and the hard link file path as file information. That is, if the index number of the current file does not exist in the map file in the searching process, which means that the current file is built in the map for the first time, according to the principle of the hard link file, the hard link file found for the first time is treated as a normal file, because one hard link file is not different from other normal files, when the number of hard links of the file is greater than or equal to 2, any hard link file can be used as an original file, namely, a normal file, and other hard links are connected to the file, the original file path, the current file attribute and the current hard link file path are sent to the disaster recovery machine side together as file information, and the original file path/a.ori, the file attribute (hard link file) of the current file and the current hard link file path/a are sent to the disaster recovery machine side as file information on the assumption that the map file is searched for the value corresponding to the file index of the current file, namely the original file path,/path/a.ori is the current hard link file path (read out when traversing the data directory).
And S3, at the disaster recovery machine end, after the received file message of the working machine, carrying out corresponding backup processing according to different file attributes.
Specifically, for the file message of the directory attribute, creating a subdirectory according to the received directory attribute message, and synchronizing the directory attribute; for file information with the attribute of a common file, directly writing the data content of the file into a disk according to the received file information, and synchronizing the file attribute; for file messages with the attribute of hard link files, the hard link files are created directly according to the paths of the original files and the paths of the link files.
FIG. 2 is a system architecture diagram of a remote backup system for hard-linked files according to the present invention. As shown in fig. 2, the system for backing up hard-linked files in different places of the present invention comprises:
the working machine 20 is configured to create a map file for a data directory to be backed up on the working machine before the backup is performed, traverse the files under the data directory to be backed up on the working machine during the backup, obtain the file index number nodeid of each file, respectively determine the files of different types, mark the map file, and send the corresponding file message to the disaster recovery machine according to the processing result.
Specifically, work machine 20 further includes:
the Map file creating unit 201 is configured to create a Map file for a data directory to be backed up on the working machine before backup, where a key value of the Map file is a file index number and a value is a path of the file.
In a specific embodiment of the present invention, assuming that the data directory a is data to be protected by a user on the working machine, the Map file creating unit 201 first creates a Map file, where the Map file includes a key value and a value, the key value is used to store a file index number of a file under the data directory, and the value is used to store a path of a corresponding file, that is, each record key value in the Map file records a file index number of a corresponding file under the data directory a, and the value records a path of a corresponding file.
The traversal processing unit 202 is configured to traverse the files under the data directory to be backed up on the working machine, obtain the file index number nodeid of each file, respectively determine the files of different types, mark the map file for processing, and send the corresponding file message to the disaster recovery machine according to the processing result.
The traversal processing unit 202 is specifically configured to:
traversing each file under the data directory, reading the file index number nodeid of each file under the data directory A, and judging different types of files;
for the current file with the file type being the directory, marking the attribute as the directory, and sending a file message containing the directory attribute to the disaster recovery device terminal;
for the current file with the file type of a common file, marking the current file with the attribute of the common file, and sending a file message containing the file data and the file attribute to a disaster recovery device end;
and for the current file with the file type of the hard link file, searching whether a file index number nodeid of the current file exists in the map file, marking the attribute of the map file as a common file to be processed as the common file or marking the attribute of the map file as the hard link file to be processed as the hard link file according to the searching result, and sending a corresponding file message to the disaster recovery device. Specifically, if the map file does not have the file index number nodeid, inserting the file index number nodeid and the file path of the current file into the map file, marking the file attribute as a common file, and sending the file attribute and the file data content to a disaster recovery device end; if the index number nodeid of the current file can be found in the map file, marking the file attribute as a hard link file, recording the value corresponding to the key value of the map file as the index number nodeid, namely the original file path of the link file, and sending the value to the disaster recovery device together with the file attribute of the current file and the hard link file path as file information.
The disaster recovery device 21 is configured to perform corresponding backup processing according to the received file message of the working machine and different file attributes of the file message.
Specifically, at the disaster recovery device 21, for the file message of the directory attribute, creating a subdirectory according to the received directory attribute message, and synchronizing the directory attribute; for file information with the attribute of a common file, directly writing the data content of the file into a disk according to the received file information, and synchronizing the file attribute; for file messages with the attribute of hard link files, the hard link files are created directly according to the paths of the original files and the paths of the link files.
Examples
FIG. 3 is a flowchart of a remote backup of a hard link file according to an embodiment of the present invention. As shown in fig. 3, the working machine is a user working server, and the disaster recovery machine is a user data backup server.
The data catalog A is data to be protected by a user on the working machine, and the data catalog B is a data copy backed up by the user on the disaster recovery machine.
When backing up, the user establishes a backup task, which comprises the following specific steps:
step one: first the user selects the work machine server and the data directory a to be protected on the server. For example only, the number of directories is not limited, and a user may choose to protect multiple directories at the same time.
Step two: and selecting a disaster recovery server and a catalog B of data to be backed up on the server. Also, for example only, the number of directories is not limited, and the user may select the corresponding disaster recovery directory according to the number of directories selected by the working machine.
Step three: and traversing the data catalog A of the working machine, and judging and processing different types of files under the data catalog A.
Step four: creating a map file before traversing the data directory A directory, wherein the key value of the map file is a file index number, and the value is a path of the file.
Step five: for files with the file type being the directory, marking the attribute as the directory, sending the directory attribute to the B directory of the disaster recovery device, creating a subdirectory by the disaster recovery device according to the received directory attribute message, and synchronizing the directory attribute.
Step six: for a file with a general file type, marking the file with a general file attribute, sending data to the disaster recovery device, directly writing the file content according to the received file message under the B directory of the disaster recovery device, and synchronizing the file attribute.
Step seven: for a file with a file type of a hard link file, searching whether a file index number nodeid of the file exists in the map file, if the file index number nodeid of the file does not exist in the map file, inserting the file index number nodeid and a file path of the file into the map, marking the file as a common file, and sending file attributes and file data contents to a B directory corresponding to a disaster backup machine; if the file index number nodeid of the file is found in the map file, the file is marked as a hard link file, the value of the key value in the map file corresponding to the file index number nodeid value of the key value is recorded, namely the original file path of the link file, and the value is sent to a disaster recovery machine together with the link path of the hard link file, and the disaster recovery machine creates the hard link file according to the link file path and the original file path under the B catalogue after receiving the original file path of the link file and the file message of the link file path.
It should be noted that, the method for remote backup of hard link files provided by the present invention is also suitable for data recovery, and the process of recovery is a reverse backup process for hard links, and the original data is the data backed up to the disaster recovery machine, i.e. the working machine end is regarded as the disaster recovery machine end, and the disaster recovery machine end is regarded as the working machine end, which is not described herein.
In summary, the present invention creates a map file for a file under a data directory to be backed up on a working machine before backing up, traverses the file under the data directory to be backed up on the working machine during backing up, obtains a file index number of each file, respectively determines different types of files, marks the map file according to a determination result, sends a corresponding file message to a disaster recovery machine end according to a processing result, and performs corresponding backup processing according to different file attributes after receiving the file message of the working machine at the disaster recovery machine end.
Compared with the prior art, the invention has the following advantages:
1. according to the invention, one data content is not required to be retransmitted for the hard link file in the backup process, so that the time for data transmission is saved.
2. In the backup process, the data does not need to be copied to the disaster recovery catalog, so that the disk space is greatly saved, and the time for copying the data is greatly saved.
3. In the process of data recovery, the steps are the same as the backup process, so that the time for data transmission and the time for writing into a disk are saved, and the space of the disk is greatly saved.
The above embodiments are merely illustrative of the principles of the present invention and its effectiveness, and are not intended to limit the invention. Modifications and variations may be made to the above-described embodiments by those skilled in the art without departing from the spirit and scope of the invention. Accordingly, the scope of the invention is to be indicated by the appended claims.
Claims (6)
1. A method for backing up hard-linked files in different places comprises the following steps:
step S1, creating a map file for a data directory to be backed up on a working machine, wherein a key value of the map file records a file index number of a file under the data directory, and the value is used for storing a path of a corresponding file;
step S2, traversing files under a data catalog to be backed up on the working machine, acquiring a file index number of each file, respectively judging different types of files, marking the map files according to a judging result, and sending corresponding file information to a disaster recovery machine end according to a processing result; step S2 further comprises:
step S200, traversing each file under the data directory, reading a file index number nodeid of each file under the data directory, and judging different types of files;
step S201, for the current file with the file type being the directory, marking the attribute as the directory, and sending the file message containing the directory attribute to the disaster recovery device terminal;
step S202, for the current file with the file type of a general file, marking the current file as a general file, and sending a file message containing the file data and the file attribute to a disaster recovery device end;
step S203, for the current file with the file type of hard link file, searching whether the current file has the file index number nodeid in the map file, marking the attribute of the map file as a common file according to the searching result to be processed as the common file or marking the attribute of the map file as the hard link file to be processed as the hard link file, and sending the corresponding file message to the disaster recovery device; in step S203, if the map file does not have the file index number nodeid of the current file, inserting the file index number nodeid and the file path of the current file into the map file, marking the file attribute as a common file, and sending the file attribute and the file data content to the disaster recovery device;
and S3, at the disaster recovery machine end, after the received file message of the working machine, carrying out corresponding backup processing according to different file attributes.
2. The method for off-site backup of hard link files as recited in claim 1, wherein: in step S203, if the file index nodeid of the current file is found in the map file, the file attribute of the current file is marked as a hard link file, the original file path corresponding to the key value in the map file as the value of the file index nodeid is recorded, and the original file path, the file attribute of the current file and the hard link file path are sent to the disaster recovery device together as a file message.
3. The method for off-site backup of hard link files as claimed in claim 2, wherein: in step S3, at the disaster recovery device side, for the file message of the directory attribute, creating a subdirectory according to the received directory attribute message, and synchronizing the directory attribute.
4. The method for off-site backup of hard link files as claimed in claim 2, wherein: and at the disaster recovery machine end, for file information with the attribute of a common file, directly writing the data content of the file into a disk according to the received file information, and synchronizing the file attribute.
5. The method for off-site backup of hard link files as claimed in claim 2, wherein: for file messages with the attribute of hard link files, the hard link files are directly created according to the path of the original file, the file attribute of the current file and the path of the link file.
6. A system for off-site backup of hard-linked files, comprising:
the working machine is used for creating a map file for the data directory to be backed up on the working machine, traversing the files under the data directory to be backed up on the working machine during backup, acquiring the file index number of each file, respectively judging the files of different types, marking the map file for processing, and sending the corresponding file information to the disaster recovery machine end according to the processing result; the working machine further includes:
the Map file creating unit is used for creating a Map file for a data directory to be backed up on the working machine before backup, wherein a key value of the Map file records a file index number of a file under the data directory, and the value is used for storing a path of a corresponding file;
the traversing processing unit is used for traversing files under the data directory to be backed up on the working machine, acquiring a file index number nodeid of each file, respectively judging different types of files, marking the map files, and sending corresponding file information to a disaster recovery machine end according to a processing result; the traversal processing unit is specifically configured to:
traversing each file under the data directory, reading a file index number nodeid of each file under the data directory, and judging files of different types;
for the current file with the file type being the directory, marking the attribute as the directory, and sending a file message containing the directory attribute to the disaster recovery device terminal;
for the current file with the file type of a common file, marking the current file with the attribute of the common file, and sending a file message containing the file data and the file attribute to a disaster recovery device end;
for the current file with the file type of the hard link file, searching whether a file index number nodeid of the current file exists in the map file, marking the attribute of the map file as a common file to be processed as the common file or marking the attribute of the map file as the hard link file to be processed as the hard link file according to the searching result, and sending a corresponding file message to the disaster recovery device; if the map file does not have the file index number nodeid of the current file, inserting the file index number nodeid and the file path of the current file into the map file, marking the file attribute as a common file, and sending the file attribute and the file data content to a disaster recovery device end;
and the disaster recovery machine is used for carrying out corresponding backup processing according to the received file message of the working machine and different file attributes thereof.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010395549.0A CN111581029B (en) | 2020-05-12 | 2020-05-12 | Remote backup method and system for hard link files |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010395549.0A CN111581029B (en) | 2020-05-12 | 2020-05-12 | Remote backup method and system for hard link files |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111581029A CN111581029A (en) | 2020-08-25 |
| CN111581029B true CN111581029B (en) | 2023-05-05 |
Family
ID=72122907
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010395549.0A Active CN111581029B (en) | 2020-05-12 | 2020-05-12 | Remote backup method and system for hard link files |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111581029B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112035298A (en) * | 2020-09-10 | 2020-12-04 | 北京城市网邻信息技术有限公司 | Data backup method and device, electronic equipment and storage medium |
| CN114675995A (en) * | 2020-12-24 | 2022-06-28 | 北京金山云网络技术有限公司 | Data backup method, device and electronic device |
| CN112764972A (en) * | 2021-01-27 | 2021-05-07 | 上海英方软件股份有限公司 | Cross-platform file attribute backup and recovery method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101403988A (en) * | 2008-11-05 | 2009-04-08 | 中国科学院计算技术研究所 | File back-up system and method of computer system |
| CN104866394A (en) * | 2015-06-08 | 2015-08-26 | 肖选文 | Distributed file backup method and system |
| CN108733507A (en) * | 2017-04-17 | 2018-11-02 | 伊姆西Ip控股有限责任公司 | The method and apparatus of file backup and recovery |
| US10204016B1 (en) * | 2014-07-08 | 2019-02-12 | EMC IP Holding Company LLC | Incrementally backing up file system hard links based on change logs |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10783041B2 (en) * | 2017-09-22 | 2020-09-22 | Mcafee, Llc | Backup and recovery of data files using hard links |
-
2020
- 2020-05-12 CN CN202010395549.0A patent/CN111581029B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101403988A (en) * | 2008-11-05 | 2009-04-08 | 中国科学院计算技术研究所 | File back-up system and method of computer system |
| US10204016B1 (en) * | 2014-07-08 | 2019-02-12 | EMC IP Holding Company LLC | Incrementally backing up file system hard links based on change logs |
| CN104866394A (en) * | 2015-06-08 | 2015-08-26 | 肖选文 | Distributed file backup method and system |
| CN108733507A (en) * | 2017-04-17 | 2018-11-02 | 伊姆西Ip控股有限责任公司 | The method and apparatus of file backup and recovery |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111581029A (en) | 2020-08-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111581029B (en) | Remote backup method and system for hard link files | |
| JP4181044B2 (en) | A backup method for saving a snapshot of selected data in a mass storage system | |
| US7814056B2 (en) | Method and apparatus for data backup using data blocks | |
| EP1306761B1 (en) | File managing method | |
| US8015441B2 (en) | Verification of computer backup data | |
| US8103840B2 (en) | Snapshot mechanism and method thereof | |
| US7415586B2 (en) | Data backup method and system | |
| US6535967B1 (en) | Method and apparatus for transferring data between a primary storage system and a secondary storage system using a bridge volume | |
| US8589353B2 (en) | Method for backing up terminal data and system thereof | |
| US20030142953A1 (en) | Album generation program and apparatus and file display apparatus | |
| US20130204893A1 (en) | Methods for generating a unified virtual snapshot and systems thereof | |
| CN104360914B (en) | Incremental snapshot method and apparatus | |
| JP2006268829A (en) | Method and apparatus for mirroring objects between storage systems | |
| CN106649467B (en) | Blue-ray disc library filing management method and system | |
| US20110282843A1 (en) | Method and system for data backup and replication | |
| CN107229540A (en) | A kind of database restoring method and system based on time point | |
| US20090204648A1 (en) | Tracking metadata for files to automate selective backup of applications and their associated data | |
| JP2005182683A (en) | Data transfer method, system, and program | |
| CN108255638A (en) | A kind of snapshot rollback method and device | |
| JP3857259B2 (en) | Object state transfer method, object state transfer device, object state transfer program, and recording medium for the program | |
| JP2003330782A (en) | Computer system | |
| CN115658382B (en) | Incremental object backup and recovery method, system and storage medium for object storage | |
| CN108829779B (en) | A data processing method and related equipment | |
| JP6697101B2 (en) | Information processing system | |
| CN109325005A (en) | A kind of data processing method and electronic equipment |
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 |