CN109426588B - Method and system for realizing data protection and data distribution processing module - Google Patents
Method and system for realizing data protection and data distribution processing module Download PDFInfo
- Publication number
- CN109426588B CN109426588B CN201710750080.6A CN201710750080A CN109426588B CN 109426588 B CN109426588 B CN 109426588B CN 201710750080 A CN201710750080 A CN 201710750080A CN 109426588 B CN109426588 B CN 109426588B
- Authority
- CN
- China
- Prior art keywords
- data
- volume
- backup
- storage
- 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; 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/1448—Management of the data involved in backup or backup restore
-
- 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
-
- 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
- G06F11/1461—Backup scheduling policy
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
A method for realizing data protection is applied to a storage system, and the storage system comprises: a data distribution processing module and one or more storage volumes; the method comprises the following steps: after receiving the data writing request, the data distribution processing module determines a storage volume to be written in by the data indicated by the data writing request; determining at least one of a backup volume and a disaster tolerance volume to which the data indicated by the data writing request is to be written according to the source information of the data writing request and the backup disaster tolerance attribute of the storage volume to be written; and respectively writing the data indicated by the data writing request into at least one of the backup volume and the disaster recovery volume which are deployed corresponding to the storage volume and the storage volume. Therefore, the backup and disaster recovery implementation can be simultaneously supported aiming at the same storage volume on the storage system.
Description
Technical Field
The present invention relates to the field of storage, and in particular, to a method and a system for implementing data protection, and a data distribution processing module.
Background
Disaster Recovery (DR) and Backup (BR, backup) are two important methods for data protection in the storage field. The disaster recovery means that one or more sets of the same data disaster recovery systems are established in different places, and when the storage system suffers from various irresistible natural disasters such as natural disasters, war, earthquake and the like, the disaster recovery systems can maintain the data availability and the service continuity. The backup is a backup system for backing up data of a storage system in a local place, and because the backup system is in the local place, the data synchronization speed is fast compared with that in a different place, but the data cannot be damaged by natural disasters such as natural disasters. The local backup system can play a good role in protecting data damage caused by virus attack, manual misoperation, software errors and the like, and the remote disaster recovery system can play a critical role in local data damage caused by ineffectiveness.
For some important data, the disaster recovery system needs to be deployed in a remote place, and meanwhile, local backup needs to be carried out. When the storage system is damaged by files or data due to manual misoperation or virus invasion, local different backup point data can be used for quick recovery. Currently, most storage devices can provide backup and disaster recovery functions, however, there are two limitations:
one situation is that a storage device can only support data synchronization in one direction, and cannot distribute data to two or more sets of other storage devices at the same time;
in another situation, when data on one set of backup or disaster recovery device is synchronized to the storage device in the opposite direction, the data cannot be synchronously written to other backup or disaster recovery devices, which causes inconsistency between the data on the storage device and the data on the backup or disaster recovery device, and if the data is required to be consistent again, only deployment and data synchronization can be performed again, thereby greatly reducing the availability of the backup and disaster recovery system.
Disclosure of Invention
The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.
The embodiment of the application provides a method and a system for realizing data protection and a data distribution processing module, which can simultaneously support backup and disaster recovery for the same storage volume on a storage system.
In a first aspect, an embodiment of the present application provides a method for implementing data protection, where the method is applied to a storage system, where the storage system includes: a data distribution processing module and one or more storage volumes, the method comprising:
after receiving a data writing request, a data distribution processing module determines a storage volume to be written in by data indicated by the data writing request;
determining at least one of a backup volume and a disaster tolerance volume to which the data indicated by the data writing request is to be written according to the source information of the data writing request and the backup disaster tolerance attribute of the storage volume to be written;
and writing the data indicated by the data writing request into at least one of a backup volume and a disaster recovery volume which are deployed corresponding to the storage volume and the storage volume respectively.
In a second aspect, an embodiment of the present application provides a data distribution processing module, which is applied to a storage system, where the storage system includes one or more storage volumes; the data distribution processing module comprises: the system comprises a volume management unit, a data processing unit and a data distribution unit;
the volume management unit is used for recording backup disaster recovery attributes of one or more storage volumes of the storage system;
the data processing unit is used for determining a storage volume to be written in the data indicated by the data writing request after receiving the data writing request; determining at least one of a backup volume and a disaster tolerance volume to which the data indicated by the data writing request is to be written according to the source information of the data writing request and the backup disaster tolerance attribute of the storage volume to be written;
and the data distribution unit is used for writing the data indicated by the data writing request into at least one of a backup volume and a disaster recovery volume which are deployed corresponding to the storage volume and the storage volume respectively.
In a third aspect, an embodiment of the present application provides a system for implementing data protection, including: a storage system, a backup system and a disaster recovery system; the storage system comprises a data distribution processing module and one or more storage volumes, the backup system comprises one or more backup volumes deployed corresponding to the storage volumes, and the disaster recovery system comprises one or more disaster recovery volumes deployed corresponding to the storage volumes;
the data distribution processing module is used for determining a storage volume to be written in the data indicated by the data writing request after receiving the data writing request; determining at least one of a backup volume and a disaster tolerance volume to which the data indicated by the data writing request is to be written according to the source information of the data writing request and the backup disaster tolerance attribute of the storage volume to be written; and writing the data indicated by the data writing request into at least one of a backup volume and a disaster recovery volume which are deployed corresponding to the storage volume and the storage volume respectively.
In a fourth aspect, an embodiment of the present application provides an apparatus, including a memory and a processor, where the memory is used to store a program for implementing data protection, and the program, when executed by the processor, implements the steps of the method for implementing data protection of the first aspect.
In a fifth aspect, an embodiment of the present application provides a computer-readable medium, which stores a program for implementing data protection, and when the program is executed by the processor, the program implements the steps of the method for implementing data protection according to the first aspect.
In the embodiment of the application, after a data distribution processing module included in a storage system receives a data writing request, a storage volume to be written in by data indicated by the data writing request is determined; determining at least one of a backup volume and a disaster tolerance volume to which the data is to be written, which is indicated by the data writing request, according to the source information of the data writing request and the backup disaster tolerance attribute of the storage volume to be written; and respectively writing the data indicated by the data writing request into at least one of the backup volume and the disaster recovery volume which are deployed corresponding to the storage volume and the storage volume. Therefore, the method for realizing backup and disaster recovery can be provided for the same storage volume on the storage system at the same time. Moreover, in the embodiment of the application, multi-time point backup data of the storage volume are provided locally, disaster recovery data of the storage volume are generated in different places, and when the backup data of a certain local time point is selected for recovery, the disaster recovery data in different places can be updated simultaneously, so that the backup and disaster recovery data can be ensured to be available in real time. Moreover, in the embodiment of the application, when the remote disaster recovery data is selected for recovery, the local backup data can be updated simultaneously, so that the backup and disaster recovery data can be ensured to be available in real time.
Other aspects will be apparent upon reading and understanding the attached figures and detailed description.
Drawings
Fig. 1 is a schematic diagram of a system for implementing data protection according to an embodiment of the present application;
fig. 2 is a flowchart of a method for implementing data protection according to an embodiment of the present application;
fig. 3 is a schematic diagram of a data distribution processing module according to an embodiment of the present application;
FIG. 4 is an exemplary schematic diagram of an embodiment of the present application;
fig. 5 is a schematic diagram of a backup implementation provided in the embodiment of the present application;
FIG. 6 is another exemplary schematic diagram of an embodiment of the present application;
FIG. 7 is a diagram illustrating an example of a deployment of a system for implementing data protection according to an embodiment of the present application;
fig. 8 is a schematic diagram of a device for implementing the method for protecting data according to the embodiment of the present application.
Detailed Description
The embodiments of the present application will be described in detail below with reference to the accompanying drawings, and it should be understood that the embodiments described below are only used for illustrating and explaining the present application and are not used for limiting the present application.
Fig. 1 is a schematic diagram of a system for implementing data protection according to an embodiment of the present application. As shown in fig. 1, the system for implementing data protection provided by this embodiment includes: a storage system, a backup system and a disaster recovery system; the storage system comprises a data distribution processing module and one or more storage volumes, the backup system comprises one or more backup volumes deployed corresponding to the storage volumes, and the disaster recovery system comprises one or more disaster recovery volumes deployed corresponding to the storage volumes. Illustratively, one or more backup volumes and one or more disaster recovery volumes may be deployed for a storage volume. However, this is not limited in this application.
In this embodiment, the data distribution processing module is configured to determine, after receiving the data writing request, a storage volume to which data indicated by the data writing request is to be written; determining at least one of a backup volume and a disaster-tolerant volume to which the data indicated by the data writing request is to be written according to the source information of the data writing request and the backup disaster-tolerant attribute of the storage volume to be written; and respectively writing the data indicated by the data writing request into at least one of the backup volume and the disaster recovery volume which are deployed corresponding to the storage volume and the storage volume.
The data distribution processing module can record backup disaster tolerance attributes of each storage volume, and the backup disaster tolerance attributes of one storage volume include information about whether a backup and a disaster tolerance are deployed corresponding to the storage volume and about a backup volume and a disaster tolerance volume deployed corresponding to the storage volume.
Exemplarily, the data distribution processing module is configured to determine, when it is determined that the data write request is from the host according to source information of the data write request, a backup volume and a disaster recovery volume to which data indicated by the data write request is to be written according to a backup disaster recovery attribute of a storage volume to be written; and respectively writing the data indicated by the data writing request into the storage volume to be written, the disaster recovery volume and the backup volume which are deployed corresponding to the storage volume.
Illustratively, when the data indicated by the data writing request is successfully written into the storage volume, the backup volume and the disaster recovery volume deployed corresponding to the storage volume, the data distribution processing module returns a data writing success response to the host;
and when the data indicated by the data writing request fails to be written into the storage volume, the backup volume and the disaster recovery volume which are deployed corresponding to the storage volume, the data distribution processing module returns a data writing failure response to the host.
Exemplarily, the data distribution processing module is configured to determine, when it is determined that the data write request is from a backup volume according to source information of the data write request, a disaster recovery volume to which data indicated by the data write request is to be written according to a backup disaster recovery attribute of a storage volume to be written; and respectively writing the data indicated by the data writing request into the storage volume and the disaster recovery volume deployed corresponding to the storage volume.
Exemplarily, the data distribution processing module is configured to determine, when it is determined that the data write request is from the disaster recovery volume according to the source information of the data write request, a backup volume to which data indicated by the data write request is to be written according to a backup disaster recovery attribute of a storage volume to be written; and respectively writing the data indicated by the data writing request into the storage volume and the backup volume deployed corresponding to the storage volume.
In this embodiment, the data distribution processing module may write data issued by the host into the storage volume, the backup volume, and the disaster recovery volume synchronously, and may also reversely restore data on the backup volume to the storage volume and the disaster recovery volume, and reversely restore data on the disaster recovery volume to the storage volume and the backup volume, thereby ensuring consistency of data on the storage volume, the backup volume, and the disaster recovery volume, and ensuring real-time availability of backup and disaster recovery data.
Fig. 2 is a flowchart of a method for implementing data protection according to an embodiment of the present application. As shown in fig. 2, the method for implementing data protection provided by this embodiment is applied to a storage system, where the storage system includes a data distribution processing module and one or more storage volumes; the method provided by the embodiment comprises the following steps:
s201, after receiving a data writing request, a data distribution processing module determines a storage volume to be written in by data indicated by the data writing request;
s202, determining at least one of a backup volume and a disaster recovery volume to which data is to be written, which is indicated by the data writing request, according to the source information of the data writing request and the backup disaster recovery attribute of the storage volume to be written;
and S203, respectively writing the data indicated by the data writing request into at least one of the backup volume and the disaster recovery volume deployed corresponding to the storage volume and the storage volume.
Illustratively, a data write request may carry data to be written to the storage system, information indicating which storage volume on the storage system the carried data is written to, and origin information indicating who originated the data write request.
Illustratively, S202 may include: when the data writing request is determined to come from the host according to the source information of the data writing request, determining a backup volume to be written in and a disaster recovery volume to be written in of the data indicated by the data writing request according to the backup disaster recovery attribute of the storage volume to be written in;
s203 may include: and respectively writing the data indicated by the data writing request into the storage volume, the backup volume deployed corresponding to the storage volume and the disaster recovery volume.
After S203, the method of this embodiment may further include:
when the data indicated by the data writing request is successfully written into the storage volume, the backup volume and the disaster recovery volume which are deployed corresponding to the storage volume, a data writing success response is returned to the host;
and when the data indicated by the data writing request fails to be written into the storage volume, the backup volume and the disaster recovery volume which are deployed corresponding to the storage volume, returning a data writing failure response to the host.
In other words, the successful data writing is only confirmed when the data issued by the host computer is successfully written into the storage volume, the backup volume and the disaster recovery volume, so that the consistency of the data on the storage volume, the backup volume and the disaster recovery volume is ensured.
Illustratively, S202 may include: when the data writing request is determined to be from a backup volume according to the source information of the data writing request, determining a disaster recovery volume to which the data indicated by the data writing request is to be written according to the backup disaster recovery attribute of the storage volume to be written;
s203 may include: and respectively writing the data indicated by the data writing request into the storage volume and the disaster recovery volume deployed corresponding to the storage volume.
When the data indicated by the data writing request is successfully written into the storage volume and the disaster recovery volume deployed corresponding to the storage volume, the data writing is confirmed to be successful; otherwise, the data write is considered to fail.
Illustratively, S202 may include: when the data writing request is determined to be from the disaster recovery volume according to the source information of the data writing request, determining a backup volume to be written in by the data indicated by the data writing request according to the backup disaster recovery attribute of the storage volume to be written in;
s203 may include: and respectively writing the data indicated by the data writing request into the storage volume and the backup volume deployed corresponding to the storage volume.
When the data indicated by the data writing request is successfully written into the storage volume and the backup volume deployed corresponding to the storage volume, the data writing is confirmed to be successful; otherwise, the data write is considered to fail.
Fig. 3 is a schematic diagram of a data distribution processing module according to an embodiment of the present application. As shown in fig. 3, the data distribution processing module provided in this embodiment is applied to a storage system, where the storage system includes one or more storage volumes; the data distribution processing module provided in this embodiment includes: a volume management unit 301, a data processing unit 302, and a data distribution unit 303;
a volume management unit 301, configured to record backup disaster recovery attributes of one or more storage volumes of a storage system;
a data processing unit 302, configured to determine a storage volume to which data indicated by a data write request is to be written after receiving the data write request; determining at least one of a backup volume and a disaster tolerance volume to which the data is to be written, which is indicated by the data writing request, according to the source information of the data writing request and the backup disaster tolerance attribute of the storage volume to be written;
a data distributing unit 303, configured to write the data indicated by the data writing request into at least one of the backup volume and the disaster recovery volume deployed corresponding to the storage volume to be written and the storage volume to be written, respectively.
Illustratively, the data processing unit 302 is configured to, when determining that the data write request is from the host according to the source information of the data write request, determine a backup volume and a disaster recovery volume to which the data indicated by the data write request is to be written according to the backup disaster recovery attribute of the storage volume to be written;
a data distributing unit 303, configured to write the data indicated by the data writing request into the storage volume, the disaster recovery volume and the backup volume that are deployed corresponding to the storage volume, respectively.
Illustratively, the data processing unit 302 is configured to, when determining that the data write request is from a backup volume according to the source information of the data write request, determine a disaster recovery volume to which the data indicated by the data write request is to be written according to the backup disaster recovery attribute of the storage volume to be written;
a data distributing unit 303, configured to write the data indicated by the data writing request into the storage volume to be written and the disaster recovery volume deployed for the storage volume to be written, respectively.
Illustratively, the data processing unit 302 is configured to, when determining that the data write request is from a disaster-tolerant volume according to the source information of the data write request, determine a backup volume to which data indicated by the data write request is to be written according to a backup disaster-tolerant attribute of a storage volume to be written;
the data distributing unit 303 is configured to write the data indicated by the data writing request into the storage volume to be written and the backup volume deployed for the storage volume to be written, respectively.
Illustratively, the data processing unit 302 is further configured to, when data indicated by the data writing request is successfully written into the storage volume, the backup volume and the disaster recovery volume deployed corresponding to the storage volume, return a data writing success response to the host; and when the data indicated by the data writing request fails to be written into the storage volume, the backup volume and the disaster recovery volume which are deployed corresponding to the storage volume, returning a data writing failure response to the host.
The present application is explained below by way of example.
Fig. 4 is an exemplary schematic diagram of an embodiment of the present application. As shown in fig. 4, a data distribution processing module is arranged inside the storage system, and is used for splitting the data write request. The data distribution processing module comprises a volume management unit, a data processing unit and a data distribution unit. The volume management unit is used for recording backup disaster recovery attributes of storage volumes in the storage system, wherein information of whether the storage volumes deploy backup and disaster recovery volumes and deployed backup and disaster recovery volumes is recorded. The data processing unit may determine, according to information carried in a data writing request received from the host, a storage volume to which data carried in the data writing request is to be written, and split the data writing request into a data writing request of a backup volume and a data writing request of a disaster recovery volume according to a backup disaster recovery attribute of the storage volume. The data distribution unit writes the data indicated by the data writing request into the backup volume and the disaster recovery volume respectively, and the data distribution unit can determine whether to write the data into the storage volume according to the success or failure of the data writing of the backup volume and the disaster recovery volume so as to ensure the consistency of the three data.
Fig. 5 is a schematic diagram of a backup implementation provided in the embodiment of the present application. As shown in FIG. 5, a backup volume may be created on a local backup system, the size of the backup volume being consistent with the size of the storage volume on the storage system. And carrying out full synchronization for the first time, wherein all subsequent synchronizations adopt an incremental synchronization mode, and a snapshot is created for the backup volume after each synchronization, so that a data backup set with different time points is generated for the storage volume.
The implementation flow for generating a multi-point-in-time backup for a storage volume is as follows:
firstly, when a backup strategy is deployed for a storage volume, a backup volume with the same size is created on a backup system, a backup relation between the storage volume and the backup volume is established, a bitmap representing data change of a source volume is distributed for the storage volume, and a data synchronization strategy is set;
at the second time T0, the storage volume carries out full data synchronization on the backup volume for the first time, namely, the data of the storage volume is completely synchronized to the backup volume, after the synchronization is completed, a snapshot S0 is created for the backup volume, and a bitmap of the storage volume is removed, wherein S0 is effective data at the time T0 of the storage volume;
thirdly, the change of each block of data on the storage volume is recorded in a bitmap, data synchronization is needed again at the moment of T1 according to a set synchronization strategy, and only incremental data marked as 1 in the bitmap needs to be synchronized to the backup volume at the moment; after synchronization is completed, clearing the bitmap and creating another snapshot S1 for the backup volume, wherein the S1 is the effective data of the storage volume T1 at the moment;
fourthly, by analogy, backup data at different time points can be generated for the storage volume according to the data synchronization strategy.
When data on a storage volume is damaged and abnormal due to human misoperation or other reasons at a certain moment, for example, a file is deleted by mistake, all backup time points on a local backup volume can be inquired, and a latest backup point is selected for data recovery.
Fig. 6 is another exemplary schematic diagram of an embodiment of the present application. As shown in fig. 6, the backup data S1 at the time T1 is selected to be restored in reverse to the storage volume. In this embodiment, a backup volume initiates a data write request, where the data to be restored to a storage volume, information of the storage volume to which the data is to be written, and source information are carried, and the source information may be used to indicate that the data write request is from the backup volume or a backup system in which the backup volume is located; the data processing unit on the storage system can determine a storage volume of data to be written according to the received data writing request, and determine a disaster recovery volume deployed corresponding to the storage volume according to the backup disaster recovery attribute of the storage volume, and then the data distribution unit can only write the data into the disaster recovery volume and the storage volume synchronously without writing the backup volume.
Fig. 7 is a deployment diagram of a system for implementing data protection according to an embodiment of the present application. As shown in fig. 7, the disaster recovery backup management platform is interconnected with the storage center and the disaster recovery center via a network, performs data configuration and deployment on backup and disaster recovery, sets a disaster recovery and backup policy, monitors the state of the storage center in real time, and performs backup recovery or disaster recovery switching. The user can deploy applications such as a virtual machine cluster and a database cluster in the storage center, one or more backup systems can be configured for each set of storage system of the applications, and one set of disaster recovery system can be deployed in the remote disaster recovery center.
Fig. 8 is a schematic diagram of a device for implementing the method for protecting data according to this embodiment. As shown in fig. 8, the apparatus 800 of the present embodiment includes: a memory 804 and a processor 802. Those skilled in the art will appreciate that the configuration of the device illustrated in fig. 8 does not constitute a limitation of the device 800, and that the device 800 may include more or fewer components than illustrated, or some components may be combined, or a different arrangement of components.
The processor 802 may include, but is not limited to, a processing device such as a Microprocessor (MCU) or a Programmable logic device (FPGA). The memory 804 may be used to store software programs and modules of application software, such as program instructions or modules corresponding to the method for implementing data protection in the embodiment, and the processor 802 executes various functional applications and data processing by running the software programs and modules stored in the memory 804, that is, implements the method for implementing data protection in the embodiment. The memory 804 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 804 can further include memory located remotely from the processor 802, which can be connected to the device 800 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The apparatus 800 may further include a communication unit 806; the communication unit 806 may receive or transmit data via a network. In one example, the communication unit 806 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
In addition, an embodiment of the present application further provides a computer readable medium, in which a program for implementing data protection is stored, and when the program is executed by a processor, the program implements the steps of the method for implementing data protection.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, or suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software can be distributed on machine-readable media (e.g., computer-readable media), which can include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
The foregoing shows and describes the principles and features of the present application, together with the advantages thereof. The present application is not limited to the above-described embodiments, and the embodiments and descriptions are only illustrative of the principles of the present application, and various changes and modifications can be made without departing from the spirit and scope of the present application, and these changes and modifications are intended to fall within the scope of the present application as claimed.
Claims (15)
1. A method for realizing data protection is applied to a storage system, and the storage system comprises: a data distribution processing module and one or more storage volumes, the method comprising:
after receiving a data writing request, a data distribution processing module determines a storage volume to be written in by data indicated by the data writing request;
determining at least one of a backup volume and a disaster recovery volume to which the data indicated by the data writing request is to be written according to the source information of the data writing request and the backup disaster recovery attribute of the storage volume to be written;
and respectively writing the data indicated by the data writing request into at least one of a backup volume and a disaster recovery volume which are deployed corresponding to the storage volume and the storage volume.
2. The method according to claim 1, wherein the determining, according to the source information of the data write request and the backup disaster recovery attribute of the storage volume to be written, at least one of the backup volume and the disaster recovery volume to be written with the data indicated by the data write request includes:
when the data writing request is determined to come from the host according to the source information of the data writing request, determining a backup volume and a disaster recovery volume to be written in the data indicated by the data writing request according to the backup disaster recovery attribute of the storage volume to be written in;
the writing the data indicated by the data writing request into at least one of a backup volume and a disaster recovery volume deployed corresponding to the storage volume and the storage volume respectively includes:
and respectively writing the data indicated by the data writing request into the storage volume, the backup volume and the disaster recovery volume which are deployed corresponding to the storage volume.
3. The method according to claim 1, wherein the determining, according to the source information of the data write request and the backup disaster recovery attribute of the storage volume to be written, at least one of the backup volume and the disaster recovery volume to be written with the data indicated by the data write request includes:
when the data writing request is determined to be from a backup volume according to the source information of the data writing request, determining a disaster recovery volume to which the data indicated by the data writing request is to be written according to the backup disaster recovery attribute of the storage volume to be written;
the writing the data indicated by the data writing request into at least one of a backup volume and a disaster recovery volume deployed corresponding to the storage volume and the storage volume respectively comprises:
and respectively writing the data indicated by the data writing request into the storage volume and the disaster recovery volume deployed corresponding to the storage volume.
4. The method according to claim 1, wherein the determining, according to the source information of the data write request and the backup disaster recovery attribute of the storage volume to be written, at least one of the backup volume and the disaster recovery volume to be written with the data indicated by the data write request includes:
when the data writing request is determined to be from a disaster recovery volume according to the source information of the data writing request, determining a backup volume to be written in by the data indicated by the data writing request according to the backup disaster recovery attribute of the storage volume to be written in;
the writing the data indicated by the data writing request into at least one of a backup volume and a disaster recovery volume deployed corresponding to the storage volume and the storage volume respectively includes:
and respectively writing the data indicated by the data writing request into the storage volume and a backup volume deployed corresponding to the storage volume.
5. The method according to claim 2, wherein after the data indicated by the data writing request is written into the storage volume, the backup volume deployed corresponding to the storage volume, and the disaster recovery volume, respectively, the method further comprises:
when the data indicated by the data writing request is successfully written into the storage volume, the backup volume and the disaster recovery volume which are deployed corresponding to the storage volume, a data writing success response is returned to the host;
and when at least one of the data writing into the storage volume, the backup volume and the disaster recovery volume deployed corresponding to the storage volume, which is indicated by the data writing request, fails, returning a data writing failure response to the host.
6. A data distribution processing module is applied to a storage system, wherein the storage system comprises one or more storage volumes; the data distribution processing module comprises: the system comprises a volume management unit, a data processing unit and a data distribution unit;
the volume management unit is used for recording backup disaster recovery attributes of one or more storage volumes of the storage system;
the data processing unit is used for determining a storage volume to be written in the data indicated by the data writing request after receiving the data writing request; determining at least one of a backup volume and a disaster recovery volume to which the data indicated by the data writing request is to be written according to the source information of the data writing request and the backup disaster recovery attribute of the storage volume to be written;
and the data distribution unit is used for writing the data indicated by the data writing request into at least one of a backup volume and a disaster recovery volume which are deployed corresponding to the storage volume and the storage volume respectively.
7. The data distribution processing module according to claim 6, wherein the data processing unit is configured to, when determining that the data write request is from the host according to the source information of the data write request, determine, according to the backup disaster tolerance attribute of the storage volume to be written, a backup volume and a disaster tolerance volume to which data indicated by the data write request is to be written;
and the data distribution unit is used for respectively writing the data indicated by the data writing request into the storage volume, the disaster recovery volume and the backup volume which are deployed corresponding to the storage volume.
8. The data distribution processing module according to claim 6, wherein the data processing unit is configured to, when determining that the data write request is from a backup volume according to source information of the data write request, determine, according to a backup disaster recovery attribute of the storage volume to be written, a disaster recovery volume to which data indicated by the data write request is to be written;
and the data distribution unit is used for writing the data indicated by the data writing request into the storage volume and the disaster recovery volume deployed corresponding to the storage volume respectively.
9. The data distribution processing module according to claim 6, wherein the data processing unit is configured to, when determining that the data write request is from a disaster-tolerant volume according to source information of the data write request, determine a backup volume to which data indicated by the data write request is to be written according to a backup disaster-tolerant attribute of the storage volume to be written;
and the data distribution unit is used for writing the data indicated by the data writing request into the storage volume and the backup volume deployed corresponding to the storage volume respectively.
10. A system for implementing data protection, comprising: a storage system, a backup system and a disaster recovery system; the storage system comprises a data distribution processing module and one or more storage volumes, the backup system comprises one or more backup volumes deployed corresponding to the storage volumes, and the disaster recovery system comprises one or more disaster recovery volumes deployed corresponding to the storage volumes;
the data distribution processing module is used for determining a storage volume to be written in the data indicated by the data writing request after receiving the data writing request; determining at least one of a backup volume and a disaster recovery volume to which the data indicated by the data writing request is to be written according to the source information of the data writing request and the backup disaster recovery attribute of the storage volume to be written; and writing the data indicated by the data writing request into at least one of a backup volume and a disaster recovery volume which are deployed corresponding to the storage volume and the storage volume respectively.
11. The system according to claim 10, wherein the data distribution processing module is configured to, when it is determined that the data write request is from the host according to the source information of the data write request, determine, according to the backup disaster recovery attribute of the storage volume to be written, a backup volume and a disaster recovery volume to be written in the data indicated by the data write request; and respectively writing the data indicated by the data writing request into the storage volume, the disaster recovery volume and the backup volume which are deployed corresponding to the storage volume.
12. The system according to claim 10, wherein the data distribution processing module is configured to, when determining that the data write request is from a backup volume according to source information of the data write request, determine, according to a backup disaster recovery attribute of the storage volume to be written, a disaster recovery volume to which data indicated by the data write request is to be written; and respectively writing the data indicated by the data writing request into the storage volume and the disaster recovery volume deployed corresponding to the storage volume.
13. The system according to claim 10, wherein the data distribution processing module is configured to, when determining that the data write request is from a disaster recovery volume according to source information of the data write request, determine, according to a backup disaster recovery attribute of the storage volume to be written, a backup volume to be written in by data indicated by the data write request; and respectively writing the data indicated by the data writing request into the storage volume and a backup volume deployed corresponding to the storage volume.
14. An apparatus comprising a memory for storing a program for implementing data protection and a processor, wherein the program when executed by the processor implements the steps of a method for implementing data protection as claimed in any one of claims 1 to 5.
15. A computer-readable medium, characterized in that a program for implementing data protection is stored, which program, when being executed by a processor, implements the steps of a method for implementing data protection according to any one of claims 1 to 5.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710750080.6A CN109426588B (en) | 2017-08-28 | 2017-08-28 | Method and system for realizing data protection and data distribution processing module |
| PCT/CN2018/100898 WO2019042142A1 (en) | 2017-08-28 | 2018-08-16 | Method and system for implementing data protection, and data distribution processing apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710750080.6A CN109426588B (en) | 2017-08-28 | 2017-08-28 | Method and system for realizing data protection and data distribution processing module |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109426588A CN109426588A (en) | 2019-03-05 |
| CN109426588B true CN109426588B (en) | 2023-03-14 |
Family
ID=65502643
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710750080.6A Active CN109426588B (en) | 2017-08-28 | 2017-08-28 | Method and system for realizing data protection and data distribution processing module |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109426588B (en) |
| WO (1) | WO2019042142A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113867996B (en) * | 2021-08-18 | 2024-09-20 | 广州方硅信息技术有限公司 | Data disaster recovery processing method, server, live broadcast system and storage medium |
| CN114185489A (en) * | 2021-12-02 | 2022-03-15 | 中国电信股份有限公司 | Data synchronization method and device, electronic equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101414277A (en) * | 2008-11-06 | 2009-04-22 | 清华大学 | Need-based increment recovery disaster-containing system and method based on virtual machine |
| CN101436209A (en) * | 2008-12-15 | 2009-05-20 | 中兴通讯股份有限公司 | Method and apparatus for synchronizing multiple databases |
| CN101635638A (en) * | 2008-07-25 | 2010-01-27 | 中兴通讯股份有限公司 | Disaster tolerance system and disaster tolerance method thereof |
| CN103793291A (en) * | 2012-11-01 | 2014-05-14 | 华为技术有限公司 | Distributed data copying method and device |
| CN103838646A (en) * | 2014-02-13 | 2014-06-04 | 中国科学院国家天文台 | System and method for big data remote disaster recovery backup of ground application |
| CN105827738A (en) * | 2016-05-27 | 2016-08-03 | 浪潮(北京)电子信息产业有限公司 | Disaster recovery synchronization method under high availability architecture and system |
| CN106502823A (en) * | 2016-09-29 | 2017-03-15 | 北京许继电气有限公司 | data cloud backup method and system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102123358A (en) * | 2010-01-08 | 2011-07-13 | 中兴通讯股份有限公司 | Method and system for realizing dynamic load sharing in short message system |
| US9336226B2 (en) * | 2013-01-11 | 2016-05-10 | Commvault Systems, Inc. | Criteria-based data synchronization management |
-
2017
- 2017-08-28 CN CN201710750080.6A patent/CN109426588B/en active Active
-
2018
- 2018-08-16 WO PCT/CN2018/100898 patent/WO2019042142A1/en active Application Filing
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101635638A (en) * | 2008-07-25 | 2010-01-27 | 中兴通讯股份有限公司 | Disaster tolerance system and disaster tolerance method thereof |
| CN101414277A (en) * | 2008-11-06 | 2009-04-22 | 清华大学 | Need-based increment recovery disaster-containing system and method based on virtual machine |
| CN101436209A (en) * | 2008-12-15 | 2009-05-20 | 中兴通讯股份有限公司 | Method and apparatus for synchronizing multiple databases |
| CN103793291A (en) * | 2012-11-01 | 2014-05-14 | 华为技术有限公司 | Distributed data copying method and device |
| CN103838646A (en) * | 2014-02-13 | 2014-06-04 | 中国科学院国家天文台 | System and method for big data remote disaster recovery backup of ground application |
| CN105827738A (en) * | 2016-05-27 | 2016-08-03 | 浪潮(北京)电子信息产业有限公司 | Disaster recovery synchronization method under high availability architecture and system |
| CN106502823A (en) * | 2016-09-29 | 2017-03-15 | 北京许继电气有限公司 | data cloud backup method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2019042142A1 (en) | 2019-03-07 |
| CN109426588A (en) | 2019-03-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9990256B1 (en) | Storage management system and method | |
| CN101539873B (en) | Data recovery method, data node and distributed file system | |
| US9563517B1 (en) | Cloud snapshots | |
| US9323750B2 (en) | Storage array snapshots for logged access replication in a continuous data protection system | |
| US9251233B2 (en) | Merging an out of synchronization indicator and a change recording indicator in response to a failure in consistency group formation | |
| CN108351821B (en) | Data recovery method and storage device | |
| US9535617B2 (en) | Marking a flashcopy backup for collapse without breaking a flashcopy chain | |
| EP4068099A1 (en) | State management method, master and backup application server switching method, and electronic device | |
| CN110018783B (en) | Data storage method, device and system | |
| CN105630632A (en) | Virtual machine recovery method and virtual machine management device | |
| CN104462563A (en) | File storage method and system | |
| US9817719B2 (en) | Efficient Flashcopy backup and mount, clone, or restore collision avoidance using dynamic volume allocation with reuse and from a shared resource pool | |
| CN101763321B (en) | Disaster-tolerant method, device and system | |
| CN104679611A (en) | Data resource copying method and device | |
| US10372554B1 (en) | Verification and restore of replicated data using a cloud storing chunks of data and a plurality of hashes | |
| US9454315B2 (en) | Efficient flashcopy backup target volume allocation from a shared resource pool while ingesting a flashcopy backup in a repository | |
| CN109491832A (en) | Data disaster tolerance method and website | |
| EP4060514A1 (en) | Distributed database system and data disaster backup drilling method | |
| US9542106B2 (en) | Efficient repository ingest of a target volume without breaking a flashcopy chain | |
| US9817723B2 (en) | Efficient FlashCopy backup and mount, clone, or restore collision avoidance using dynamic volume allocation with reuse | |
| CN109426588B (en) | Method and system for realizing data protection and data distribution processing module | |
| US9507536B2 (en) | Creating a stable flashcopy map (FCMAPS) for ingest | |
| CN105550071A (en) | System file upgrading and detecting method and communication device | |
| CN106933700B (en) | Method and apparatus for restoring data backup between memories | |
| CN104133742A (en) | Data protection method and device |
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 |