Abstract:
In one aspect, a method includes splitting empty RAID stripes into sub-stripes and storing pages into the sub-stripes based on a compressibility score. In another aspect, a method includes reading pages from 1-stripes, storing compressed data in a temporary location, reading multiple stripes, determining compressibility score for each stripe and filling stripes based on the compressibility score. In a further aspect, a method includes scanning a dirty queue in a system cache, compressing pages ready for destaging, combining compressed pages in to one aggregated page, writing one aggregated page to one stripe and storing pages with same compressibility score in a stripe.
Abstract:
Described embodiments provide systems and processes for performing data migration in a storage system. One or more volumes are migrated from a source device to a target device in a storage system. A discovery state of the migrated volumes is determined by one or more host devices in communication with the storage system. An initiator group is configured for each host device. Each initiator group sends at least one inquiry to each of one or more volumes of the target devices. Responses to each inquiry from each volume are tracked. The system receives a selection of one or more migrated volumes to include in a cutover operation, the selection based at least in part upon the determined discovery states. One or more volumes of the source devices associated with the included volumes are deactivated.
Abstract:
In one aspect, a method includes sending a short hash handle from a production site to a replication site, the short hash handle being generated using a hash signature and being smaller than the hash signature, determining at the replication site whether the short hash handle exists at the replication, reading and sending the hash signature associated with the short hash handle if the short hash handle exists at the replication site, determining at the replication site whether the hash signature exists at the replication and emulating a write operation by associating the hash signature to an address in a second storage volume at the replication site if the hash signature exists at the replication site. The hash signature is generated using a data block from a first storage volume at the production site.
Abstract:
Described embodiments may provide systems and processes for migrating a replica hierarchy from at least one source device to at least one target device in a storage system. A configuration of the replica hierarchy is migrated, one or more internal nodes of the replica hierarchy are migrated, and one or more leaf nodes of the replica hierarchy are migrated. A cutover operation is performed by deactivating the at least one source device associated with the included replica hierarchy.
Abstract:
Described embodiments provide systems and processes for performing data migration in a storage system. One or more consistency groups are migrated from at least one source device to at least one target device in the storage system. The consistency groups are replicated from the source device to the target device by an asynchronous data replication operation from the source device to the target device and one or more synchronous data replication operations from the source device to the target device if data stored on the source device is changed. The consistency groups are operated on the source device and the target device in an active-active mode, wherein the source device and target device are active and accessible by host devices. Replicated consistency groups are determined to include in a cutover operation that is performed by deactivating the at least one source device associated with the included consistency groups.
Abstract:
In one aspect, a method includes sending a first short hash handle and a first identity bit associated with the first short hash handle to a replication site, determining if a second hash handle is identical to the first short hash handle, determining if a second identity bit associated with the second short hash handle at the replication is set if the second short hash handle is identical to the first short hash handle and using the second hash handle to identify the data if the second identity bit being is set. The first short hash handle is an identifier of data stored on a disk.
Abstract:
In one aspect, a method includes assigning a base key to a storage array, assigning a volume auxiliary key to each volume in the storage array, for each volume in the storage array that is encrypted, encrypting every block of a backend using the base key and one of a full hash auxiliary key or a short hash handle auxiliary key and for each volume in the storage array that is encrypted, encrypting an address-to-hash table of a volume using the base key and the volume auxiliary key.
Abstract:
In one aspect, a method includes receiving notification that a volume in a plurality of volumes has failed, determining a smallest consistency group with a replication trigger point designation using a hierarchical volume tree that includes the failed volume, stopping replication of volumes in a first consistency group if it is determined that the first consistency group is the smallest consistency group with a replication trigger point that includes the failed volume and stopping replication of the plurality of volumes if it is not determined which is the smallest consistency group with a replication trigger point that includes the failed volume.