Nutanix, Inc.

Emc IP Holding Company LLC

Pradeep Thomas

Manoj Premanand Naik

Uday Jonnala

Kalpesh Ashok Bafna

Shyamsunder Prayagchand Rathi

Abhishek Rajimwale

Yamini Allu

Pankaj Kumar Sinha

Hemanth Kumar Thummala

Balaji Subramanian

Gaurav Gangalwar

Lakshmana Reddy

Daniel Chilton

Will Strickland

An elastic request handling technique limits a number of threads used to service input/output (I/O) requests of a low-latency I/O workload received by a file system server executing on a cluster having a plurality of nodes deployed in a virtualization environment. The limited number of threads (server threads) is constantly maintained as 'active' and running on virtual central processing units (vCPUs) of a node. The file system server spawns and organizes the active server threads as one or more pools of threads. The server prioritizes the low-latency I/O requests by loading them onto the active threads and allowing the requests to run on those active threads to completion, thereby obviating overhead associated with lock contention and vCPU migration after a context switch (i.e., to avoid rescheduling a thread on a different vCPU after execution of the thread was suspended).

Elastic request handling technique for optimizing workload performance

Examples of file analytics systems are described that may obtain metadata data and events data from a virtualized file server. The file analytics systems may detect one or more events from the events data matching a criteria indicating malicious activity. The file analytics systems may validate the detection of malicious activity. The validation may be performed by comparing the file type, such as the MIME type, of sample files before and after the suspected malicious activity. The systems may recover a share of the distributed file server including the one or more affected files by replacing the one or more affected files with stored versions of the one or more affected files from a snapshot of the share taken prior to the detected malicious activity.

Malicious activity detection, validation, and remediation in virtualized file servers

An example file server manager updates a selected share of a destination distributed file server based on a snapshot of at least a portion of a selected share of a source distributed file server. The selected share of the destination distributed file server is updated while the source distributed file server serves client requests for storage items of the selected share of the source distributed file server. The file server manager receives a request to failover from the source distributed file server to the destination distributed file server and configures the destination distributed file server to service read and write requests for storage items of the selected share of the destination distributed file server. The file server manager further redirects client requests for storage items of the selected share of the source distributed file server to the destination distributed file server by updating active directory information.

Failover and failback of distributed file servers

According to some embodiment, a backup storage system receives, by a first phase of a data deduplication pipeline, a request from a client for reading or writing a data segment associated with a data stream stored in or to a storage system. In response to the request, the system retrieves, by the first phase, load parameters associated with a second phase in the data deduplication pipeline. For each of the load parameters associated with the second phase, the system determines, by the first phase, whether the load parameter has exceeded a load threshold associated with the second phase. The system throttles, by the first phase, performance of a specific job in the data deduplication pipeline by the second phase in response to a determination that at least one of the load parameters associated with the second job phase has exceeded the load threshold associated with the second phase.

Method and system for data deduplication based on load information associated with different phases in a data deduplication pipeline

According to some embodiment, a backup storage system receives a plurality of input/output (IO) requests at the storage system. The IO requests include random IO requests and sequential IO requests. The storage system determines whether there is a pending random IO request from the plurality of IO requests. In response to determining that there is a pending random IO request, the storage system determines whether a total latency of the sequential IO requests exceeds a predicted latency of the pending random IO request. The storage system services the pending random IO request in response to determining that the total latency of the sequential IO requests exceeds the predicted latency of the pending random IO request.

Method and system for input/output (IO) scheduling in a storage system

Growing community of inventors

Santa Clara, CA, United States of America

Pradeep Thomas