IP Library Granted Patent US 12,056,155
Granted Patent B2
US 12,056,155 · App. 18/278,383 · Granted Aug 6, 2024

Method for cross-node cloning of storage volume, device, apparatus and storage medium

Inventors: Yuchao Xu (Jiangsu, CN); Zhiguo Wang (Jiangsu, CN)
Assignee: INSPUR SUZHOU INTELLIGENT TECHNOLOGY CO., LTD.
G06F16/27G06F11/1469G06F2201/84
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,056,155
App. No.
18/278,383
Granted
Aug 6, 2024
Kind
B2
Abstract

The present application provides a method for cross-node cloning of a storage volume, a device, apparatus and a storage medium. The method includes: creating AEP storage in a node of a cluster by using pmem-csi, and monitoring whether a clone volume of the AEP storage exist in other nodes of the cluster, in response to that a clone volume of the AEP storage is monitored in the other nodes of the cluster, stopping the AEP storage and the clone volume; creating a snapshot of the AEP storage, and recovering the AEP storage; and starting the clone volume after transmitting snapshot data of the AEP storage to the clone volume. By using the solution of the present application, the problem of performing application migration and data backup of an AEP storage volume used in a cloud platform may be solved.

Claims (57)

1. A method for cross-node cloning of a storage volume, executed by a processor and comprising the following steps:

by using pmem-csi, creating AEP storage in a node of a cluster, and monitoring whether a clone volume of the AEP storage exists in other nodes of the cluster;

in response to monitoring that a clone volume of the AEP storage exists in the other nodes of the cluster, stopping using the AEP storage and the clone volume;

creating a snapshot of the AEP storage, and recovering using the AEP storage; and

transmitting snapshot data of the AEP storage to the clone volume to start using the clone volume;

wherein the step of, creating a snapshot of the AEP storage, and recovering using the AEP storage comprises:

by means of a name of the AEP storage, finding a mapped host directory;

by means of a liswatch mechanism, acquiring data of the AEP storage in the host directory, wherein the data comprise a capacity of the AEP storage;

setting a name of a snapshot to be created, and transmitting the name, the capacity and a directory parameter of the snapshot into a lvm snapshot interface to create the snapshot of the AEP storage;

in response to that the snapshot of the AEP storage is created, recovering using the AEP storage;

wherein the step of, by using the pmem-csi, creating the AEP storage in the node of the cluster, and monitoring whether the clone volume of the AEP storage exists in the other nodes of the cluster comprises:

on the basis of a listwatch mechanism of Kubernetes, monitoring data of the storage volume in other nodes of the cluster;

judging whether the monitored data carry a node datum tag of the AEP storage;

in response to that the node datum tag of the AEP storage is carried by the monitored data, determining that the storage volume in other nodes is the clone volume of the AEP storage.

2. The method according to claim 1 , wherein the method further comprises:

according to a threshold size, dividing the snapshot data of the AEP storage into a plurality of data slices.

3. The method according to claim 2 , wherein the step of, transmitting snapshot data of the AEP storage to the clone volume to start using the clone volume, comprises:

sending one data slice of the snapshot data of the AEP storage to the clone volume;

by the clone volume, storing the received data slice, and sending a response message to the AEP storage;

in response to the AEP storage receiving the response message of storing successfully that sent by the clone volume, sending next data slice of the snapshot data of the AEP storage to the clone volume until all the data is successfully stored in the clone volume.

4. The method according to claim 1 , wherein the step of, in response to monitoring that a clone volume of the AEP storage exists in other nodes of the cluster, stopping using the AEP storage and the clone volume comprises:

in response to monitoring that the clone volume of the AEP storage exists in other nodes of the cluster, by using a freeze command: fsfreeze-freeze, freezing the AEP storage and the clone volume.

5. The method according to claim 1 , wherein the method further comprises:

in response to the AEP storage receiving the response message of storing unsuccessfully that sent by the clone volume, stopping the clone operation, and sending a warn of cloning unsuccessfully.

6. The method according to claim 5 , wherein, the step of, in response to the AEP storage receiving the response message of storing unsuccessfully that sent by the clone volume, stopping the clone operation, and sending a warn of cloning unsuccessfully further comprises:

the warn of cloning unsuccessfully is sent to the administrator's mobile device and e-mail box via the network, and displayed on the display device where the AEP storage is located.

7. The method according to claim 5 , wherein, the step of, in response to the AEP storage receiving the response message of storing unsuccessfully that sent by the clone volume, stopping the clone operation, and sending a warn of cloning unsuccessfully further comprises:

the warn of cloning unsuccessfully is displayed on the display device where the AEP storage is located.

8. A computer device, comprising:

at least one processor; and

a memory storing computer instructions that, when executed by the processor, cause the processor to implement steps of:

by using pmem-csi, creating AEP storage in a node of a cluster, and monitoring whether a clone volume of the AEP storage exists in other nodes of the cluster;

in response to monitoring that a clone volume of the AEP storage exists in the other nodes of the cluster, stopping using the AEP storage and the clone volume;

creating a snapshot of the AEP storage, and recovering using the AEP storage; and

transmitting snapshot data of the AEP storage to the clone volume to start using the clone volume;

wherein the step of, creating a snapshot of the AEP storage, and recovering using the AEP storage comprises:

by means of a name of the AEP storage, finding a mapped host directory;

by means of a liswatch mechanism, acquiring data of the AEP storage in the host directory, wherein the data comprise a capacity of the AEP storage;

setting a name of a snapshot to be created, and transmitting the name, the capacity and a directory parameter of the snapshot into a lvm snapshot interface to create the snapshot of the AEP storage;

in response to that the snapshot of the AEP storage is created, recovering using the AEP storage;

wherein the step of, by using the pmem-csi, creating the AEP storage in the node of the cluster, and monitoring whether the clone volume of the AEP storage exists in the other nodes of the cluster comprises:

on the basis of a listwatch mechanism of Kubernetes, monitoring data of the storage volume in other nodes of the cluster;

judging whether the monitored data carry a node datum tag of the AEP storage;

in response to that the node datum tag of the AEP storage is carried by the monitored data, determining that the storage volume in other nodes is the clone volume of the AEP storage.

9. The computer device according to claim 8 , wherein the processor is further configured to implement steps of:

according to a threshold size, dividing the snapshot data of the AEP storage into a plurality of data slices.

10. The computer device according to claim 9 , wherein the step of, transmitting snapshot data of the AEP storage to the clone volume to start using the clone volume, comprises:

sending one data slice of the snapshot data of the AEP storage to the clone volume;

by the clone volume, storing the received data slice, and sending a response message to the AEP storage;

in response to the AEP storage receiving the response message of storing successfully that sent by the clone volume, sending next data slice of the snapshot data of the AEP storage to the clone volume until all the data is successfully stored in the clone volume.

11. The computer device according to claim 8 , wherein the step of, in response to monitoring that a clone volume of the AEP storage exists in other nodes of the cluster, stopping using the AEP storage and the clone volume comprises:

in response to monitoring that the clone volume of the AEP storage exists in other nodes of the cluster, by using a freeze command: fsfreeze-freeze, freezing the AEP storage and the clone volume.

12. The computer device according to claim 8 , wherein the processor is further configured to implement steps of:

in response to the AEP storage receiving the response message of storing unsuccessfully that sent by the clone volume, stopping the clone operation, and sending a warn of cloning unsuccessfully.

13. The computer device according to claim 12 , wherein, the step of, in response to the AEP storage receiving the response message of storing unsuccessfully that sent by the clone volume, stopping the clone operation, and sending a warn of cloning unsuccessfully further comprises:

the warn of cloning unsuccessfully is sent to the administrator's mobile device and e-mail box via the network.

14. A non-transitory computer readable storage medium, in which a computer program is stored, wherein when the computer program is executed by a processor, the method of claim 1 is performed.

Assignments (2)
LICENSE Recorded Jun 30, 2026
From: IEIT SYSTEMS CO., LTD
To: AIVRES SYSTEMS INC.
Reel/Frame 075857/0939 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 22, 2023
From: XU, YUCHAO; WANG, ZHIGUO
To: INSPUR SUZHOU INTELLIGENT TECHNOLOGY CO., LTD.
Reel/Frame 064674/0257 →
Priority Claims (1)
CN 202111141286.1 · Sep 28, 2021 · national
Continuity (1)
Related Publication 20240037120A1 · Feb 1, 2024