CN111737056A - File breakpoint reentrant method and device - Google Patents
File breakpoint reentrant method and device Download PDFInfo
- Publication number
- CN111737056A CN111737056A CN202010587122.0A CN202010587122A CN111737056A CN 111737056 A CN111737056 A CN 111737056A CN 202010587122 A CN202010587122 A CN 202010587122A CN 111737056 A CN111737056 A CN 111737056A
- Authority
- CN
- China
- Prior art keywords
- file
- job
- output file
- copying
- backup
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000004590 computer program Methods 0.000 claims description 17
- 238000010586 diagram Methods 0.000 description 18
- 230000006870 function Effects 0.000 description 5
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a file breakpoint re-entry method and a device, wherein the method comprises the following steps: when the operation is re-promoted after the operation is interrupted, a backup file and an output file are obtained; when the backup file is inconsistent with the output file, emptying the backup file, and copying the output file to the backup file; when the copying is successful, the output file is emptied, and the job data from the job starting point to the COMMIT point in the backup file is copied to the output file according to the COMMIT point stored in the database, so that the consistency of the processing positions of the job program and the output file can be realized; when the copying is successful, the job program is executed from the COMMIT point, and the output file is written. The invention can realize automatic backup after the operation is interrupted, improve the efficiency of file backup and ensure the accuracy and the integrity of data after the file breakpoint reentry.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a file breakpoint reentry method and device.
Background
In the current operation process, when the operation is re-lifted after the operation is interrupted, the last output file needs to be emptied, and the previous operation file is copied from the backup file to the output file, however, when the file is backed up, the file backup fails or the file backup is incomplete due to abnormal reasons such as environment, resources and the like, at this time, if the operation is re-lifted, the incomplete backup file will cause data loss, if a downtime or manual forced interrupt processing occurs in the operation process, the output file cannot complete the backup, the backup processing must be manually intervened, if the intervention is not performed, the data loss is directly caused after the fault re-lifting operation is eliminated, and when the number of the output files is large, the manual backup efficiency is low.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the invention provides a file breakpoint reentry method, which is used for avoiding data loss and comprises the following steps:
when the operation is re-promoted after the operation is interrupted, a backup file and an output file are obtained; the output file stores the job data from a job starting point to a job interruption point;
when the backup file is inconsistent with the output file, emptying the backup file, and copying the output file to the backup file;
when the copying is successful, clearing the output file, and copying the job data from the job starting point to the COMMIT point in the backup file to the output file according to the COMMIT point stored in the database;
when the copying is successful, the job program is executed from the COMMIT point, and the output file is written.
The embodiment of the invention provides a file breakpoint reentry device, which is used for avoiding data loss and comprises the following components:
the file obtaining module is used for obtaining a backup file and an output file when the operation is restarted after the operation is interrupted; the output file stores the job data from a job starting point to a job interruption point;
the first copying module is used for emptying the backup file and copying the output file to the backup file when the backup file is inconsistent with the output file;
the second copying module is used for emptying the output file when the copying is successful, and copying the job data from the job starting point to the COMMIT point in the backup file to the output file according to the COMMIT point stored in the database;
and the execution job module is used for starting to execute the job program from the COMMIT point and writing the output file when the copying is successful.
The embodiment of the invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the file breakpoint reentry method when executing the computer program.
The embodiment of the invention also provides a computer readable storage medium, and the computer readable storage medium stores a computer program for executing the file breakpoint re-entry method.
The embodiment of the invention comprises the following steps: when the operation is re-promoted after the operation is interrupted, a backup file and an output file are obtained; when the backup file is inconsistent with the output file, emptying the backup file, and copying the output file to the backup file; when the copying is successful, the output file is emptied, and the job data from the job starting point to the COMMIT point in the backup file is copied to the output file according to the COMMIT point stored in the database, so that the consistency of the processing positions of the job program and the output file can be realized; when the copying is successful, the operation program is executed from the COMMIT point, and the output file is written.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts. In the drawings:
FIG. 1 is a schematic diagram illustrating a process of a file breakpoint reentry method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating a breakpoint reentry flow of a file when a backup file is consistent with an output file according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a flow chart of an embodiment of the present invention;
FIG. 4 is a diagram illustrating a structure of a file breakpoint reentry apparatus according to an embodiment of the present invention;
fig. 5 is a schematic diagram of another structure of the file breakpoint reentry apparatus in the embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As will be appreciated by one skilled in the art, embodiments of the present invention may be embodied as a system, apparatus, method or computer program product. Accordingly, the present disclosure may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.
Before describing the embodiment of the present invention, first, the inventor finds technical problems and proposes a concept of a file breakpoint reentry method.
In the existing operation process, when the operation is restarted after the operation is interrupted, the output file of the previous time needs to be emptied, and the operation file is copied from the backup file to the output file, however, the file backup failure or the file backup is incomplete when the file is backed up exists, at this time, if the operation is restarted, the incomplete backup file will cause data loss, if the operation is stopped or the manual forced interrupt processing occurs in the operation process, the manual backup processing must be manually intervened, the efficiency of the manual backup is low, and the error rate is high.
The invention provides a file breakpoint reentry method, which mainly judges whether a backup file is consistent with an output file when a job is resumed after the job is interrupted, and if not, clears the backup file, copies the output file to the backup file, can realize automatic backup after the job is interrupted, improves the efficiency of file backup, and ensures the accuracy and integrity of data after the file breakpoint reentry. The file breakpoint reentry method provided by the embodiment of the present invention is described in detail below.
Fig. 1 is a schematic diagram of a process of a file breakpoint reentry method in an embodiment of the present invention, as shown in fig. 1, the method includes:
step 101: when the operation is re-promoted after the operation is interrupted, a backup file and an output file are obtained; the output file stores the job data from a job starting point to a job interruption point;
step 102: when the backup file is inconsistent with the output file, emptying the backup file, and copying the output file to the backup file;
step 103: when the copying is successful, clearing the output file, and copying the job data from the job starting point to the COMMIT point in the backup file to the output file according to the COMMIT point stored in the database;
step 104: when the copying is successful, the job program is executed from the COMMIT point, and the output file is written.
As shown in fig. 1, an embodiment of the present invention is implemented by: when the operation is re-promoted after the operation is interrupted, a backup file and an output file are obtained; when the backup file is inconsistent with the output file, emptying the backup file, and copying the output file to the backup file; when the copying is successful, the output file is emptied, and the job data from the job starting point to the COMMIT point in the backup file is copied to the output file according to the COMMIT point stored in the database, so that the consistency of the processing positions of the job program and the output file can be realized; when the copying is successful, the operation program is executed from the COMMIT point, and the output file is written.
In specific implementation, when a job program is executed for the first time, an output file and a backup file need to be initialized, the job program is executed from a job starting point and written into the output file, when the written output file reaches a specified number of times, the job program can carry out COMMIT (COMMIT) in a database, and a COMMIT point is recorded in the database, the COMMIT point is a COMMIT point of job data, which indicates that a job has been executed from the starting point to the COMMIT point, and if a downtime, a manual forced interrupt or other error occurs during a job, the job needs to be re-lifted, in step 101, when the job is re-lifted, the backup file and the output file can be acquired, and the job data from the job starting point to the job interrupt point is stored in the output file due to the last job interrupt.
In one embodiment, the method further comprises: when the output file is copied to the backup file, the following operations are repeatedly executed until the copying is successful:
and clearing the backup file, and copying the output file to the backup file.
In specific implementation, in step 102, after obtaining the backup file and the output file, first determining whether the backup file is consistent with the output file, if not, indicating that the backup file is empty or the backup file is incorrect and incomplete, that is, the backup is failed after the last operation is interrupted, if so, indicating that the last operation is successful in interrupting the backup, when the backup file is inconsistent with the output file, the backup file may be emptied, the output file is copied to the backup file, and in the process of copying the output file to the backup file, there may be a case of copy failure due to problems of environment, resources, and the like, and the operations may be repeatedly executed, that is: the backup file is emptied, and the output file is copied to the backup file until the output file is copied successfully, so that automatic re-backup after the backup failure can be realized, and the data loss caused by manual intervention or backup failure is avoided.
In specific implementation, in step 103, when the copying is successful, the output file may be cleared, since the output file stores the job data from the job starting point to the job interruption point, and the database stores the COMMIT point, when the job is re-lifted, the job program needs to roll back to the COMMIT point to start execution, and the job interruption point does not coincide with the location of the COMMIT point, if the backup file is directly copied to the output file, since the job program does not coincide with the processing location of the output file, there may be a part of repeated job data after the re-lifted job writes in the output file, which may cause an error in the job data, in an embodiment of the present invention, the job data from the job starting point to the COMMIT point in the backup file may be copied to the output file according to the COMMIT point already stored in the database, which may ensure that the job program and the output file both start from the COMMIT point when the job is re-lifted, and further, the consistency of the processing positions of the job program and the output file is realized.
Fig. 2 is a schematic diagram of a file breakpoint reentry flow when a backup file is consistent with an output file in an embodiment of the present invention, as shown in fig. 2, in an embodiment, the method further includes:
step 201: when the backup file is consistent with the output file, clearing the output file, and copying the job data from the job starting point to the COMMIT point in the backup file to the output file according to the COMMIT point stored in the database;
step 202: when the copying is successful, the job program is executed from the COMMIT point, and the output file is written.
In one embodiment, the method further comprises: when the stored COMMIT point does not exist in the database, the job program is executed from the job starting point, and the output file is written.
In specific implementation, in step 201, when the backup file is consistent with the output file, it indicates that the last job interruption backup is successful, and the output file does not need to be backed up again, and then the job data from the job starting point to the COMMIT point in the backup file is copied to the output file according to the COMMIT point stored in the database. In step 104 or step 202, when copying the job data from the job starting point to the COMMIT point in the backup file to the output file is successful, the job program may be executed from the COMMIT point, the output file may be written from the COMMIT point until the job execution is completed, a complete output file may be obtained, and the recorded COMMIT point may be cleared. If the operation interruption occurs in the operation executing process, the steps can be executed again until the operation execution is completed. It should be noted that, if there is no COMMIT point stored in the database, the job program may be executed directly from the job starting point after the output file is emptied, and the output file may be written from the job starting point until the job execution is completed.
In one embodiment, the method further comprises:
when copying of the job data from the job start point to the COMMIT point in the backup file to the output file fails, the following operations are repeatedly performed until the copying succeeds:
and clearing the output file, and copying the job data of the backup file from the job starting point to the COMMIT point to the output file according to the COMMIT point stored in the database.
In specific implementation, in the process of copying the job data from the job starting point to the COMMIT point in the backup file to the output file at any time, when there may be a copy failure due to problems of environment, resources, and the like, the output file may be emptied, the job data from the job starting point to the COMMIT point of the backup file is copied to the output file according to the COMMIT point stored in the database, and if the copy failure still occurs, the above operations may be repeatedly performed until the copy failure succeeds, so that automatic re-backup after the backup failure may be implemented, and data loss due to manual intervention or backup failure is avoided.
The following is a specific example to facilitate an understanding of how the invention may be practiced.
Fig. 3 is a schematic diagram of a flow of an embodiment of the present invention, as shown in fig. 3, including:
when the job program is executed for the first time, initializing an output file and a backup file, starting to execute the job program from a job starting point and writing the output file, and then executing the following steps:
the first step is as follows: when the operation is re-promoted after the operation is interrupted, acquiring a backup file and an output file, judging whether the backup file is consistent with the output file, if not, executing the second step, and if so, executing the third step;
the second step is that: emptying the backup file, copying the output file to the backup file, executing the third step when the copying is successful, and circularly executing the second step when the copying is failed until the copying is successful;
the third step: clearing the output file, copying the job data from the job starting point to the COMMIT point in the backup file to the output file according to the stored COMMIT point in the database, if the stored COMMIT point does not exist in the database, copying is not needed, executing the fourth step when copying is successful, and circularly executing the third step when copying is failed until copying is successful;
the fourth step: and if the stored COMMIT point does not exist in the database, executing the job program from the job starting point, and writing the output file from the job starting point until the job execution is completed.
And if the operation is interrupted in the operation executing process, repeatedly executing the first step to the fourth step until the operation is executed, and obtaining a complete output file.
Based on the same inventive concept, the embodiment of the present invention further provides a file breakpoint reentry apparatus, as in the following embodiments. Because the principle of the file breakpoint reentry device for solving the problem is similar to that of the file breakpoint reentry method, the implementation of the device can refer to the implementation of the method, and repeated parts are not described again. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
An embodiment of the present invention provides a file breakpoint reentry device to avoid data loss, and fig. 4 is a schematic diagram of a structure of the file breakpoint reentry device in the embodiment of the present invention, as shown in fig. 4, the device includes:
the file obtaining module 01 is used for obtaining a backup file and an output file when the operation is restarted after the operation is interrupted; the output file stores the job data from a job starting point to a job interruption point;
the first copying module 02 is used for emptying the backup file and copying the output file to the backup file when the backup file is inconsistent with the output file;
the second copying module 03 is configured to clear the output file when the copying is successful, and copy the job data from the job starting point to the COMMIT point in the backup file to the output file according to the COMMIT point already stored in the database;
and an execution job module 04, configured to, when the copying is successful, execute the job program from the COMMIT point, and write the output file.
Fig. 5 is a schematic diagram of another structure of a file breakpoint reentry apparatus in an embodiment of the present invention, as shown in fig. 5, in an embodiment, the apparatus further includes: a third replication module 05 to:
when the backup file is consistent with the output file, clearing the output file, and copying the job data from the job starting point to the COMMIT point in the backup file to the output file according to the COMMIT point stored in the database;
and the execution job module is used for starting to execute the job program from the COMMIT point and writing the job program into an output file when the copying is successful.
In one embodiment, a re-copy module 06 is further included for:
when the output file is copied to the backup file, the following operations are repeatedly executed until the copying is successful:
and clearing the backup file, and copying the output file to the backup file.
In one embodiment, the re-copy module 06 is further to:
when copying of the job data from the job start point to the COMMIT point in the backup file to the output file fails, the following operations are repeatedly performed until the copying succeeds:
and clearing the output file, and copying the job data of the backup file from the job starting point to the COMMIT point to the output file according to the COMMIT point stored in the database.
In one embodiment, when there is no COMMIT point stored in the database, the job program is executed from the job start point, writing to the output file.
The embodiment of the invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the file breakpoint reentry method when executing the computer program.
The embodiment of the invention also provides a computer readable storage medium, and the computer readable storage medium stores a computer program for executing the file breakpoint re-entry method.
In summary, the embodiment of the present invention provides: when the operation is re-promoted after the operation is interrupted, a backup file and an output file are obtained; when the backup file is inconsistent with the output file, emptying the backup file, and copying the output file to the backup file; when the copying is successful, clearing the output file, and copying the job data from the job starting point to the COMMIT point in the backup file to the output file according to the COMMIT point stored in the database; when the copying is successful, the operation program is executed from the COMMIT point, and the output file is written.
By copying the job data from the job start point to the COMMIT point in the backup file to the output file, it can be ensured that both the job program and the output file start from the COMMIT point when the job is restarted, achieving consistency of the job program and the processing location of the output file.
When the copying fails in the process of copying the output file to the backup file or copying the job data from the job starting point to the COMMIT point in the backup file to the output file, the automatic re-copying can be automatically carried out until the copying succeeds, so that the automatic re-backup after the backup failure is realized, and the data loss caused by manual intervention or backup failure is avoided.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and variations of the embodiment of the present invention may occur to those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A file breakpoint reentry method is characterized by comprising the following steps:
when the operation is re-promoted after the operation is interrupted, a backup file and an output file are obtained; the output file stores the job data from a job starting point to a job interruption point;
when the backup file is inconsistent with the output file, emptying the backup file, and copying the output file to the backup file;
when the copying is successful, clearing the output file, and copying the job data from the job starting point to the COMMIT point in the backup file to the output file according to the COMMIT point stored in the database;
when the copying is successful, the job program is executed from the COMMIT point, and the output file is written.
2. The method of claim 1, wherein upon a copy failure of the output file to the backup file, repeatedly performing the following operations until the copy is successful:
and clearing the backup file, and copying the output file to the backup file.
3. The method of claim 1, further comprising:
when the backup file is consistent with the output file, clearing the output file, and copying the job data from the job starting point to the COMMIT point in the backup file to the output file according to the COMMIT point stored in the database;
when the copying is successful, the job program is executed from the COMMIT point, and the output file is written.
4. The method of claim 1 or 3, wherein when copying of job data from a job start point to the COMMIT point in a backup file to an output file fails, the following operations are repeatedly performed until copying succeeds:
and clearing the output file, and copying the job data of the backup file from the job starting point to the COMMIT point to the output file according to the COMMIT point stored in the database.
5. The method as claimed in claim 1, wherein when the stored COMMIT point does not exist in the database, the job program is executed from a job start point, and the output file is written.
6. A file breakpoint reentry apparatus, comprising:
the file obtaining module is used for obtaining a backup file and an output file when the operation is restarted after the operation is interrupted; the output file stores the job data from a job starting point to a job interruption point;
the first copying module is used for emptying the backup file and copying the output file to the backup file when the backup file is inconsistent with the output file;
the second copying module is used for emptying the output file when the copying is successful, and copying the job data from the job starting point to the COMMIT point in the backup file to the output file according to the COMMIT point stored in the database;
and the execution job module is used for starting to execute the job program from the COMMIT point and writing the job program into an output file when the copying is successful.
7. The apparatus of claim 6, further comprising: a re-copy module to: when the output file is copied to the backup file, the following operations are repeatedly executed until the copying is successful:
and clearing the backup file, and copying the output file to the backup file.
8. The apparatus of claim 7, wherein the re-copy module is further to: when the backup file is consistent with the output file, clearing the output file, and copying the job data from the job starting point to the COMMIT point in the backup file to the output file according to the COMMIT point stored in the database;
and the execution job module is used for starting to execute the job program from the COMMIT point and writing the job program into an output file when the copying is successful.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 5 when executing the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for executing the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010587122.0A CN111737056A (en) | 2020-06-24 | 2020-06-24 | File breakpoint reentrant method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010587122.0A CN111737056A (en) | 2020-06-24 | 2020-06-24 | File breakpoint reentrant method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111737056A true CN111737056A (en) | 2020-10-02 |
Family
ID=72651689
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010587122.0A Pending CN111737056A (en) | 2020-06-24 | 2020-06-24 | File breakpoint reentrant method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111737056A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5907673A (en) * | 1996-09-03 | 1999-05-25 | Kabushiki Kaisha Toshiba | Checkpointing computer system having duplicated files for executing process and method for managing the duplicated files for restoring the process |
| CN104021043A (en) * | 2014-06-23 | 2014-09-03 | 中国银行股份有限公司 | Interruption reentry method and system of batch applications |
| CN105045679A (en) * | 2015-07-08 | 2015-11-11 | 安徽兆尹信息科技股份有限公司 | Database backup and recovery method for financial management system |
| CN105573859A (en) * | 2014-10-15 | 2016-05-11 | 中兴通讯股份有限公司 | Data recovery method and device of database |
| CN109445983A (en) * | 2018-08-28 | 2019-03-08 | 天阳宏业科技股份有限公司 | File backup method and file backup system |
-
2020
- 2020-06-24 CN CN202010587122.0A patent/CN111737056A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5907673A (en) * | 1996-09-03 | 1999-05-25 | Kabushiki Kaisha Toshiba | Checkpointing computer system having duplicated files for executing process and method for managing the duplicated files for restoring the process |
| CN104021043A (en) * | 2014-06-23 | 2014-09-03 | 中国银行股份有限公司 | Interruption reentry method and system of batch applications |
| CN105573859A (en) * | 2014-10-15 | 2016-05-11 | 中兴通讯股份有限公司 | Data recovery method and device of database |
| CN105045679A (en) * | 2015-07-08 | 2015-11-11 | 安徽兆尹信息科技股份有限公司 | Database backup and recovery method for financial management system |
| CN109445983A (en) * | 2018-08-28 | 2019-03-08 | 天阳宏业科技股份有限公司 | File backup method and file backup system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7386752B1 (en) | Using asset dependencies to identify the recovery set and optionally automate and/or optimize the recovery | |
| CN109032838B (en) | Automatic verification method for consistency of backup and recovery data of virtual machine | |
| CN108255576B (en) | Virtual machine live migration exception handling method and device and storage medium | |
| EP3474143B1 (en) | Method and apparatus for incremental recovery of data | |
| US8229892B2 (en) | Storage apparatus and data restoring method used therein | |
| US8095827B2 (en) | Replication management with undo and redo capabilities | |
| CN108664255B (en) | Software upgrading method and device | |
| CN114265603A (en) | System upgrading method and device based on asymmetric partition and electronic equipment | |
| CN111737056A (en) | File breakpoint reentrant method and device | |
| CN104331311A (en) | Upgrade package generating method and device | |
| CN113448978B (en) | Method and device for guaranteeing data consistency in same-name image file replacement operation | |
| CN116225779A (en) | Method and device for improving cache and data source data consistency based on pre-write log mechanism | |
| CN107544868B (en) | Data recovery method and device | |
| WO2021115117A1 (en) | File backup method and device, file recovery method and device, and file update method and device | |
| CA2299850C (en) | System and method for the management of computer software maintenance | |
| CN111324413B (en) | Data migration method and data migration management equipment | |
| CN111984472A (en) | Data snapshot method, device and related equipment | |
| JP2853527B2 (en) | Automatic file failure recovery system | |
| CN104572350A (en) | Method and device for processing metadata | |
| US20210247904A1 (en) | Using any-pit backups for retroactive backup compliance and hardening | |
| US12079094B2 (en) | Data backup method, data recovery method, and electronic equipment | |
| CN113708981B (en) | Method and system for repairing fault of cloud host system | |
| US20220327025A1 (en) | Smart automation of reliable differential backups of always on availability group databases to optimize the restore time | |
| US20210406139A1 (en) | True zero rto: planned failover | |
| JP2006293582A (en) | Automatic job rerun system |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201002 |
|
| RJ01 | Rejection of invention patent application after publication |