WO2017211099A1

WO2017211099A1 - Data backup method and apparatus

Info

Publication number: WO2017211099A1
Application number: PCT/CN2017/075489
Authority: WO
Inventors: 伏高顶; 杨文珺
Original assignee: 华为技术有限公司
Priority date: 2016-06-06
Filing date: 2017-03-02
Publication date: 2017-12-14
Also published as: CN106055433A; CN106055433B

Abstract

Disclosed are a data backup method and apparatus. The method comprises: determining an application requiring data backup, and determining at least one storage device storing data of the application (S200); freezing disk IO corresponding to each of the at least one storage devices (S210); for each of the at least one storage devices, instructing a backup device to perform data backup for the application (S220); and after determining that the backup device has completed data backup for the application, restoring disk IO corresponding to each storage device (S230). In the present invention a host agent ensures consistency of application data by freezing disk IO. The backup device only needs to interface with the host agent via a standard southbound interface, and does not need to carry out specific backup pre-processing and backup post-processing actions for an upper-layer application, thus reducing the complexity and improving efficiency of data backup.

Description

Data backup method and device

Technical field

The present invention relates to the field of computers, and in particular, to a data backup method and apparatus.

Background technique

IT systems in enterprise data centers may cause unplanned downtime due to natural disasters such as fires, floods, earthquakes, etc., resulting in business interruptions, or business interruptions due to human factors such as misuse, software errors, and virus intrusions. Once the business is interrupted, it will cause unpredictable losses to the enterprise. As a result, more and more companies are realizing the need to build their own disaster recovery sites to prevent unknown disasters.

When the application data of each application in the system is backed up to the disaster recovery site, in order to ensure that the service can be correctly restored when the disaster occurs, it is necessary to ensure the consistency of the application data during data backup. The application data consistency here refers to the application having The caching mechanism, so the data stored in the storage device is not the complete data for the application, and the data backup needs to ensure that the cached data for the application and the data on the storage device are backed up. Otherwise, in the event of a disaster, although the data has been backed up to the disaster recovery site, the backup data does not guarantee the consistency of the application data, which is very difficult or even unrecoverable for service recovery.

For example, because the database has a caching mechanism inside, part of the data in the database is written to the disk, and some of it is stored in its own cache space. When the system does not have a disaster recovery site, the database cache space after the system is out of plan. The saved data will be lost, and only the data in the disk can be recovered. This will result in inconsistent data before the system is shut down and after the system is restarted, which may make the database service recovery difficult and even cause the database to fail to restart. When the system has a disaster recovery site, all the data in the database must be backed up to the disaster recovery site. The data written to the disk and the data stored in the cache space are backed up to the disaster recovery site to ensure the consistency of the application data.

Therefore, the self-built disaster recovery system needs to freeze the application IO before the data is backed up, and flush the dirty data cached in the application to the storage device to ensure the consistency of the application data and enable the service to be restored. The technical principles of application data consistency backup for different applications are basically similar. As shown in Figure 1, the application that needs to perform data backup is a database, and the backup device that performs data backup is a storage array. The application data is described below with reference to Figure 1. Typical process of backup:

S101: The management server sends a startup data backup protection command to the host agent.

S102: The host agent notifies the database to submit the cached dirty data to the corresponding storage device and freezes the database IO.

Freezing the database IO means stopping the write operation to the database.

S103: The management server sends a startup data backup command to the storage array to perform data backup on each storage device that stores the database data.

For example, the data can be backed up by remote replication, snapshot, clone, etc. of the storage array. When the storage array uses the backup mode for data backup, the state of the database needs to be judged, and it is determined that the dirty data has been submitted to the corresponding data. When the storage device freezes the database IO, the data backup for each storage device that holds the database data is started.

S104: After determining that the application data backup for the database ends, the management server sends an end backup protection command to the host agent.

S105: The host agent notifies the database to restore the database IO.

Restoring the database IO restores the write operation to the database.

Therefore, the above steps can ensure that the data backed up to the disaster recovery site meets the requirements of application data consistency, and the service can be restored when the data is used for service recovery.

However, due to the diversity of applications deployed on Linux service hosts, such as database Oracle, DB2, Sybase, MySQL, large-scale application SAP, file system EXT3, EXT4, JFS, VXFS, HFS, etc., therefore, it is necessary to ensure that for each Applications perform application data consistency backup processing, but different methods for ensuring application data consistency are different. For example, Oracle ensures application data consistency by setting the database to hot standby mode; SQL Server ensures application data. The way to be consistent is: brush database cache, VSS freeze disk write IO; DB2 ensures application data consistency is to freeze database write IO, brush database cache; file system to ensure application data consistency is: freeze file system write IO , brush the file system cache.

Therefore, in the prior art, when the backup device performs data backup of the application, it is necessary to consider the backup features of each application itself, and even the backup features corresponding to different versions of one application respectively, resulting in performing various applications in the system. Data backup is more complicated.

Summary of the invention

The purpose of the embodiments of the present invention is to provide a data backup method and device, which solves the problem of high complexity when the backup device performs data backup for each application in the system.

The purpose of the embodiment of the present invention is achieved by the following technical solutions:

A data backup method, including:

Determining an application requiring data backup, and at least one storage device storing data of the application;

Freeing the disk IO corresponding to each of the at least one storage device;

Notifying the backup device to perform a data backup for the storage device for each of the at least one storage device;

After determining that the backup device completes the data backup for the application, the disk IO corresponding to each storage device is restored.

Therefore, by freezing the disk IO to ensure application data consistency, the backup device does not need to care about the specific backup pre-processing and backup post-processing of the upper-layer application, and only needs to connect to the host agent through the standard southbound interface, thereby reducing the backup complexity. , improve backup efficiency.

In a possible implementation, the application that needs to perform data backup is determined, including:

Receiving an application registration message sent by a third-party system, where the application registration message is used to indicate an application that needs to perform data backup.

In a possible implementation, after determining at least one storage device storing data of the application, before freezing the disk IO corresponding to each of the at least one storage device, further comprising:

Receive a startup data backup message sent by a third-party system.

Notifying the application to perform backup pre-processing, the backup pre-processing is to notify the application to store the cached dirty data to the corresponding storage device and/or to notify the application to process the transaction being executed.

In a possible implementation, the disk IO corresponding to each of the at least one storage device is frozen, include:

Cache the received IO command for each storage device to the IO queue of the corresponding storage device; or

The received IO command for each storage device is discarded.

Therefore, the embodiments of the present invention propose various ways of freezing the disk IO, which increases the flexibility of freezing the disk IO.

In a possible implementation, after the backup device is notified to perform data backup for the application for each of the at least one storage device, the method further includes:

Start the data backup timer;

After determining that the backup device completes the data backup for the application, the method further includes:

When it is determined that the data backup timer has not timed out, the data backup timer is cleared.

Therefore, the data backup timer can freeze the disk IO for too long, which affects the system operation.

In a possible implementation, after recovering the disk IO corresponding to each storage device, the method further includes:

The IO commands cached in the IO queue of each storage device are sequentially taken out and submitted to the corresponding storage device; or,

Stop dropping IO commands for each storage device and restore the initial settings for the corresponding storage device.

Therefore, when recovering disk IO, it is necessary to recover according to different frozen disk IO modes.

Sending a backup end notification message to the third-party system, the backup end notification message is used to notify the third-party system whether the data backup for the application is successful.

In a second aspect, a data backup device includes:

a backup control module for determining an application that needs to perform data backup;

An application driver module, configured to determine at least one storage device that stores data of the application;

a disk drive module, configured to freeze a disk IO corresponding to each of the at least one storage device;

a backup driver module, configured to notify the backup device to perform a data backup for the storage device for each of the at least one storage device;

The disk drive module is further configured to restore the disk IO corresponding to each storage device after determining that the backup device completes the data backup for the application.

In a possible implementation, when determining an application that needs to perform data backup, the backup control module is specifically configured to:

In a possible implementation manner, the backup control module is further configured to:

After determining the at least one storage device storing the data of the application, receiving a startup data backup message sent by the third-party system before freezing the disk IO corresponding to each of the at least one storage device.

In a possible implementation manner, the application driving module is further used to

After the analyzing unit determines the at least one storage device storing the data of the application, before the freezing unit freezes the disk IO corresponding to each of the at least one storage device, notifying the application to perform a backup front Processing, the backup pre-processing is to notify the application to store the cached dirty data to the corresponding storage device and/or notify the application to process the transaction being executed.

In a possible implementation, when the disk IO corresponding to each of the at least one storage device is frozen, the disk drive module is specifically configured to:

The received IO command for each storage device is discarded.

In a possible implementation, the disk drive module is further configured to:

After the backup device is notified to perform data backup for the application for each of the at least one storage device, start a data backup timer;

The disk drive module is further configured to:

After determining that the backup device completes the data backup for the application, determining that the data backup timer has not timed out, the data backup timer is cleared.

In a possible implementation, the disk drive module is further configured to:

After recovering the disk IO corresponding to each storage device, the IO commands cached in the IO queue of each storage device are sequentially taken out and submitted to the corresponding storage device; or

After restoring the disk IO corresponding to each storage device, stop dropping the IO command for each storage device and restore the initial settings for the corresponding storage device.

After the disk IO corresponding to each storage device is restored, a backup end notification message is sent to the third-party system, and the backup end notification message is used to notify the third-party system whether the data backup for the application is successful.

In a third aspect, an embodiment of the present invention provides a data backup device, including:

transceiver;

a memory for storing instructions; and

a processor, coupled to the memory and the transceiver, for executing the instructions to perform the following steps when executing the instructions:

Freeing the disk IO corresponding to each of the at least one storage device;

The embodiment of the present invention provides a data backup method, the method includes: determining an application that needs to perform data backup, and storing at least one storage device of the application data; and freezing the disk IO corresponding to each storage device in the at least one storage device, To ensure that the application data is consistent; the backup device is configured to perform data backup for the application for each storage device in the at least one storage device, and the backup device does not need to care about the specific backup pre-processing and backup post-processing of the upper-layer application at this time, and only needs to pass The standard southbound interface is connected to the host agent; after determining that the backup device completes the data backup for the application, the disk IO corresponding to each storage device is restored. Therefore, the backup complexity is reduced and the backup efficiency is improved.

DRAWINGS

1 is a typical process of applying data backup in the background art of the present invention;

2 is a flowchart of an overview of data backup in an embodiment of the present invention;

3 is a schematic structural diagram of a Host agent according to an embodiment of the present invention;

4 is a specific process of data backup for applying Oracle and DB2 according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a data backup apparatus according to an embodiment of the present invention; FIG.

FIG. 6 is a schematic structural diagram of a data backup device according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

Referring to FIG. 2, an embodiment of the present invention provides a data backup method, including:

S200: The Host agent determines an application that needs to perform data backup, and at least one storage device that stores data of the application.

S210: The Host agent freezes the disk IO corresponding to each storage device in at least one storage device.

S220: The host agent notifies the backup device to perform data backup for the application for each of the at least one storage device.

S230: After determining that the backup device completes the data backup for the application, the host agent restores the disk IO corresponding to each storage device.

The backup device here can be a storage array or a backup server.

Specifically, for S200, the Host agent receives an application registration message sent by a third-party system, and the application registration message is used to indicate an application that needs to perform data backup. For example, the application registration message contains the database instance name and password. The third party system here can be the management server in FIG.

After the Host agent determines the application that needs to perform data backup, it begins to perform environment preparation for the application, that is, further determines at least one storage device that stores data of the application. For example, a database application has multiple types of data, and various types of data are stored in different storage devices.

Optionally, after executing S200, before performing S210, that is, after determining at least one storage device storing data of the application, the Host agent receives the third party before freezing the disk IO corresponding to each storage device in the at least one storage device. A startup data backup message sent by the system, the message is used to trigger the host agent to send an instruction to the storage device to perform data backup for the application.

Optionally, after executing S200, before executing S210, the Host agent notifies the application to perform backup pre-processing, the backup pre-processing is to notify the application to store the cached dirty data to the corresponding storage device and/or notify the application that the processing is being executed. Business.

For different applications, the content of the backup pre-processing is different. Some applications only need to store the cached dirty data to the corresponding storage device. Some applications need to process the transaction being executed, including ending the currently executing transaction or waiting for the current The executed transaction is completed, etc. The backup pre-processing here is triggered by the Host agent, and the backup device does not need to care about the backup pre-processing content of each application.

Specifically, for S210, the host agent freezes the disk IO corresponding to each storage device in the at least one storage device, but is not limited to the following two methods:

The first way: the host agent caches the received IO command for each storage device to the IO queue of the corresponding storage device.

After recovering the disk IO corresponding to each storage device in the above manner, the host agent sequentially takes out the IO commands cached in the IO queue of each storage device and submits them to the corresponding storage device.

The second way: The host agent discards the received IO commands for each storage device.

After the disk 10 corresponding to each storage device is restored in the above manner, the IO command for each storage device is stopped and the initial setting for the corresponding storage device is restored.

For S220, when the backup device receives the data backup instruction for the application, the backup device backs up the data for the application to the disaster recovery site. For example, when the backup device is a storage array, the storage array can back up the data by remote copying tasks, or by creating snapshots, or by launching clones, or by specific backup software.

Further, after performing S220, that is, after notifying the backup device to perform data backup for the application for each of the at least one storage device, the Host agent starts a data backup timer.

If the host agent determines that the backup device completes the data backup for the application, and the data backup timer has not timed out, the data backup timer is cleared.

If the data backup timer expires, the host agent determines that there is a storage device that does not complete the data backup for the application in at least one storage device, and then restores the disk IO corresponding to each storage device, so as to prevent the disk IO from being frozen for a long time to run on the system. Have an impact.

Optionally, after executing S230, the Host agent notifies the application to perform backup post processing, and the backup post processing corresponds to the backup preprocessing. Unlike backup pre-processing, the content of backup post-processing is different for different applications. For example, if the backup pre-processing performed by the application is to store the cached dirty data to the corresponding storage device, the backup post-processing is not required. If the backup pre-processing performed by the application is to block the commit transaction, the backup post-processing performed by the application is the resume transaction commit.

Optionally, after recovering the disk IO corresponding to each storage device, the host agent sends a backup end notification message to the third-party system, and the backup end notification message is used to notify the third-party system whether the data backup for the application is successful.

Referring to FIG. 3 and FIG. 4, the host agent is divided into four modules in FIG. 3, and the backup control module (BackupController) interfaces with a third-party system through a standard northbound interface, and is used for communication with a third-party system, and the application driver module is used. (AppDriver) for determining at least one storage device storing data of the application, and notifying each application to perform backup pre-processing (for example, notifying that OracleDriver and DB2Driver respectively perform backup pre-processing as shown in FIG. 4), disk drive module (DiskDriver) ) Used to freeze disk IO and recover disk IO. The backup driver module (BackupDriver) is used to interface with the backup device through the standard southbound interface. Figure 4 shows the specific process of data backup for Oracle and DB2, including:

S401: The third-party system sends an application registration message to the Host agent, where the password includes the application name of Oracle and Oracle and the passwords of the application names DB2 and DB2.

Here, the third-party system registers the application message that needs to be backed up by the standard to the BackupController through the standard northbound interface.

S402: The Host agent receives the application registration message, and determines, according to the application registration message, that the application that needs to perform data backup is Oracle and DB2.

S403: The host agent prepares an application environment for the Oracle and the DB2, and determines at least one storage device corresponding to the Oracle and at least one storage device corresponding to the DB2.

For example, the host agent obtains at least one storage device corresponding to Oracle from the Oracle according to the application registration message.

S404: The third-party system sends a startup data backup message to the host agent.

S405: The Host agent receives the startup data backup message, and notifies Oracle and DB2 to perform backup pre-processing.

That is, through AppDriver, Oracle and DB2 are notified to perform backup pre-processing.

S406: Oracle and DB2 perform backup pre-processing separately.

For example, Oracle needs to set the database to hot standby mode.

S407: The host agent freezes the disk IO corresponding to each storage device in the at least one storage device corresponding to the Oracle device, and the disk IO corresponding to each storage device in the at least one storage device corresponding to the DB2.

That is, the disk IO is frozen by DiskDriver.

S408: The host agent notifies the backup device to perform data backup for Oracle corresponding to at least one storage device corresponding to the Oracle, and notifies the backup device to perform data backup for the DB2 by using at least one storage device corresponding to the DB2.

That is, BackupDriver notifies the backup device to perform data backup through the standard southbound interface, and does not need to care about the specific backup pre-processing and backup post-processing of the upper-layer application. The backup device here is a storage array or a backup server.

S409: The backup server performs data backup for Oracle for at least one storage device corresponding to Oracle, and performs data backup for DB2 for at least one storage device corresponding to DB2.

S410: The host agent determines, when the data backup for Oracle is completed, restores the disk IO corresponding to each storage device in the at least one storage device corresponding to the Oracle, and determines that at least one storage device corresponding to the Oracle is restored when the data backup for the DB2 is completed. Disk IO corresponding to each storage device.

That is to restore disk IO through DiskDriver.

S411: The Host agent notifies the Oracle and DB2 data backups to complete.

S412: Oracle and DB2 perform backup post processing separately.

S413: The Host agent sends a backup end notification message to the third-party system to notify the third-party system that the data backup for Oracle and DB2 is successful.

Based on the same inventive concept, the embodiment of the present invention further provides a data backup device, which includes the host agent in the embodiment shown in FIG. 2, which can be used to execute the method embodiment corresponding to FIG. 2, and thus the present invention is implemented. For the implementation of the data backup device provided in the example, refer to the implementation manner of the method, and the repeated description is not repeated.

Referring to FIG. 5, an embodiment of the present invention provides a data backup device 50, including:

The backup control module 51 is configured to determine an application that needs to perform data backup;

An application driver module 52, configured to determine at least one storage device that stores data of the application;

The disk drive module 53 is configured to freeze the disk IO corresponding to each of the at least one storage device;

The backup driver module 54 is configured to notify the backup device to perform data backup for the storage device for each of the at least one storage device;

The disk drive module 53 is further configured to restore the disk IO corresponding to each storage device after determining that the backup device completes the data backup for the application.

In a possible implementation manner, when determining an application that needs to perform data backup, the backup control module 51 is specifically configured to:

In a possible implementation, the backup control module 51 is further configured to:

In a possible implementation manner, the application driving module 52 is further used to

In a possible implementation, when the disk IO corresponding to each of the at least one storage device is frozen, the disk drive module 53 is specifically configured to:

The received IO command for each storage device is discarded.

In a possible implementation, the disk drive module 53 is further configured to:

The disk drive module 53 is further configured to:

Based on the same inventive concept, the data backup device is also provided in the embodiment of the present invention, and the device can be used to perform the method embodiment corresponding to the foregoing FIG. 2, and therefore, the implementation manner of the data backup device provided by the embodiment of the present invention can be referred to The implementation of the method, the repetition will not be repeated.

Referring to FIG. 6, an embodiment of the present invention provides a data backup device, including:

Transceiver 61;

a memory 62 for storing instructions; and

The processor 63 is respectively connected to the memory 62 and the transceiver 61 for executing the instructions to perform the following steps when executing the instructions:

Freeing the disk IO corresponding to each of the at least one storage device;

It should be noted that the connection manner between the parts shown in FIG. 6 is only one possible example. It may also be that the transceiver 61 and the memory 63 are both connected to the processor 62, and between the transceiver 61 and the memory 63. There is no connection, or it can be other possible connections.

In summary, the method provided by the embodiment of the present invention, on the Linux service host, the host agent ensures the application data consistency by freezing the disk IO mode, and the backup device only needs to connect to the host agent through the standard southbound interface. Pay attention to the specific backup pre-processing and backup post-processing of the upper application, which reduces the backup complexity and improves the backup efficiency.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

While the preferred embodiment of the invention has been described, it will be understood that Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and

It is apparent that those skilled in the art can make various modifications and variations to the embodiments of the invention without departing from the spirit and scope of the embodiments of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the embodiments of the invention.

Claims

A data backup method, comprising:

Determining an application requiring data backup, and at least one storage device storing data of the application;

Freeing the disk IO corresponding to each of the at least one storage device;

Notifying the backup device to perform a data backup for the storage device for each of the at least one storage device;

After determining that the backup device completes the data backup for the application, the disk IO corresponding to each storage device is restored.
The method of claim 1 wherein the determining the application for data backup comprises:

Receiving an application registration message sent by a third-party system, where the application registration message is used to indicate an application that needs to perform data backup.
The method according to claim 1 or 2, wherein after determining at least one storage device storing data of the application, before freezing the disk IO corresponding to each of the at least one storage device, include;

Receive a startup data backup message sent by a third-party system.
The method according to any one of claims 1 to 3, wherein, after determining at least one storage device storing data of the application, freezing a disk IO corresponding to each of the at least one storage device Previously, including;

Notifying the application to perform backup pre-processing, the backup pre-processing is to notify the application to store the cached dirty data to the corresponding storage device and/or to notify the application to process the transaction being executed.
The method of any one of the preceding claims, wherein the freezing of the disk IO corresponding to each of the at least one storage device comprises:

Cache the received IO command for each storage device to the IO queue of the corresponding storage device; or

The received IO command for each storage device is discarded.
The method of any one of the preceding claims, further comprising: after notifying the backup device to perform data backup for the application for each of the at least one storage device, further comprising:

Start the data backup timer;

After determining that the backup device completes the data backup for the application, the method further includes:

When it is determined that the data backup timer has not timed out, the data backup timer is cleared.
The method of claim 5, further comprising: after restoring the disk IO corresponding to each storage device,

The IO commands cached in the IO queue of each storage device are sequentially taken out and submitted to the corresponding storage device; or,

Stop dropping IO commands for each storage device and restore the initial settings for the corresponding storage device.
The method according to any one of claims 2-7, further comprising: after restoring the disk IO corresponding to each storage device, further comprising:

Sending a backup end notification message to the third-party system, the backup end notification message is used to notify the third-party system whether the data backup for the application is successful.
A data backup device, comprising:

a backup control module for determining an application that needs to perform data backup;

An application driver module, configured to determine at least one storage device that stores data of the application;

a disk drive module, configured to freeze a disk IO corresponding to each of the at least one storage device;

a backup driver module, configured to notify the backup device to perform a data backup for the storage device for each of the at least one storage device;

The disk drive module is further configured to restore the disk IO corresponding to each storage device after determining that the backup device completes the data backup for the application.
The device according to claim 9, wherein when the application for data backup is determined, the backup control module is specifically configured to:

Receiving an application registration message sent by a third-party system, where the application registration message is used to indicate an application that needs to perform data backup.
The device of claim 9 or 10, wherein the backup control module is further configured to:

After determining the at least one storage device storing the data of the application, receiving a startup data backup message sent by the third-party system before freezing the disk IO corresponding to each of the at least one storage device.
The device according to any one of claims 9 to 11, wherein the application driving module is further used for

After the analyzing unit determines the at least one storage device storing the data of the application, before the freezing unit freezes the disk IO corresponding to each of the at least one storage device, notifying the application to perform a backup front Processing, the backup pre-processing is to notify the application to store the cached dirty data to the corresponding storage device and/or notify the application to process the transaction being executed.
The device according to any one of claims 9 to 12, wherein, when the disk IO corresponding to each of the at least one storage device is frozen, the disk drive module is specifically configured to:

Cache the received IO command for each storage device to the IO queue of the corresponding storage device; or

The received IO command for each storage device is discarded.
The device according to any one of claims 9 to 13, wherein the disk drive module is further configured to:

After the backup device is notified to perform data backup for the application for each of the at least one storage device, start a data backup timer;

The disk drive module is further configured to:

After determining that the backup device completes the data backup for the application, determining that the data backup timer has not timed out, the data backup timer is cleared.
The device of claim 13, wherein the disk drive module is further configured to:

After recovering the disk IO corresponding to each storage device, the IO commands cached in the IO queue of each storage device are sequentially taken out and submitted to the corresponding storage device; or

After restoring the disk IO corresponding to each storage device, stop dropping the IO command for each storage device and restore the initial settings for the corresponding storage device.
The device according to any one of claims 10-15, wherein the backup control module is further configured to:

After the disk IO corresponding to each storage device is restored, a backup end notification message is sent to the third-party system, and the backup end notification message is used to notify the third-party system whether the data backup for the application is successful.