Host disk data snapshot replication method, device, equipment and storage medium

Abstract

The present specification relates to the field of host storage technology, and provides a host disk data snapshot replication method, device, equipment and storage medium, the method comprising: using a disaster recovery termination script to terminate the disaster recovery replication of a source disk volume; using a volume pair creation script to read a configuration from a configuration file and create a volume pair replication relationship; the volume pair replication relationship includes a replication relationship between a source disk volume and a target disk volume; using a replication enablement script to execute a flash copy instruction according to the volume pair replication relationship to generate a data snapshot of the source disk volume, and copy the data snapshot to the corresponding target disk volume; using a disaster recovery recovery script to restore the disaster recovery replication of the source disk volume. The embodiments of the present specification can improve the timeliness of host disk data replication.

Description

Technical Field

[0001] The present invention relates to the field of host storage technology, and in particular to a host disk data snapshot replication method, device, equipment and storage medium. Background Art

[0002] Before a business application version is put into production or upgraded, it must be fully tested and verified in the test environment before it can be put into production. The test process needs to be simulated using real production data, so the latest production data needs to be copied to the test environment. However, with the rapid growth of business, the disk capacity of the host (generally refers to large hosts) is also growing, and the process and efficiency of data replication have become important considerations. Especially for enterprise-level data replication, due to its huge amount of data, the replication process is complex and involves many manual steps, resulting in a long overall data replication cycle and low timeliness. Summary of the invention

[0003] The purpose of the embodiments of this specification is to provide a host disk data snapshot replication method, device, equipment and storage medium to improve the timeliness of host disk data replication.

[0004] To achieve the above object, on the one hand, an embodiment of the present specification provides a host disk data snapshot copying method, including:

[0005] Use the disaster recovery termination script to terminate the disaster recovery replication of the source disk volume;

[0006] Using a volume pair creation script to read configuration from a configuration file and create a volume pair replication relationship; the volume pair replication relationship includes a replication relationship between a source disk volume and a target disk volume;

[0007] Executing a flash copy instruction according to the volume pair replication relationship using a copy activation script to generate a data snapshot of the source disk volume, and copying the data snapshot to a corresponding target disk volume;

[0008] The disaster recovery copy of the source disk volume is restored using a disaster recovery script.

[0009] In an embodiment of this specification, the method further includes:

[0010] After the data snapshot is copied to the corresponding target disk volume, a volume label recovery script is used to recover the volume label of the target disk that is overwritten due to storing the data snapshot.

[0011] In an embodiment of this specification, the method further includes:

[0012] After each step is completed, the status monitoring script is used to determine whether the current step is executed successfully;

[0013] If the current step is executed successfully, the next step will be triggered.

[0014] In the embodiment of this specification, the processing logic of the status monitoring script includes:

[0015] Within a preset time after each current step is completed, periodically search the system log to see whether there is execution log information of the current step;

[0016] If the execution log information of the current step is found in the system log within the preset time period, determining whether the information header of the execution log information carries an execution success mark;

[0017] If the information header of the execution log information carries an execution success mark, it is confirmed that the current step is executed successfully.

[0018] In an embodiment of this specification, the processing logic of the status monitoring script further includes:

[0019] If the execution log information of the current step is found in the system log within the preset time period, or,

[0020] If the information header of the execution log information does not carry an execution success mark, it is confirmed that the current step execution has failed.

[0021] In the embodiment of the present specification, the disaster recovery replication includes extended remote replication.

[0022] In the embodiment of this specification, the data snapshot is a full data snapshot.

[0023] On the other hand, the embodiment of the present specification also provides a host disk data snapshot copying device, including:

[0024] A disaster recovery abort module is used to abort the disaster recovery replication of the source disk volume using a disaster recovery abort script;

[0025] A volume pair creation module, used to read the configuration from the configuration file using the volume pair creation script and create a volume pair replication relationship; the volume pair replication relationship includes a replication relationship between a source disk volume and a target disk volume;

[0026] A flash copy module, configured to execute a flash copy instruction according to the volume pair copy relationship using a copy enabling script to generate a data snapshot of the source disk volume, and copy the data snapshot to a corresponding target disk volume;

[0027] The disaster recovery module is used to recover the disaster recovery copy of the source disk volume using a disaster recovery script.

[0028] On the other hand, an embodiment of the present specification further provides a computer device, including a memory, a processor, and a computer program stored in the memory, wherein when the computer program is executed by the processor, the instructions of the above method are executed.

[0029] On the other hand, an embodiment of the present specification further provides a computer storage medium on which a computer program is stored. When the computer program is executed by a processor of a computer device, the instructions of the above method are executed.

[0030] It can be seen from the technical solutions provided in the above embodiments of this specification that the embodiments of this specification script the manual operations that may be involved in the data replication process, that is, by submitting and executing automated scripts such as disaster recovery termination scripts, volume pair creation scripts, replication enablement scripts and disaster recovery recovery scripts, manual operations are replaced, thereby realizing automated transformation of obtaining host disk data snapshots, greatly improving the timeliness of host disk data replication for enterprise-level disk data scales. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art description. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative labor. In the drawings:

[0032] Figure 1 A flowchart of a host disk data snapshot replication method in some embodiments of this specification is shown;

[0033] Figure 2 A schematic diagram showing a volume pair replication relationship in some embodiments of the present specification;

[0034] Figure 3 It shows a structural block diagram of a host disk data snapshot replication device in some embodiments of this specification;

[0035] Figure 4 The structure block diagram of the computer device in some embodiments of the present specification is shown.

[0036] [Description of Reference Numerals]

[0037] 31. Disaster recovery termination module;

[0038] 32. Volume pair creation module;

[0039] 33. Flash copy module;

[0040] 34. Disaster recovery module;

[0041] 402. Computer equipment;

[0042] 404, processor;

[0043] 406. Memory;

[0044] 408. Driving mechanism;

[0045] 410, input / output interface;

[0046] 412. Input devices;

[0047] 414. Output device;

[0048] 416. Presentation equipment;

[0049] 418. Graphical user interface;

[0050] 420, network interface;

[0051] 422. Communication link;

[0052] 424. Communication bus. DETAILED DESCRIPTION

[0053] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.

[0054] Business systems based on IBM mainframes often use FlashCopy technology to achieve enterprise-level data replication. FlashCopy technology can generate a data snapshot (equivalent to a complete image of the data at an instant) for the source disk volume, and establish a copy relationship between the source disk volume and the target disk volume, so that the data snapshot can be copied from the source disk volume to the target disk volume. However, data replication based on FlashCopy technology requires a lot of manual operation or intervention, and the timeliness of data replication is low.

[0055] It should be noted that the disk volume mentioned in the embodiments of this specification can be a logical volume or a physical volume; and the data replication mentioned in the embodiments of this specification refers to a full physical copy (i.e., a real copy), rather than a shallow copy like the Copy on Write (COW) technology. The embodiments of this specification utilize the function of FlashCopy to generate a data snapshot to ensure the availability of the source volume and the data consistency between the source volume and the target volume during the data replication process.

[0056] The data snapshot in the embodiments of this specification refers to: a fully available copy of a specified data set, which includes an image of the corresponding data at a certain point in time (the start time of the copy). The data snapshot can be a copy of the data it represents, or a replica of the data. It is similar to a camera, where the shutter flashes to record the image at that moment. The main function of the data snapshot is to enable online data backup and recovery. When an application failure or file damage occurs in the storage device, data recovery can be performed quickly, and the data can be rolled back to a state at a time point where it is eligible for use. Another function of the data snapshot is to provide another data access channel for storage users. When metadata is processed by online applications, users can access the data snapshot and can also use the data snapshot for testing and other tasks.

[0057] In view of this, in order to improve the timeliness of host disk data replication, the embodiments of this specification provide an improved host disk data replication solution based on the FlashCopy technology. In some embodiments of this specification, a host disk data snapshot replication method is provided, which can be applied to any suitable computer device, refer to Figure 1 As shown, the host disk data snapshot replication method may include the following steps:

[0058] S101, using a disaster recovery termination script to terminate the disaster recovery replication of the source disk volume.

[0059] S102: Using a volume pair creation script to read configuration from a configuration file and create a volume pair replication relationship; the volume pair replication relationship includes a replication relationship between a source disk volume and a target disk volume.

[0060] S103: Utilize a replication enabling script to execute a flash copy instruction according to the volume pair replication relationship to generate a data snapshot of the source disk volume, and copy the data snapshot to a corresponding target disk volume.

[0061] S104: Restore the disaster recovery copy of the source disk volume using a disaster recovery script.

[0062] The embodiments of this specification script the manual operations that may be involved in the data replication process, that is, by submitting and executing automated scripts such as disaster recovery termination scripts, volume pair creation scripts, replication activation scripts, and disaster recovery recovery scripts, manual operations are replaced, thereby achieving automated transformation of obtaining host disk data snapshots, greatly improving the timeliness of host disk data replication for enterprise-level disk data scales, and thus helping to reduce the difficulty of system operation and maintenance.

[0063] Before implementing the host disk data snapshot replication method, it is necessary to count in advance the various manual operations involved in data replication based on FlashCopy technology (such as respective operation instructions input manually, etc.), and then transform these manual operations into scripts to generate one or more script programs. In this way, when the script program is submitted for execution, the computer device will automatically execute a series of operations to replace the manual operations.

[0064] In order to ensure information security, business systems and databases need to be replicated for disaster recovery. That is, when the primary business system and database are used to provide external services, the real-time online backup business system and database can synchronize data with the primary business system and database. When the primary business system and database become unavailable due to failure or other reasons, the real-time online backup business system and database can be used to take over in time to ensure smooth transactions.

[0065] In this case, in order to reduce or avoid affecting the normal operation of the primary business system and the primary database, the disk volumes corresponding to the backup business system and the backup database can also be used as the source disk volumes. In addition, in order to reduce or avoid the impact of disaster recovery replication on data replication based on FlashCopy technology, the disaster recovery replication of the backup business system and the backup database can be suspended first to temporarily put the source disk volume in a static state (i.e., temporarily prohibiting read and write operations). Of course, in other embodiments, according to actual conditions, the disk volumes of the primary business system and the primary database can also be used as the source disk volumes, and this specification does not make the sole limitation on this.

[0066] Taking Extended Remote Copy (XRC) as an example, traditionally stopping XRC replication usually requires manually logging into the General Data Process Service (GDPS) and performing the XRC termination operation through the corresponding user interface, which is relatively complicated. In the embodiments of this specification, after scripting, a series of actions for stopping XRC replication are integrated into the disaster recovery termination script. Only by submitting the script in the terminal can one easily stop the XRC replication operation with one click, thereby realizing the use of the disaster recovery termination script to terminate the disaster recovery replication of the source disk volume. Among them, XRC replication is a remote asynchronous copy technology implemented by IBM based on host parallel coupling technology and disk hardware.

[0067] For example, in an exemplary embodiment, the disaster recovery termination script may include the following content parts:

[0068]

[0069] Data replication based on FlashCopy technology requires the establishment of a volume-pair replication relationship to clarify which data needs to be replicated to where. The volume-pair replication relationship refers to the replication relationship between the source disk volume and the target disk volume. For example, Figure 2 In the embodiment shown, four volume pair replication relationships are established: source volume A and target volume A' (that is, the data of source volume A is fully replicated to target volume A'), source volume B and target volume B' (that is, the data of source volume B is fully replicated to target volume B'), source volume C and target volume C' (that is, the data of source volume C is fully replicated to target volume C'), and source volume D and target volume D' (that is, the data of source volume D is fully replicated to target volume D'). Those skilled in the art can understand that Figure 2 The volume pair replication relationship shown is a one-to-one mapping relationship and is only used as an exemplary description. In other embodiments of this specification, the volume pair replication relationship can also be one-to-many, many-to-one or other mapping relationships. This specification does not limit this and can be selected according to actual needs.

[0070] Traditional FlashCopy technology requires manual establishment of each volume pair replication relationship. Production environments usually have tens of thousands of logical volumes, and tens of thousands of commands may need to be sent to establish each volume pair replication relationship. In the embodiments of this specification, after scripting, all volume pair configurations are pre-written into the volume pair creation script, so that you only need to submit the script in the terminal to batch create volume pair relationships.

[0071] On the basis of the established replication relationship of each volume pair, the data replication process of the traditional FlashCopy technology requires manual initiation of data replication instructions. For example, it is necessary to manually select the volume pair to be replicated from the user interface displayed on the terminal, and then manually click the "Execute Replication" button (or other similar interactive controls) to issue an instruction to start data replication. In the embodiment of this specification, after scripting, the replication activation script can be used to automatically execute the flash copy instruction according to the volume pair replication relationship.

[0072] For example, in an exemplary embodiment, the replication enablement script may include the following content sections:

[0073] / / MAKEVER EXEC PGM=SDSF,COND=(4,LE)

[0074] / / SYSPRINT DD SYSOUT = *

[0075] / / SYSTSPRT DD SYSOUT = *

[0076] / / SYSTSIN DD*

[0077] SUBMIT'XRC.XCOPY.CNTL(ZSF)'

[0078] / / STEP2 EXEC PGM=IRXJCL,

[0079] / / PARM='@SYSCMD CMD("DR,R")MSG(ANTU2220D)RPY(I)TO(900)I(20)RPYNU M(1)QUIT(Y)'

[0080] / / SYSEXEC DD DISP=SHR,DSN=SYSADM.ZOSMF.LIB

[0081] / / SYSTSPRT DD SYSOUT = *

[0082] / / SYSTSIN DD DUMMY

[0083] / *

[0084] After completing the data replication under all volume-to-volume replication, the disaster recovery replication of the source disk volume should be restored in time to ensure the stable operation of the business system and database and data security. In the traditional FlashCopy technology, after the data replication is completed, it is necessary to manually log in to the GDPS and perform the XRC enablement operation on the corresponding user interface, which is relatively complicated. In the embodiments of this specification, after scripting transformation, a series of actions to enable the XRC replication action are integrated into the disaster recovery script. You only need to submit the script on the terminal to easily realize one-click recovery of the XRC replication operation, thereby realizing the automatic recovery of the disaster recovery replication of the source disk volume using the disaster recovery script.

[0085] For example, in an exemplary embodiment, the disaster recovery script may include the following content parts:

[0086] / *

[0087] / / TIMER EXEC PGM=IEFBR14,COND=(0,NE)

[0088] / / COMMAND'SA39AT 05:31:08,ID=YTS,SUBMITSYSADM.XRC.JCL(STATXRC)'

[0089] After the data is overwritten based on FlashCopy technology, the volume label of the target disk volume is often overwritten by the source disk volume, so it is necessary to restore the original volume label of the target disk volume through a recovery (Recover) operation. In some embodiments, after the data snapshot is copied to the corresponding target disk volume, a volume label recovery script can be used to automatically restore the volume label of the target disk that was overwritten due to the storage of the data snapshot. Compared with the traditional method of manually issuing a recovery command to restore the original volume label of each target disk, the embodiment of this specification can achieve one-click recovery of the original volume labels of all target disk volumes by submitting a volume label recovery script at the terminal.

[0090] For example, in an exemplary embodiment, the volume label recovery script may include the following content parts:

[0091]

[0092] In some embodiments, the host disk data snapshot replication method may further include: after each current step is completed, using a status monitoring script to determine whether the current step is executed successfully; if the current step is executed successfully, triggering the execution of the next step; otherwise, the program is interrupted. In this way, compared with the traditional FlashCopy technology, after each step of operation is implemented, it is necessary to manually determine the execution status before determining whether to continue to execute the next step, the state monitoring script in the embodiment of this specification replaces the manual judgment and is automatically triggered according to the judgment result, which can further reduce the manual operation of the host disk data replication, thereby helping to further improve the timeliness of the host disk data replication.

[0093] In some embodiments, "a step" may refer to the processing logic of a script, and therefore, "the current step" may refer to the currently executed script, and "the next step" may refer to the next script corresponding to the currently executed script. For example, in one embodiment, the entire host disk data snapshot replication process includes multiple scripts such as a disaster recovery termination script, a volume pair creation script, a replication enablement script, and a disaster recovery recovery script. If the currently executed script is a disaster recovery termination script, then its next script is a volume pair creation script. Therefore, in the embodiments of the present specification, by transforming the entire host disk data snapshot replication process into multiple scripts and combining them with the above-mentioned status monitoring script, the execution control and management of the entire host disk data snapshot replication process can be conveniently implemented.

[0094] For example, in an exemplary embodiment, the status monitoring script may include the following content parts:

[0095]

[0096]

[0097] Based on the above-mentioned status monitoring script, after each current step is completed, the background will start an automated judgment program: PP3KSA39SETFK. This program will periodically search the system log for the execution log information of the current step within the preset time after each current step is completed; if the execution log information of the current step is found in the system log within the preset time, it will be further judged whether the information header of the execution log information carries an execution success mark; if the information header of the execution log information carries an execution success mark, it is confirmed that the current step is executed successfully, and the next operation step can be determined accordingly. Otherwise (for example, the execution log information of the current step is found in the system log within the preset time, or the information header of the execution log information does not carry an execution success mark), it can be considered that the current step has failed to execute, the program is interrupted, and the next operation step is not performed. In this way, it is conducive to achieving the purpose of obtaining a full data snapshot with one click.

[0098] For example, in the above-mentioned status monitoring script, if the program retrieves the information header GEO152E, it is determined that the execution has failed and the program is interrupted; if the information header GEO306E is retrieved, it indicates that the execution has been successful and the program automatically continues to the next step.

[0099] Although the process flows described above include multiple operations that occur in a particular order, it should be clearly understood that the processes may include more or fewer operations, which may be performed sequentially or in parallel (eg, using parallel processors or a multi-threaded environment).

[0100] Corresponding to the above host disk data snapshot replication method, this specification also provides a host disk data snapshot replication device. Figure 3 As shown, the host disk data snapshot replication device may include:

[0101] A disaster recovery termination module 31 can be used to terminate the disaster recovery replication of the source disk volume using a disaster recovery termination script;

[0102] The volume pair creation module 32 may be used to read the configuration from the configuration file using the volume pair creation script and create a volume pair replication relationship; the volume pair replication relationship includes a replication relationship between a source disk volume and a target disk volume;

[0103] The flash copy module 33 may be used to execute a flash copy instruction according to the volume pair replication relationship using a replication enabling script to generate a data snapshot of the source disk volume, and to copy the data snapshot to a corresponding target disk volume;

[0104] The disaster recovery module 34 may be used to recover the disaster recovery copy of the source disk volume using a disaster recovery script.

[0105] In some embodiments, the host disk data snapshot copying device may further include a volume label recovery module which can use a volume label recovery script to recover the volume label of the target disk that is overwritten by storing the data snapshot after the flash copy module copies the data snapshot to the corresponding target disk volume.

[0106] In some embodiments, the host disk data snapshot replication device may further include a status monitoring module. The volume label recovery module may use the status monitoring script to determine whether the current step is successfully executed after other modules (such as the disaster recovery termination module, the volume pair creation module, the flash copy module, etc.) complete the current step execution; if the current step is successfully executed, the execution of the next step is triggered.

[0107] In some embodiments, the processing logic of the status monitoring script may include:

[0108] Within a preset time after each current step is completed, periodically search the system log to see whether there is execution log information of the current step;

[0109] If the execution log information of the current step is found in the system log within the preset time period, determining whether the information header of the execution log information carries an execution success mark;

[0110] If the information header of the execution log information carries an execution success mark, it is confirmed that the current step is executed successfully.

[0111] In some embodiments, the processing logic of the status monitoring script may further include:

[0112] If the execution log information of the current step is found in the system log within the preset time period, or,

[0113] If the information header of the execution log information does not carry an execution success mark, it is confirmed that the current step execution has failed.

[0114] In some embodiments, the disaster recovery replication includes extended remote replication.

[0115] In some embodiments, the data snapshot is a full data snapshot.

[0116] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0117] The embodiments of this specification also provide a computer device. Figure 4As shown, in some embodiments of the present specification, the computer device 402 may include one or more processors 404, such as one or more central processing units (CPUs) or graphics processing units (GPUs), and each processing unit may implement one or more hardware threads. The computer device 402 may also include any memory 406, which is used to store any kind of information such as code, settings, data, etc. In a specific embodiment, the computer program on the memory 406 and can be run on the processor 404, when the computer program is run by the processor 404, can execute the instructions of the host disk data snapshot replication method described in any of the above embodiments. Non-limiting, for example, the memory 406 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory can use any technology to store information. Further, any memory can provide volatile or non-volatile retention of information. Further, any memory can represent a fixed or removable component of the computer device 402. In one case, when the processor 404 executes an associated instruction stored in any memory or a combination of memories, the computer device 402 can perform any operation of the associated instruction. The computer device 402 also includes one or more drive mechanisms 408 for interacting with any storage, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.

[0118] The computer device 402 may also include an input / output interface 410 (I / O) for receiving various inputs (via input device 412) and for providing various outputs (via output device 414). A specific output mechanism may include a presentation device 416 and an associated graphical user interface 418 (GUI). In other embodiments, the input / output interface 410 (I / O), input device 412, and output device 414 may not be included, and the computer device 402 may be used as a computer device in a network. The computer device 402 may also include one or more network interfaces 420 for exchanging data with other devices via one or more communication links 422. One or more communication buses 424 couple the components described above together.

[0119] The communication link 422 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 422 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

[0120] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products of some embodiments of the present specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processor to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processor generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0121] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processor to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0122] These computer program instructions can also be loaded onto a computer or other programmable data processor so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0123] In a typical configuration, a computer device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0124] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0125] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computer device. As defined in this specification, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0126] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, the embodiments of this specification may take the form of complete hardware embodiments, complete software embodiments or embodiments combining software and hardware. Moreover, the embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0127] The present specification embodiments may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present specification embodiments may also be practiced in distributed computing environments where tasks are performed by remote processors connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0128] It should also be understood that in the embodiments of this specification, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0129] Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. In the description of this specification, the description of the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiment of this specification. In this specification, the schematic representation of the above terms does not necessarily target the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, in the absence of contradiction, a person skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0130] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A host disk data snapshot replication method, characterized in that: include: Use the disaster recovery termination script to terminate the disaster recovery replication of the source disk volume; Use the volume pair creation script to read the configuration from the configuration file and create a volume pair replication relationship; The volume pair replication relationship includes a replication relationship between a source disk volume and a target disk volume; Executing a flash copy instruction according to the volume pair replication relationship using a copy activation script to generate a data snapshot of the source disk volume, and copying the data snapshot to a corresponding target disk volume; The disaster recovery script is used to restore the disaster recovery copy of the source disk volume, and the volume label recovery script is used to restore the volume label of the target disk that is overwritten due to storing the data snapshot.

2. The host disk data snapshot replication method according to claim 1, characterized in that: Also includes: After each step is completed, the status monitoring script is used to determine whether the current step is executed successfully; If the current step is executed successfully, the next step will be triggered.

3. The host disk data snapshot replication method according to claim 2, characterized in that: The processing logic of the status monitoring script includes: Within a preset time after each current step is completed, periodically search the system log to see whether there is execution log information of the current step; If the execution log information of the current step is found in the system log within the preset time period, determining whether the information header of the execution log information carries an execution success mark; If the information header of the execution log information carries an execution success mark, it is confirmed that the current step is executed successfully.

4. The host disk data snapshot replication method according to claim 3, characterized in that: The processing logic of the status monitoring script also includes: If the execution log information of the current step is not retrieved in the system log within the preset time period, or, If the information header of the execution log information does not carry an execution success mark, it is confirmed that the current step execution has failed.

5. The host disk data snapshot replication method according to claim 1, characterized in that: The disaster recovery replication includes extended remote replication.

6. The host disk data snapshot replication method according to claim 1, characterized in that: The data snapshot is a full data snapshot.

7. A host disk data snapshot replication device, characterized in that: include: A disaster recovery abort module is used to abort the disaster recovery replication of the source disk volume using a disaster recovery abort script; A volume pair creation module, used to read the configuration from the configuration file using the volume pair creation script and create a volume pair replication relationship; the volume pair replication relationship includes a replication relationship between a source disk volume and a target disk volume; A flash copy module, configured to execute a flash copy instruction according to the volume pair copy relationship using a copy enabling script to generate a data snapshot of the source disk volume, and copy the data snapshot to a corresponding target disk volume; A disaster recovery module, used for restoring the disaster recovery copy of the source disk volume using a disaster recovery script; The volume label recovery module is used to use a volume label recovery script to recover the volume label of the target disk that is overwritten due to storing the data snapshot after the flash copy module copies the data snapshot to the corresponding target disk volume.

8. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that: When the computer program is executed by the processor, the computer program executes the instructions of the method according to any one of claims 1 to 6.

9. A computer storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor of a computer device, the computer program executes instructions of the method according to any one of claims 1 to 6.

Images