Emc IP Holding Company LLC

Dell Products Inc.

Maneesh Singhal

Adarsh Pradhan Jmt

Adnan Sahin

Ajay Potnis

Bharadwaj R Sathavalli

Shampavman Chenjeri Gururajarao

Jharanabala Nayak

Michael E Specht

Gopinath Marappan

Amit Dharmadhikari

Ramrao Patil

Venu Madhava Gunda

For processing nodes of a cluster of a file server, the IO modules associated with the nodes may be required to be part of a same sub-network. A cluster may be configured to ensure that, for each cluster processing node, at least one other cluster processing node is associated with an IO module on a same sub-network as the IO module associated with the cluster processing node. The user may configure a file server to ensure that a primary node and one or more failover nodes of the file server are on a same sub-network. When configuring IO modules, physical ports having similar or same characteristics may be configured to be on a same sub-network. By doing so, and restricting nodes of a file server to being on a same sub-network, a relatively seamless failover between nodes of a file server may be achieved.

Configuring a file server

Storage volumes are pre-provisioned in the operating system of a storage system before they are required to be assigned to an emulation on the storage system. Details of the previously created storage volumes are stored in a management database. If a storage volume is required, the process that needs the storage volume obtains details about a pre-provisioned storage volume from the management database, and instructs the storage system operating system to add the storage volume to a storage group for the process. By pre-provisioning storage volumes in the operating system, it is possible to greatly reduce the amount of time it takes to add storage volumes to processes. The number of storage volumes to be pre-created can be determined based on a regression between the previous storage volume usage and time, and a deterministically obtained value of a number of filesystems that will be created in an upcoming time interval.

Performance efficient and resilient creation of network attached storage objects

Mechanisms and techniques are employed for managing the allocation and load balancing of storage system resources for the containerized, distributed execution of applications on a storage system. A control component executing on a processing component of the storage system may control reserving the necessary resources on one or more processing components to implement an application, and control a container management module to create, deploy and/or modify one or more containers on one or more processing components of the storage system. The one or more containers then may be executed to implement the application. Multiple processing components of the storage system may have a resource management module executing thereon. The control component may exchange communications with the one or more resource management modules of each processing component to determine the resources available within the processing component; e.g., to determine whether the processing component can satisfy the resource requirements of the application.

Managing containers on a data storage system

Techniques for providing client interfaces may include: configuring a plurality of file server applications, wherein each of the plurality of file server applications is associated with a different one of a plurality of virtual network devices, wherein each of the plurality of virtual network devices is bound to a different one of a plurality of unique MAC (media access control) addresses; binding the plurality of virtual network devices to a second network device; and exposing the plurality of virtual network devices directly on a network using the plurality of unique MAC addresses, wherein each of the plurality of virtual network devices exposes an associated one of the plurality of file server applications directly on the network to one or more clients.

Techniques for providing client interfaces

A host device comprises a kernel space comprising a multipath driver component and a user space comprising a container comprising an application, a daemon process and a data structure comprising a plurality of file system entries. The multipath driver component comprises a handler that is configured to detect changes to the file system entries. The host device is configured to mount the data structure to the container and the file system entries are modifiable by the application via the mounting. The multipath driver component is configured to determine that a given file system entry has been modified based at least in part on a detection of a change by the handler and to issue an event to the daemon process. The daemon process is configured to execute an operation associated with the multipath driver in the user space based at least in part on the issued event.

Execution of multipath operation triggered by container application

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

Disaster recovery is provided for Software Defined Network Attached Storage where the data backup is implemented using asynchronous remote data replication. An asynchronous replication facility is created between a primary storage array and a backup storage array. User filesystems being handled by a virtual data mover (VDM) and a configuration filesystem describing the location of the user filesystems on the primary storage array are replicated on the remote data facility to the backup storage array. During failover, all filesystems associated with the asynchronous remote data facility are failed over from a primary storage system associated with the primary storage array to a backup storage system associated with the backup storage array. Where an individual filesystem or individual VDM is to be failed over to the backup storage system, a separate asynchronous replication remote data facility is created to separately replicate data for the aspect to be individually failed over.

Disaster recovery for software defined network attached storage using storage array asynchronous data replication

Disaster recovery is provided for Software Defined Network Attached Storage where the data backup is implemented synchronous data replication. A synchronous replication remote data facility is created between a primary storage array and a backup storage array. User filesystems being handled by a virtual data mover (VDM) and a configuration filesystem describing the location of the user filesystems on the primary storage array are replicated on the remote data facility to the backup storage array. Individual filesystems, individual VDMs, or groups of VDMs may be selectively failed over from the primary storage array to the backup storage array.

Growing community of inventors

Bengaluru, India

Maneesh Singhal