Apparatus and method for utilizing different data storage types to store primary and replicated database directories

Patent metadata

Field	Value
Publication number	US-11030045-B2
Application number	US-201514811739-A
Country	US
Kind code	B2
Filing date	Jul 28, 2015
Priority date	Jul 28, 2015
Publication date	Jun 8, 2021
Grant date	Jun 8, 2021

Abstract

An apparatus and method are provided for utilizing different data storage types to store primary and replicated database directories. Included is a first data storage of a first data storage type including a direct-access storage type. The first data storage is configured to store a primary database directory. Also included is a second data storage of a second data storage type including a share type. The second data storage is configured to store a replicated database directory that replicates at least a portion of the primary database directory.

First claim

What is claimed is:

1. A method, comprising:
configuring each first data storage of a plurality of first data storages to store a primary database directory, the plurality of first data storages comprising a direct-access storage type, a first data storage of the plurality of first data storages being in communication with a corresponding node of the plurality of nodes, the first data storage being configured to store the primary database directory for access by only the corresponding node and is not shared with other nodes;
detecting a failure in connection with at least one node of the plurality of nodes; and
in response to detection of the failure, accessing a shared storage apparatus via a network interface coupled to the plurality of nodes, the shared storage apparatus including a plurality of second data storages, each second data storage of the plurality of second data storages configured to store a replicated database directory that replicates at least a portion of the primary database directory.

2. The method of claim 1 , wherein after detecting the failure in connection with the at least one of the plurality of nodes, the method further comprising:
determining whether a spare node exists.

3. The method of claim 2 , further comprising:
in response to the determination that the spare node exists, starting a database instance on the spare node for accessing the replicated database directory.

4. The method of claim 3 , further comprising:
in response to the determination that the spare node exists, mounting the replicated database directory in connection with the started database instance.

5. The method of claim 2 , further comprising:
in response to the determination that the spare node does not exist, starting a database instance on an available node for accessing the replicated database directory.

6. The method of claim 5 , further comprising:
in response to the determination that the spare node does not exist, mounting the replicated database directory in connection with the started database instance.

7. The method of claim 1 , further comprising:
initiating a rebuild operation; and
starting a read-only lock in response to an instance accessing the replicated database directory.

8. The method of claim 7 , the rebuild operation further comprising:
copying at least a portion of the replicated database directory to a new data storage of the direct-access storage type.

9. The method of claim 8 , the rebuild operation further comprising:
starting a database instance on the node.

10. The method of claim 9 , the rebuild operation further comprising:
mounting at least the portion of the replicated database directory in connection with the started database instance.

11. The method of claim 10 , the rebuild operation further comprising:
removing the read-only lock and stopping the database instance.

12. The method of claim 1 , further comprising:
performing a data operation by determining whether the replicated database directory exists.

13. The method of claim 12 , further comprising:
in response to determining that the replicated database directory exists, starting at least two threads including a first thread for performing the data operation on the primary database directory and a second thread for performing the data operation on the replicated database directory.

14. The method of claim 13 , wherein the at least two threads operate simultaneously to write data to the primary database directory and the replicated database directory respectively.

15. A system, comprising:
at least one network interface;
a plurality of nodes in communication with the at least one network interface;
a plurality of first data storages of a direct-access storage type, a first data storage of the plurality of first data storages being in communication with a corresponding node of the plurality of nodes, the first data storage being configured to store a primary database directory for access by only the corresponding node and is not shared with other nodes; and
a shared storage apparatus in communication with the at least one network interface and including a plurality of second data storages, each second data storage of the plurality of second data storages configured to store a replicated database directory that replicates at least a portion of the primary database directory, and at least one corresponding second data storage being accessed in response to a failure detected in connection with at least one node of the plurality of nodes.

16. The system of claim 15 , wherein the system is configured for, in response to the detection of the failure in connection with the at least one node, determining whether a spare node exists.

17. The system of claim 16 , wherein the system is configured for, in response to the determination that the spare node exists, starting a database instance on the spare node for accessing the replicated database directory.

18. The system of claim 17 , wherein the system is configured for, in response to the determination that the spare node exists, mounting the replicated database directory in connection with the started database instance.

19. The system of claim 16 , wherein the system is configured for, in response to the determination that the spare node does not exist, starting a database instance on an available node for accessing the replicated database directory.

20. The system of claim 19 , wherein the system is configured for, in response to the determination that the spare node does not exist, mounting the replicated database directory in connection with the started database instance.

21. The system of claim 15 , wherein the system is configured for initiating a rebuild operation.

22. The system of claim 21 , wherein the system is configured such that the rebuild operation includes starting a read-only lock in response to an instance accessing the replicated database directory.

23. The system of claim 22 , wherein the system is configured such that the rebuild operation further includes copying at least a portion of the replicated database directory to a new data storage of the direct-access storage type.

24. The system of claim 23 , wherein the system is configured such that the rebuild operation further includes starting a database instance on the at least one node.

25. The system of claim 24 , wherein the system is configured such that the rebuild operation further includes mounting at least the portion of the replicated database directory in connection with the started database instance.

26. The system of claim 25 , wherein the system is configured such that the rebuild operation further includes removing the read-only lock and stopping the database instance.

27. The system of claim 15 , wherein the system is configured for performing a data operation by determining whether the replicated database directory exists.

28. The system of claim 27 , wherein the system is configured for, in response to determining that the replicated database directory exists, starting at least two threads including a first thread for performing the data operation on the primary database directory and a second thread for performing the data operation on the replicated database directory.

29. The system of claim 28 , wherein the system is configured for, in response to determining that the replicated database

Assignees

• Futurewei Technologies Inc

Inventors

• Yang Bai
• Zhang Guogen

Classifications

• G06F11/2023 Primary

  Failover techniques · CPC title

• G06F11/1662

  the resynchronized component or unit being a persistent storage device (re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008) · CPC title

• G06F11/2046

  where the redundant components share persistent storage (G06F11/2043 takes precedence) · CPC title

• G06F11/2035

  without idle spare hardware · CPC title

• G06F11/2094

  Redundant storage or storage space (G06F11/2056 takes precedence) · CPC title