Abstract: Systems and methods that result in a stable storage system are provided. In the storage system, the latency spikes may be reduced when multiple volumes are aggregated into transfer sets according to system characteristics. The storage system transfers ownership of volumes in each transfer set as a single transaction. In the storage system, connectivity between the host and the storage controller is re-established based on the connectivity in a physical transport layer and a single path. In the storage system, pre-mature failback is also avoided when ownership of volumes is transferred back to a preferred storage controller when the same number of paths existed between the host and the preferred storage controller before and after a failover operation. Further, the storage system generates connectivity reports that display connectivity paths between hosts, storage controllers, and volumes.

Abstract: Systems and methods that select a cache flushing algorithm are provided. A stripe that spans multiple storage devices and includes a plurality of segments is provided. The stripe also includes dirty data stored in a picket-fence pattern in at least a subset of segments in the plurality of segments. A memory cache that stores data separately from the plurality of storage devices and a metadata cache that stores metadata associated with the dirty data are also provided. A cache flushing algorithm is selected using the metadata. The selected cache flushing algorithm flushes data from the memory cache to the stripe.

Abstract: Systems and methods that result in a stable storage system are provided. In the storage system, the latency spikes may be reduced when multiple volumes are aggregated into transfer sets according to system characteristics. The storage system transfers ownership of volumes in each transfer set as a single transaction. In the storage system, connectivity between the host and the storage controller is re-established based on the connectivity in a physical transport layer and a single path. In the storage system, pre-mature failback is also avoided when ownership of volumes is transferred back to a preferred storage controller when the same number of paths existed between the host and the preferred storage controller before and after a failover operation. Further, the storage system generates connectivity reports that display connectivity paths between hosts, storage controllers, and volumes.

Abstract: Systems and methods that result in a stable storage system are provided. In the storage system, the latency spikes may be reduced when multiple volumes are aggregated into transfer sets according to system characteristics. The storage system transfers ownership of volumes in each transfer set as a single transaction. In the storage system, connectivity between the host and the storage controller is re-established based on the connectivity in a physical transport layer and a single path. In the storage system, pre-mature failback is also avoided when ownership of volumes is transferred back to a preferred storage controller when the same number of paths existed between the host and the preferred storage controller before and after a failover operation. Further, the storage system generates connectivity reports that display connectivity paths between hosts, storage controllers, and volumes.

Abstract: Systems and methods that select a cache flushing algorithm are provided. A stripe that spans multiple storage devices and includes a plurality of segments is provided. The stripe also includes dirty data stored in a picket-fence pattern in at least a subset of segments in the plurality of segments. A memory cache that stores data separately from the plurality of storage devices and a metadata cache that stores metadata associated with the dirty data are also provided. A cache flushing algorithm is selected using the metadata. The selected cache flushing algorithm flushes data from the memory cache to the stripe.

Abstract: Systems and methods that result in a stable storage system are provided. In the storage system, the latency spikes may be reduced when multiple volumes are aggregated into transfer sets according to system characteristics. The storage system transfers ownership of volumes in each transfer set as a single transaction. In the storage system, connectivity between the host and the storage controller is re-established based on the connectivity in a physical transport layer and a single path. In the storage system, pre-mature failback is also avoided when ownership of volumes is transferred back to a preferred storage controller when the same number of paths existed between the host and the preferred storage controller before and after a failover operation. Further, the storage system generates connectivity reports that display connectivity paths between hosts, storage controllers, and volumes.

Abstract: A system and method for connectivity-aware assignment of volumes among the storage controllers of a storage system is provided. In some embodiments, during a discovery phase, a connectivity metric is determined from a device discovery command. The connectivity metric is recorded into a data structure that identifies a plurality of hosts and a plurality of storage controllers of a storage system. In response to the determining of the connectivity metric, a storage controller ownership of a first volume is changed to improve connectivity between a host of the plurality of hosts and the first volume. In some such embodiments, a storage controller ownership of a second volume is changed to balance load among the plurality of storage controllers, and the discovery phase is, in part, a response to the change in the storage controller ownership of the second volume.

Abstract: Disclosed are a method and a simplex array controller device that synchronize firmware revisions between an original, native, storage array controller in a single controller storage array system (i.e., a simplex array controller) and a replacement storage array controller that replaces the original, native, storage array controller. An embodiment may create and store an original firmware code image containing a copy of the firmware revision information running on an original simplex array controller along with controller and firmware revision identification off-board of the original array controller on a firmware repository storage device. The firmware repository storage device may be one of the storage devices selected from the array of storage devices controlled by the original array controller.

Abstract: Disclosed are a method and a simplex array controller device that synchronize firmware revisions between an original, native, storage array controller in a single controller storage array system (i.e., a simplex array controller) and a replacement storage array controller that replaces the original, native, storage array controller. An embodiment may create and store an original firmware code image containing a copy of the firmware revision information running on an original simplex array controller along with controller and firmware revision identification off-board of the original array controller on a firmware repository storage device. The firmware repository storage device may be one of the storage devices selected from the array of storage devices controlled by the original array controller.

Abstract: The present invention is directed to a system and method for disabling and recreating a snapshot volume. A method of disabling repository volume activity corresponding to a point-in-time image and retaining repository volume attributes may include initiating a command in a electronic data storage system. The command disables copy-on-write activity to a repository volume created in relation to a first point-in-time image of a base volume, in which repository volume attributes are retained suitable for providing a repository volume corresponding to a second point-in-time image. A method of creating a point-in-time image of a base volume may include initiating a command to create a second point-in-time image of a base volume. The second point-in-time image is created utilizing a repository volume having attributes retained from a repository volume created previously with respect to a first point-in-time image.

Abstract: The present invention is directed to a system and method for disabling and recreating a snapshot volume. A method of disabling repository volume activity corresponding to a point-in-time image and retaining repository volume attributes may include initiating a command in a electronic data storage system. The command disables copy-on-write activity to a repository volume created in relation to a first point-in-time image of a base volume, in which repository volume attributes are retained suitable for providing a repository volume corresponding to a second point-in-time image. A method of creating a point-in-time image of a base volume may include initiating a command to create a second point-in-time image of a base volume. The second point-in-time image is created utilizing a repository volume having attributes retained from a repository volume created previously with respect to a first point-in-time image.