CN116266098A - Storage pool importing method and device - Google Patents
Storage pool importing method and device Download PDFInfo
- Publication number
- CN116266098A CN116266098A CN202111544981.2A CN202111544981A CN116266098A CN 116266098 A CN116266098 A CN 116266098A CN 202111544981 A CN202111544981 A CN 202111544981A CN 116266098 A CN116266098 A CN 116266098A
- Authority
- CN
- China
- Prior art keywords
- heartbeat
- heartbeat data
- node
- storage pool
- importing
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 35
- 230000001960 triggered effect Effects 0.000 claims abstract description 6
- 230000008676 import Effects 0.000 claims description 17
- 230000008569 process Effects 0.000 claims description 10
- 238000004364 calculation method Methods 0.000 claims description 4
- 241000283070 Equus zebra Species 0.000 claims description 3
- 230000002159 abnormal effect Effects 0.000 abstract description 12
- 230000000694 effects Effects 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000013496 data integrity verification Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0614—Improving the reliability of storage systems
- G06F3/0619—Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a storage pool importing method and device, which are applied to nodes included in a NAS cluster. When detecting that a target LUN in a storage pool is locked, the node sends a heartbeat reading command to the storage device at preset time intervals, wherein the heartbeat reading command comprises a pre-designated address segment for storing heartbeat data, so that the storage device reads the heartbeat data from the address segment and returns the heartbeat data to the node, and the heartbeat data in the address segment is periodically triggered to be updated by another node which is importing the storage pool; and if the preset reading times are reached and the read heartbeat data are consistent, importing the heartbeat data into the storage pool. According to the method and the device, when the node being imported is abnormal, other nodes can normally take over the abnormal node service, service interruption is avoided, and meanwhile, the disastrous effect of data damage caused by simultaneous importing of multiple nodes can be effectively avoided.
Description
Technical Field
The present invention relates to the field of storage technologies, and in particular, to a storage pool import method and apparatus.
Background
The network attached storage (english: network Attached Storage, abbreviated: NAS) is a device which is connected to a network and has a data storage function, and is also called a network storage, and is a dedicated data storage server. The method takes data as a center, thoroughly separates the storage device from the server, and centrally manages the data, thereby releasing bandwidth, improving performance and reducing total ownership cost. Its cost is far lower than using server storage, while its efficiency is far higher than the latter.
The zebra byte file system (English: zettabyte File System, abbreviated: ZFS) is a novel file system with 128-bit addressing capability, and has the advantages of self-optimization, automatic data integrity verification, easy management of a storage pool/volume system, snapshot copying and the like, and is often used as a bottom file system of the NAS.
NAS clusters are composed of several NAS nodes (hereinafter referred to as nodes), and in order to meet the requirement of a user for high availability of storage, NAS clusters generally operate in a primary-standby mode. That is, one master node corresponds to one or more standby nodes, and when the master node fails, the standby nodes take over the service of the master node to continue working.
The existence of the opposite side is generally perceived by adopting a heartbeat mechanism between the main node and the standby node, once the heartbeat is detected abnormally, the opposite side is considered to be faulty, and the main node and the standby node can contend for resources at the same time. For example, the heartbeat is lost due to network reasons, and the master node and the standby node simultaneously import the storage pool. Because the primary and backup nodes operate on the same storage pool, data in the storage pool may be damaged, and catastrophic results of data damage may occur.
To avoid simultaneous importation of multiple nodes, a locking mechanism may be employed. That is, after one node locks a storage pool, other nodes cannot import the storage pool. However, in practical use, if a node locking the storage pool is abnormal in the importing process, for example, if power is turned off and the node is stopped, other nodes cannot normally take over the abnormal node service, so that the service is interrupted.
Disclosure of Invention
In view of this, the present application proposes a method and apparatus for importing a storage pool, which are used to ensure that a node normally takes over services, and at the same time, avoid catastrophic consequences of data corruption.
In order to achieve the purposes of the application, the application provides the following technical scheme:
in a first aspect, the present application provides a storage pool importing method, which is applied to a node included in a NAS cluster, where the method includes:
when detecting that a target logic unit number (English: logical Unit Number, abbreviated: LUN) in a storage pool is locked, sending a heartbeat reading command to a storage device at preset time intervals, wherein the heartbeat reading command comprises a pre-designated address segment for storing heartbeat data, so that the storage device reads the heartbeat data from the address segment and returns the heartbeat data to a local node, and the heartbeat data in the address segment is periodically triggered to be updated by another node which is importing the heartbeat data into the storage pool;
and if the preset reading times are reached and the read heartbeat data are consistent, importing the heartbeat data into the storage pool.
Optionally, the method further comprises:
if inconsistent heartbeat data is read before the preset reading times are reached, the storage pool is not imported.
Optionally, the method further comprises:
in the process of importing the node into the storage pool, the following operations are executed at preset time intervals:
calculating new heartbeat data according to a preset heartbeat algorithm;
and sending a heartbeat update command to the storage device, wherein the heartbeat update command comprises the address segment and the new heartbeat data, so that the storage device writes the new heartbeat data into the address segment.
Optionally, the address field is located in a Boot Header area included in the ZFS tag of the target LUN.
Optionally, after the node imports the storage pool, the method further includes:
and sending an unlocking command for the target LUN to the storage device so that the storage device can execute unlocking operation on the target LUN.
In a second aspect, the present application provides a storage pool importing apparatus, applied to a node included in a NAS cluster, where the apparatus includes:
a sending unit, configured to send, when it is detected that a target LUN in a storage pool is locked, a heartbeat reading command to a storage device at a preset time interval, where the heartbeat reading command includes a pre-specified address segment for storing heartbeat data, so that the storage device reads the heartbeat data from the address segment and returns the heartbeat data to the node, where the heartbeat data in the address segment is periodically triggered to be updated by another node that is importing into the storage pool;
and the importing unit is used for importing the storage pool if the preset reading times are reached and the read heartbeat data are consistent.
Optionally, the importing unit is further configured to not import the storage pool if inconsistent heartbeat data is read before the preset number of reads is reached.
Optionally, the apparatus further includes:
the calculation unit is used for calculating new heartbeat data according to a preset heartbeat algorithm at preset time intervals in the process of importing the node into the storage pool;
the sending unit is further configured to send a heartbeat update command to the storage device, where the heartbeat update command includes the address segment and the new heartbeat data, so that the storage device writes the new heartbeat data into the address segment.
Optionally, the address field is located in a Boot Header area included in the ZFS tag of the target LUN.
Optionally, the sending unit is further configured to send an unlocking command for the target LUN to the storage device after importing the storage pool, so that the storage device performs an unlocking operation on the target LUN.
As can be seen from the above description, in the embodiment of the present application, by monitoring the node being imported, the operation state of the importing node is perceived, and when determining that the importing node is abnormal, the node executes strong importing, so as to ensure that the node normally takes over the service of the abnormal node, avoiding service interruption.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a storage pool importation method according to an embodiment of the present application;
FIG. 2 is a heartbeat data update flow diagram illustrating an embodiment of the present application;
FIG. 3 is a ZFS tag schematic of a LUN as shown in an embodiment of the application;
fig. 4 is a schematic diagram of a storage pool importing apparatus according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application.
The terminology used in the embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of the application. As used in the embodiments of the present application, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in embodiments of the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the negotiation information may also be referred to as second information, and similarly, the second information may also be referred to as negotiation information, without departing from the scope of embodiments of the present application. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
For the purposes, technical solutions and advantages of the present application, the following detailed description of the present application is described with reference to the accompanying drawings and specific embodiments:
referring to fig. 1, a flowchart of a storage pool importing method is shown in an embodiment of the present application, where the flowchart is applied to a node included in a NAS cluster.
As shown in fig. 1, the process may include the steps of:
step 101, when detecting that the target LUN in the storage pool is locked, sending a heartbeat reading command to the storage device at preset time intervals.
The node needs to access the storage Chi Jiasuo before importing the storage pool to obtain the import right to the storage pool.
The storage pool is made up of at least one LUN. The node achieves the purpose of locking the storage pool by sending a locking command to the target LUN in the storage pool. Wherein the target LUN may be any LUN in a pre-designated storage pool.
As an example, the target LUN may be the first LUN in the storage pool to improve the efficiency of the storage device traversing to the target LUN, thereby improving the locking and importing efficiency.
The locking command may be an atomic operation including read, compare, write, such as compare and write command based on a small computer system interface (English: small Computer System Interface, abbreviation: SCSI). The compare and write command typically includes an address field to be operated on, desired data, and new data to be written to, the new data being written to the address field to be operated on when the data read by the storage device from the address field to be operated on is consistent with the desired data; if not, then no write operation is performed.
In this embodiment of the present application, the address field to be operated included in the locking command may be an address field where a pre-designated lock is located, the expected data may be data indicating that the lock is not locked (for example, all 0 s), and the data to be written may be data indicating that the lock is locked (for example, all 1 s).
When the data read by the storage device from the address field of the lock is consistent with the data (for example, all 0) indicating that the target LUN is not locked, the data (for example, all 1) indicating that the lock is locked can be written into the address field of the lock, so as to realize locking the target LUN, and a successful locking message is returned to the node.
Otherwise, when the data read by the storage device from the address field of the lock is inconsistent with the data representing that the lock is not locked, indicating that the target LUN is locked, the storage device does not execute writing of the locking data into the address field of the lock, and meanwhile returns a locking failure message to the node.
If the node receives a lock success message, importing into the storage pool may be performed. Otherwise, if the node receives the lock failure message, it may be determined that there are other nodes currently locking the target LUN and performing import into the storage pool.
At this time, the present node may transmit a heartbeat read command including a pre-designated address field for storing heartbeat data to the storage device at a preset time interval (e.g., 2 seconds).
Here, it should be noted that, the heartbeat data in the address segment may be updated by the node that is executing the import into the storage pool. I.e. the heartbeat data in the address field changes dynamically.
The storage device returns the heartbeat data read each time to the node.
Step 102, if the preset reading times are reached and the read heartbeat data are consistent, importing the heartbeat data into a storage pool.
In the embodiment of the application, the node compares the periodically read heartbeat data.
If it is determined that inconsistent heartbeat data exists, i.e., the heartbeat data is changing, before a preset number of readings (e.g., 3 times) is reached, indicating that the node currently executing import is functioning properly, the node does not execute the operation of importing the storage pool, so as to avoid the catastrophic consequences of data corruption of simultaneous importation of multiple nodes.
Otherwise, if the actual reading times reach the preset reading times and the read heartbeat data are consistent, the fact that the heartbeat data are not updated for a long time by the node which is executing the importing is indicated, and the importing node operates abnormally, the node can be forcedly imported into the storage pool so as to take over the business of the abnormal node and avoid business interruption.
Thus, the flow shown in fig. 1 is completed.
As can be seen from the flow shown in fig. 1, in the embodiment of the present application, by monitoring the node being imported, the operation state of the importing node is perceived, and when it is determined that the importing node is abnormal, the node executes strong importing, so as to ensure that the node normally takes over the service of the abnormal node, avoiding service interruption.
As an example, the present node may also perform the heartbeat data update procedure shown in fig. 2 during the process of performing the import into the storage pool via step 102.
As shown in fig. 2, the process may include the steps of:
step 201, calculating heartbeat data according to a preset heartbeat algorithm at preset time intervals.
That is, the present node needs to update the heartbeat data at regular time during the import process.
Here, the preset heartbeat algorithm needs to ensure that the heartbeat data obtained by each calculation is different, i.e. dynamically changed. For example, the preset heartbeat algorithm may be an increment algorithm, a decrement algorithm, or the like. The embodiments of the present application are not limited to a specific heartbeat algorithm.
Step 202, sending a heartbeat update command to the storage device, wherein the heartbeat update command comprises a pre-designated address segment for storing heartbeat data and the calculated heartbeat data.
After obtaining the new heartbeat data in step 201, the node sends a heartbeat update command to the storage device.
And the storage equipment writes the heartbeat data calculated by the nodes into an address segment for storing the heartbeat data according to the heartbeat updating command, so that the heartbeat data is updated.
In this way, other nodes can determine whether the node is abnormal according to the change of the central hop data of the address segment, and further determine whether the strong import is required.
Thus, the flow shown in fig. 2 is completed. The update of the heartbeat data is achieved by the flow shown in fig. 2.
As one example, after the import of the storage pool is completed by step 102, the present node may send an unlock command to the storage device for the target LUN, where the unlock command includes an address field of the lock in the target LUN, data indicating that the lock is locked, and data for unlocking.
After receiving the unlocking command, the storage device reads data from the address field where the lock is located in the target LUN, compares the read data with the data (for example, all 1) which indicates that the lock is locked in the unlocking command, and if the read data is consistent with the data (for example, all 0) in the unlocking command is written into the address field where the lock is located, so that the purpose of unlocking is achieved.
Thus, the description of the implementation is completed, and the unlocking of the storage pool is realized.
As one example, the address field used to store the heartbeat data may be located in a Boot Header region included in a ZFS Label (Label) of the target LUN. The Boot Header region is a reserved 8K size region.
Referring to FIG. 3, a ZFS tag schematic of a LUN is shown in an embodiment of the application. In the diagram, the LUN has 4 ZFS labels, L0-L3, where L0 and L1 are at the front of the LUN, and L2 and L3 are at the end of the LUN.
As one example, an address field for storing heartbeat data may be located in a Boot Header region included in a first ZFS tag (L0) of a target LUN, so that the storage device may quickly traverse to the address field, performing heartbeat data reading and updating operations.
As an example, the address field for storing the heartbeat data and the address field where the lock is located may be both located in a Boot Header area included in the first ZFS tag of the target LUN, as shown in fig. 3.
As one example, the address field where the lock is located and the address field for storing the heartbeat data each occupy one sector size of the Boot Header area (512B). Accordingly, the length of the locking data, the unlocking data and the heartbeat data is one sector size.
Because the sector is the minimum unit of the operation of the storage device, the resource occupation can be effectively reduced and the processing efficiency can be improved by operating the sector in the Boot Header region.
Thus, the description of the present embodiment is completed. It can be seen that, in this embodiment, the reserved area of the ZFS tag is used to perform locking and unlocking and record heartbeat data, so that the influence on actual service data can be effectively avoided.
The method provided by the embodiment of the present application is described above, and the device provided by the embodiment of the present application is described below:
referring to fig. 4, a storage pool importing apparatus shown in an embodiment of the present application is applied to a node included in a NAS cluster, where the apparatus includes a sending unit 401 and an importing unit 402, where:
a sending unit 401, configured to send, when it is detected that a target LUN in a storage pool is locked, a heartbeat reading command to a storage device at a preset time interval, where the heartbeat reading command includes a pre-specified address segment for storing heartbeat data, so that the storage device reads the heartbeat data from the address segment and returns the heartbeat data to the node, where the heartbeat data in the address segment is periodically triggered to be updated by another node that is importing into the storage pool;
and an importing unit 402, configured to import the storage pool if the preset number of readings is reached and the read heartbeat data are consistent.
As an embodiment, the importing unit 402 is further configured to not import the storage pool if inconsistent heartbeat data is read before the preset number of reads is reached.
As an embodiment, the apparatus further comprises:
the calculation unit is used for calculating new heartbeat data according to a preset heartbeat algorithm at preset time intervals in the process of importing the node into the storage pool;
the sending unit 401 is further configured to send a heartbeat update command to the storage device, where the heartbeat update command includes the address segment and the new heartbeat data, so that the storage device writes the new heartbeat data into the address segment.
As an embodiment, the address segment is located in a Boot Header area included in the ZFS tag of the target LUN.
As an embodiment, the sending unit 401 is further configured to send, after importing the storage pool, an unlock command for the target LUN to the storage device, so that the storage device performs an unlock operation on the target LUN.
The description of the apparatus shown in fig. 4 is thus completed.
As can be seen from the above description, in the embodiment of the present application, by monitoring the node being imported, the operation state of the importing node is perceived, and when the importing node is determined to be abnormal, the node executes strong importing, so as to ensure that the node normally takes over the service of the abnormal node, avoiding service interruption.
The foregoing description of the preferred embodiments is merely exemplary in nature and is not intended to limit the invention to the precise form disclosed, and thus, any modification, equivalents, and alternatives falling within the spirit and scope of the embodiments are intended to be included within the scope of the invention.
Claims (10)
1. A storage pool importing method, applied to a node included in a network attached storage NAS cluster, the method comprising:
when detecting that a target logic unit number LUN in a storage pool is locked, sending a heartbeat reading command to storage equipment at preset time intervals, wherein the heartbeat reading command comprises a pre-designated address segment for storing heartbeat data, so that the storage equipment reads the heartbeat data from the address segment and returns the heartbeat data to the node, and the heartbeat data in the address segment is periodically triggered to be updated by another node which is importing the storage pool;
and if the preset reading times are reached and the read heartbeat data are consistent, importing the heartbeat data into the storage pool.
2. The method of claim 1, wherein the method further comprises:
if inconsistent heartbeat data is read before the preset reading times are reached, the storage pool is not imported.
3. The method of claim 1, wherein the method further comprises:
in the process of importing the node into the storage pool, the following operations are executed at preset time intervals:
calculating new heartbeat data according to a preset heartbeat algorithm;
and sending a heartbeat update command to the storage device, wherein the heartbeat update command comprises the address segment and the new heartbeat data, so that the storage device writes the new heartbeat data into the address segment.
4. The method of claim 1, wherein the address field is located in a Boot Header region included in a zebra byte file system ZFS tag of the target LUN.
5. The method of claim 1, wherein after the node imports the storage pool, the method further comprises:
and sending an unlocking command for the target LUN to the storage device so that the storage device can execute unlocking operation on the target LUN.
6. A storage pool importation apparatus for use with a node comprised by a network attached storage NAS cluster, said apparatus comprising:
a sending unit, configured to send, when it is detected that a target logical unit number LUN in a storage pool is locked, a heartbeat reading command to a storage device at a preset time interval, where the heartbeat reading command includes an address segment that is specified in advance and is used to store heartbeat data, so that the storage device reads the heartbeat data from the address segment and returns the heartbeat data to the node, where the heartbeat data in the address segment is periodically triggered to be updated by another node that is importing into the storage pool;
and the importing unit is used for importing the storage pool if the preset reading times are reached and the read heartbeat data are consistent.
7. The apparatus of claim 6, wherein:
the importing unit is further configured to not import the storage pool if inconsistent heartbeat data is read before the preset reading times are reached.
8. The apparatus of claim 6, wherein the apparatus further comprises:
the calculation unit is used for calculating new heartbeat data according to a preset heartbeat algorithm at preset time intervals in the process of importing the node into the storage pool;
the sending unit is further configured to send a heartbeat update command to the storage device, where the heartbeat update command includes the address segment and the new heartbeat data, so that the storage device writes the new heartbeat data into the address segment.
9. The apparatus of claim 6, wherein the address field is located in a Boot Header region included in a zebra byte file system ZFS tag of the target LUN.
10. The apparatus of claim 6, wherein:
the sending unit is further configured to send an unlocking command for the target LUN to the storage device after the storage pool is imported, so that the storage device performs an unlocking operation on the target LUN.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111544981.2A CN116266098A (en) | 2021-12-16 | 2021-12-16 | Storage pool importing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111544981.2A CN116266098A (en) | 2021-12-16 | 2021-12-16 | Storage pool importing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116266098A true CN116266098A (en) | 2023-06-20 |
Family
ID=86743271
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111544981.2A Pending CN116266098A (en) | 2021-12-16 | 2021-12-16 | Storage pool importing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116266098A (en) |
-
2021
- 2021-12-16 CN CN202111544981.2A patent/CN116266098A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110071821B (en) | Method, node and storage medium for determining the status of a transaction log | |
| US7949636B2 (en) | Systems and methods for a read only mode for a portion of a storage system | |
| US6701455B1 (en) | Remote copy system with data integrity | |
| CN106776130B (en) | Log recovery method, storage device and storage node | |
| US8108606B2 (en) | Computer system and control method for the computer system | |
| US7827144B1 (en) | Methods of reading and writing data | |
| US20100106907A1 (en) | Computer-readable medium storing data management program, computer-readable medium storing storage diagnosis program, and multinode storage system | |
| US20100138687A1 (en) | Recording medium storing failure isolation processing program, failure node isolation method, and storage system | |
| US20080140963A1 (en) | Methods and systems for storage system generation and use of differential block lists using copy-on-write snapshots | |
| US20120109919A1 (en) | High availability database management system and database management method using same | |
| CN109491609B (en) | Cache data processing method, device and equipment and readable storage medium | |
| CN113326006B (en) | Distributed block storage system based on erasure codes | |
| CN109726036B (en) | Data reconstruction method and device in storage system | |
| US12050778B2 (en) | Data restoration method and related device | |
| CN110597779A (en) | Data reading and writing method in distributed file system and related device | |
| CN115599607B (en) | Data recovery method and related device of RAID array | |
| CN108234465B (en) | Redundancy method and device for handling exception in distributed file system | |
| US6363457B1 (en) | Method and system for non-disruptive addition and deletion of logical devices | |
| US11809295B2 (en) | Node mode adjustment method for when storage cluster BBU fails and related component | |
| US20090164839A1 (en) | Storage control apparatus and storage control method | |
| CN116974489A (en) | Data processing method, device and system, electronic equipment and storage medium | |
| CN111176886B (en) | Database mode switching method and device and electronic equipment | |
| CN116266098A (en) | Storage pool importing method and device | |
| US10168935B2 (en) | Maintaining access times in storage systems employing power saving techniques | |
| CN116048878A (en) | Business service recovery method, device and computer equipment |
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 |