CN112416652A - Data backup method and data backup - Google Patents
Data backup method and data backup Download PDFInfo
- Publication number
- CN112416652A CN112416652A CN201910779318.7A CN201910779318A CN112416652A CN 112416652 A CN112416652 A CN 112416652A CN 201910779318 A CN201910779318 A CN 201910779318A CN 112416652 A CN112416652 A CN 112416652A
- Authority
- CN
- China
- Prior art keywords
- data
- metadata
- backup
- backup data
- target
- 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
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
Abstract
The embodiment of the application discloses a data backup method and data backup: the backup data and the metadata (including the system metadata) on the production system are firstly acquired, then the target logical unit is created on the target system according to the system metadata, the target logical unit is mounted to the host computer, and the backup data is written into the target logical unit. That is, only the system metadata acquired from the production system is needed to create a target logical unit completely consistent with the attribute information of the source logical unit on the production system on any target system (including the production system itself), and the backup data on the production system can be directly used on the target system by writing the backup data into the target logical unit (that is, the backup data can be considered as the backup data that can be directly mounted and used by the host of the target system as the production storage), so that the backup data does not need to be written back, and time is saved.
Description
Technical Field
The present application relates to the field of data backup, and in particular, to a data backup method and a data backup apparatus.
Background
At present, technologies such as cloud computing, internet of things, social networks, mobile internet and the like promote explosive increase of data types and scales in various fields. With the advent of the big data era, data is converted from a simple processing object into important basic resources, and meanwhile, the scale and complexity of the big data also bring great challenges to the processing and computing capacity of the existing machine.
Data backup refers to a process of copying all or part of a data set from a hard disk or an array of an application host to another storage medium in order to prevent data loss caused by system misoperation or system failure. Data backup is the basis for disaster recovery, which can protect the security of data and improve the continuous availability of data.
The traditional data backup mainly adopts a built-in or external tape unit for cold backup. However, this conventional data backup method has a large limitation, and the backup data obtained in this way cannot be directly read by the host computer of the device.
Disclosure of Invention
A first aspect of an embodiment of the present invention provides a method for data backup, including:
first, a target system (e.g., a production system, a backup system, etc.) acquires backup data and metadata on the production system, the metadata includes system metadata describing attribute information of a source logical unit of backup data located in the production system, and the target system creates a target logical unit on the target system based on the system metadata, the attribute information of the target logical unit is consistent with the attribute information of the source logical unit on the production system, and the target system mounts the target logical unit to a host on the target system (e.g., a host mounted on a production system or a host of a backup system), and finally the target system writes the backup data to the target logical unit, so that the backup data written to the target logical unit can be accessed by the host on the target system.
In the above embodiment of the present application, only the system metadata acquired from the production system is needed to create a target logic unit on any target system (including the production system itself), where the target logic unit is completely consistent with the attribute information of the source logic unit on the production system, and the backup data is written into the target logic unit, so that the backup data on the production system can be directly used on the target system (i.e., the backup data can be considered as the production storage that can be directly mounted and used by the host of the target system), and thus, the backup data does not need to be written back, and time is saved.
With reference to the first aspect of the embodiment of the present application, in the first implementation manner of the first aspect of the embodiment of the present application, the target system obtains metadata that includes, in addition to system metadata, fragmentation data, where the fragmentation metadata is used to describe attribute information of each fragmentation data in a plurality of fragmentation data, such as attribute information used to describe a position, a size, an occupied space, a type, and the like of each fragmentation data. The target system may then restore the plurality of sliced data to a complete backup data according to the sliced metadata.
In the above embodiment of the present application, how the target system restores the fragmented metadata and the multiple fragmented data to obtain complete backup data through the process of the fragmentation processing is described, so that it can be ensured that the data format of the backup data on the target system is consistent with that of the corresponding source data, and thus the restored backup data can be directly accessed by the host after the target system writes the restored backup data into the target logical unit.
With reference to the first aspect of the embodiment of the present application and the first implementation manner of the first aspect of the embodiment of the present application, in a second implementation manner of the first aspect of the embodiment of the present application, after the target system writes the backup data into the created target logic unit, if the target system obtains the trigger instruction, the trigger instruction is used to instruct the target system to access the backup data in the target logic unit through the host. For example, if the target system is a backup system, the trigger instruction may be failure information sent to the corresponding backup system when the source logic unit of the production system fails, or may also be information of damage to source data sent to the backup system when the source data of the production system is damaged, and the trigger instruction is not limited herein specifically; if the target system is the production system itself, the trigger instruction may be failure information sent to the operating system of the production system when the source logic unit of the production system fails, or may also be information that source data sent to the operating system of the production system is damaged when the source data of the production system is damaged, and similarly, the trigger instruction is not limited herein. The trigger command is different for different target systems, and is not limited herein.
In the foregoing embodiment of the present application, after the target system acquires the trigger instruction, the host of the target system will respond to the trigger instruction, so as to access the backup data in the created target logic unit, so that the service performed on the operating system of the production system is not interrupted, thereby ensuring the continuous availability of the data.
With reference to the first aspect of the embodiment of the present application and the first implementation manner to the second implementation manner of the first aspect of the embodiment of the present application, in the third implementation manner of the first aspect of the embodiment of the present application, the manner in which the target system acquires the backup data and the metadata may be: and acquiring corresponding backup data and metadata from the operating system through corresponding data interfaces and metadata interfaces on the target system respectively. For example, the target system may obtain the corresponding plurality of fragment data through the data interface and obtain the system metadata and the fragment metadata through the metadata interface; the target system may also obtain the corresponding plurality of fragment data and fragment metadata through the data interface and obtain the system metadata or obtain the system metadata through the metadata interface, which is not limited herein.
In the foregoing embodiments of the present application, an implementation manner of obtaining backup data and metadata by a target system is specifically described, which has operability.
With reference to the first aspect of the embodiment of the present application and the first to third implementation manners of the first aspect of the embodiment of the present application, in the fourth implementation manner of the first aspect of the embodiment of the present application, the system metadata may be any one or more of a SCSI number (SCSI-ID), a WWN, a capacity, a storage protocol version (e.g., SCSI2 version, SCSI3 version, etc. of a SCSI protocol), and a device mount mapping relationship of the source logical unit, and the attribute information of the source logical unit can be obtained according to the system metadata.
In the above embodiments of the present application, various concrete expressions of the system metadata are given, and flexibility is provided.
A second aspect of embodiments of the present application provides a data backup, which has a function of implementing a method according to the first aspect or any one of the possible implementation manners of the first aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.
A third aspect of the embodiments of the present application further provides a data backup, which may include: the system comprises a memory, a processor and a bus system, wherein the memory and the processor are connected through the bus system; wherein the memory is used for storing programs and instructions; the processor is configured to call the instructions stored in the memory to execute the method in the first aspect of the embodiment of the present application and any one of the possible implementation manners of the first aspect.
A fourth aspect of the embodiments of the present application provides a computer-readable storage medium, which stores instructions that, when executed on a computer, enable the computer to perform the method of the first aspect and any one of the possible implementation manners of the first aspect.
A fifth aspect of embodiments of the present application provides a computer program product containing instructions, which when executed on a computer, enables the computer to perform the method of any one of the above first aspect and possible implementation manners of the first aspect.
According to the technical scheme, the embodiment of the application has the following advantages: first, a target system (e.g., a production system, a backup system, etc.) acquires backup data and metadata on the production system, the metadata includes system metadata describing attribute information of a source logical unit of backup data located in the production system, and the target system creates a target logical unit on the target system based on the system metadata, the attribute information of the target logical unit is consistent with the attribute information of the source logical unit on the production system, and the target system mounts the target logical unit to a host on the target system (e.g., a host mounted on a production system or a host of a backup system), and finally the target system writes the backup data to the target logical unit, so that the backup data written to the target logical unit can be accessed by the host on the target system. In the above embodiment of the present application, only the system metadata acquired from the production system is needed to create a target logical unit that is completely consistent with the attribute information of the source logical unit on the production system on any target system (including the production system itself), and the backup data is written into the target logical unit, so that the backup data on the production system can be directly used on the target system (that is, the backup data can be considered as the production storage that can be directly mounted and used by the host of the target system), and thus, the backup data does not need to be written back, and time is saved.
Drawings
FIG. 1 is a schematic diagram of a transmission process of backup data between a production system and a backup system in an embodiment of the present application;
FIG. 2 is a schematic diagram of a transmission process of backup data among a production system, a backup system, and a recovery system in an embodiment of the present application;
FIG. 3 is a diagram illustrating a data backup method according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a backup system to which the data backup method of the embodiment of the present application is applied;
FIG. 5 is a diagram illustrating an implementation manner of a data backup method in an embodiment of the present application;
FIG. 6 is a diagram illustrating another specific implementation manner of a data backup method in an embodiment of the present application;
FIG. 7 is a schematic diagram of data backup in an embodiment of the present application;
fig. 8 is another schematic diagram of data backup in the embodiment of the present application.
Detailed Description
The embodiment of the application provides a data backup method, a target system (which may also include a production system) can create a target logic unit on the target system completely consistent with attribute information of a source logic unit on the production system through system metadata acquired from the production system, and direct use of backup data on the production system on the target system can be realized by writing the backup data acquired from the production system into the target logic unit, so that write-back of the backup data is not needed, and time is saved.
Before describing the present embodiment, concepts that may appear in the embodiments of the present application are first described. It should be understood that the related conceptual explanations may be limited by the specific details of the embodiments of the present application, but do not mean that the present application is limited to the specific details, and that the specific details of the embodiments may vary from one embodiment to another, and are not limited herein.
A World Wide Name (WWN), typically a unique 48-or 64-digit number assigned by an authoritative organization, is specifically tailored to recognized Name authorizations (typically assigned to manufacturers by region) to distinguish one or a group of network connections to identify a connection or set of connections on a network, primarily for Fibre Channel (FC) technology.
Small Computer System Interface (SCSI) is a standard for independent processor for System-level interfacing between computers and their Interface devices (hard disk drives, floppy drives, optical drives, printers, scanners, etc.). The SCSI _ ID is a device identification number recorded on the interface.
Metadata, also called intermediate data, is data used to describe target data (e.g., source data, backup data, etc.), and is mainly information describing data attributes, which is used to support functions such as indicating storage locations, history data, resource lookups, file records, etc.
Software defined storage is a data storage means, and all storage related control work is only in external software relative to physical storage hardware.
It should be noted that the target system described in this embodiment of the present application may include a production system, a backup system, and a recovery system, and the target system is specifically defined herein. The production system refers to a device that runs a corresponding operating system and directly generates source data corresponding to backup data, and the backup system described in this embodiment of the present application refers to a system that is specially prepared for replacing a failed system in order to prevent a failure of the entire production system (i.e., multiple production systems) caused by a failure of a certain critical or vulnerable production system during operation, or refers to a device that is specially prepared for storing backup data corresponding to source data on a production system in order to prevent loss of source data generated on a production system (which may be one or multiple production systems, which is not limited herein), where the backup system is sometimes referred to as a "backup machine" for short. The recovery system is a device for further receiving and storing the backup data sent from the backup system, and is used to directly utilize the backup data in the recovery system when the backup system is not available, or send the backup data to the production system/backup system when the backup system/production system needs to use the backup data.
For convenience of understanding, the following description of a system framework structure according to an embodiment of the present application is specifically illustrated in fig. 1, where fig. 1 illustrates a transmission process of backup data between a production system and a backup system: there are hosts (e.g., a host on the production system in fig. 1 may be referred to as host 1 and a host on the backup system may be referred to as host 2) and storage devices (e.g., a storage device on the production system in fig. 1 may be referred to as storage device 1 and a storage device on the backup system may be referred to as storage device 2) in the production system and the backup system, respectively. The host may comprise any computing device known in the art, such as a server, desktop computer, etc. Inside the host, an operating system and other application programs are installed. The Storage devices may include Storage devices known in the art, such as one or more interconnected disk drives Of a Redundant array Of independent Disks (RAID), a cluster Of Disks (JBOD), a Direct Access Storage Device (DASD), a tape Storage Device such as a tape library, one or more Storage units, or the like. It should be noted that, for most storage devices, the physical disks included in the storage device are not directly presented to the operating system, but the storage space provided by each physical disk is mapped into a segment of Logical area, i.e., Logical Unit Number (LUN), for use by a user. In the embodiment of the present application, the source logical unit refers to a logical unit in which backup data is stored on a production system, and the target logical unit is a new logical unit created by a target system (e.g., a production system or a backup system) on the target system according to system metadata, and the target logical unit is used for storing backup data obtained from the source logical unit on the production system. In fig. 1, what is shown is how a backup system acquires backup data from a production system, and in some embodiments of the present application, this process may be specifically implemented by a copy Client (Client) in a host, that is, the production system loads the backup data and metadata by using a container technology by adding the backup data and the metadata to the Client in the host, and then the backup data and the metadata on the production system are acquired by the Client and flow into the backup system (that is, the Client in the backup system creates a target logical unit 1 according to the acquired system metadata and mounts the target logical unit 1 in a host 2 of the backup system, and then writes the backup data into the target logical unit 1), and implements restoration of the metadata and the backup data in the Client in the backup system, when the backup system needs to directly utilize the restored backup data, only the host 2 in the backup system needs to directly access the backup data in the target logical unit 1.
Similarly, as shown in fig. 2, when the recovery system needs to use the backup data, the backup data stored on the backup system is further obtained from the backup system in a similar manner, that is, the host 3 and the storage device 3 also exist on the recovery system, in some embodiments of the present application, the Client on the recovery system receives the backup data sent from the backup system, and stores the backup data in the target logical unit 2 created by the Client on the recovery system, so that the host 3 of the recovery system can directly access the backup data in the target logical unit 2, or when the production system or the backup system needs to use the backup data, the recovery system sends the backup data to the production system or the backup system.
In this embodiment of the present application, the method for backing up data is executed by a Client of a target system, where the target system may be the host 1 in the production system, the host 2 in the backup system, or the host 3 in the recovery system, and is not limited herein. The specific process can be as shown in fig. 3:
301. backup data and metadata are obtained.
The target system acquires backup data and metadata from the production system, wherein the metadata comprises system metadata, and the system metadata is used for describing attribute information of a source logical unit of the backup data in the production system. For example, the system metadata may be any one or more of SCSI-ID, WWN, capacity, storage protocol version (e.g., SCSI2 version, SCSI3 version, etc. of SCSI protocol), device mount mapping, from which attribute information of the source logical unit can be obtained.
It should be explained that the operating system of the production system generates active data during the running process, when the source data needs to be backed up, the production system can obtain backup data and metadata from its own operating system during the backup process, where the metadata includes system metadata, and the system metadata is used to describe attribute information of a source logical unit of the backup data in the production system, and the attribute information of the source logical unit can be obtained according to the system metadata.
It should also be noted that the backup data may be a copy of the source data generated on the production system. In some embodiments of the present application, the metadata may further include fragment metadata, and when the backup data needs to be utilized, the target system may restore the plurality of fragment data to the backup data according to the fragment metadata. For ease of understanding, the description is made here by way of example: when some source data generated in the production system needs to be backed up, backup data obtained through a backup operation is stored in a source logical unit in the production system. Because the backup data is large, the process of acquiring the backup data from the production system by the target system (e.g., the backup system) generally includes performing fragmentation processing on the backup data, and the fragmentation processing is to divide the backup data into a plurality of pieces of data with equal or unequal sizes (e.g., if the size of the backup data is 1G, the backup data can be fragmented into a plurality of pieces of data with 64M sizes), which has several advantages: 1) the data transmission failure caused by sudden interruption of transmission in the transmission process due to overlarge backup data is avoided; 2) the fragmentation processing process is also used for carrying out format conversion on the backup data, because generally, the data formats of the source data and the corresponding backup data are different, and the backup data and the corresponding source data can be kept consistent in data format through the fragmentation processing process; 3) the fragmentation processing enables one complete backup data to be divided into a plurality of fragmentation data for parallel transmission, and transmission efficiency is higher.
302. A target logical unit is created on the target system based on the system metadata.
After the target system acquires the system metadata, a target logical unit is created on the target system according to the system metadata, and the attribute information of the target logical unit is consistent with the attribute information of the source logical unit on the production system.
It should be further noted that, because the system metadata is used to describe the attribute information of the source logical unit, the target logical unit created by the target system according to the acquired system metadata is a virtual logical unit, which has the attribute information consistent with the source logical unit and can implement the same function as the source logical unit.
303. And mounting the target logic unit to the host.
After the target system creates the target logical unit according to the system metadata, the target logical unit is mounted to the host. After mounting, the host can access the target logical unit. For example, if the target system is a production system, the production system mounts the target logical unit to a host on the production system; if the target system is a backup system, the backup system can mount the target logic unit to a host on the backup system; the recovery system is similar and will not be described herein.
304. And writing the backup data into the target logic unit.
In some embodiments of the present application, the target system obtains metadata that is used to describe attribute information of each piece of data in the multiple pieces of data, such as attribute information used to describe the location, size, occupied space, type, and the like of each piece of data. Then, the target system can restore the plurality of fragment data into a complete backup data according to the fragment metadata to ensure that the backup data on the target system is consistent with the data format of the corresponding source data, so that the restored backup data can be directly accessed by the host after the target system writes the restored backup data into the target logical unit.
It should be noted that, in some embodiments of the present application, the manner in which the target system acquires the backup data and the metadata may be: the backup data and the metadata are obtained from the operating system through the same data transmission interface on the target system, or the corresponding backup data and the metadata are obtained from the operating system through the corresponding data interface and the corresponding metadata interface on the target system, and the manner of how the backup system receives the backup data and the metadata is not limited herein. For example, the target system may obtain the corresponding plurality of fragment data through the data interface and obtain the system metadata and the fragment metadata through the metadata interface; the target system may also obtain the corresponding plurality of sharded data and sharded metadata through the data interface and obtain the system metadata through the metadata interface.
305. The host accesses the backup data in the target logical unit in response to the trigger instruction.
It should be noted that, in some embodiments of the present application, step 305 may also be included. Namely: after the target system writes the backup data into the created target logic unit, if the target system obtains a trigger instruction, the trigger instruction is used to instruct the target system to access the backup data in the target logic unit through the host, for example, if the target system is a backup system, the trigger instruction may be failure information sent to the corresponding backup system when the source logic unit of the production system fails, or may also be information of damage to the source data sent to the backup system when the source data of the production system is damaged, and the trigger instruction is not limited herein specifically; if the target system is the production system itself, the trigger instruction may be failure information sent to the operating system of the production system when the source logic unit of the production system fails, or may also be information that source data sent to the operating system of the production system is damaged when the source data of the production system is damaged, and similarly, the trigger instruction is not limited herein. The trigger command is different for different target systems, and is not limited herein. After the target system acquires the trigger instruction, the host of the target system responds to the trigger instruction, so that the backup data is accessed in the created target logic unit, the service performed on the operating system of the production system is not interrupted, and the continuous availability of the data is ensured.
In the above embodiment of the present application, only the system metadata acquired from the production system is needed to create a target logical unit that is completely consistent with the attribute information of the source logical unit on the production system on any target system (including the production system itself), and the backup data is written into the target logical unit, so that the backup data on the production system can be directly used on the target system (that is, the backup data can be considered as the production storage that can be directly mounted and used by the host of the target system), and thus, the backup data does not need to be written back, and time is saved.
It should be further noted that, the data backup method in the present application is applied to the target system, that is, the method may be applied to the backup system so that the backup system can directly utilize the backup data, may also be applied to the production system so that the production system can directly utilize the backup data under some special conditions (for example, the source data corresponding to the backup data is damaged, etc.), and may also be applied to the recovery system to further receive and store the backup data sent from the backup system, which is not limited herein. For convenience of understanding, a method for backing up data on a backup system by taking a target system as the backup system is described below.
Fig. 4 is a schematic diagram of a data backup method in an embodiment of the present application, and a specific implementation manner is as follows:
401. the backup system receives backup data sent by the production system along with the metadata.
The backup system acquires backup data and metadata sent by the production system, wherein the metadata comprises system metadata, and the system metadata is used for describing attribute information of a source logic unit of the backup data in the production system. Similar to the embodiment shown in fig. 3, the system metadata may be any one or more of SCSI-ID, WWN, capacity, storage protocol version (e.g., SCSI2 version, SCSI3 version, etc. of the SCSI protocol), and device mount mapping of the source logical unit, from which the attribute information of the source logical unit can be obtained.
Similarly, when the production system needs to backup some source data, the backup data obtained through the backup operation may also be stored in the source logic unit in the production system, and the backup data may also be subjected to fragmentation processing, where a specific fragmentation sending manner is similar to that described in the embodiment corresponding to fig. 3, and is not described here again.
402. The backup system creates a target logical unit from the system metadata.
After the backup system acquires the system metadata, a target logic unit is created on the backup system according to the system metadata, and the attribute information of the target logic unit is consistent with the attribute information of the source logic unit on the production system.
It should be further noted that, because the system metadata is used to describe the attribute information of the source logical unit, the target logical unit created by the backup system according to the acquired system metadata is a virtual logical unit, which has the attribute information consistent with the source logical unit and can implement the same function as the source logical unit.
403. The backup system mounts the target logical unit to the host.
After the backup system creates the target logical unit according to the system metadata, the target logical unit is mounted to the host. After mounting, the host can access the target logical unit.
404. And the backup system writes the backup data into the target logic unit.
After the backup system receives the backup data sent by the production system, the backup system writes the backup data into the created target logic unit. In some embodiments of the present application, the metadata received by the backup system from the production system may include, in addition to the system metadata, shard metadata for describing attribute information of each shard data in the plurality of shard data, such as attribute information describing a location, a size, an occupied space, a type, and the like of each shard data. Then, the backup system can restore the plurality of fragment data into a complete backup data according to the fragment metadata to ensure that the backup data on the backup system is consistent with the data format of the corresponding source data on the production system, so that the backup system can be directly accessed by the host computer after writing the restored backup data into the target logical unit.
Similarly, in some embodiments of the present application, the manner in which the backup system receives the backup data and the metadata may be: the backup data and the metadata are obtained from the operating system of the production system from the same data transmission interface on the backup system, or the corresponding backup data and the metadata are obtained from the operating system of the production system through the corresponding data interface and the corresponding metadata interface on the backup system, and the manner of how the backup system receives the backup data and the metadata is not limited herein. For example, the backup system may obtain the corresponding plurality of fragment data through the data interface and obtain the system metadata and the fragment metadata through the metadata interface; the backup system may also obtain the corresponding plurality of fragment data and fragment metadata through the data interface and obtain the system metadata through the metadata interface.
It should be noted that, in the embodiment corresponding to fig. 3 described above in this application, the method for implementing data backup by the target system may be implemented specifically based on a Client installed in the target system, and for convenience of understanding, the target system is taken as a backup system and a production system for example, and fig. 5 is first taken as a target system for illustration: the backup system obtains the backup data and the metadata of the source logical unit 51 on the production system through a Client installed on the backup system, and specifically, the backup data and the metadata may be obtained through a data Application Program Interface (API) 52 and a metadata API53 in the Client, respectively, and then the Client may create a target logical unit 55 by using a software-defined storage manner (e.g., through a software-defined storage module 54 in the Client) according to the system metadata, that is, create a target logical unit 55 on the Client by using the software-defined storage capability of the software-defined storage module 54, and write the backup data into the target logical unit 55, so that when the backup system needs to use the backup data, a host on which the target logical unit 55 is mounted can directly access the backup data in the target logical unit 55.
In the above embodiment of the present application, only the system metadata acquired from the production system is needed to create a target logic unit on any backup system, where the target logic unit is completely consistent with the attribute information of the source logic unit on the production system, and the backup data on the production system can be directly used on the backup system by writing the backup data on the production system into the target logic unit (that is, the backup data can be considered as being directly used as production storage and mounted by a host of the backup system), so that the backup data does not need to be written back, and time is saved.
Fig. 6 is a schematic diagram of a target system as a production system: that is, in some embodiments of the present application, the method for the production system to implement the data backup may be implemented based on a Client installed in the production system, and the production system obtains the backup data and the metadata of the source logical unit 61 of the production system through the Client installed in the production system, and may specifically obtain the backup data and the metadata through the data API62 and the metadata API63 in the Client, respectively, and then the Client may obtain the backup data and the metadata according to the system metadata, the target logical unit 65 is created by the software defined storage module 64 in the Client, i.e., create a target logical unit 65 on the Client using the software defined storage capability of the software defined storage module 64, and write the backup data to the target logical unit 65, so that when the production system needs to use the backup data, the host on the production system on which the target logical unit 65 is mounted can directly access the backup data in the target logical unit 65. In some implementations, the backup data may be further sent to other storage devices, such as the storage logic 66 of the backup system in fig. 6, so that the backup data is more secure.
It should be further noted that, in some embodiments of the present application, after the Client writes the backup data into the created target logical unit, the Client may further send the backup data to another storage device, for example, to the backup system in the embodiment corresponding to fig. 2, or send the backup data to the recovery system by the backup system, so as to further improve the security of the data.
In the embodiment of the application, the production system directly creates a target logical unit which is completely consistent with the attribute information of the source logical unit on the production system according to the system metadata, and writes the backup data in the source logical unit into the created target logical unit, so that when the source data is unavailable, the host can also directly access the backup data in the target logical unit, so that the service performed on the operating system on the production system is not interrupted, and the continuous availability of the data is ensured.
In the embodiment of the present application, according to the example of the data backup method, functional modules of a system related to data backup (i.e., a target system) may be divided, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.
For example, fig. 7 shows a schematic diagram of a data backup, and the data backup provided in the embodiment of the present application may include:
an obtaining module 701, configured to obtain backup data and metadata, where the metadata includes system metadata, and the system metadata is used to describe attribute information of a source logical unit of the backup data in a production system;
a creating module 702, configured to create a target logical unit according to the system metadata, where attribute information of the target logical unit is consistent with attribute information of the source logical unit;
a mounting module 703, configured to mount the target logical unit to the host;
a writing module 704, configured to write the backup data into the target logical unit, so that the backup data can be accessed by the host.
Preferably, in some embodiments of the present application, the backup data may further include a plurality of fragmentation data, the metadata may further include fragmentation metadata, and the writing module 704 is further specifically configured to: and restoring the plurality of fragment data into the backup data according to the fragment metadata.
Preferably, in some embodiments of the present application, after the writing module 704 writes the backup data into the target logical unit, the writing module 704 may further be configured to: the backup data is accessed in the target logical unit by the host in response to a triggering instruction.
Preferably, in some embodiments of the present application, the obtaining module 701 is specifically configured to: and respectively acquiring corresponding backup data and metadata from an operating system of the production system through the data interface and the metadata interface.
Preferably, in some embodiments of the present application, the system metadata includes: the source logical unit has at least one of a small computer system interface number SCSI-ID, a world wide unique name WWN, capacity, storage protocol version, and device mount mapping.
The specific functions and structures of the data backup in the embodiment corresponding to fig. 7 are used to implement the steps processed by the target system in fig. 3 to fig. 6, and details thereof are not repeated here.
Fig. 8 is another schematic diagram of data backup according to an embodiment of the present application, which only shows a portion related to the embodiment of the present application for convenience of description, and please refer to a method portion of the embodiment of the present application for details that are not disclosed. The data backup 800 may vary significantly due to configuration or performance differences and may include one or more Central Processing Units (CPUs) 822 (e.g., one or more processors) and memory 832, one or more storage media 830 (e.g., one or more mass storage devices) storing applications 842 or data 844. Memory 832 and storage medium 830 may be, among other things, transient or persistent storage. The program stored in the storage medium 830 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Still further, central processor 822 may be configured to communicate with storage medium 830 to perform a series of instructional operations on storage medium 830 on data backup 800.
The steps performed by the target system in the embodiments corresponding to fig. 3 to 6 described above may be implemented based on the structure shown in fig. 8.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.
The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium. The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk), among others.
Claims (17)
1. A method of data backup, comprising:
the method comprises the steps of obtaining backup data and metadata, wherein the metadata comprises system metadata, and the system metadata is used for describing attribute information of a source logic unit of the backup data in a production system;
creating a target logic unit according to the system metadata, wherein the attribute information of the target logic unit is consistent with the attribute information of the source logic unit;
mounting the target logic unit to a host;
writing the backup data to the target logical unit to enable the backup data to be accessed by the host.
2. The method of claim 1, wherein the backup data comprises a plurality of sharded data, wherein the metadata further comprises sharded metadata, and wherein the method further comprises:
and restoring the plurality of sliced data into the backup data according to the sliced metadata.
3. The method of any of claims 1-2, wherein after writing the backup data to the target logical unit, the method further comprises:
accessing, by the host, the backup data in the target logical unit in response to a triggering instruction.
4. The method of any of claims 1-3, wherein obtaining backup data and metadata comprises:
and respectively acquiring corresponding backup data and metadata from an operating system of the production system through the data interface and the metadata interface.
5. The method of any of claims 1-4, wherein the system metadata comprises:
and the source logic unit comprises at least one of a small computer system interface number SCSI-ID, a worldwide unique name WWN, capacity, a storage protocol version and a device mounting mapping relation.
6. A data backup, comprising:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring backup data and metadata, the metadata comprises system metadata, and the system metadata is used for describing attribute information of a source logic unit of the backup data in a production system;
the creating module is used for creating a target logic unit according to the system metadata, and the attribute information of the target logic unit is consistent with the attribute information of the source logic unit;
the mounting module is used for mounting the target logic unit to a host;
and the writing module is used for writing the backup data into the target logic unit so as to enable the backup data to be accessed by the host.
7. The data backup according to claim 6, wherein the backup data comprises a plurality of sharded data, the metadata further comprises sharded metadata, and the write module is specifically configured to:
and restoring the plurality of sliced data into the backup data according to the sliced metadata.
8. The data backup according to any one of claims 6 to 7, wherein after the writing module writes the backup data into the target logical unit, the writing module is further specifically configured to:
accessing, by the host, the backup data in the target logical unit in response to a triggering instruction.
9. The data backup according to any one of claims 6 to 8, wherein the obtaining module is specifically configured to:
and respectively acquiring corresponding backup data and metadata from an operating system of the production system through the data interface and the metadata interface.
10. The data backup according to any of claims 6-9, wherein the system metadata comprises:
and the source logic unit comprises at least one of a small computer system interface number SCSI-ID, a worldwide unique name WWN, capacity, a storage protocol version and a device mounting mapping relation.
11. A data backup, comprising: a memory, a processor, and a bus system;
the memory is used for storing programs and instructions;
the processor is used for executing the program in the memory;
the bus system is used for connecting the memory and the processor so as to enable the memory and the processor to communicate;
wherein the processor is configured to call program instructions in the memory, and is configured to perform the following steps:
the method comprises the steps of obtaining backup data and metadata, wherein the metadata comprises system metadata, and the system metadata is used for describing attribute information of a source logic unit of the backup data in a production system;
creating a target logic unit according to the system metadata, wherein the attribute information of the target logic unit is consistent with the attribute information of the source logic unit;
mounting the target logic unit to a host;
writing the backup data to the target logical unit to enable the backup data to be accessed by the host.
12. The data backup according to claim 11, wherein the backup data comprises a plurality of sharded data, the metadata further comprising sharded metadata, the processor further configured to perform the steps of:
and restoring the plurality of sliced data into the backup data according to the sliced metadata.
13. The data backup according to any of claims 11-12, wherein after writing the backup data to the target logical unit, the processor is further configured to perform the steps of:
accessing, by the host, the backup data in the target logical unit in response to a triggering instruction.
14. The data backup according to any of claims 11-13, wherein the processor is specifically configured to perform the steps of:
and respectively acquiring corresponding backup data and metadata from an operating system of the production system through the data interface and the metadata interface.
15. The data backup according to any of claims 11-14, wherein the system metadata comprises:
and the source logic unit comprises at least one of a small computer system interface number SCSI-ID, a worldwide unique name WWN, capacity, a storage protocol version and a device mounting mapping relation.
16. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any of claims 1-5.
17. A computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1-5.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910779318.7A CN112416652A (en) | 2019-08-22 | 2019-08-22 | Data backup method and data backup |
| PCT/CN2020/088834 WO2021031618A1 (en) | 2019-08-22 | 2020-05-06 | Data backup method, data backup apparatus, and data backup system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910779318.7A CN112416652A (en) | 2019-08-22 | 2019-08-22 | Data backup method and data backup |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112416652A true CN112416652A (en) | 2021-02-26 |
Family
ID=74660122
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910779318.7A Pending CN112416652A (en) | 2019-08-22 | 2019-08-22 | Data backup method and data backup |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112416652A (en) |
| WO (1) | WO2021031618A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022267627A1 (en) * | 2021-06-25 | 2022-12-29 | 华为技术有限公司 | Data processing method and related device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104794028A (en) * | 2014-01-16 | 2015-07-22 | 中国移动通信集团浙江有限公司 | Disaster tolerance processing method and device, main data center and backup data center |
| CN106528327A (en) * | 2016-09-30 | 2017-03-22 | 华为技术有限公司 | Data processing method and backup server |
| CN107656705A (en) * | 2017-10-25 | 2018-02-02 | 郑州云海信息技术有限公司 | A kind of computer-readable storage medium and a kind of data migration method, apparatus and system |
| CN108345515A (en) * | 2017-01-22 | 2018-07-31 | 中国移动通信集团四川有限公司 | Storage method and device and its storage system |
| CN109669815A (en) * | 2018-12-14 | 2019-04-23 | 武汉烽火信息集成技术有限公司 | A kind of method and system restored by the long-range Mapping implementation Backup Data of LUN |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2008186142A (en) * | 2007-01-29 | 2008-08-14 | Hitachi Ltd | Remote backup method and storage system |
| US8166264B2 (en) * | 2009-02-05 | 2012-04-24 | Hitachi, Ltd. | Method and apparatus for logical volume management |
| CN103647849B (en) * | 2013-12-24 | 2017-02-08 | 华为技术有限公司 | Method and device for migrating businesses and disaster recovery system |
| CN104407939A (en) * | 2014-11-24 | 2015-03-11 | 浪潮电子信息产业股份有限公司 | Method and device for processing storage pool element data among plurality of controllers |
| CN109669812A (en) * | 2018-11-27 | 2019-04-23 | 武汉烽火信息集成技术有限公司 | Cloud data center disaster tolerance system and method based on data distribution backup |
-
2019
- 2019-08-22 CN CN201910779318.7A patent/CN112416652A/en active Pending
-
2020
- 2020-05-06 WO PCT/CN2020/088834 patent/WO2021031618A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104794028A (en) * | 2014-01-16 | 2015-07-22 | 中国移动通信集团浙江有限公司 | Disaster tolerance processing method and device, main data center and backup data center |
| CN106528327A (en) * | 2016-09-30 | 2017-03-22 | 华为技术有限公司 | Data processing method and backup server |
| CN108345515A (en) * | 2017-01-22 | 2018-07-31 | 中国移动通信集团四川有限公司 | Storage method and device and its storage system |
| CN107656705A (en) * | 2017-10-25 | 2018-02-02 | 郑州云海信息技术有限公司 | A kind of computer-readable storage medium and a kind of data migration method, apparatus and system |
| CN109669815A (en) * | 2018-12-14 | 2019-04-23 | 武汉烽火信息集成技术有限公司 | A kind of method and system restored by the long-range Mapping implementation Backup Data of LUN |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022267627A1 (en) * | 2021-06-25 | 2022-12-29 | 华为技术有限公司 | Data processing method and related device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021031618A1 (en) | 2021-02-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8473462B1 (en) | Change tracking for shared disks | |
| US10162722B2 (en) | Virtual machine aware replication method and system | |
| EP2731013B1 (en) | Backing up method, device, and system for virtual machine | |
| US8555278B2 (en) | Method and system for migrating a selected set of virtual machines between volumes | |
| US9009724B2 (en) | Load balancing data access in virtualized storage nodes | |
| US8924358B1 (en) | Change tracking of individual virtual disk files | |
| KR101471879B1 (en) | Hypervisor-based server duplication system, method thereof and recording medium storing the computer program for the duplication | |
| US9535907B1 (en) | System and method for managing backup operations of virtual machines | |
| US8713362B2 (en) | Obviation of recovery of data store consistency for application I/O errors | |
| US9354907B1 (en) | Optimized restore of virtual machine and virtual disk data | |
| US9329792B2 (en) | Storage thin provisioning and space reclamation | |
| US8555009B1 (en) | Method and apparatus for enabling and managing application input/output activity while restoring a data store | |
| US6944789B2 (en) | Method and apparatus for data backup and recovery | |
| US10146454B1 (en) | Techniques for performing data storage copy operations in an integrated manner | |
| US10061540B1 (en) | Pairing of data storage requests | |
| US11803412B2 (en) | Containerized application management system and management method | |
| US11023415B2 (en) | Reducing feature dependencies of block storage used to back NAS cluster | |
| US9003139B1 (en) | Systems and methods for recovering virtual machines after disaster scenarios | |
| US10025510B1 (en) | Technique for copying unallocated logical regions of thin logical units | |
| US20220398221A1 (en) | Persistent memory tiering supporting fast failover in a deduplicated file system | |
| WO2021031618A1 (en) | Data backup method, data backup apparatus, and data backup system | |
| US10162542B1 (en) | Data protection and incremental processing for multi-span business applications | |
| US9971532B2 (en) | GUID partition table based hidden data store system | |
| US11301156B2 (en) | Virtual disk container and NVMe storage management system and method | |
| US11144221B1 (en) | Efficient resilience in a metadata paging array for in-flight user data |
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 |