Mukesh G Gupta, 48Shrewsbury, MA

2022022, Jul 21, 2022

Jan 21, 2021

17/154027

- Hopkinton MA, US
David L. Black - Acton MA, US
Marina Shem Tov - Hod Hasharon, IL
Mukesh Gupta - Shrewsbury MA, US

G06F 3/06

A command is received from a host regarding accessing an NVMe dispersed namespace in a metro cluster configuration of storage arrays. A namespace group state corresponding to the host and the port is determined and returned to the host. The namespace group state indicates whether the specific communication path between the host and the port is optimized or non-optimized. The namespace group state indicates that the communication path is non-optimized where the host is not located at the same location as the storage array, and that the communication path is optimized where the host is located at the same location as the storage array and the node of the storage array is a preferred node for processing I/O directed to the NVMe dispersed namespace from hosts located in the same location as the storage array.

2022022, Jul 21, 2022

Jan 21, 2021

17/154000

- Hopkinton MA, US
Dmitry Nikolayevich Tylik - Westborough MA, US
Alexey Vladimirovich Shusharin - Saint Petersburg, RU
Marina Shem Tov - Hod Hasharon, IL
Mukesh Gupta - Shrewsbury MA, US

G06F 3/06
G06F 9/455

Discovery service contact information is provided from a data storage system to administration logic of a virtualization environment, and distributed within the virtualization environment to hypervisor hosts, enabling the hypervisor hosts to discover logical ports within the data storage system, and then establish logical communication paths between the hypervisor hosts and the ports. In response to determining that the data storage system supports virtual volumes, the hypervisor hosts indicate hypervisor capability of using virtual volumes to the data storage system, and the data storage system exposes virtual volumes to hypervisors in response to indications of the ability of those hypervisors to use virtual volumes.

2021028, Sep 16, 2021

Mar 13, 2020

16/817726

- Hopkinton MA, US
Mukesh Gupta - Shrewsbury MA, US
Sathya Krishna Murthy - Morrisville NC, US
Marina Shem Tov - Hod Hasharon, IL
Chen Reichback - Tel Aviv, IL

G06F 3/06
G06F 11/20
G06F 11/14

Migrating a source volume from a source appliance to a destination appliance, wherein the source volume is assigned to an asymmetric namespace access (ANA) group and initially exposed to a host computer as accessible at the source appliance, includes creating a destination volume on the destination appliance and expanding the ANA group to include the destination volume, with the ANA group initially exposing the destination volume as inaccessible to the host computer at the destination appliance. Subsequently, the destination volume is synchronized to the source volume and then a cutover is performed that includes (i) copying volume metadata including host reservations from the source volume to the destination volume, and (ii) changing the ANA group to expose the source volume as inaccessible at the source appliance and the destination volume as accessible at the destination appliance.

2021013, May 6, 2021

Nov 1, 2019

16/672088

- Hopkinton MA, US
Mukesh Gupta - Shrewsbury MA, US
David L. Black - Acton MA, US

G06F 3/06
G06F 9/455

A method, computer program product, and computing system for defining a vVol NVMe subsystem for a plurality of vVol NVMe namespaces within a storage system; and enabling an Asymmetric Namespace Access (ANA) group that aggregates two or more vVol NVMe namespaces defined within the plurality of vVol NVMe namespaces and communicates ANA group information in-band, thus eliminating the need for out-of-band communication of vVol protocol endpoint information.

2017004, Feb 9, 2017

Mar 30, 2015

15/024250

- Hopkinton MA, US
Vasiliy Mihailovich Tolstoy - St. Petersburg, RU
Sergey Alexandrovich Kovalev - St. Petersburg, RU
Arthur O. Harris - Framingham MA, US
Mukesh Gupta - Shrewsbury MA, US

H04L 29/12
H04L 29/08

Improved techniques of running multitenant applications involve opening sockets in multiple network namespaces through which respective tenants may access a monolithic application thread. A server running such an application may assign tenants network bandwidth through one or more network namespaces. Each network namespace has its own independent set of network addresses that may overlap or even be identical to another namespace's set of network addresses. The server may then identify a request to access application data with a particular tenant by network identifiers such as virtual local area network (VLAN) identifiers attached to the request. Thus, even though two established sockets may include identical source and destination addresses, data may be exchanged between the server and the intended tenants.