Emc IP Holding Company LLC

Emc Corporation

Michael E Specht

Arieh Don

Vinay G Rao

Ian Wigmore

Mark J Halstead

Adnan Sahin

Yaron Dar

Subin George

Steven Goldberg

Douglas Eric LeCrone

Owen Martin

Paul A Linstead

Deepak Vokaliga

Aharon Blitzer

Aviram Katz

Daryl Francis Kinney

David Barta

John S Copley

Vaishali Kochavara

Xuedong Jiang

Sanjib Mallick

Alexandr Veprinsky

Marik Marshak

Dmitry Nikolayevich Tylik

Benjamin W Yoder

Dan Aharoni

Patrick Brian Riordan

Anestis Panidis

Michael Ferrari

Philip E Tamer

Ning Wu

Ajay Potnis

Bhaskar Bora

Alexey Vladimirovich Shusharin

Benjamin Randolph

Robert DeCrescenzo

Mohammed Asher

Maneesh Singhal

Eugene D Pflueger

Daniel A Murphy

Kevin C Heasley

Violet S Beckett

Pei-Ching Hwang

Bharadwaj R Sathavalli

Shampavman Chenjeri Gururajarao

Jeffrey A Lewis

Denis Hall

Michael R Barber

Christopher G LeClair

Andrew Ralich

Raymond Wong

Stewart C Woodworth, Iii

Mona S Tse

A technique for deploying virtual volumes in a metro cluster across first and second arrays includes impersonating a third array that purports to host single-site virtual volumes. The technique further includes mapping the single-site virtual volumes purportedly hosted by the third array to respective pairs of actual virtual volumes. Each pair includes a first virtual volume in the first array and a second virtual volume in the second array and realizes a stretched virtual volume, with writes being mirrored between the virtual volumes of each pair.

Metro cluster for virtual volumes

Embodiments of the present disclosure relate to load balancing application processing between storage platforms. Input/output (I/O) workloads can be anticipated during one or more time-windows. Each I/O workload can comprise one or more I/O operations corresponding to one or more applications. Processing I/O operations of each application can be dynamically migrated to one or more storage platforms of a plurality of storage platforms based on the anticipated workload.

Dynamic application migration across storage platforms

Snapshots are created on replicated storage systems Rand Rin a manner resulting in identical snapshots being generated on Rand R. In response to an instruction to create a snapshot on a storage system (Rand/or R), command-phase write operations (CWOs) are held and data-phase write operations (DWOs) are completed on the storage system before the snapshot is created. Determining that DWOs includes querying processes, and using information, available on the storage system, by which a state of a write operation&#x2014;e.g., whether the write operation is a DWO and when the DWO completes&#x2014;may be determined. A CWO queue may be maintained on the storage system for tracking the status of CWOs. A DWO queue may be maintained on the storage system for tracking DWOs, to determine DWOs when the snapshot is created, and track their processing, including when they are completed.

Creating indentical snapshots

Maintaining consistency for asynchronous replication of LUNs of a local storage system to corresponding LUNs of a remote storage system includes copying application data written to LUNs to cache slots, copying metadata of LUNs to cache slots, associating a first sequence number to all metadata modifications and all application data writes that are begun after a first time and before a second time, associating a second sequence number, different from the first sequence number, to all metadata modifications and all application data writes that are begun after the second time, and, after completion of all metadata modifications and all application data writes associated with the first sequence number, initiating transfer to the remote storage system of all metadata modifications and all application data writes associated with the first sequence number. Each cache slot may include a field that indicates a corresponding sequence number.

Maintaining consistency of asynchronous replication

The described technology is generally directed towards adaptively tuning storage systems. According to an embodiment, a system can comprise a processor and computer executable components that can comprise an interval determiner to determine a polling interval based on an estimate of a workload of a shared data store on a data storage array, based on a change activity detected by the system. Further, a host controller can receive transactions from a host application, wherein the transactions perform one or more of updating the local data store, or querying the local data store for results, and a daemon process that, at the polling interval, performs one or more of, polling the data storage array for updates to the local data store based on the shared data store, or updating the shared data store based on the local data store.

Adaptively tuning polling intervals of control hosts in distributed storage systems

A storage entity of the data storage system may be visible to the host over a first path and a second path. The first path may operate in accordance with a first protocol and the second path may operate in accordance with a second different protocol. The storage entity may have a first protocol level personality and identity when presented to the host over the first path and a second protocol level personality and identity when presented to the host over the second path. A first native identifier associated of the storage entity on the first path and a second native identifier of the storage entity on the second path may be used to determine that the same storage entity is visible over the first and second paths even though the storage entity may have different protocol level identifiers on the first and second paths that operate using different protocols.

Storage device protocol dual personality

Combinations of host ports and storage ports (e.g., I-T pairs) on a storage network that are zoned but not masked may be determined, without accessing a switch or network administrator. Heartbeat communications (heartbeats) may be transmitted from host systems to each storage device of a storage system of which the host system is aware, along the one or more I/O paths of which the host is aware to the storage port of the I/O path. The storage devices may include one or more nominal devices defined for I-T pairs for which I/O connectivity has not been defined for any storage devices. The storage system may maintain a master heartbeat (heartbeat) table that may include a plurality of entries, each entry corresponding to a combination of a host port, storage port and storage device, and storing a time stamp value for a most recent heartbeat received for the combination.

Determining zoned but inactive I/O paths

Automated port selection for data migration includes an algorithm that selects a set of SAN ports with the following properties: the selected ports have the least port utilization among all possible port selections; the number of independent data paths between the selected ports is no smaller than a user configurable minimum number; and the difference between the aggregate bandwidth of the ports on both arrays is minimized.

Optimal port selection for data migration

Software Defined Network Attached Storage data backup is implemented using storage array synchronous data replication. A TLU is created for each user filesystem managed by a Virtual Data Mover (VDM). A VDM configuration filesystem is also created containing metadata describing a mapping of user file system TLU to physical storage resources on the storage array. Both the user filesystem TLUs and the VDM configuration filesystem are mapped to an asynchronous Remote Data Forwarding (RDF) group of the storage array, which is used by the storage array to replicate both the user filesystem TLUs and VDM configuration filesystem. Filesystem ID and export path information are reserved on the primary storage array and backup storage array when the RDF group is set up, to enable transparent failover from the primary to the backup node of selected VDMs.

Software defined network attached storage backup using storage array synchronous or asynchronous data replication

Techniques for performing data migration may include: receiving host information regarding hosts registered on a source data storage system; issuing registration commands from a host to a target data storage system; determining, at the target data storage system in accordance with the registration commands, a host registration table including a corresponding entry for the host, the corresponding entry denoting a host name for the host and initiators of the host that sent the registration commands; and determining a masking view for the host on the target data storage system, the masking view including an initiator group of the initiators of the host that sent the registration commands to the target data storage system, wherein the masking view is used by the target data storage system to determine whether to service received I/O operations.

Data migration techniques

In a data storage system in which a first storage array and a second storage array maintain first and second replicas of a production volume, the replicas are made discoverable and accessible while inconsistent. Each storage array maintains an invalid track list of inconsistencies. Initially, all tracks are marked as invalid. While background synchronization is eliminating inconsistencies, accesses to invalid tracks are resolved by exchanging data associated with IOs and updating the invalid track lists based on IO bias and other factors.

Instant-ready active-active storage nodes

Techniques and mechanisms for establishing and implementing performance objectives for an application based at least in part on a workload type of the application. A system includes a storage system on which an application imposes a workload by utilizing storage resources of the storage system, and a performance level has been associated with the application. A workload type is associated with the application based on the type of workload, and a performance objective is determined for the application based on the performance level and the workload type of the application. The storage resources are manipulated to achieve the performance objective.

Application-specific workload-based I/O performance management

A system, computer program product, and computer-executable method, including creating a production Logical Unit (LU) and one or more snapshots of the production LU on a data storage system, wherein the data storage system provides an interface to the production LU and each of the one or more snapshots, receiving an I/O request at the interface to the production LU, analyzing the received I/O request to determine whether a code is embedded in the received I/O request, and processing the received I/O request based on the code, wherein the received I/O request is enabled to be sent to the production LU or a first snapshot of the one or more snapshots based on the code.

Accessing multiple data snapshots via one access point

Techniques are described providing secure authentication of control commands executed on a data storage system. A pass code may be generated in accordance with criteria in response to successful two-factor authentication of a user identifier. Providing a valid generated passcode may be required with a control command in order for a data storage system to execute the control command. The control command may be one of a subset of possible control command that may be performed with respect to storage entities, such as logical devices and snapshots thereof. In another embodiment, rather than providing a pass code, the two factor authentication information and user identifier may be provided with the control command whereby successful completion of two-factor authentication of the user identifier and two factor authentication information may be required in order to execute the control command.

Securing storage control path against unauthorized access

Masking information may be automatically determined for a host after zoning between the host and data storage system is complete. Processing may include the host sending host registration commands from host initiators. From registration information provided with the host registration commands, an initiator group may be determined for the masking view as including the initiators identified as belonging to the host. A port group may be determined as those target ports at which the host registration commands are received. A default storage group with a default device may be created. A masking view for the host may be created that includes the initiator group, the target port group and the default storage group whereby the masking view indicates that the first device is accessible or exposed, through each target port of the target port group, to each initiator of the initiator group.

Automated configuration of host connectivity

Growing community of inventors

Bolton, MA, United States of America

Michael E Specht