CN114385420A - Copy volume management system, copy volume management method, device, and storage medium - Google Patents

Copy volume management system, copy volume management method, device, and storage medium Download PDF

Info

Publication number
CN114385420A
CN114385420A CN202210004900.8A CN202210004900A CN114385420A CN 114385420 A CN114385420 A CN 114385420A CN 202210004900 A CN202210004900 A CN 202210004900A CN 114385420 A CN114385420 A CN 114385420A
Authority
CN
China
Prior art keywords
replication volume
management
volume
replication
management node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210004900.8A
Other languages
Chinese (zh)
Inventor
时培植
李向东
江俊
周华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Information2 Software Inc
Original Assignee
Shanghai Information2 Software Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shanghai Information2 Software Inc filed Critical Shanghai Information2 Software Inc
Priority to CN202210004900.8A priority Critical patent/CN114385420A/en
Publication of CN114385420A publication Critical patent/CN114385420A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/242—Query formulation
    • G06F16/2428—Query predicate definition using graphical user interfaces, including menus and forms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
    • G06F16/2471—Distributed queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Mathematical Physics (AREA)
  • Computational Linguistics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Software Systems (AREA)
  • Fuzzy Systems (AREA)
  • Computing Systems (AREA)
  • Human Computer Interaction (AREA)
  • Quality & Reliability (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The embodiment of the invention discloses a copy volume management system, a copy volume management method, a device and a storage medium. The method comprises the following steps: the method comprises the steps of controlling a cluster consisting of a front end, an information center and a plurality of nodes; the cluster comprises at least one management node; the information center is used for storing a replication volume information association table containing the binding relationship between each pre-created replication volume and the corresponding management node; the control front end is used for determining a target management node related to the replication volume to be managed through a replication volume information association table acquired from the information center, generating a replication volume management request of the replication volume to be managed and sending the replication volume management request to the target management node; the target management node is used for receiving and analyzing the replication volume management request and performing replication volume management on the obtained replication volume to be managed; and the control front end is also used for providing a web page for the user to perform administrative operation of copying the volume. According to the scheme, different copy volume management work can be completed by different management nodes without being issued to the same management node, and the management efficiency is improved.

Description

Copy volume management system, copy volume management method, device, and storage medium
Technical Field
The embodiment of the invention relates to the technical field of computer disaster recovery backup, in particular to a replication volume management system, a replication volume management method, a replication volume management device and a storage medium.
Background
To avoid single point of failure, data backup systems have begun to make use of the clustering technology of backup nodes + shared replication volume technology to achieve high availability of backup nodes. And when the data backup task is down, the replication volume can be mounted by other healthy nodes, so that the data backup task can be continuously carried out. In addition to data backup tasks, the creation, management, and deletion tasks of replication volumes are also highly available, which tasks still require nodes to handle when a management node is down.
In existing implementations, the data backup cluster utilizes a virtual Internet Protocol (IP) mechanism to achieve high availability of the replication volume management node. The cluster has a fixed virtual IP address, the cluster always lands on one node in the cluster at the same time, and when the node is down, the virtual IP is automatically migrated to another node. Inside and outside the cluster, a healthy node in the cluster can be always accessed through the fixed virtual IP. Therefore, when a user creates, manages and deletes the copy volume on the control console page, the control console only needs to know the fixed virtual IP and send the copy volume management task request to the IP address. The copy volume management work of the data backup cluster is always completed by the node where the virtual IP is located.
The disadvantage of the existing method is that the efficiency and scalability of the virtual IP mechanism are not good. The cluster is provided with a plurality of nodes, but only one node can have the virtual IP and process the request sent to the virtual IP at the same time, and a plurality of requests cannot be executed in parallel; when a cluster using virtual IP adds or deletes a node, a complicated process is also required.
Disclosure of Invention
The embodiment of the invention provides a copy volume management system, a copy volume management method, a device and a storage medium, wherein management work of different copy volumes can be completed by different management nodes, and commands are not required to be ensured to be issued to the same management node through a cluster virtual IP (Internet protocol), so that the management efficiency is improved.
In a first aspect, an embodiment of the present invention provides a replication volume management system, where the system includes: the method comprises the steps of controlling a cluster consisting of a front end, an information center and a plurality of nodes;
the cluster comprises at least one management node;
the information center is used for storing a replication volume information association table containing the binding relationship between each pre-created replication volume and the corresponding management node and health information of all nodes in the cluster;
the control front end is used for determining a target management node related to the replication volume to be managed through a replication volume information association table acquired from the information center, generating a replication volume management request of the replication volume to be managed and sending the replication volume management request to the target management node;
the target management node is used for receiving and analyzing the replication volume management request and performing replication volume management on the obtained replication volume to be managed;
the control front end is also used for providing a web page for the user to do management operation of the copy volume.
In a second aspect, an embodiment of the present invention further provides a replication volume management method, where the method is executed by the replication volume management system provided in the first aspect, and includes:
determining a target management node associated with the replication volume to be managed through a replication volume information association table acquired from the information center, generating a replication volume management request of the replication volume to be managed, and sending the replication volume management request to the target management node;
and receiving and analyzing the replication volume management request, and performing replication volume management on the obtained replication volume to be managed.
In a third aspect, an embodiment of the present invention provides a computer device, which is used as a control terminal in the replication volume management system or a management node in a cluster in the first aspect, and includes:
one or more processors;
storage means for storing one or more programs;
the one or more programs are executed by the one or more processors, so that the one or more processors implement the replication volume management method provided by the embodiment of the second aspect of the present invention.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the replication volume management method provided in the second aspect of the present invention.
The embodiment of the invention discloses a copy volume management system, a copy volume management method, a device and a storage medium. The system comprises: the method comprises the following steps: the method comprises the steps of controlling a cluster consisting of a front end, an information center and a plurality of nodes; the cluster comprises at least one management node; the information center is used for storing a replication volume information association table containing the binding relationship between each pre-created replication volume and the corresponding management node and health information of all nodes in the cluster; the control front end is used for determining a target management node related to the replication volume to be managed through a replication volume information association table acquired from the information center, generating a replication volume management request of the replication volume to be managed and sending the replication volume management request to the target management node; the target management node is used for receiving and analyzing the replication volume management request and performing replication volume management on the obtained replication volume to be managed; the control front end is also used for providing a web page for the user to do management operation of the copy volume. The technical scheme provided by this embodiment stores the binding relationship between each pre-created replication volume and the corresponding management node in the information center, manages the replication volumes bound with the pre-created replication volumes through the corresponding management nodes, and does not need to ensure that the instruction is issued to the same management node through the cluster virtual IP, and the management work of different replication volumes can be completed by different nodes, thereby improving the management efficiency.
Drawings
Fig. 1 is a block diagram illustrating a structure of a replication volume management system according to an embodiment of the present invention;
fig. 2 is another block diagram of a replication volume management system according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a flow of copy volume management according to an embodiment of the present invention;
fig. 4 is a block diagram of another structure of a replication volume management system according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a process of creating a replication volume according to an embodiment of the present invention;
fig. 6 is a flowchart illustrating a replication volume management method according to a second embodiment of the present invention;
fig. 7 is a block diagram of a computer device according to a third embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention.
It should be further noted that, for the convenience of description, only some but not all of the relevant aspects of the present invention are shown in the drawings. Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
The terms "first" and "second," and the like in the description and claims of embodiments of the invention and in the drawings, are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not set forth for a listed step or element but may include steps or elements not listed.
In the prior art, to avoid a single point of failure, data backup has started to realize high availability of backup nodes by using a cluster technology + a shared replication volume technology of the backup nodes. And when the data backup task is down, the replication volume can be mounted by other healthy nodes, so that the data backup task can be continuously carried out. In addition to data backup tasks, the creation, management, and deletion tasks of replication volumes are also highly available, which tasks still require nodes to handle when a management node is down. The embodiment of the invention provides a copy volume management system, a copy volume management method, a device and a storage medium.
Example one
Fig. 1 is a block diagram of a replication volume management system according to an embodiment of the present invention, where the system is adapted to manage a replication volume, and as shown in fig. 1, the replication volume management system includes: the system comprises a control front end 1, an information center 2 and a cluster 3 formed by a plurality of nodes. The cluster 3 comprises at least one management node 31; the information center 2 is used for storing a replication volume information association table containing the binding relationship between each pre-created replication volume and the corresponding management node and health information of all nodes in the cluster; the control front end 1 is used for determining a target management node related to the replication volume to be managed through the replication volume information association table acquired from the information center 2, generating a replication volume management request of the replication volume to be managed and sending the replication volume management request to the target management node; the target management node is used for receiving and analyzing the replication volume management request and performing replication volume management on the obtained replication volume to be managed; the control front end 1 is also used to provide web pages for the user to do administrative operations for copying volumes.
A replication volume is understood to be a virtual space in a storage pool, which is logically continuous and physically distributed on one or more storage devices, and is a logical concept. Here, a storage pool may be specifically understood as a plurality of storage devices that are managed in a unified manner, and a combination of software and hardware for managing the storage devices is a physical concept. Illustratively, the existing hard disk 1 and hard disk 2, the memory of hard disk 1 is 400G, the memory of hard disk 2 is 500G, and three copy volumes need to be created in hard disk 1 and hard disk 2. Wherein the hard disk 1 and the hard disk 2 can be understood as a storage pool, a space virtualized from the storage pool is divided into three parts, 3 copy volumes are created, and the capacity of each copy volume is 300G. The management of the replication volume may specifically include operations of capacity expansion, capacity reduction, deletion, and the like.
The replication volume management system in this embodiment includes a control front end 1, an information center 2, and a cluster 3. The control front end 1 may be specifically understood as a website (web) server, which provides a web page based on a browser, and a user may perform management work on a storage device and a node on the web page. The information center 2 can be specifically understood as a distributed Key-Value Pair (Key/Value Pair) system, which provides a Key-Value Pair service for managing nodes and stored information such as an instant state, and controls the front end 1 and the nodes to share some data through the information center 2, so as to achieve the purpose of cooperative work. The cluster 3 is specifically understood to be a loosely coupled computing node set consisting of two or more node machines (servers) that provide users with a fault recovery capability close to that of a fault-tolerant machine.
When the replication volume is successfully created, the created replication volume and the corresponding management node form a binding relationship, and the binding relationship can be embodied in a key-value pair manner. And forming a key value pair corresponding to the replication volume according to the Identity identification number (ID) and other information of the replication volume and the ID of the corresponding management node. For example, the key-value pair identification may be represented as a key. And representing the key value pair data identification by the key, wherein the value is the content of the key value pair data, and generating the key value pair data of < key, value >. Here, the ID of the replication volume may be denoted as key, and the value is often a complex data structure and includes a plurality of fields, for example, information such as the ID of the management node corresponding to the replication volume is denoted as value, and it should be noted that the "management node" field in the value should be set to correspond to "itself". It can be clear that a plurality of replication volumes can respectively correspond to a plurality of management nodes, that is, the plurality of replication volumes and the corresponding management nodes are bound to form a plurality of key value pairs. The plurality of key value pairs are collected to finally form a copy volume information association table to be stored in the information center 2.
When a copy volume is to be managed, a management node corresponding to the copy volume needs to be determined, and the control front end 1 manages the copy volume through the management node. After the target management node is determined, the corresponding replication volume can be managed through the target management node. When the management node corresponding to the replication volume is in a normal state, the management node corresponding to the replication volume may be determined as the target management node. When the management node corresponding to the replication volume is in a down state, communication cannot be performed through the management node, so that a new management node needs to be selected as a target management node for managing the management volume through the management node.
The replication volume management request includes a management operation on the replication volume, which may be embodied in a communication protocol, and may include an ID of the replication volume, an ID of a target management node, a management operation, and the like. For example, the management request for the replication volume may be a replication volume expansion request, a replication volume contraction request, a replication volume deletion request, or the like.
Specifically, after the replication volume is successfully created, the information center 2 stores the binding relationship between the created replication volume and the corresponding management node used in the creation; when the copy volume management operation is triggered, the control front end 1 acquires a copy volume information association table from the information center 2, inquires a key value pair corresponding to the ID of the copy volume to be managed through the ID of the copy volume to be managed, and determines a management node bound with the ID of the copy volume to be managed as a target management node; generating a replication volume management request of the replication volume to be managed according to the ID of the replication volume, the ID of the target management node and the management operation, and sending the replication volume management request to the target management node; and the target management node receives and analyzes the replication volume management request and performs replication volume management on the obtained replication volume to be managed.
The embodiment of the invention discloses a copy volume management system, a copy volume management method, a device and a storage medium. The system comprises: the method comprises the steps of controlling a cluster consisting of a front end, an information center and a plurality of nodes; the cluster comprises at least one management node; the information center is used for storing a replication volume information association table containing the binding relationship between each pre-created replication volume and the corresponding management node and health information of all nodes in the cluster; the control front end is used for determining a target management node related to the replication volume to be managed through a replication volume information association table acquired from the information center, generating a replication volume management request of the replication volume to be managed and sending the replication volume management request to the target management node; the target management node is used for receiving and analyzing the replication volume management request and performing replication volume management on the obtained replication volume to be managed; and the control front end is also used for providing a web page for the user to perform administrative operation of copying the volume. The technical scheme provided by this embodiment stores the binding relationship between each pre-created replication volume and the corresponding management node in the information center, manages the replication volumes bound with the pre-created replication volumes through the corresponding management nodes, and does not need to ensure that the instruction is issued to the same management node through the cluster virtual IP, and the management work of different replication volumes can be completed by different nodes, thereby improving the management efficiency.
As an alternative embodiment of the present invention, on the basis of the above embodiment, fig. 2 is another structural block diagram of a replication volume management system provided in an embodiment of the present invention. As shown in fig. 2, the control front end 1 includes a target node determining module 11, configured to: and searching the identification code of the replication volume to be managed from the pulled replication volume information association table, and determining a target management node of the replication volume to be managed based on the searching result.
The identification code of the copy volume can be understood as an identity of the copy volume, different copy volumes have different identification codes, and the identification code is a unique identity of the copy volume. Illustratively, the identification code of the copy volume may be represented in a hash format, e.g., by a random combination of 32 letters and numbers. The search result can be understood as the binding relationship corresponding to the copy volume to be managed.
Specifically, according to the identification code of the replication volume to be managed, the binding relationship corresponding to the replication volume to be managed can be searched from the replication volume information association table stored in the information center 2, and the management node bound to the replication volume to be managed is determined as the target management node.
Optionally, the target node determining module 11 is specifically configured to:
a1) and when the user triggers the copy volume management operation request, searching the identification code of the copy volume to be managed from the pulled copy volume information association table.
Specifically, when a user triggers a copy volume management operation request, it indicates that the user needs to perform management work on the copy volume, and at this time, a management node corresponding to the copy volume to be managed needs to be determined first, and the management work is performed on the copy volume to be managed through the management node. When the user triggers the copy volume management operation request, the target node determination module 11 searches the identification code of the copy volume to be managed from the copy volume information association table stored in the information center 2.
b1) And determining a corresponding management node bound with the replication volume to be managed.
Specifically, the target node determining module 11 searches the identification code of the replication volume to be managed from the replication volume information association table stored in the information center 2, and may determine the corresponding management node bound to the replication volume to be managed.
c1) And judging whether the management node is in a normal state, and if so, determining that the management node is a target management node of the replication volume to be managed.
Specifically, whether the management node is in a normal state or not is judged, and the management node may be in a normal state or a down state. If the replication volume management node is in a normal state, determining that the management node bound with the replication volume is a target management node of the replication volume to be managed, and managing the replication volume to be managed through the management node.
d1) And if not, binding the replication volume to be managed with the new management node again, and returning to continuously execute the corresponding management node bound with the replication volume to be managed.
Specifically, if the management node bound to the replication volume is in a down state, the management node cannot manage the replication volume. And selecting a new management node from the cluster according to the healthy node information in the cluster stored in the information center 2, binding the selected new management node with the replication volume to be managed, and acquiring the new management node of the replication volume to be managed from the cluster 3 as a target management node.
Preferably, the step of the target node determining module executing to bind the replication volume to be managed with the new management node includes:
d11) and if the corresponding management node bound with the replication volume to be managed is in the downtime state, reselecting any healthy node in the cluster 3 as a new management node corresponding to the replication volume to be managed.
Specifically, if the corresponding management node bound to the replication volume to be managed is in the down state, the replication volume cannot be controlled by the management node, the binding relationship between the replication volume to be managed and the management node in the down state is released, and according to the health information list provided by the information center 2, any one of the health nodes in the cluster 3 is reselected as a new management node corresponding to the replication volume to be managed. It may be clear that when a healthy node in the cluster is reselected, any healthy node may be selected as the new management node.
d12) And binding the replication volume to be managed with the new management node to form a new binding relationship.
Specifically, the management node rewrites the administrator in the key value pair corresponding to the replication volume to be managed into "itself", thereby forming a new binding relationship.
d13) And updating the new binding relation to the replication volume information association table.
Specifically, the new binding relationship is updated to the copy volume information association table stored in the information center 2.
For example, assuming that the replication volume a and the management node 1 are stored in the replication volume information association table in a key value pair form, when the management node 1 goes down, a new management node needs to be determined for the replication volume a, assuming that the healthy node 2 is selected as the management node of the replication volume a, the replication volume a and the management node 1 are unbundled and are bound with the management node 2 again, and the new management node rewrites a manager in the key value pair corresponding to the replication volume to be managed into "itself" and updates the key value pair form to the replication volume information association table.
To more clearly describe the management process of the replication volume after the downed management node according to the embodiment of the present invention, fig. 3 is an exemplary diagram of a flow of the replication volume management according to an embodiment of the present invention. As shown in fig. 3, when performing copy volume management, the control front end acquires a management node corresponding to an identifier of a copy volume to be managed from the information center. If the management node is down, assuming that the management node 1 is down, controlling the front end to inquire the healthy nodes in a node health information list stored in the information center, selecting any healthy node from the cluster as a new management node of the replication volume to be managed, determining the healthy node 2 as a new management node, controlling the front end 1 to send a management instruction to the healthy node 2, forming a binding relationship between the replication volume a and the healthy node 2, setting the management node as the healthy node 2, and managing the replication volume a by the healthy node 2 according to the instruction. It is assumed here that the node (short for healthy node) 2 binds to the volume (short for replication volume) a, and stores the replication volume information association table in the information center 2. Subsequently, the node 2 may manage the replication volume a, such as performing management operations such as capacity expansion.
It can be clear that, before managing the replication volume, the replication volume needs to be created first, when creating the replication volume, the creation of the replication volume can be controlled by different management nodes respectively, and a plurality of replication volumes are also controlled by different management nodes to be created simultaneously.
As an alternative embodiment of the present invention, on the basis of the above embodiment, fig. 4 is a block diagram of another structure of a replication volume management system according to an embodiment of the present invention. As shown in fig. 4, the control front end 1 includes a management node determining module 12 for:
a2) when a user triggers a copy volume creation operation, any healthy node in the cluster 3 is determined to be a management node.
The cluster 3 includes a plurality of healthy nodes, and when a user triggers a copy volume creation operation, any one of the healthy nodes may be selected as a management node. Compared with the prior art, the instruction is not required to be ensured to be issued to the same node through the cluster virtual IP any more, and the creation task of the replicated volume is randomly distributed to any healthy node in the cluster 3 to be completed, so that the management node determining module 12 can make any healthy node in the cluster 3 become a management node of the replicated volume to complete the creation work of the replicated volume.
b2) A replication volume creation request is generated for creating a replication volume.
c2) And sending the replication volume creation request and the storage pool address information to a management node.
Specifically, address information of the storage pool and a target address of a network main stream protocol (ISCSI) are sent to the management node, the ISCSI is a network main stream protocol for accessing the storage device through the network, the user is an initiator, and the provider is a target.
With continued reference to fig. 4, optionally, the management node 31 includes:
a replication volume creation unit 311, configured to, when receiving a replication volume creation request sent by the control front end 1, create a replication volume based on the storage pool.
The replication volume creation request may include information such as the size of the replication volume to be created, and 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.
Optionally, the replication volume creating unit 311 is specifically configured to: when a replication volume creation request sent by a control front end 1 is received, determining the address information of a replication volume to be created based on the address information of the storage pool and the existing replication volume information on the storage pool; and creating the replication volume based on the storage pool and combining the address information of the replication volume to be created.
Specifically, when a replication volume request sent by the control front end 1 is received, the address information of the existing replication volume on the storage pool is subtracted from the known storage pool address information, so as to obtain the remaining address information on the storage pool. And creating the replication volume according to the residual address information and the size of the replication volume to be created.
Illustratively, assume that the address range of the storage pool is: 0000-: 0000-: 0501-0600. It may be clear that a storage pool is a number of storage devices that are uniformly managed. When creating a replication volume, when one of the storage devices runs out of memory, the next storage device may be continuously used, or it may be understood that one replication volume may use partial memories of two or more storage devices, respectively. This is related to the replication volume size and the storage device size and is not specifically limited herein.
The binding relationship storage unit 312 is configured to bind the newly created replication volume with the corresponding management node, and store the replication volume information association table containing the binding relationship to the information center 2.
Specifically, a key value pair corresponding to the replication volume is formed from information such as the ID of the replication volume and the ID of the corresponding management node. For example, the key-value pair identification may be represented as a key. And representing the key value pair data identification by the key, wherein the value is the content of the key value pair data, and generating the key value pair data of < key, value >. Note that the ID of the replication volume may be referred to as a key, the information such as the ID of the management node corresponding to the replication volume may be referred to as a value, and the "management node" field in the value should be referred to as "itself". And binding the newly created replication volume with the corresponding management node, and assembling the binding relationship into a replication volume information association table and storing the replication volume information association table into the information center 2.
For example, assuming that a replication volume a is newly created, and a corresponding management node thereof is a management node 1, the replication volume a and the management node 1 are bound to form a key value pair, and stored in the information center in the form of a replication volume information association table. When the copy volume is managed, the management node corresponding to the copy volume can be acquired from the information center, the management request is sent to the corresponding management node address, and the copy volume is managed through the management node.
To more clearly describe the creation process of the replication volume provided by the embodiment of the present invention, fig. 5 is an exemplary diagram of a flow of creating the replication volume provided by an embodiment of the present invention. As shown in fig. 5, when creating the replication volume, the control front end queries a node health information list provided by the information center, selects any health node in the cluster, determines that the health node 1 is a management node, sends a creation instruction to the health node 1, creates a replication volume a in the storage pool according to the instruction by the health node, and forms a binding relationship between the replication volume a and the health node 1. Here, it is assumed that node (short for healthy node) 1 binds to volume (short for replication volume) a, node 2 binds to volume b, and the like, and stores the replication volume information association table in the information center. At this point, the creation process of the replication volume is complete.
As an optional embodiment of the present invention, the implementation embodies a workflow of copy volume management, and the implementation determines a target management node of a copy volume to be managed based on a search result by searching for an identifier of the copy volume to be managed from a pulled copy volume information association table, and manages the copy volume through the target management node. Meanwhile, when the management node is down, any healthy node can be randomly selected as the management node. Additionally disclosed is a creation process of the replication volume. Compared with the prior art, in the technical scheme provided by this embodiment, the tasks of creating, managing, and deleting the replication volume are randomly allocated to any node in the cluster 3 to be completed. Because the information center 2 and the cluster node can provide the management node address of the current replication volume, the control front end can make any healthy node in the cluster 3 become the management node of the replication volume, and the management work of the replication volume is completed. Therefore, on one hand, the command is not required to be ensured to be issued to the same node through the cluster virtual IP, and the management work of different copy volumes can be completed by different nodes, so that the efficiency is improved; on the other hand, the cluster virtual IP is not necessary, and the maintenance of the cluster is simplified.
Example two
Fig. 6 is a flowchart illustrating a method for managing a replication volume according to a second embodiment of the present invention, where the system is suitable for managing a replication volume, as shown in fig. 6, the method for managing a replication volume according to the second embodiment of the present invention may specifically include the following steps:
s210, determining a target management node related to the replication volume to be managed through a replication volume information association table acquired from the replication volume management information center, generating a replication volume management request of the replication volume to be managed, and sending the replication volume management request to the target management node.
S220, receiving and analyzing the replication volume management request, and performing replication volume management on the obtained replication volume to be managed.
The method can be executed by the copy volume management system provided by the embodiment of the invention, and has the beneficial effect of the copy volume management system.
EXAMPLE III
Fig. 7 is a block diagram of a computer device according to a third embodiment of the present invention, and as shown in fig. 7, the computer device, as a control terminal in the replication volume management system or a management node in a cluster according to the third embodiment of the present invention, 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 may be one or more, and one processor 41 is taken as an example in fig. 7; the processor 41, the memory 42, the input device 43 and the output device 44 in the computer apparatus may be connected by a bus or other means, and the connection by the bus is exemplified in fig. 7.
In particular, in an embodiment, when processor 41 executes one or more programs stored in memory 42, the following operations may be implemented: determining a target management node associated with the replication volume to be managed through a replication volume information association table acquired from the information center, generating a replication volume management request of the replication volume to be managed, and sending the replication volume management request to the target management node; and receiving and analyzing the replication volume management request, and performing replication volume management on the obtained replication volume to be managed.
The memory 42 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 42 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, memory 42 may further include memory located remotely from processor 41, which may be connected to a computer device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 43 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function controls of the computer apparatus. The output device 44 may include a display device such as a display screen.
Example four
An embodiment of the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, perform a replication volume management method, including:
determining a target management node associated with the replication volume to be managed through a replication volume information association table acquired from the information center, generating a replication volume management request of the replication volume to be managed, and sending the replication volume management request to the target management node;
and receiving and analyzing the replication volume management request, and performing replication volume management on the obtained replication volume to be managed.
Of course, the storage medium provided by the embodiment of the present invention contains computer-executable instructions, and the computer-executable instructions are not limited to the operations of the method described above, and may also perform related operations in the replication volume management method provided by any embodiment of the present invention.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It should be noted that, in the embodiment of the copy volume management system, the included units and modules are only divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (10)

1. A replication volume management system, comprising: the method comprises the steps of controlling a cluster consisting of a front end, an information center and a plurality of nodes;
the cluster comprises at least one management node;
the information center is used for storing a replication volume information association table containing the binding relationship between each pre-created replication volume and the corresponding management node and health information of all nodes in the cluster;
the control front end is used for determining a target management node related to the replication volume to be managed through a replication volume information association table acquired from the information center, generating a replication volume management request of the replication volume to be managed and sending the replication volume management request to the target management node;
the target management node is used for receiving and analyzing the replication volume management request and performing replication volume management on the obtained replication volume to be managed;
the control front end is also used for providing a web page for the user to do management operation of the copy volume.
2. The system of claim 1, wherein the control front end comprises a target node determination module configured to:
and searching the identification code of the replication volume to be managed from the pulled replication volume information association table, and determining the target management node of the replication volume to be managed based on the searching result.
3. The system of claim 2, wherein the target node determining module is specifically configured to:
when a user triggers a copy volume management operation request, searching an identification code of a copy volume to be managed from a pulled copy volume information association table;
determining a corresponding management node bound with the replication volume to be managed;
judging whether the management node is in a normal state, if so, determining that the management node is a target management node of the replication volume to be managed;
and if not, binding the replication volume to be managed with the new management node again, and returning to continuously execute the corresponding management node bound with the replication volume to be managed.
4. The system according to claim 3, wherein the target node determining module performs the step of binding the replication volume to be managed with a new management node, and comprises:
if the corresponding management node bound with the replication volume to be managed is in a downtime state, reselecting any healthy node in the cluster as a new management node corresponding to the replication volume to be managed;
binding the replication volume to be managed with the new management node to form a new binding relationship;
and updating the new binding relationship to the replication volume information association table.
5. The system of claim 1, wherein the control front end comprises a management node determination module configured to:
when a user triggers a copy volume creating operation, determining any healthy node in the cluster as a management node;
generating a replication volume creation request of a replication volume to be created;
and sending the replication volume creation request and the storage pool address information to the management node.
6. The system of claim 5, wherein the management node comprises:
a replication volume creating unit, configured to create a replication volume based on a storage pool when receiving a replication volume creation request sent by the control front end;
and the binding relation storage unit is used for binding the newly created replication volume with the corresponding management node and storing the replication volume information association table containing the binding relation to the information center.
7. The system of claim 6, wherein the replication volume creation module is specifically configured to:
when a replication volume creation request sent by the control front end is received, determining the address information of the replication volume to be created based on the address information of the storage pool and the existing replication volume information on the storage pool;
and creating the replication volume by combining the address information of the replication volume to be created based on the storage pool.
8. A replication volume management method performed by the replication volume management system according to any one of claims 1 to 7, comprising:
determining a target management node associated with the replication volume to be managed through a replication volume information association table acquired from the information center, generating a replication volume management request of the replication volume to be managed, and sending the replication volume management request to the target management node;
and receiving and analyzing the replication volume management request, and performing replication volume management on the obtained replication volume to be managed.
9. A computer device, which is the control terminal in the replication volume management system according to any one of claims 1 to 7, or the management node in the cluster, comprising:
one or more processors;
storage means for storing one or more programs;
the one or more programs being executable by the one or more processors to cause the one or more processors to perform the replication volume management method of claim 8.
10. A storage medium containing computer-executable instructions, which when executed by a computer processor, perform the replication volume management method of claim 8.
CN202210004900.8A 2022-01-05 2022-01-05 Copy volume management system, copy volume management method, device, and storage medium Pending CN114385420A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210004900.8A CN114385420A (en) 2022-01-05 2022-01-05 Copy volume management system, copy volume management method, device, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210004900.8A CN114385420A (en) 2022-01-05 2022-01-05 Copy volume management system, copy volume management method, device, and storage medium

Publications (1)

Publication Number Publication Date
CN114385420A true CN114385420A (en) 2022-04-22

Family

ID=81200832

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210004900.8A Pending CN114385420A (en) 2022-01-05 2022-01-05 Copy volume management system, copy volume management method, device, and storage medium

Country Status (1)

Country Link
CN (1) CN114385420A (en)

Similar Documents

Publication Publication Date Title
EP3668009B1 (en) Network service lifecycle management method and device
US11296940B2 (en) Centralized configuration data in a distributed file system
US9558194B1 (en) Scalable object store
WO2016199232A1 (en) Storage management computer and management method for storage device
US20200192689A1 (en) Container migration in computing systems
WO2009098909A1 (en) Virtual appliance assignment system
KR20130137897A (en) Method for managing data in asymmetric cluster file system
CN113268472B (en) Distributed data storage system and method
CN115168061B (en) Calculation storage separation method and system, electronic equipment and storage medium
WO2023040538A1 (en) Data migration method and apparatus, and device, medium and computer product
JP2014044553A (en) Program, information processing device, and information processing system
WO2016040393A1 (en) Application transparent continuous availability using synchronous replication across data stores in a failover cluster
CN114253459A (en) Method and device for creating persistent data volume and server
WO2020233002A1 (en) Container instance ip switching method and apparatus, computer device, and storage medium
KR101563292B1 (en) Cloud virtualization system and method using virtual session manager
CN112035062B (en) Migration method of local storage of cloud computing, computer equipment and storage medium
US10050834B1 (en) Multi-region virtual data center template
CN112199176A (en) Service processing method, device and related equipment
CN114385420A (en) Copy volume management system, copy volume management method, device, and storage medium
US20210081455A1 (en) Object search with pagination and non-duplicates support
CN115510016A (en) Client response method, device and medium based on directory fragmentation
US11609754B2 (en) Tool for latency optimized system placement
CN114584545A (en) Data management method, device, system, storage medium and electronic equipment
WO2006043322A1 (en) Server management program, server management method, and server management apparatus
CN110221868B (en) Host system deployment method and device, electronic equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination