Method and apparatus for restoring an instance of a storage server

Patent metadata

Field	Value
Publication number	US-10175910-B2
Application number	US-201615140141-A
Country	US
Kind code	B2
Filing date	Apr 27, 2016
Priority date	Oct 19, 2012
Publication date	Jan 8, 2019
Grant date	Jan 8, 2019

Abstract

Implementations of the present disclosure involve a system and/or method for gracelessly rebooting a storage appliance. The method and system includes a storage appliance in association with an event that will result in the loss of a state table from volatile memory that halts changes to at least one state table of the storage appliance. The state tables describe a plurality of file system states of one or more clients connected to the first storage appliance. The state information is written to a persistent memory of the storage appliance. The state table may then be repopulated using the state table information stored in persistent memory.

First claim

What is claimed is:

1. A method for restoring an instance of a storage appliance following an event, the method comprising:
receiving an indication of the event at the storage appliance, the storage appliance in communication with one or more client devices over a network, the storage appliance maintaining a state table in volatile memory, the state table listing the one or more client devices and detailing a state of interaction with the storage appliance for each of the one or more client devices;
halting modification to the state table;
writing state table information for reproducing the state table to persistent memory in communication with the storage appliance;
transferring an Internet Protocol address for the storage appliance and control of the persistent memory to a second storage appliance to execute requests from the one or more client devices during the event; and
following the event, restoring the state table in the volatile memory from the state table information stored in the persistent memory.

2. The method of claim 1 , further comprising:
deleting the state table information from the persistent memory after the state table is restored in the volatile memory.

3. The method of claim 1 , wherein the event is at least one of: a reboot, a failover, a takeover, a failback, a planned event, or an unplanned event.

4. The method of claim 1 , wherein the state table information is written to the persistent memory after any in-progress requests from the one or more client devices to the storage appliance are completed.

5. The method of claim 1 , wherein prior to writing the state table information to the persistent memory, an initiation marker is stored in the persistent memory at each location where the state table information will be stored in the persistent memory.

6. The method of claim 5 , wherein after the state table information is written to the persistent memory, the initiation marker is replaced with a completion marker in the persistent memory.

7. The method of claim 6 , wherein a timestamp for the completion marker is matched to a corresponding timestamp for a second state table to confirm the state table and the second state table correspond to the instance of the storage appliance.

8. The method of claim 6 , wherein restoring the state table in the volatile memory from the state table information stored in the persistent memory is aborted where the completion marker is missing.

9. The method of claim 1 , wherein the state table information is stored in the persistent memory according to a distributed stable storage path for the state for each of the one or more client devices.

10. The method of claim 1 , wherein the Internet Protocol address for the storage appliance and control of the persistent memory are transferred from the second storage appliance to the storage appliance following the event.

11. A system for restoring an instance of a storage appliance following an event, the system comprising:
one or more client devices in communication with the storage appliance over a network;
volatile memory storing a state table maintained by the storage appliance, the state table listing the one or more client devices and detailing a state of interaction with the storage appliance for each of the one or more client devices; and
persistent memory in communication with the storage appliance, wherein the storage appliance:
writes, following an indication of the event, state table information for reproducing the state table to the persistent memory;
subsequently stores a completion marker in the persistent memory at each location where the state table information is stored;
confirms that the state table and a second state table correspond to the instance of the storage appliance by matching a timestamp for the completion marker to a corresponding timestamp for the second state table; and
restores, following the event, the state table in the volatile memory from the state table information stored in the persistent memory.

12. The system of claim 11 , wherein the storage appliance deletes the state table information from the persistent memory after the state table is restored in the volatile memory.

13. The system of claim 11 , wherein prior to writing the state table information to the persistent memory, the storage appliance halts any modification to the state table.

14. The system of claim 11 , wherein the storage appliance writes the state table information to the persistent memory after any in-progress requests from the one or more client devices to the storage appliance are completed.

15. The system of claim 11 , wherein the state table information is stored in the persistent memory according to a distributed stable storage path for the state for each of the one or more client devices.

16. A system for restoring an instance of a first storage appliance following an event, the system comprising:
one or more client devices in communication with the first storage appliance over a network;
volatile memory storing a state table maintained by the first storage appliance, the state table listing the one or more client devices and detailing a state of interaction with the first storage appliance for each of the one or more client devices;
persistent memory in communication with the first storage appliance, following an indication of the event, the first storage appliance writing state table information for reproducing the state table to the persistent memory, and following the event, the first storage appliance restoring the state table in the volatile memory from the state table information stored in the persistent memory; and
a second storage appliance in communication with the one or more client devices and the first storage appliance over the network, an Internet Protocol address for the first storage appliance and control of the persistent memory being transferred to a second storage appliance to execute requests from the one or more client devices during the event and being transferred from the second storage appliance to the first storage appliance following the event.

17. The system of claim 16 , wherein the first storage appliance and the second storage appliance are configured as a cluster.

18. The system of claim 16 , wherein the first storage appliance deletes the state table information from the persistent memory after the state table is restored in the volatile memory.

19. The system of claim 16 , wherein prior to writing the state table information to the persistent memory, the first storage appliance halts any modification to the state table.

Assignees

• Oracle Int Corp

Inventors

• Smith Jeffrey Anderson
• Shivam Piyush
• Baker William Eugene

Classifications

• G06F3/0685

  Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays · CPC title

• H04L49/65

  Re-configuration of fast packet switches · CPC title

• G06F2201/805

  Real-time · CPC title

• H04L45/28

  using route fault recovery · CPC title

• G06F2201/84

  Using snapshots, i.e. a logical point-in-time copy of the data · CPC title