Data disaster recovery service and comprehensive monitoring system
Through the design of data disaster recovery services and comprehensive monitoring system, the problem of insufficient monitoring efforts in data backup of off-site disaster recovery systems is solved, and data authenticity and consistency management is realized, ensuring data stability and backup integrity.
Patent Information
- Application Number
- CN202411088251.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-09
- Publication Date
- 2025-01-07
AI Technical Summary
The data backup of existing off-site disaster recovery systems has insufficient monitoring efforts, resulting in insufficient authenticity and consistency of backup data. The long-term data accumulation has burdened the storage space and it is difficult to ensure the stability of the data backup process.
A data disaster recovery service and comprehensive monitoring system were designed, and data verification of remote disaster recovery system was checked through the data acquisition unit, storage and update unit realized data deletion consistency management, abnormal testing unit carried out data abnormality detection, and encrypted through the remote control unit and Decrypt the data to ensure the authenticity and consistency of the data.
It effectively ensures the stability of data in the off-site disaster recovery system, avoids the problems of data accumulation and backup mess, and ensures the integrity and reliability of the data backup process.
Smart Images

Figure CN119271455A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of data monitoring, and in particular to a data disaster recovery service and a comprehensive monitoring system. Background Art
[0002] Referring to a Chinese patent for a data disaster recovery service and integrated monitoring system (announcement number: CN103281208A, announcement date: 2013.09.04), this patent provides disaster recovery services for enterprises that need disaster recovery, greatly reducing the disaster recovery construction investment of each enterprise and providing enterprises with reliable disaster recovery support. The present invention also realizes the visualization of disaster recovery data. Users can not only see the storage location and occupied size of their data in the disaster recovery center, but also view the most recent data remote asynchronous replication time and snapshot time in real time. This system also facilitates the disaster recovery project management of the data disaster recovery service center, and meets the purpose of users understanding disaster recovery and the disaster recovery center promoting disaster recovery.
[0003] However, the existing off-site disaster recovery system data backup still has defects. Although it can provide good protection for the data, due to the lack of monitoring, the off-site disaster recovery system data is not checked in time, and the authenticity and consistency of the backup data are insufficient. In addition, long-term data accumulation will cause a large storage burden on the storage space. The data backup is messy, and the data is always in a backup but not read state. It is also difficult to ensure whether there is any damage during the data backup process, resulting in poor stability of the off-site disaster recovery system data. For this reason, the present invention proposes a data disaster recovery service and a comprehensive monitoring system to solve the above-mentioned problems. Summary of the invention
[0004] In view of the deficiencies of the prior art, the present invention provides a data disaster recovery service and a comprehensive monitoring system, which solves the problems mentioned in the above background technology.
[0005] To achieve the above objectives, the present invention is implemented through the following technical solutions: a data disaster recovery service and integrated monitoring system, comprising: Data collection unit: a first client sends basic information, and a second client is obtained according to the first client, and the second client is used to receive the basic information sent by the first client, wherein the basic information is remote disaster recovery system data; Storage update unit: the first client sends a data deletion instruction, performs a consistent operation on the second client according to the data deletion instruction, and sends a deletion feedback instruction according to the second client, prompting the first client whether to perform the consistent operation; Abnormal testing unit: The second client tests the data of the basic information and determines whether the basic information is abnormal based on the test result, and then the second client sends feedback information to the first client, wherein the specific method of the test is to extract the basic information.
[0006] As an improved technical solution, the specific manner in which the second client in the data acquisition unit receives the basic information sent by the first client is: S1: First, mark the basic information as Hj, where j is the type serial number of the basic information, then mark the location of the first client as OA, and the location of the second client as OB. The basic information Hj is located in the first client. At this time, the first client sends the basic information Hj to the second client; S2: Then mark the basic information obtained in the second client as SHj. At this time, check the data between the two. If Hj is consistent with SHj, the remote disaster recovery system data is successfully built. If Hj is inconsistent with SHj, the remote disaster recovery system data is failed.
[0007] As an improved technical solution, if Hj and SHj in S2 are inconsistent and the off-site disaster recovery system data construction fails, the difference data between Hj and SHj is marked and recorded as CHj, and then CHj is manually entered into the second client until CHj+Hj is consistent with SHj and the off-site disaster recovery system data construction is successful.
[0008] As an improved technical solution, the specific manner in which the second client in the storage update unit performs a consistent operation and the first client prompts whether to perform a consistent operation is: P1: First, the first client marks the data to be deleted as Gj, and then the second client receives the instruction from the first client, brings in the data Gj, and deletes the data that is consistent with it. At this time, the first client compares the updated basic data with the basic data in the second client, and completely deletes the data Gj if the data is consistent; P2: Then set the time threshold YT. In the second client, extract the data that exceeds the time threshold YT and mark it as Fj. Then send a deletion instruction to the first client and confirm the deletion of the data Fj. The first client refuses to retain the data Fj.
[0009] As an improved technical solution, if data inconsistency occurs in P1, the deletion operation of the data Gj is canceled. At this time, it is necessary to check the initial state of the first client basic data and the second client basic data, and then delete the data Gj after confirming that they are consistent.
[0010] As an improved technical solution, when the data Fj is retained in P2 after being rejected by the first client, the retention period of Fj is still the time threshold YT. After the time threshold YT is reached, the deletion feedback of the data Fj executes step P2 again.
[0011] As an improved technical solution, the specific method of testing the data of the basic information in the abnormality testing unit and determining whether the basic information is abnormal based on the test result is: M1: First, mark the data to be extracted as Kj, then extract the data Kj from the second client, and read the data Kj. After the data Kj is read correctly, the data Kj is stored, and it is determined that there is no abnormality in the second client; M2: Then set the reading algorithm of data Kj, mark the read data as Ly, according to the principle of binary division, when j is an odd number, it is j, when j is an even number, it is j+1, the first reading , read the second time ..., until the nth read , until the nth reading is normal, the test process is completed.
[0012] As an improved technical solution, the data Kj is read in M1, and after the data Kj is read correctly, when the data Kj is stored, the read data is sent to the first client to check whether they are consistent.
[0013] As an improved technical solution, the system further includes a remote control unit: the second client data is encrypted, and after the first client decrypts the second client data, the first client can remotely read the data information of the second client.
[0014] The present invention provides a data disaster recovery service and integrated monitoring system. Compared with the prior art, it has the following beneficial effects: This data disaster recovery service and integrated monitoring system builds off-site disaster recovery system data and verifies the data between the two to ensure the authenticity and consistency of the backup data. At the same time, it actively deletes data from the first client and passively deletes data from the second client, and obtains the permission of the first client. It can process useless data in a timely manner to avoid the storage burden caused by data accumulation and the problem of messy data backup. In conjunction with data anomaly testing, it effectively ensures the stability of the off-site disaster recovery system data. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 A block diagram of a data disaster recovery service and integrated monitoring system shown in an embodiment of the present application; Figure 2 This is a schematic diagram of the structure of an electronic device shown in an embodiment of the present application. DETAILED DESCRIPTION
[0016] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0017] See also Figure 1-Figure 2 , the embodiment of the present invention provides four technical solutions: Example
[0018] A data disaster recovery service and integrated monitoring system, comprising: Data collection unit: The first client sends basic information, and the second client is obtained according to the first client. The second client is used to receive the basic information sent by the first client, wherein the basic information is the remote disaster recovery system data; the specific manner in which the second client in the data collection unit receives the basic information sent by the first client is: S1: First, mark the basic information as Hj, where j is the type serial number of the basic information, then mark the location of the first client as OA, and the location of the second client as OB. The basic information Hj is located in the first client. At this time, the first client sends the basic information Hj to the second client; S2: Then mark the basic information obtained in the second client as SHj, and then check the data between the two. If Hj is consistent with SHj, the remote disaster recovery system data is successfully constructed. If Hj is inconsistent with SHj, the remote disaster recovery system data construction fails. In S2, if Hj is inconsistent with SHj and the remote disaster recovery system data construction fails, the difference data between Hj and SHj is marked as CHj, and then CHj is manually entered into the second client until CHj+Hj is consistent with SHj, and the remote disaster recovery system data is successfully constructed.
[0019] Combined with actual analysis, taking the first client as an enterprise and the second client as an off-site department of the enterprise as an example, the enterprise's data information is sent to the off-site department of the enterprise in the form of a backup. The two are in different locations, and when earthquakes, fires, etc. occur, they are not affected at the same time as much as possible. At this time, the enterprise's data information will be checked with the off-site department of the enterprise after the backup. If they are consistent, the off-site disaster recovery system data is successfully built. If there is an inconsistency, the inconsistent data will be manually entered until the off-site disaster recovery system data is successfully built.
[0020] Storage update unit: the first client sends a data deletion instruction, performs a consistent operation on the second client according to the data deletion instruction, and sends a deletion feedback instruction according to the second client, so that the first client is prompted whether to perform the consistent operation; the specific manner in which the second client performs the consistent operation and the first client is prompted whether to perform the consistent operation in the storage update unit is: P1: First, the first client marks the data to be deleted as Gj, and then the second client receives the instruction of the first client, brings in the data Gj, and deletes the data consistent with it. At this time, the first client compares the updated basic data with the basic data in the second client. If the data is consistent, the data Gj is completely deleted. If there is data inconsistency in P1, the deletion operation of the data Gj is revoked. At this time, it is necessary to check the initial state of the first client basic data and the second client basic data. After confirming that they are consistent, the data Gj can be deleted.
[0021] Based on actual analysis, the enterprise will send the data instructions that need to be deleted to the remote department of the enterprise. The remote department of the enterprise will receive the information and execute the above command, and then check the deleted content with the enterprise data. If the two are consistent, the data will be completely deleted according to the instructions. If the data is inconsistent, the instruction needs to be revoked, and then check whether the data of the initial state of the enterprise and the remote department of the enterprise are consistent, and then re-operate after confirming that they are consistent.
[0022] P2: Then set the time threshold YT, extract the data that exceeds the time threshold YT in the second client, mark it as Fj, and give a deletion instruction to the first client. The first client confirms the deletion of data Fj and refuses to retain data Fj. In P2, when data Fj is retained after the first client refuses, the retention period of Fj is still the time threshold YT. After reaching the time threshold YT, the deletion feedback of data Fj executes step P2 again.
[0023] Combined with actual analysis, taking the time threshold YT as 1 year as an example, after 1 year, the data of the enterprise's off-site departments will be fed back to the enterprise, prompting whether the data older than one year needs to be deleted. The enterprise confirms that it can be deleted, and the enterprise's off-site department deletes the data. If the enterprise refuses, the data will be retained and the time threshold YT will be repeated. After 1 year, the deletion feedback will be prompted again to prompt the enterprise whether to delete the data.
[0024] Abnormal test unit: The second client tests the data of the basic information and determines whether the basic information is abnormal based on the test results. Then the second client sends feedback information to the first client. The specific method of testing is to extract the basic information. The specific method of testing the data of the basic information and determining whether the basic information is abnormal based on the test results is: M1: First, mark the data to be extracted as Kj, then extract the data Kj from the second client, and read the data Kj. After the data Kj is read correctly, the data Kj is stored, and it is determined that there is no abnormality in the second client; read the data Kj in M1. After the data Kj is read correctly, the data Kj is stored, and the read data is sent to the first client to check whether it is consistent.
[0025] M2: Then set the reading algorithm of data Kj, mark the read data as Ly, according to the principle of binary division, when j is an odd number, it is j, when j is an even number, it is j+1, the first reading , read the second time ..., until the nth read , until the nth reading is normal, the test process is completed.
[0026] Combined with actual analysis, taking j as 101 as an example, the first read , specifically K51, the second read , specifically K26, the third read , specifically K14, the fourth read , specifically K8, the fifth read , specifically K5, the sixth read , specifically K3, the seventh read , specifically K2. Example
[0027] The method is implemented on the basis of the first embodiment and differs from the first embodiment in that it further includes a remote control unit: the second client data is encrypted, and after the first client decrypts the second client data, the first client can remotely read the data information of the second client.
[0028] Based on actual analysis, the off-site departments of the enterprise encrypt the data stored off-site. The enterprise can read the data after decryption, and can see the storage location and size of its data in the disaster recovery center. Example
[0029] Compared with the first and second embodiments, the technical solution of this embodiment is to combine the solutions of the first and second embodiments for implementation. Example
[0030] A data disaster recovery service and integrated monitoring system, comprising: Data collection unit: a first client sends basic information, and a second client is obtained according to the first client, and the second client is used to receive the basic information sent by the first client, wherein the basic information is remote disaster recovery system data; Storage update unit: the first client sends a data deletion instruction, performs a consistent operation on the second client according to the data deletion instruction, and sends a deletion feedback instruction according to the second client, prompting the first client whether to perform the consistent operation; Abnormality testing unit: the second client tests the data of the basic information, and determines whether the basic information is abnormal according to the test result, and then the second client sends feedback information to the first client, wherein the specific method of the test is to extract the basic information; Remote control unit: The second client data is encrypted. After the first client decrypts the second client data, the first client can remotely read the data information of the second client.
[0031] Meanwhile, the contents not described in detail in this specification belong to the prior art known to those skilled in the art.
[0032] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.
[0033] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.
[0034] Corresponding to the aforementioned application function implementation method embodiment, the present application also provides an electronic device and corresponding embodiments.
[0035] See also Figure 2 , the electronic device 1000 includes a memory 1010 and a processor 1020 .
[0036] The processor 1020 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.
[0037] The memory 1010 may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage devices. Among them, ROM can store static data or instructions required by the processor 1020 or other modules of the computer. The permanent storage device may be a readable and writable storage device. The permanent storage device may be a non-volatile storage device that does not lose the stored instructions and data even after the computer is powered off. In some embodiments, the permanent storage device uses a large-capacity storage device (such as a magnetic or optical disk, flash memory) as a permanent storage device. In some other embodiments, the permanent storage device may be a removable storage device (such as a floppy disk, optical drive). The system memory may be a readable and writable storage device or a volatile readable and writable storage device, such as a dynamic random access memory. The system memory may store some or all instructions and data required by the processor at runtime. In addition, the memory 1010 may include any combination of computer-readable storage media, including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and disks and / or optical disks may also be used. In some embodiments, the memory 1010 may include a readable and / or writable removable storage device, such as a laser disc (CD), a read-only digital versatile disc (such as a DVD-ROM, a double-layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (such as an SD card, a mini SD card, a Micro-SD card, etc.), a magnetic floppy disk, etc. The computer-readable storage medium does not include carrier waves and transient electronic signals transmitted wirelessly or wired.
[0038] The memory 1010 stores executable codes, and when the executable codes are processed by the processor 1020 , the processor 1020 can execute part or all of the methods described above.
[0039] The scheme of the present application has been described in detail above with reference to the accompanying drawings. In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. Those skilled in the art should also be aware that the actions and modules involved in the description are not necessarily required for the present application. In addition, it can be understood that the steps in the method of the embodiment of the present application can be adjusted in order, merged and deleted according to actual needs, and the modules in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.
[0040] In addition, the method according to the present application may also be implemented as a computer program or a computer program product, which includes computer program code instructions for executing some or all of the steps in the above method of the present application.
[0041] Alternatively, the present application can also be implemented as a non-temporary machine-readable storage medium (or computer-readable storage medium, or machine-readable storage medium) on which executable code (or computer program, or computer instruction code) is stored. When the executable code (or computer program, or computer instruction code) is executed by a processor of an electronic device (or electronic device, server, etc.), the processor executes part or all of the steps of the above-mentioned method according to the present application.
[0042] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the application herein may be implemented as electronic hardware, computer software, or combinations of both.
[0043] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system and method according to multiple embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a part of a module, a program segment or a code, and the part of the module, the program segment or the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or the flow chart, and the combination of the square boxes in the block diagram and / or the flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0044] The embodiments of the present application have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.
Claims
1. A data disaster recovery service and integrated monitoring system, characterized in that: include: Data collection unit: a first client sends basic information, and a second client is obtained according to the first client, and the second client is used to receive the basic information sent by the first client, wherein the basic information is remote disaster recovery system data; Storage update unit: the first client sends a data deletion instruction, performs a consistent operation on the second client according to the data deletion instruction, and sends a deletion feedback instruction according to the second client, prompting the first client whether to perform the consistent operation; Abnormal testing unit: The second client tests the data of the basic information and determines whether the basic information is abnormal based on the test result, and then the second client sends feedback information to the first client, wherein the specific method of the test is to extract the basic information.
2. A data disaster recovery service and integrated monitoring system according to claim 1, characterized in that: The specific method for the second client in the data collection unit to receive the basic information sent by the first client is: S1: First, mark the basic information as Hj, where j is the type serial number of the basic information, then mark the location of the first client as OA, and the location of the second client as OB. The basic information Hj is located in the first client. At this time, the first client sends the basic information Hj to the second client; S2: Then mark the basic information obtained in the second client as SHj. At this time, check the data between the two. If Hj is consistent with SHj, the remote disaster recovery system data is successfully built. If Hj is inconsistent with SHj, the remote disaster recovery system data is failed.
3. A data disaster recovery service and integrated monitoring system according to claim 2, characterized in that: If Hj and SHj in S2 are inconsistent and the off-site disaster recovery system data construction fails, the difference data between Hj and SHj is marked as CHj, and then CHj is manually entered into the second client until CHj+Hj is consistent with SHj and the off-site disaster recovery system data construction is successful.
4. A data disaster recovery service and integrated monitoring system according to claim 1, characterized in that: The specific manner in which the second client in the storage update unit performs the consistent operation and the first client prompts whether to perform the consistent operation is: P1: First, the first client marks the data to be deleted as Gj, and then the second client receives the instruction from the first client, brings in the data Gj, and deletes the data that is consistent with it. At this time, the first client compares the updated basic data with the basic data in the second client, and completely deletes the data Gj if the data is consistent; P2: Then set the time threshold YT. In the second client, extract the data that exceeds the time threshold YT and mark it as Fj. Then send a deletion instruction to the first client and confirm the deletion of the data Fj. The first client refuses to retain the data Fj.
5. A data disaster recovery service and integrated monitoring system according to claim 4, characterized in that: If data inconsistency occurs in P1, the deletion operation of the data Gj is canceled. At this time, the first client basic data and the second client basic data in the initial state need to be checked, and the deletion operation of the data Gj can be performed after confirming that they are consistent.
6. A data disaster recovery service and integrated monitoring system according to claim 4, characterized in that: When the data Fj is retained after being rejected by the first client in P2, the retention period of Fj is still the time threshold YT. After the time threshold YT is reached, the deletion feedback of the data Fj executes step P2 again.
7. A data disaster recovery service and integrated monitoring system according to claim 1, characterized in that: The specific method of testing the data of the basic information in the abnormality testing unit and determining whether the basic information is abnormal according to the test result is: M1: First, mark the data to be extracted as Kj, then extract the data Kj from the second client, and read the data Kj. After the data Kj is read correctly, the data Kj is stored, and it is determined that there is no abnormality in the second client; M2: Then set the reading algorithm of data Kj, mark the read data as Ly, according to the principle of binary division, when j is an odd number, it is j, when j is an even number, it is j+1, the first reading , read the second time ..., until the nth read , until the nth reading is normal, the test process is completed.
8. A data disaster recovery service and integrated monitoring system according to claim 7, characterized in that: The data Kj is read in the M1. After the data Kj is read correctly, when the data Kj is stored, the read data is sent to the first client to check whether they are consistent.
9. A data disaster recovery service and integrated monitoring system according to claim 1, characterized in that: The remote control unit also includes: the second client data is encrypted, and after the first client decrypts the second client data, the first client can remotely read the data information of the second client.
Citation Information
Patent Citations
Data disaster backup service and integrated monitoring system
CN103281208A