Replication volume management system, replication volume management method, device and storage medium

Abstract

The embodiment of the present invention discloses a replica volume management system, a replica volume management method, a device and a storage medium. It includes: a control front end, an information center and a cluster composed of multiple nodes; the cluster includes at least one management node; the information center is used to store a replica volume information association table containing the binding relationship between each pre-created replica volume and the corresponding management node; the control front end is used to determine the target management node associated with the replica volume to be managed through the replica volume information association table obtained from the information center, generate a replica volume management request for the replica volume to be managed and send it to the target management node; the target management node is used to receive and parse the replica volume management request, and perform replica volume management on the obtained replica volume to be managed; the control front end is also used to provide a web page for users to perform management operations on the replica volume. In this solution, different replica volume management tasks can be completed by different management nodes, and do not need to be sent to the same management node, thereby improving management efficiency.

Description

Technical Field

[0001] The embodiments of the present invention relate to the technical field of computer disaster recovery and backup, and in particular to a replication volume management system, a replication volume management method, a device and a storage medium. Background Art

[0002] In order to avoid single point failures, data backup systems have begun to use cluster technology + shared replication volume technology of backup nodes to achieve high availability of backup nodes. In the event of a crash, the replication volume will be mounted by other healthy nodes, allowing data backup tasks to continue. In addition to data backup tasks, the creation, management, and deletion of replication volumes also require high availability. When the management node crashes, these tasks still need to be handled by a node.

[0003] In the existing implementation, the data backup cluster uses the virtual Internet Protocol (IP) mechanism to achieve high availability of the replication volume management node. The cluster has a fixed virtual IP address, which always lands on a node in the cluster at the same time. When the node goes down, the virtual IP will be automatically migrated to another node. A healthy node in the cluster can always be accessed through the fixed virtual IP inside and outside the cluster. In this way, when users create, manage, and delete replication volumes on the console page, the console only needs to know the fixed virtual IP and send the replication volume management task request to the IP address. The replication volume management work of the data backup cluster is always completed by the node where the virtual IP is located.

[0004] The disadvantage of the existing method is that the efficiency and scalability of the virtual IP mechanism are poor. A cluster has multiple nodes, but only one node can have a virtual IP and process requests sent to the virtual IP at the same time, and multiple requests cannot be executed in parallel; when adding or deleting nodes in a cluster using a virtual IP, a complicated process is required. Summary of the invention

[0005] The embodiments of the present invention provide a replica volume management system, a replica volume management method, a device and a storage medium. The management of different replica volumes can be completed by different management nodes. It is no longer necessary to use a cluster virtual IP to ensure that instructions are sent to the same management node, thereby improving management efficiency.

[0006] In a first aspect, an embodiment of the present invention provides a replication volume management system, the system comprising: a control front end, an information center, and a cluster consisting of multiple nodes;

[0007] The cluster includes at least one management node;

[0008] The information center is used to store a replication volume information association table including binding relationships between each pre-created replication volume and a corresponding management node and health information of all nodes in the cluster;

[0009] The control front end is used to determine the target management node associated with the to-be-managed replicated volume through the replicated volume information association table obtained from the information center, generate a replicated volume management request for the to-be-managed replicated volume, and send it to the target management node;

[0010] The target management node is used to receive and parse the replica volume management request, and perform replica volume management on the obtained replica volume to be managed;

[0011] The control front end is also used to provide a web page for users to perform management operations on the replication volume.

[0012] In a second aspect, an embodiment of the present invention further provides a replication volume management method, which is performed by the replication volume management system provided by the first aspect, and includes:

[0013] Determine the target management node associated with the to-be-managed replicated volume by obtaining the replicated volume information association table from the information center, generate a replicated volume management request for the to-be-managed replicated volume, and send the request to the target management node;

[0014] The copy volume management request is received and parsed, and copy volume management is performed on the obtained copy volume to be managed.

[0015] In a third aspect, an embodiment of the present invention provides a computer device, which serves as a control terminal in the replication volume management system of the first aspect, or a management node in a cluster, including:

[0016] one or more processors;

[0017] A storage device for storing one or more programs;

[0018] The one or more programs are executed by the one or more processors, so that the one or more processors implement the copy volume management method provided by the embodiment of the second aspect of the present invention.

[0019] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the copy volume management method provided in the embodiment of the second aspect of the present invention.

[0020] The embodiment of the present invention discloses a replication volume management system, replication volume management method, device and storage medium. The system includes: a control front end, an information center and a cluster composed of multiple nodes; the cluster includes at least one management node; the information center is used to store a replication volume information association table containing the binding relationship between each pre-created replication volume and the corresponding management node and the health information of all nodes in the cluster; the control front end is used to determine the target management node associated with the replication volume to be managed through the replication volume information association table obtained from the information center, generate a replication volume management request for the replication volume to be managed and send it to the target management node; the target management node is used to receive and parse the replication volume management request, and perform replication volume management on the obtained replication volume to be managed; the control front end is also used to provide a web page for users to perform management operations on the replication volume. The technical solution provided in this embodiment stores the binding relationship between each pre-created replication volume and the corresponding management node in the information center, and manages the replication volume bound thereto through the corresponding management node. It is no longer necessary to ensure that the instructions are sent to the same management node through the cluster virtual IP. The management of different replication volumes can be completed by different nodes, which improves management efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 A structural block diagram of a replication volume management system provided in Embodiment 1 of the present invention;

[0022] Figure 2 Another structural block diagram of the replication volume management system provided in the first embodiment of the present invention;

[0023] Figure 3 An example diagram of a process for managing a replication volume provided in the first embodiment of the present invention;

[0024] Figure 4 Another structural block diagram of the replication volume management system provided in the first embodiment of the present invention;

[0025] Figure 5 An example diagram of a process for creating a replica volume provided in the first embodiment of the present invention;

[0026] Figure 6 A schematic diagram of a flow chart of a replication volume management method provided in Embodiment 2 of the present invention;

[0027] Figure 7 This is a structural block diagram of a computer device provided in Embodiment 3 of the present invention. DETAILED DESCRIPTION

[0028] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention.

[0029] It should also be noted that, for ease of description, only the part relevant to the present invention but not all content is shown in the accompanying drawings. It should be mentioned before discussing exemplary embodiments in more detail that some exemplary embodiments are described as processing or methods depicted as flow charts. Although the flow chart describes each operation (or step) as sequential processing, many operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of each operation can be rearranged. When its operation is completed, the processing can be terminated, but it can also have additional steps not included in the accompanying drawings. The processing can correspond to methods, functions, procedures, subroutines, subprograms, etc.

[0030] The terms "first" and "second" and the like in the description, claims and drawings of the embodiments of the present invention are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device including a series of steps or units is not limited to the listed steps or units, but may include steps or units that are not listed.

[0031] In the prior art, in order to avoid single point failures, data backup has begun to use the cluster technology of backup nodes + shared replication volume technology to achieve high availability of backup nodes. In the event of a crash, the replication volume will be mounted by other healthy nodes so that the data backup task can continue. In addition to data backup tasks, the creation, management, and deletion of replication volumes also require high availability. When the management node crashes, these tasks still need to be processed by a node. The embodiments of the present invention provide a replication volume management system, a replication volume management method, a device, and a storage medium.

[0032] Embodiment 1

[0033] Figure 1 The structure block diagram of a replication volume management system provided in the first embodiment of the present invention is applicable to the situation of managing replication volumes, such as Figure 1 As shown, the replica volume management system includes: a control front end 1, an information center 2, and a cluster 3 composed of multiple nodes. The cluster 3 includes at least one management node 31; the information center 2 is used to store a replica volume information association table including binding relationships between each pre-created replica volume and the corresponding management node and health information of all nodes in the cluster; the control front end 1 is used to determine the target management node associated with the replica volume to be managed through the replica volume information association table obtained from the information center 2, generate a replica volume management request for the replica volume to be managed and send it to the target management node; the target management node is used to receive and parse the replica volume management request, and perform replica volume management on the obtained replica volume to be managed; the control front end 1 is also used to provide a web page for users to perform management operations on the replica volume.

[0034] Among them, the replica volume can be specifically understood as a virtual space in the storage pool, which is logically continuous and can be physically distributed on one or more storage devices. It is a logical concept. Here, the storage pool can be specifically understood as a number of storage devices that are managed in a unified manner, and a combination of software and hardware for managing storage devices. It is a physical concept. For example, there are hard disk 1 and hard disk 2. The memory of hard disk 1 is 400G, and the memory of hard disk 2 is 500G. Three replica volumes need to be created on hard disk 1 and hard disk 2. Hard disk 1 and hard disk 2 can be understood as storage pools. The space virtualized from the storage pool is divided into three parts, and three replica volumes are created. The capacity of each replica volume is 300G. The management of replica volumes can specifically include expansion, reduction, deletion and other tasks.

[0035] The replication volume management system in this embodiment includes a control front end 1, an information center 2 and a cluster 3. Among them, the control front end 1 can be specifically understood as a website (web) server, which provides a browser-based web page, and users can manage storage devices and nodes on the web page. The information center 2 can be specifically understood as a distributed key / value pair (Key / Value Pair) system, which provides key-value pair services for managing information such as the real-time status of nodes and storage. The control front end 1 and the nodes share some data through the information center 2 to achieve the purpose of collaborative work. The cluster 3 can be specifically understood as a loosely coupled computing node collection composed of two or more node machines (servers), which provides users with fault recovery capabilities close to those of fault-tolerant machines.

[0036] When the replica volume is successfully created, the created replica volume and the corresponding management node will form a binding relationship, which can be reflected in the form of a key-value pair. The key-value pair corresponding to the replica volume is formed according to the identity document (ID) and other information of the replica volume and the ID of the corresponding management node. For example, the key-value pair identifier can be represented as key. The key represents the key-value pair data identifier, and the value is the key-value pair data content.<key,value> Key-value pair data. Among them, the ID of the replica volume can be recorded as the key, and the value is often a complex data structure containing multiple fields. For example, the ID of the management node corresponding to the replica volume and other information are recorded as the value. Note that the "management node" field in the value should be set to correspond to "self". It is clear that multiple replica volumes can correspond to multiple management nodes respectively, that is, multiple replica volumes are bound to corresponding management nodes to form multiple key-value pairs. Multiple key-value pairs are aggregated to finally form a replica volume information association table and stored in the information center 2.

[0037] Among them, when it is necessary to manage the replicated volume, it is necessary to determine the management node corresponding to the replicated volume, and the management operation of the replicated volume is managed by the control front end 1 through the management node. After the target management node is determined, the corresponding replicated volume can be managed through the target management node. It should be noted that when the management node corresponding to the replicated volume is in a normal state, the management node corresponding to the replicated volume can be determined as the target management node. When the management node corresponding to the replicated volume is in a downtime state, communication cannot be carried out through the management node, so a new management node needs to be selected as the target management node for managing the management volume through the management node.

[0038] The replicated volume management request includes management operations on the replicated volume, which can be specifically embodied in the form of a communication protocol, which may include the ID of the replicated volume, the target management node ID, and the management operation, etc. Exemplarily, the management request for the replicated volume may be a replicated volume expansion request, a replicated volume reduction request, or a replicated volume deletion request, etc.

[0039] Specifically, when the replica volume is successfully created, the information center 2 stores the binding relationship between the created replica volume and the corresponding management node used during creation; when the replica volume management operation is triggered, the control front end 1 obtains the replica volume information association table from the information center 2, and queries the corresponding key-value pair through the ID of the replica volume to be managed, and determines that the management node bound to the ID of the replica volume to be managed is the target management node; based on the ID of the replica volume, the target management node ID and the management operation, a replica volume management request for the replica volume to be managed is generated and sent to the target management node; the target management node receives and parses the replica volume management request, and performs replica volume management on the obtained replica volume to be managed.

[0040] The embodiment of the present invention discloses a replication volume management system, a replication volume management method, a device and a storage medium. The system includes: a control front end, an information center and a cluster composed of multiple nodes; the cluster includes at least one management node; the information center is used to store a replication volume information association table including the binding relationship between each pre-created replication volume and the corresponding management node and the health information of all nodes in the cluster; the control front end is used to determine the target management node associated with the replication volume to be managed through the replication volume information association table obtained from the information center, generate a replication volume management request for the replication volume to be managed and send it to the target management node; the target management node is used to receive and parse the replication volume management request, and perform replication volume management on the obtained replication volume to be managed; the control front end is also used to provide a web page for users to perform management operations on the replication volume. The technical solution provided in this embodiment stores the binding relationship between each pre-created replication volume and the corresponding management node in the information center, and manages the replication volume bound thereto through the corresponding management node. It is no longer necessary to ensure that the instructions are sent to the same management node through the cluster virtual IP. The management of different replication volumes can be completed by different nodes, which improves management efficiency.

[0041] As an optional embodiment of the embodiment of the present invention, based on the above embodiment, Figure 2 Another structural block diagram of the replication volume management system provided in the first embodiment of the present invention. Figure 2 As shown, the control front end 1 includes a target node determination module 11, which is used to: search for the identification code of the to-be-managed replica volume from the pulled replica volume information association table, and determine the target management node of the to-be-managed replica volume based on the search result.

[0042] The identification code of the replica volume can be understood as the identity of the replica volume. Different replica volumes have different identification codes, and the identification code is the unique identification of the replica volume. Exemplarily, the identification code of the replica volume can be represented in a hash format, for example, represented by a random combination of 32 letters and numbers. The search result can be understood as the binding relationship corresponding to the replica volume to be managed.

[0043] Specifically, according to the identification code of the replicated volume to be managed, the binding relationship corresponding to the replicated volume to be managed can be found from the replicated volume information association table stored in the information center 2, and the management node bound to the replicated volume to be managed is determined as the target management node.

[0044] Optionally, the target node determination module 11 is specifically configured to:

[0045] a1) When a user triggers a replication volume management operation request, the identification code of the replication volume to be managed is searched from the pulled replication volume information association table.

[0046] Specifically, when the user triggers a replication volume management operation request, it indicates that the user wants to manage the replication volume. At this time, it is necessary to first determine the management node corresponding to the replication volume to be managed, and manage the replication volume to be managed through the management node. When the user triggers a replication volume management operation request, the target node determination module 11 searches for the identification code of the replication volume to be managed from the replication volume information association table stored in the information center 2.

[0047] b1) Determine the corresponding management node bound to the replica volume to be managed.

[0048] Specifically, the target node determination module 11 searches for the identification code of the to-be-managed replicated volume from the replicated volume information association table stored in the information center 2, and can determine the corresponding management node bound to the to-be-managed replicated volume.

[0049] c1) determining whether the management node is in a normal state; if so, determining the management node as a target management node for the replica volume to be managed.

[0050] Specifically, it is determined whether the management node is in a normal state. The management node may be in a normal state or a down state. If the replication volume management node is in a normal state, the management node bound to the replication volume is determined to be the target management node of the replication volume to be managed, and the replication volume to be managed can be managed through the management node.

[0051] d1) Otherwise, the to-be-managed replicated volume is bound to the new management node again, and the process returns to continue to determine the corresponding management node bound to the to-be-managed replicated volume.

[0052] Specifically, if the management node bound to the replicated volume is down, the replicated volume cannot be managed through the management node. It is necessary to reselect a new management node from the cluster based on the healthy node information in the cluster stored in the information center 2, bind the selected new management node to the replicated volume to be managed, and re-acquire the new management node of the replicated volume to be managed from the cluster 3 as the target management node.

[0053] Preferably, the step of binding the to-be-managed replica volume to the new management node executed by the target node determination module includes:

[0054] d11) If the corresponding management node bound to the to-be-managed replicated volume is in a down state, any healthy node in cluster 3 is reselected as a new management node corresponding to the to-be-managed replicated volume.

[0055] Specifically, if the corresponding management node bound to the replica volume to be managed is in a down state, the replica volume cannot be controlled through the management node, and the binding relationship between the replica volume to be managed and the down management node is released, and any healthy node in the cluster 3 is reselected as the new management node corresponding to the replica volume to be managed according to the health information list provided by the information center 2. It can be clearly seen that when reselecting a healthy node in the cluster, any healthy node can be selected as the new management node.

[0056] d12) Bind the replica volume to be managed to the new management node to form a new binding relationship.

[0057] Specifically, the management node will rewrite the manager in the key-value pair corresponding to the replica volume to be managed into "itself", thereby forming a new binding relationship.

[0058] d13) Update the new binding relationship to the replication volume information association table.

[0059] Specifically, the new binding relationship is updated to the replication volume information association table stored in the information center 2 .

[0060] For example, assume that replica volume a and management node 1 are stored in the replica volume information association table in the form of key-value pairs. When management node 1 goes down, it is necessary to determine a new management node for replica volume a. Assuming that healthy node 2 is selected as the management node of replica volume a, replica volume a is unbound from management node 1 and rebound to management node 2. The new management node will rewrite the manager in the key-value pair corresponding to the replica volume to be managed as "itself" and update it to the replica volume information association table in the form of a key-value pair.

[0061] In order to more clearly describe the management process of the replication volume after the management node crashes provided by the embodiment of the present invention, exemplarily, Figure 3 This is an example diagram of the process of replica volume management provided in the first embodiment of the present invention. Figure 3 As shown, when performing replicated volume management, the control front end obtains the management node corresponding to the identification code of the replicated volume to be managed from the information center. If the management node is down, here it is assumed that the management node 1 is down, the control front end queries the healthy nodes in the node health information list stored in the information center, and selects any healthy node from the cluster as the new management node for the replicated volume to be managed. Here, the healthy node 2 is determined as the new management node. The control front end 1 sends the management instruction to the healthy node 2, and forms a binding relationship between the replicated volume a and the healthy node 2, and sets the management node to the healthy node 2. The healthy node 2 manages the replicated volume a according to the instruction. Here it is assumed that the node (short for healthy node) 2 is bound to the volume (short for replicated volume) a, and the replicated volume information association table is stored in the information center 2. The replicated volume a can be managed through node 2 later, such as capacity expansion and other management operations.

[0062] It is clear that before managing the replicated volume, it is necessary to create the replicated volume first. When creating the replicated volume, different management nodes can be used to control the creation of the replicated volume respectively, and multiple replicated volumes can also be controlled by different management nodes to be created simultaneously.

[0063] As an optional embodiment of the embodiment of the present invention, based on the above embodiment, Figure 4 This is another structural block diagram of the replication volume management system provided in the first embodiment of the present invention. Figure 4 As shown, the control front end 1 includes a management node determination module 12, which is used to:

[0064] a2) When the user triggers the replication volume creation operation, any healthy node in cluster 3 is determined as the management node.

[0065] Among them, cluster 3 includes multiple healthy nodes. When the user triggers the replication volume creation operation, any healthy node can be selected as the management node. Compared with the prior art, it is no longer necessary to use the cluster virtual IP to ensure that the instruction is sent to the same node. The replication volume creation task will be randomly assigned to any healthy node in cluster 3 to complete. Therefore, the management node determination module 12 can make any healthy node in cluster 3 become the management node of the replication volume to complete the replication volume creation work.

[0066] b2) Generate a replication volume creation request for the replication volume to be created.

[0067] c2) Send the replication volume creation request and storage pool address information to the management node.

[0068] Specifically, the address information of the storage pool and the target address of the mainstream network protocol (Internet Small Computer System Interface, ISCSI) are sent to the management node. ISCSI is a mainstream network protocol for accessing storage devices through the network. The user is the initiator and the provider is the target.

[0069] Continue to refer Figure 4 Optionally, the management node 31 includes:

[0070] The replication volume creation unit 311 is used to create a replication volume based on the storage pool when receiving a replication volume creation request sent by the control front end 1.

[0071] The replication volume creation request may include information such as the size of the replication volume to be created. When receiving the replication volume creation request sent by the control front end, the replication volume creation unit 311 creates the replication volume according to the storage pool information and the size of the replication volume to be created.

[0072] Optionally, the replica volume creation unit 311 is specifically used to: when receiving a replica volume creation request sent by the control front end 1, determine the address information of the replica volume to be created based on the address information of the storage pool and the existing replica volume information on the storage pool; create a replica volume based on the storage pool and in combination with the address information of the replica volume to be created.

[0073] Specifically, when receiving a replication volume request sent by the control front end 1, the address information of the existing replication volume in the storage pool is subtracted from the known storage pool address information to obtain the remaining address information in the storage pool. The replication volume is created according to the remaining address information and the size of the replication volume to be created.

[0074] Exemplarily, assuming that the address range of the storage pool is: 0000-0999, where the address range occupied by the existing replicated volumes on the storage pool is: 0000-0500, and the size of the replicated volume to be created is 100, then the address range of the replicated volume to be created can be: 0501-0600. It is clear that the storage pool is a number of storage devices that are managed in a unified manner. When creating a replicated volume, if the memory of one of the storage devices runs out, the next storage device can be used. It can also be understood that a replicated volume can use part of the memory of two or more storage devices respectively. This is related to the size of the replicated volume and the size of the storage device, and no specific restrictions are made here.

[0075] The binding relationship storage unit 312 is used to bind the newly created replica volume to the corresponding management node, and store the replica volume information association table containing the binding relationship to the information center 2.

[0076] Specifically, a key-value pair corresponding to the replicated volume is formed based on the ID of the replicated volume and the ID of the corresponding management node. For example, the key-value pair identifier can be represented as key. The key represents the key-value pair data identifier, and the value represents the key-value pair data content.<key,value> Key-value pair data. The ID of the replica volume can be recorded as the key, and the ID of the management node corresponding to the replica volume and other information can be recorded as the value. Note that the "management node" field in the value should be set to "self". Bind the newly created replica volume to the corresponding management node, and summarize the binding relationship into a replica volume information association table and store it in the information center 2.

[0077] For example, assuming that a new replica volume a is created and its corresponding management node is management node 1, the replica volume a is bound to management node 1 to form a key-value pair, and is stored in the information center in the form of a replica volume information association table. When managing the replica volume, the management node corresponding to the replica volume can be obtained from the information center, and a management request can be sent to the corresponding management node address to manage the replica volume through the management node.

[0078] In order to more clearly describe the process of creating a replica volume provided by an embodiment of the present invention, exemplarily, Figure 5 This is an example diagram of the process of creating a replica volume provided in the first embodiment of the present invention. Figure 5 As shown, when creating a replicated volume, the control front end queries the node health information list provided by the information center, selects any healthy node in the cluster, and here determines that healthy node 1 is the management node. The control front end sends the creation instruction to healthy node 1. The healthy node creates replicated volume a in the storage pool according to the instruction, and forms a binding relationship between replicated volume a and healthy node 1. It is assumed here that node (short for healthy node) 1 is bound to volume (short for replicated volume) a, node 2 is bound to volume b, and so on, and the replicated volume information association table is stored in the information center. At this point, the creation process of the replicated volume is completed.

[0079] As an optional embodiment of the present invention, this implementation concretizes the workflow of replica volume management, by searching the identification code of the replica volume to be managed from the pulled replica volume information association table, determining the target management node of the replica volume to be managed based on the search result, and managing the replica volume through the target management node. At the same time, when the management node is down, any healthy node can be randomly selected as the management node. In addition, the creation process of the replica volume is disclosed. Compared with the prior art, in the technical solution provided by this embodiment, the creation, management, and deletion tasks of the replica volume will be randomly assigned to any node in the cluster 3 to complete. Since the information center 2 and the cluster node can provide the management node address of the current replica volume, the control front end can make any healthy node in the cluster 3 become the management node of the replica volume to complete the management of the replica volume. In this way, on the one hand, it is no longer necessary to ensure that the instructions are sent to the same node through the cluster virtual IP, and the management of different replica volumes can be completed by different nodes, which improves efficiency; on the other hand, it also makes the cluster virtual IP no longer necessary, simplifying the maintenance of the cluster.

[0080] Embodiment 2

[0081] Figure 6 A flowchart of a method for managing a replicated volume provided in the second embodiment of the present invention is shown. The method is applicable to the case where replicated volumes are managed, such as Figure 6 As shown, a copy volume management method provided by Embodiment 2 of the present invention may specifically include the following steps:

[0082] S210: Determine the target management node associated with the replica volume to be managed by using the replica volume information association table obtained from the replica volume management information center, generate a replica volume management request for the replica volume to be managed, and send it to the target management node.

[0083] S220: Receive and parse the copy volume management request, and perform copy volume management on the obtained copy volume to be managed.

[0084] The above method can be executed by the copy volume management system provided by the embodiment of the present invention, and has the beneficial effects of the copy volume management system.

[0085] Embodiment 3

[0086] Figure 7 A block diagram of a computer device provided in Embodiment 3 of the present invention is shown in FIG. Figure 7 As shown, the computer device serves as a control terminal in the replication volume management system provided in the above embodiment, or a management node in a cluster, and includes a processor 41, a memory 42, an input device 43, and an output device 44; the number of processors 41 in the computer device can be one or more. Figure 7 A processor 41 is taken as an example; the processor 41, memory 42, input device 43 and output device 44 in the computer device can be connected by a bus or other means. Figure 7 The example of connecting through bus is taken in the following.

[0087] Specifically, in the embodiment, when the processor 41 executes one or more programs stored in the memory 42, the following operations can be implemented: determine the target management node associated with the replica volume to be managed by obtaining the replica volume information association table from the information center, generate a replica volume management request for the replica volume to be managed and send it to the target management node; receive and parse the replica volume management request, and perform replica volume management on the obtained replica volume to be managed.

[0088] The memory 42 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function; the data storage area may store data created according to the use of the terminal, etc. In addition, the memory 42 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 42 may further include a memory remotely arranged relative to the processor 41, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0089] The input device 43 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the computer device. The output device 44 may include display devices such as a display screen.

[0090] Embodiment 4

[0091] Embodiment 4 of the present invention further provides a storage medium including computer executable instructions, wherein the computer executable instructions are used to execute a copy volume management method when executed by a computer processor, the method comprising:

[0092] Determine the target management node associated with the to-be-managed replicated volume by obtaining the replicated volume information association table from the information center, generate a replicated volume management request for the to-be-managed replicated volume, and send the request to the target management node;

[0093] The copy volume management request is received and parsed, and copy volume management is performed on the obtained copy volume to be managed.

[0094] Of course, the computer executable instructions of a storage medium including computer executable instructions provided by an embodiment of the present invention are not limited to the operations of the method described above, and can also execute related operations in the replication volume management method provided by any embodiment of the present invention.

[0095] Through the above description of the implementation methods, the technicians in the relevant field can clearly understand that the present invention can be implemented by means of software and necessary general hardware, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0096] It is worth noting that in the above-mentioned embodiment of the replication volume management system, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

[0097] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A replication volume management system, characterized in that: include: Control the cluster consisting of the front end, information center and multiple nodes; The cluster includes at least one management node; wherein the management node is a server in the cluster; The information center is used to store a replication volume information association table including binding relationships between each pre-created replication volume and a corresponding management node and health information of all nodes in the cluster; The control front end is used to determine the target management node associated with the to-be-managed replicated volume through the replicated volume information association table obtained from the information center, generate a replicated volume management request for the to-be-managed replicated volume, and send it to the target management node; The target management node is used to receive and parse the replica volume management request, and perform replica volume management on the obtained replica volume to be managed; The control front end is also used to provide a web page for users to perform management operations on the replication volume; The control front end includes a target node determination module, which is used to: Searching for an identification code of the to-be-managed replica volume from the pulled replica volume information association table, and determining a target management node for the to-be-managed replica volume based on the search result; The target node determination module is specifically used for: When the user triggers a replication volume management operation request, the identification code of the replication volume to be managed is searched from the pulled replication volume information association table; Determine the corresponding management node bound to the replica volume to be managed; Determining whether the management node is in a normal state, and if so, determining that the management node is a target management node for the replica volume to be managed; Otherwise, the to-be-managed replicated volume is bound to the new management node again, and the process returns to continue to determine the corresponding management node bound to the to-be-managed replicated volume; The step of binding the to-be-managed replication volume to the new management node by the target node determination module includes: If the corresponding management node bound to the replica volume to be managed is in a downtime state, reselect any healthy node in the cluster as a new management node corresponding to the replica volume to be managed; Binding the to-be-managed replica volume to the new management node to form a new binding relationship; The new binding relationship is updated to the replication volume information association table.

2. The system according to claim 1, characterized in that The control front end includes a management node determination module, which is used to: When a user triggers a replication volume creation operation, any healthy node in the cluster is determined as a management node; Generate a replication volume creation request for the replication volume to be created; The replication volume creation request and storage pool address information are sent to the management node.

3. The system according to claim 2, characterized in that The management node includes: A replica volume creation unit, configured to create a replica volume based on a storage pool when receiving a replica volume creation request sent by the control front end; The binding relationship storage unit is used to bind the newly created replica volume to the corresponding management node, and store the replica volume information association table containing the binding relationship in the information center.

4. The system according to claim 3, characterized in that The replica volume creation unit is specifically used for: When receiving a copy volume creation request sent by the control front end, determining the address information of the copy volume to be created based on the address information of the storage pool and the existing copy volume information on the storage pool; Based on the storage pool and in combination with the address information of the to-be-created replica volume, a replica volume is created.

5. A method for managing a copy volume, characterized in that: The method is performed by the replication volume management system according to any one of claims 1 to 4, comprising: Determine the target management node associated with the to-be-managed replicated volume by obtaining the replicated volume information association table from the information center, generate a replicated volume management request for the to-be-managed replicated volume, and send the request to the target management node; The copy volume management request is received and parsed, and copy volume management is performed on the obtained copy volume to be managed.

6. A storage medium containing computer executable instructions, characterized in that: The computer executable instructions are used to perform the replication volume management method according to claim 5 when executed by a computer processor.

Images