Network storage failover systems and associated methods

A non-transitory machine readable medium having stored thereon instructions comprising machine executable code which when executed by a machine, causes the machine to:

• generate a metadata data structure before starting a replay of entries of a log stored in a non-volatile memory of a second storage node for a failover operation, initiated in response to a failure at a first storage node, the second storage node operating as a partner node of the first storage node to mirror at the non-volatile memory, one or more write requests and data associated with the one or more write requests received by the first storage node prior to the failure, wherein the metadata structure stores a metadata attribute of each data container associated with each log entry;
• persistently store, prior to the replay, the metadata attribute from the metadata structure;
• utilize the persistently stored metadata attribute to respond to a read request received during the replay by the second storage node;
• and
• utilize a write request metadata attribute for executing a write request received during the replay by the second storage node.

A system, comprising:

• a memory containing machine readable medium comprising machine executable code having stored thereon instructions;
• and a processor coupled to the memory, the processor configured to execute the machine executable code to:
• generate a metadata data structure before starting a replay of entries of a log stored in a non-volatile memory of a second storage node for a failover operation, initiated in response to a failure at a first storage node, the second storage node operating as a partner node of the first storage node to mirror at the non-volatile memory, one or more write requests and data associated with the one or more write requests received by the first storage node prior to the failure, wherein the metadata structure stores a metadata attribute of each data container associated with each log entry;
• persistently store, prior to the replay, the metadata attribute from the metadata structure;
• utilize the persistently stored metadata attribute to respond to a read request received during the replay by the second storage node;
• and
• utilize a write request metadata attribute for executing a write request received during the replay by the second storage node.