Abstract: An apparatus includes an interface and a processor. The interface is configured to communicate with a computing system in which one or more workloads issue storage commands for execution in a storage volume comprising multiple storage blocks. The computing system continually updates a data structure that tracks which of the storage blocks of the storage volume have changed due to the storage commands. The processor is configured, in response to a request to create a copy of the storage volume, to instruct the computing system to (i) create a copy of the data structure and reset the data structure, (ii) create the copy of the storage volume, while continuing to execute the storage commands and update the data structure, and (iii) after the copy of the storage volume is completed, merge the data structure into the copy of the data structure.

Abstract: An apparatus includes an interface and a processor. The interface is configured to communicate with a computing system in which one or more workloads issue storage commands for execution in a storage volume comprising multiple storage blocks. The computing system continually updates a data structure that tracks which of the storage blocks of the storage volume have changed due to the storage commands. The processor is configured, in response to a request to create a copy of the storage volume, to instruct the computing system to (i) create a copy of the data structure and reset the data structure, (ii) create the copy of the storage volume, while continuing to execute the storage commands and update the data structure, and (iii) after the copy of the storage volume is completed, merge the data structure into the copy of the data structure.

Abstract: A system for data storage includes a plurality of servers. Each server includes a respective client interface for communicating with one or more clients, and a respective Storage Area Network (SAN) interface for communicating with a SAN appliance. The servers are configured to (i) create on the SAN appliance a plurality of logical volumes, each logical volume uniquely owned by a respective one of the servers, (ii) receive from the clients storage commands relating to one or more objects, in accordance with an object-storage Application Programming Interface (API), and (iii) in response to the storage commands, maintain the objects in the logical volumes on the SAN appliance using a SAN protocol.

Abstract: Various embodiments for managing data in a data storage having data deduplication. A back reference data structure is configured for user data segments as a mechanism to identify an affected storage block to which information in the back reference data structure refers. The back reference data structure is initialized such that a resolution of the back reference data structure diminishes as a number of the user data segments referencing the affected storage block increases.

Abstract: In a computer storage system, crash dump files are secured without power fencing in a cluster of a plurality of nodes connected to a storage system. Upon an occurrence of a panic of a crashing node and prior to receiving a panic message of the crashing node by a surviving node loading, in the cluster, a capturing node to become active, prior to a totem token being declared lost by the surviving node, for capturing the crash dump files of the crashing node.

Abstract: Data file in the data deduplication system are associated with a file identifier defined to have a first part identifier for denoting a location of the data file in a storage, and a second part identifier for uniquely identifying the data file in the data deduplication system over time.

Abstract: Various embodiments for managing data in a data storage having data deduplication. A back reference data structure is configured for user data segments as a mechanism to identify an affected storage block to which information in the back reference data structure refers. The back reference data structure is initialized such that a resolution of the back reference data structure diminishes as a number of the user data segments referencing the affected storage block increases.

Abstract: A method for data storage includes sending write commands to a first storage node, for storing data in a data volume on the first storage node. In response to a decision to create a copy of the data volume on a second storage node, (i) the write commands are sent both to the first storage node and to the second storage node, and (ii) a snapshot of the data volume is created and sent from the first storage node to the second storage node. The copy of the data volume is created by the second storage node based on the snapshot and on one or more of the write commands received at the second storage node.

Abstract: In a computer storage system, crash dump files are secured without power fencing in a cluster of a plurality of nodes connected to a storage system. Upon an occurrence of a panic of a crashing node and prior to receiving a panic message of the crashing node by a surviving node loading, in the cluster, a capturing node to become active, prior to a totem token being declared lost by the surviving node, for capturing the crash dump files of the crashing node.

Abstract: In a computer storage system, crash dump files are secured without power fencing in a cluster of a plurality of nodes connected to a storage system. Upon an occurrence of a panic of a crashing node and prior to receiving a panic message of the crashing node by a surviving node loading, in the cluster, a capturing node to become active, prior to a totem token being declared lost by the surviving node, for capturing the crash dump files of the crashing node, while restricting the capturing node from gaining access to the storage system for preventing unsynchronized access to the storage system in order to prevent data corruption.

Abstract: A method for data storage includes sending write commands to a first storage node, for storing data in a data volume on the first storage node. In response to a decision to create a copy of the data volume on a second storage node, (i) the write commands are sent both to the first storage node and to the second storage node, and (ii) a snapshot of the data volume is created and sent from the first storage node to the second storage node. The copy of the data volume is created by the second storage node based on the snapshot and on one or more of the write commands received at the second storage node.

Abstract: In a computer storage system, crash dump files are secured without power fencing in a cluster of a plurality of nodes connected to a storage system. Upon an occurrence of a panic of a crashing node and prior to receiving a panic message of the crashing node by a surviving node loading, in the cluster, a capturing node to become active, prior to a totem token being declared lost by the surviving node, for capturing the crash dump files of the crashing node, while restricting the capturing node from gaining access to the storage system for preventing unsynchronized access to the storage system in order to prevent data corruption.

Abstract: In a computer storage system, crash dump files are secured without power fencing in a cluster of a plurality of nodes connected to a storage system. Upon an occurrence of a panic of a crashing node and prior to receiving a panic message of the crashing node by a surviving node loading, in the cluster, a capturing node to become active, prior to a totem token being declared lost by the surviving node, for capturing the crash dump files of the crashing node, while manipulating the surviving node to continue to operate under the assumption the power fencing was performed on the crashing node.

Abstract: In a computer storage system, crash dump files are secured without power fencing in a cluster of a plurality of nodes connected to a storage system. Upon an occurrence of a panic of a crashing node and prior to receiving a panic message of the crashing node by a surviving node loading, in the cluster, a capturing node to become active, prior to a totem token being declared lost by the surviving node, for capturing the crash dump files of the crashing node, while manipulating the surviving node to continue to operate under the assumption the power fencing was performed on the crashing node.

Abstract: Data file in the data deduplication system are associated with a file identifier defined to have a first part identifier for denoting a location of the data file in a storage, and a second part identifier for uniquely identifying the data file in the data deduplication system over time.

Abstract: In a computer storage system, crash dump files are secured without power fencing in a cluster of a plurality of nodes connected to a storage system. Upon an occurrence of a panic of a crashing node and prior to receiving a panic message of the crashing node by a surviving node loading, in the cluster, a capturing node to become active, prior to a totem token being declared lost by the surviving node, for capturing the crash dump files of the crashing node, while manipulating the surviving node to continue to operate under the assumption the power fencing was performed on the crashing node.

Abstract: In a computer storage system, crash dump files are secured without power fencing in a cluster of a plurality of nodes connected to a storage system. Upon an occurrence of a panic of a crashing node and prior to receiving a panic message of the crashing node by a surviving node loading, in the cluster, a capturing node to become active, prior to a totem token being declared lost by the surviving node, for capturing the crash dump files of the crashing node, while manipulating the surviving node to continue to operate under the assumption the power fencing was performed on the crashing node.