Patent Grant
12164383
Disaster recovery for distributed file servers often includes obtaining snapshots of a distributed file server. When a disaster occurs, failover (e.g., to a backup site) may take hours or longer to configure the file server at the backup site from the snapshots.
An example computer readable medium disclosed herein is encoded with instructions which, when executed, cause a system to perform operations including updating 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, where the selected share of the destination distributed corresponds to the selected share of the source distributed file server, where 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 operations further include receiving a request to failover from the source distributed file server to the destination distributed file server and configuring the destination distributed file server to service read and write requests for storage items of the selected share of the destination distributed file server, where the configuring is responsive to the request to failover from the source distributed file server to the destination distributed file server. The operations further include redirecting 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 for the source distributed file server to reference the destination distributed file server.
An example file server manager disclosed herein includes one or more processors and memory storing instructions which, when executed by the one or more processors, cause the file server manager to perform operations including updating 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, where the selected share of the destination distributed corresponds to the selected share of the source distributed file server, where 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 operations further include receiving a request to failover from the source distributed file server to the destination distributed file server and configuring the destination distributed file server to service read and write requests for storage items of the selected share of the destination distributed file server, where the configuring is responsive to the request to failover from the source distributed file server to the destination distributed file server. The operations further include redirecting 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 for the source distributed file server to reference the destination distributed file server.
An example method disclosed herein includes updating 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, where the selected share of the destination distributed corresponds to the selected share of the source distributed file server, where 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 method further includes receiving a request to failover from the source distributed file server to the destination distributed file server and configuring the destination distributed file server to service read and write requests for storage items of the selected share of the destination distributed file server, where the configuring is responsive to the request to failover from the source distributed file server to the destination distributed file server. The method further includes redirecting 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 for the source distributed file server to reference the destination distributed file server.
Additional embodiments and features are set forth in part in the description that follows, and will become apparent to those skilled in the art upon examination of the specification and may be learned by the practice of the disclosed subject matter. A further understanding of the nature and advantages of the present disclosure may be realized by reference to the remaining portions of the specification and the drawings, which form a part of this disclosure. One of skill in the art will understand that each of the various aspects and features of the disclosure may advantageously be used separately in some instances, or in combination with other aspects and features of the disclosure in other instances.
The description will be more fully understood with reference to the following figures in which components are not drawn to scale, which are presented as various examples of the present disclosure and should not be construed as a complete recitation of the scope of the disclosure, characterized in that:
Various embodiments of the present disclosure will be explained below in detail with reference to the accompanying drawings. Other embodiments may be utilized, and structural, logical and electrical changes may be made without departing from the scope of the present disclosure.
Certain details are set forth herein to provide an understanding of described embodiments of technology. However, other examples may be practiced without various of these particular details. In some instances, well-known computing system components, virtualization operations, and/or software operations have not been shown in detail in order to avoid unnecessarily obscuring the described embodiments. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here.
Examples described herein include file server managers which may manage multiple virtualized file servers. The multiple virtualized file servers managed by a file server manager may be hosted by multiple computing node clusters (e.g., in multiple virtualization environments). The file server manager may be in communication with each of the multiple virtualized file servers. In this manner, a file server manager may provide a single pane of glass management interface to help manage and orchestrate file platform and service specific operations from a single location (e.g., a single logon and/or single user interface). File server managers may accordingly implement policies and conduct other operations based on data from multiple virtualized file servers in communication with the file server manager.
In various examples described herein, file server managers may be used to configure and manage share based replication of one or more virtualized file servers. For example, the file server manager may be configurable to select shares from a source virtualized file server to be replicated to a destination virtualized file server. The file server manager may further include replication policies controlling various aspects of share based replication. In some examples, file server managers may implement active-active share based replication, such that a backed-up virtualized file server (e.g., a destination virtualized file server) may be accessed and utilized relatively quickly upon failure of a primary virtualized file server (e.g., a source virtualized file server). The file server manager may also, in some embodiments, implement fail-back to a source virtualized file server after a fail-over to a destination file server. File server managers may accordingly implement share based replication and/or backup of a virtualized file server.
Various examples of share based replication and file server level disaster recovery may provide a short recovery time, allowing for continuous availability of data after fail over to a recovery site. For example, configuration of active directory and domain name system entries may facilitate client access redirection from a failed file server to a backup file server after fail over. In the event of a planned or unplanned loss of service at a file server, corresponding shares at a backup or standby file server may be activated, and client connection requests for the file server may be redirected to the backup file server by updating address information for the file server at an active directory server or a domain name server. Accordingly, failover may occur quickly and with few noticeable changes to clients connecting to the backup file server.
The components shown in
Examples of systems described herein may accordingly include one or more virtualized file servers, such as virtualized file server 106, virtualized file server 114, and virtualized file server 122 in
A virtualized file server may include a cluster of virtual machines and/or other virtualized entities (e.g., containers), which may be referred to as file server virtual machines (FSVMs). In some examples, each of the file server virtual machines of a cluster may be implemented on different computing nodes forming a computing node cluster. For example, the FSVM 108, FSVM 110, and FSVM 112 of virtualized file server 106 may each be implemented on separate computing nodes of a computing node cluster used by the virtualized file server 106. Similarly, the FSVM 116, FSVM 118, and FSVM 120 may each be implemented on separate computing nodes of a computing node cluster used by the virtualized file server 114. Similarly, the FSVM 124, FSVM 126, and FSVM 128 may each be implemented on separate computing nodes of a computing nodes cluster. In some examples, a cluster of FSVMs may be implemented on a cloud computing system.
The FSVMs may operate to provide a file system on the storage resources of the virtualized file server. The file system may have a single namespace and may store data in accordance with filenames and/or directories. The FSVMs may accordingly support one or more file system protocols, such as NFS and/or SMB. A virtualized file server (such as virtualized file server 106, virtualized file server 114, and/or virtualized file server 122) may translate file system protocol requests for one or more files and/or directories (e.g., a file path) into one or more storage requests to access the data corresponding to the file, directory, and/or file path. Any of a variety of components of the virtualized file server may be used to perform the translation (e.g., one or more FSVMs, one or more hypervisors, and/or one or more storage controllers). The translation may be performed using a map (e.g., a shard map) relating the location of the data to the file name, share, directory, and/or file path.
Virtualized file servers described herein may include virtualized storage. For example, the virtualized file server 106 may include virtualized storage 130. The virtualized file server 114 may include virtualized storage 132. The virtualized file server 122 may include virtualized storage 134. The virtualized storage may generally include any number or kind of storage devices—for example, network attached storage, local storage of one or more computing nodes forming the virtualized file server, and/or cloud storage. Storage devices may be implemented using, for example one or more memories, hard disk drives, solid state drives. The virtualized storage for a particular virtualized file server may be referred to as a storage pool. The virtualized storage may store one or more shares. Generally, the virtualized storage may refer to a storage pool which may include any of a variety of storage devices. In some examples, the virtualized file server(s) may be implemented in a hyperconverged architecture. For example, the storage pool may include local storage devices of the computing nodes used to host the virtualized file server. For example, virtualized storage 130 may include a storage pool. One or more shares of a file system provided by the virtualized file server 106 may be distributed across storage device of the storage pool, including local storage devices of one or more computing nodes on which the FSVM 108, FSVM 110, and/or FSVM 112 reside. In some examples, each file server virtual machine (FSVM) may manage (e.g., host) a corresponding share or portion of a share. A map may store associations between shares and files, directories, and/or file paths.
Virtualized file servers described herein may include metadata. For example, virtualized file server 106 may include metadata 138. The virtualized file server 114 may include metadata 140. The virtualized file server 122 may include metadata 142. The metadata may be stored, for example, in the virtualized storage and/or other storage location accessible to the virtualized file server. The metadata may in some examples be distributed across the storage pool of a virtualized file server. In some examples, the metadata may be stored in a database accessible to and/or hosted by the virtualized file server. Metadata stored by a virtualized file server may include, for example, authentication information for the virtualized file server and/or virtual machines in the virtualized file server, authorization information for the virtualized file server and/or virtual machines in the virtualized file server, configuration information for the virtualized file server and/or virtual machines in the virtualized file server, end point information (e.g., supported API calls and/or endpoints), a number of shares stored in the virtualized storage of the virtualized file server, a protocol supported by each share and/or FSVM (e.g., NFS and/or SMB), identities of the shares stored in the virtualized storage of the virtualized file server, a number of file server virtual machines (FSVMs) present in the virtualized file server, a number of files and/or directories hosted by the virtualized file server, compute resources available and/or used at the virtualized file server, storage resources available and/or used at the virtualized file server, or other metadata regarding the virtualized file server. The metadata may be maintained by the virtualized file server, for example, the metadata may be updated as the number of shares, FSVMs, storage resources and/or compute resources change.
Examples described herein may include a file server manager, such as file server manager 102 of
File server managers, such as file server manager 102 of
Examples of file server managers described herein may provide one or more user interfaces, such as user interface 104 of
Examples of file server managers described herein may store registration information, such as registration information 144 of
Examples of file server managers described herein may include metadata, such as metadata 136. The metadata may be synchronized to the metadata of multiple virtualized file servers in communication with the file server manager. For example, the metadata 136 may be synchronized with metadata 138, metadata 140, and metadata 142. For example, the metadata 136 at any given time may include metadata 138, metadata 140, and metadata 142. Synchronization may be maintained over time—the metadata of multiple virtualized file servers may periodically (e.g., at regular and/or irregular intervals) synchronize with the metadata store of the file server manager. In this manner, the file server manager 102 may maintain an updated storage of metadata associated with each of virtualized file server 106, virtualized file server 114, and virtualized file server 122. The metadata may be accessed by the file server manager and used to manage, communicate with, and/or otherwise interact with the virtualized file servers.
While the metadata 136 and registration information 144 are depicted separately in
During operation, a file server manager described herein may register, such as by receiving a registration for, one or more virtualized file servers. For example, a virtualized file server (e.g., using an FSVM, a hypervisor, and/or another component of the virtualized file server), may transmit a registration (e.g., registration information) to the file server manager. In some examples, the file server manager may request such a registration by transmitting a request to register to the virtualized file server. In some examples, such as when the file server manager is hosted on a cluster and/or within a same system as the virtualized file server, an automatic registration may occur. For example, the registration process may include determining (e.g., from one or more IP addresses used), that a virtualized file server is hosted on a same domain as a file server manager. In other examples, virtualized file servers which are not hosted on a same domain as a file server manager may nonetheless register with the file server manager. In the example of
The file server manager may synchronize metadata of registered file servers such that up to date metadata of the registered file server may be accessible to the file server manager. For example, the metadata 136 may synchronize with metadata 138, metadata 140, and metadata 142 of
During operation, file server managers described herein, such as file server manager 102 of
The file server manager may format the received management request for the virtualization environment (e.g., virtualization platform) used to host the requested virtualized file server. For example, the file server manager may access the registration information 144 to identify a virtualization environment for a virtualized file server identified in the management request. The management request may then be formatted in a manner used by the virtualized environment. In some examples, the formatted management request may be implemented as an API call, with the API call specific to the virtualization environment of the target virtualized file server. In this manner, clients or other users providing management requests to the file server manager may not require knowledge of the virtualized environment hosting the virtualized file server. The file server manager may format the request in the manner used to communicate with the appropriate virtualization environment. This may provide flexibility in system design and usage, as multiple virtualization environments may be used, and virtualized file servers may in some examples be relocated from one virtualized environment to another without a need to update management requests being provided to the file server manager. Instead, an updated identification of the virtualized environment may be stored in registration information 144 and/or metadata 136.
During operation, the file server manager may utilize information from the registration to implement the management request. For example, access credentials provided during registration may be used to access one or more FSVMs and/or other components of the virtualized file server (e.g., hypervisor, other virtual machine(s) and/or container(s)) and implement the management request. In some examples, the management request may be provided to a particular FSVM. In some examples, the management request may be provided to an FSVM of the virtualized file server that is designated as a leader, and the leader FSVM may communicate the management request to an appropriate FSVM of the virtualized file server.
In some examples, file server managers described herein, such as file server manager 102 of
The method depicted by flowchart 200 may be implemented by file server managers described herein, such as by file server manager 102 of
In block 202, an API call 202 may be received, which may also be referred to as a management request. The API call 202 may be implemented, for example, using a REST API. The API call 202 may be received from an administrator (e.g., using an interface to a file server manager, such as user interface 104 of
The file server manager may evaluate the management request received, e.g., API call 202. For example, the file server manager 102 may receive API call 202 and may evaluate it to determine how to direct the API call. The management request may be evaluated to determine its intended destination. For example, the file server manager 102 may evaluate a management request to determine if it is files service specific (e.g., in block 204), if it is directed toward a files platform (e.g., block 206), and/or if it is a UI request (e.g., block 208). The evaluation may be based, for example, on identifying that the content of the request pertains to files services, files platform, and/or UI. The evaluation may be based, for example, on identifying a destination of the request.
If the management request (e.g., API call 202) is determined to be a files service specific request in block 204, the request may be redirected to the appropriate virtualized file server in block 210. Examples of files service specific requests include requests to create a share, create or revise one or more user quotas for the virtualized file server, monitor a number of users connected to a virtualized file server, or blocking one or more particular users of the virtualized file server. Files service specific requests may not need to be translated for the particular virtualization platform of the virtualized file server, because in some examples they may requests which are received and/or processed by one or more file server virtual machines (FSVMs) or another component of the virtualized file server (e.g., hypervisor, daemon, or other service). In redirecting to a virtualized file server, the file server manager may in some examples format the request in a manner suitable for the virtualized file server, such as the virtualized file server 212. In some examples, the file server manager may format the request in a manner suitable for a particular version of file server virtual machine operating in the requested virtualized file server. In some examples, the file server manager may receive a request for a virtualized file server that the particular version of file server virtual machine used may not support. The file server manager may identify the version of file server virtual machine (e.g., by accessing metadata and/or registration information) and may replace the unsupported request with a supported request able to be received and processed by the version of file server virtual machine in operation.
If the management request (e.g., API call 202) is determined to be a files platform request (e.g., create one or more FSVMs, scale-in the virtualized file server, scale-out the virtualized file server, add storage to the virtualized file server), then management request may be redirected to a gateway or backend for the appropriate virtualized file server in block 214, such as gateway 216. In redirecting the request, the file server manager may format the request for the particular virtualization platform (e.g., virtualization environment) on which the virtualized file server is hosted. For example, the management request may be formatted for the compute and storage resources used in a particular environment such as a NUTANIX platform, an AMAZON WEB SERVICES platform, a MICROSOFT AZURE platform, etc. The file server manager may access a database or other stored location to determine the platform hosting the requested virtualized file server (e.g., registration information 144 in
If the management request (e.g., API call 202) is determined to be a UI request, it may be redirected to a file server in block 218, such as file server 220, which may be a virtualized file server. UI requests may include, for example, requests to view the current compute resource usage, storage resources usage, number of shares, identity of shares, and/or files or directories hosted by a particular virtualized file server. In redirecting the request to a file server in block 218, the file server manager may format the request in a manner particular to the file server and/or the UI of the file server.
Accordingly, using methods such as depicted in flowchart 200 of
In some examples, the system 332 of
While three virtualized file servers are shown in
The example of
Each file system provided by a virtualized file server may have associated metadata. The file system metadata is depicted in
The database 306 may be used to store metadata and maintain synchronization between the metadata and the metadata of each of the file systems and/or virtualized file servers in communication with the file server manager 304. The file server manager 304 and/or admin system 302 may provide one or more synchronization processes which conduct synchronization between the database 306 and the metadata associated with file system 308, file system 310, file system 312, file system 314, file system 316, and/or file system 318. As metadata is created, destroyed, and/or changed at the virtualized file servers, the changes may be synchronized with the database 306. In this manner, the file server manager 304 may maintain access to accurate information regarding the metadata of one or more connected virtualized file servers. The metadata may be used to administer, manage, and/or access the virtualized file servers and/or file systems. Examples of metadata stored by a virtualized file server and/or file system may include, for example, authentication information for the virtualized file server and/or virtual machines in the virtualized file server, authorization information for the virtualized file server, file system, and/or virtual machines in the virtualized file server, configuration information for the virtualized file server and/or virtual machines in the virtualized file server, end point information (e.g., supported API calls and/or endpoints), a number of shares stored in the virtualized storage of the virtualized file server and/or file system, identities of the shares stored in the virtualized storage of the virtualized file server, a number of computing nodes and/or file server virtual machines (FSVMs) present in the virtualized file server, a number of files and/or directories hosted by the virtualized file server and/or file system, compute resources available and/or used at the virtualized file server, storage resources available and/or used at the virtualized file server, or other metadata regarding the virtualized file server.
Accordingly, in
In operation, the file server manager 304 may access the database 306 to access metadata regarding one or more of the virtualized file servers to aid in managing, accessing, and/or displaying or otherwise reporting on the status of the virtualized file servers.
The file server manager 406 may be used to implement and/or may be implemented by other file server managers described herein, such as file server manager 102 of
During operation of a security workflow, a client may provide a request to a file server manager, such as file server manager 406. The request may be provided to a gateway, such as an API gateway of the file server manager 406, such as API gateway 410. The client may be, for example, an administrator, a process (e.g., an automation script), a virtual machine and/or a container. In some examples, the client may be hosted by a computing node used to host a portion of the virtualized file server (e.g., a computing node having an FSVM). The request may be a management request to perform an operation on or for a virtualized file server. The request may include a request to authenticate and/or authentication credentials. The client may be authenticated by communicating with an authentication process provided by the file server manager, such as authentication process 412 of
Once authenticated, e.g., by authentication process 412, the API gateway 410 may implement a single-sign on to a file server, such as one or more of virtualized file servers 408. Accordingly, in some examples, credentials used to authenticate to the file server manager 406 may be the same used to sign on to one or more virtualized file servers. In some examples, the credentials may not be the same, however once authenticated to the file server manager 406, the file server manager 406 may select the appropriate credentials for sign-on to a virtualized file server, and provide the credentials to the virtualized file server (e.g., to one or more FSVMs, hypervisor(s), daemon(s), and/or other components of the virtualized file server). The sign-on credentials may be provided to a gateway of the virtualized file server, such as API gateway 414 of virtualized file servers 408. Once signed on, the virtualized file server may receive and process the request, e.g., the management request. As described herein, the file server manager 406 may format the request in a manner particular to a virtualization environment of the virtualized file server. Accordingly, the file services 416 may service the request. The file services 416 may include, for example, one or more FSVMs used to implement the virtualized file server. In some examples, the file services 416 may include one or more storage controllers or other virtualization components (e.g., hypervisor(s)).
In some examples, a client may provide a request directly to one or more virtualized file servers. For example, the client 404 is shown in
In this manner, file server managers may provide single sign-on capabilities for one or multiple virtualized file servers. A centralized authentication process, such as an identity access management process, may manage authentication and authorization policies for one or more virtualized file servers.
In some examples, the system of
While three virtualized file servers are shown in
The example of
In some examples, the file server managers described herein, such as file server manager 510 may implement cross-file server policies. For example, because file server manager 510 is in communication with multiple virtualized file servers—e.g., virtualized file server 514, virtualized file server 516, and virtualized file server 518, the file server manager 510 may implement a policy which impacts multiple virtualized file servers. For example, a policy may designate a source virtualized file server and a destination virtualized file server. For example, the file server manager 510 may designate virtualized file server 514 as a source virtualized file server and virtualized file server 516 as a destination virtualized file server. A cross-file server policy may specify that the destination virtualized file server be used to store redundant and/or backup data of the source virtualized file server. Accordingly, the file server manager 510 may communicate with virtualized file server 514 and virtualized file server 516 to implement the cross-file server policy and back-up and/or create redundant storage on virtualized file server 516 of all or portions of virtualized file server 514. In this manner, the virtualized file servers may not need to communicate directly with one another to implement a cross-file server policy. Instead, the file server manager 510 may centrally implement the cross-file server policy.
Moreover, file server managers described herein, such as file server manager 510 may present a view of one or more virtualized file servers—e.g., virtualized file server 514, virtualized file server 516, and virtualized file server 518. The view, based on metadata synchronized to a database of the file server manager 510 (e.g., as shown in database 306 of
In some examples, the system of
While three virtualized file servers are shown in
The example of
During operation, the file server manager 604 may present a view of multiple virtualized file servers to an administrator or other user. The view may be, for example, a display, a list, or other representation of the virtualized file servers in communication with the file server manager 604. A user may select or otherwise indicate a particular virtualized file server, and responsive to the selection, the file server manager 604 may display a user interface for the selected virtualized file server. The user interface for a selected virtualized file server may include a variety of selections and options specific to the virtualized file server. An administrator or other user may use the user interface specific to the virtualized file server, and commands or other selections received through the interface may be received by the file server manager 604 and communicated to the selected virtualized file server—e.g., as management requests formatted in accordance with the virtualization platform hosting the selected virtualized file server.
In this manner, the file server manager 604 may provide a centralized UI for a user to navigate to all connected file servers and to directly login through the file server manager 604 to the virtualized file server for more specific information if desired.
Accordingly,
In some examples, file server managers described herein may additionally or instead provide centralized life cycle management. File server managers may access information about software versions running on each of multiple virtualized file servers, including software versions of multiple components. The file server managers may provide software upgrades and/or software upgrade packages to multiple virtualized file servers, and may upgrade the multiple virtualized file servers in a manner which reduces or eliminates effects of dependences between the upgrades. For example, the virtualization environment on which each virtualized file server is hosted may place constraints on the pace or selection of upgrades. The central file server manager may be used to manage upgrades at a top level and resolve platform-based dependencies.
Examples of systems and methods described herein may include a file server manager in communication with one or more virtualized file servers. Examples of virtualized file servers which may be used to implement virtualized file servers are described in, for example, U.S. Published Patent Application 2017/0235760, entitled “Virtualized file server,” published Aug. 17, 2017 on U.S. application Ser. No. 15/422,220, filed Feb. 1, 2017, both of which documents are hereby incorporated by reference in their entirety for any purpose.
The clustered virtualization environment 700 and/or VFS 732 may be used to implement one or more virtualization platforms and/or virtualized file servers described herein, such as the virtualized file server 106, virtualized file server 114, and/or virtualized file server 122 of
The architectures of
Each host machine 702, 716, 708 may run virtualization software, such as VMWARE ESX(I), MICROSOFT HYPER-V, or REDHAT KVM. The virtualization software includes hypervisors 742, 744, and 746 to create, manage, and destroy user VMs, as well as managing the interactions between the underlying hardware and user VMs. User VMs may run one or more applications that may operate as “clients” with respect to other elements within clustered virtualization environment 700. A hypervisor may connect to network 754. In particular embodiments, a host machine 702, 708, or 716 may be a physical hardware computing device; in particular embodiments, a host machine 702, 708, or 716 may be a virtual machine.
CVMs 736, 738, and 740 are used to manage storage and input/output (“I/O”) activities according to particular embodiments. These special VMs act as the storage controller in the currently described architecture. Multiple such storage controllers may coordinate within a cluster to form a unified storage controller system. CVMs may run as virtual machines on the various host machines, and work together to form a distributed system that manages all the storage resources, including local storage, network-attached storage 710, and cloud storage 706. The CVMs may connect to network 754 directly, or via a hypervisor. Since the CVMs run independent of hypervisors 742, 744, 746, this means that the current approach can be used and implemented within any virtual machine architecture, since the CVMs of particular embodiments can be used in conjunction with any hypervisor from any virtualization vendor. In some examples, CVMs may not be used and one or more hypervisors (e.g., hypervisors 742, 744, and/or 746) may perform the functions described with respect to the CVMs. In some examples, one or more CVMs may not be present, and the hypervisor or other component hosted on the computing nodes may provide the functions attributed to the CVM herein.
A host machine may be designated as a leader node within a cluster of host machines. For example, host machine 708 may be a leader node. A leader node may have a software component designated to perform operations of the leader. For example, CVM 738 on host machine 708 may be designated to perform such operations. A leader may be responsible for monitoring or handling requests from other host machines or software components on other host machines throughout the virtualized environment. If a leader fails, a new leader may be designated. In particular embodiments, a management module (e.g., in the form of an agent) may be running on the leader node and/or in communication with the leader node or virtual machines or containers on the leader node. For example, file server managers described herein may be in communication with the leader node in some examples.
Each CVM 736, 738, and 740 exports one or more block devices or NFS server targets that appear as disks to user VMs 714, 718, 722, 726, 730, and 734. These disks are virtual, since they are implemented by the software running inside CVMs 736, 738, and 740. Thus, to user VMs, CVMs appear to be exporting a clustered storage appliance that contains some disks. All user data (including the operating system) in the user VMs may reside on these virtual disks.
Significant performance advantages can be gained by allowing the virtualization system to access and utilize local storage 748, 750, and 752 as disclosed herein. This is because I/O performance is typically much faster when performing access to local storage as compared to performing access to network-attached storage 710 across a network 754. This faster performance for locally attached storage can be increased even further by using certain types of optimized local storage devices, such as SSDs. Further details regarding methods and mechanisms for implementing the virtualization environment illustrated in
As a user VM performs I/O operations (e.g., a read operation or a write operation), the I/O commands of the user VM may be sent to the hypervisor that shares the same server as the user VM. For example, the hypervisor may present to the virtual machines an emulated storage controller, receive an I/O command and facilitate the performance of the I/O command (e.g., via interfacing with storage that is the object of the command, or passing the command to a service that will perform the I/O command). An emulated storage controller may facilitate I/O operations between a user VM and a vDisk. A vDisk may present to a user VM as one or more discrete storage drives, but each vDisk may correspond to any part of one or more drives within storage pool 756. Additionally or alternatively, CVMs 736, 738, 740 may present an emulated storage controller either to the hypervisor or to user VMs to facilitate I/O operations. CVMs 736, 738, and 740 may be connected to storage within storage pool 756. CVM 736 may have the ability to perform I/O operations using local storage 748 within the same host machine 702, by connecting via network 754 to cloud storage 706 or network-attached storage 710, or by connecting via network 754 to local storage 750 or 752 within another host machine 708 or 716 (e.g., via connecting to another CVM 738 or 740). In particular embodiments, any suitable computing system may be used to implement a host machine.
In particular embodiments, the VFS 732 may include a set of File Server Virtual Machines (FSVMs) 704, 712, and 720 that execute on host machines 702, 708, and 716 and process storage item access operations requested by user VMs executing on the host machines 702, 708, and 716. The FSVMs 704, 712, and 720 may communicate with storage controllers provided by CVMs 736, 744, 740 and/or hypervisors executing on the host machines 702, 708, 716 to store and retrieve files, folders, SMB shares, or other storage items on local storage 748, 750, 752 associated with, e.g., local to, the host machines 702, 708, 716. The FSVMs 704, 712, 720 may store and retrieve block-level data on the host machines 702, 708, 716, e.g., on the local storage 748, 750, 752 of the host machines 702, 708, 716. The block-level data may include block-level representations of the storage items (e.g., files, shares). The network protocol used for communication between user VMs, FSVMs, and CVMs via the network 754 may be Internet Small Computer Systems Interface (iSCSI), Server Message Block (SMB), Network Filesystem (NFS), pNFS (Parallel NFS), or another appropriate protocol.
For the purposes of VFS 732, host machine 716 may be designated as a leader node within a cluster of host machines. In this case, FSVM 720 on host machine 716 may be designated to perform such operations. A leader may be responsible for monitoring or handling requests from FSVMs on other host machines throughout the virtualized environment. If FSVM 720 fails, a new leader may be designated for VFS 732.
In particular embodiments, the user VMs may send data to the VFS 732 (e.g., to the FSVMs) using write requests, and may receive data from it using read requests. The read and write requests, and their associated parameters, data, and results, may be sent between a user VM and one or more file server VMs (FSVMs) located on the same host machine as the user VM or on different host machines from the user VM. The read and write requests may be sent between host machines 702, 708, 716 via network 754, e.g., using a network communication protocol such as iSCSI, CIFS, SMB, TCP, IP, or the like. When a read or write request is sent between two VMs located on the same one of the host machines 702, 708, 716 (e.g., between the user VM 714 and the FSVM 704 located on the host machine 702), the request may be sent using local communication within the host machine 702 instead of via the network 754. As described above, such local communication may be substantially faster than communication via the network 754. The local communication may be performed by, e.g., writing to and reading from shared memory accessible by the user VM 714 and the FSVM 704, sending and receiving data via a local “loopback” network interface, local stream communication, or the like.
In particular embodiments, the storage items stored by the VFS 732, such as files and folders, may be distributed amongst multiple FSVMs 704, 712, 720. In particular embodiments, when storage access requests are received from the user VMs, the VFS 732 identifies FSVMs 704, 712, 720 at which requested storage items, e.g., folders, files, or portions thereof, are stored, and directs the user VMs to the locations of the storage items. The FSVMs 704, 712, 720 may maintain a storage map, such as a sharding map, that maps names or identifiers of storage items to their corresponding locations. The storage map may be a distributed data structure of which copies are maintained at each FSVM 704, 712, 720 and accessed using distributed locks or other storage item access operations. Alternatively, the storage map may be maintained by an FSVM at a leader node such as the FSVM 720, and the other FSVMs 704 and 712 may send requests to query and update the storage map to the leader FSVM 720. Other implementations of the storage map are possible using appropriate techniques to provide asynchronous data access to a shared resource by multiple readers and writers. The storage map may map names or identifiers of storage items in the form of text strings or numeric identifiers, such as folder names, files names, and/or identifiers of portions of folders or files (e.g., numeric start offset positions and counts in bytes or other units) to locations of the files, folders, or portions thereof. Locations may be represented as names of FSVMs, e.g., “FSVM-1”, as network addresses of host machines on which FSVMs are located (e.g., “ip-addr1” or 128.1.1.10), or as other types of location identifiers.
When a user application executing in a user VM 714 on one of the host machines 702 initiates a storage access operation, such as reading or writing data, the user VM 714 may send the storage access operation in a request to one of the FSVMs 704, 712, 720 on one of the host machines 702, 708, 716. A FSVM 712 executing on a host machine 708 that receives a storage access request may use the storage map to determine whether the requested file or folder is located on the FSVM 712. If the requested file or folder is located on the FSVM 712, the FSVM 712 executes the requested storage access operation. Otherwise, the FSVM 712 responds to the request with an indication that the data is not on the FSVM 712, and may redirect the requesting user VM 714 to the FSVM on which the storage map indicates the file or folder is located. The client may cache the address of the FSVM on which the file or folder is located, so that it may send subsequent requests for the file or folder directly to that FSVM.
As an example and not by way of limitation, the location of a file or a folder may be pinned to a particular FSVM 704 by sending a file service operation that creates the file or folder to a CVM 736 and/or hypervisor 742 associated with (e.g., located on the same host machine as) the FSVM 704. The CVM 736 subsequently processes file service commands for that file for the FSVM 704 and sends corresponding storage access operations to storage devices associated with the file. The CVM 736 may associate local storage 748 with the file if there is sufficient free space on local storage 748. Alternatively, the CVM 736 may associate a storage device located on another host machine 702, e.g., in local storage 750, with the file under certain conditions, e.g., if there is insufficient free space on the local storage 748, or if storage access operations between the CVM 736 and the file are expected to be infrequent. Files and folders, or portions thereof, may also be stored on other storage devices, such as the network-attached storage (NAS) network-attached storage 710 or the cloud storage 706 of the storage pool 756.
In particular embodiments, a name service 724, such as that specified by the Domain Name System (DNS) Internet protocol, may communicate with the host machines 702, 708, 716 via the network 754 and may store a database of domain name (e.g., host name) to IP address mappings. The domain names may correspond to FSVMs, e.g., fsvm1.domain.com or ip-addr1.domain.com for an FSVM named FSVM-1. The name service 724 may be queried by the user VMs to determine the IP address of a particular host machine 702, 708, 716 given a name of the host machine, e.g., to determine the IP address of the host name ip-addr1 for the host machine 702. The name service 724 may be located on a separate server computer system or on one or more of the host machines 702, 708, 716. The names and IP addresses of the host machines of the VFS 732, e.g., the host machines 702, 708, 716, may be stored in the name service 724 so that the user VMs may determine the IP address of each of the host machines 702, 708, 716, or FSVMs 704, 712, 720. The name of each VFS instance, e.g., each file system such as FS1, FS2, or the like, may be stored in the name service 724 in association with a set of one or more names that contains the name(s) of the host machines 702, 708, 716 or FSVMs 704, 712, 720 of the VFS instance VFS 732. The FSVMs 704, 712, 720 may be associated with the host names ip-addr1, ip-addr2, and ip-addr3, respectively. For example, the file server instance name FS1.domain.com may be associated with the host names ip-addr1, ip-addr2, and ip-addr3 in the name service 724, so that a query of the name service 724 for the server instance name “FS1” or “FS1.domain.com” returns the names ip-addr1, ip-addr2, and ip-addr3. As another example, the file server instance name FS1.domain.com may be associated with the host names fsvm-1, fsvm-2, and fsvm-3. Further, the name service 724 may return the names in a different order for each name lookup request, e.g., using round-robin ordering, so that the sequence of names (or addresses) returned by the name service for a file server instance name is a different permutation for each query until all the permutations have been returned in response to requests, at which point the permutation cycle starts again, e.g., with the first permutation. In this way, storage access requests from user VMs may be balanced across the host machines, since the user VMs submit requests to the name service 724 for the address of the VFS instance for storage items for which the user VMs do not have a record or cache entry, as described below.
In particular embodiments, each FSVM may have two IP addresses: an external IP address and an internal IP address. The external IP addresses may be used by SMB/CIFS clients, such as user VMs, to connect to the FSVMs. The external IP addresses may be stored in the name service 724. The IP addresses ip-addr1, ip-addr2, and ip-addr3 described above are examples of external IP addresses. The internal IP addresses may be used for iSCSI communication to CVMs and/or hypervisors, e.g., between the FSVMs 704, 712, 720 and the CVMs 736, 744, 740 and/or hypervisors 742, 744, and/or 746. Other internal communications may be sent via the internal IP addresses as well, e.g., file server configuration information may be sent from the CVMs to the FSVMs using the internal IP addresses, and the CVMs may get file server statistics from the FSVMs via internal communication as needed.
Since the VFS 732 is provided by a distributed set of FSVMs 704, 712, 720, the user VMs that access particular requested storage items, such as files or folders, do not necessarily know the locations of the requested storage items when the request is received. A distributed file system protocol, e.g., MICROSOFT DFS or the like, is therefore used, in which a user VM 714 may request the addresses of FSVMs 704, 712, 720 from a name service 724 (e.g., DNS). The name service 724 may send one or more network addresses of FSVMs 704, 712, 720 to the user VM 714, in an order that changes for each subsequent request. These network addresses are not necessarily the addresses of the FSVM 712 on which the storage item requested by the user VM 714 is located, since the name service 724 does not necessarily have information about the mapping between storage items and FSVMs 704, 712, 720. Next, the user VM 714 may send an access request to one of the network addresses provided by the name service, e.g., the address of FSVM 712. The FSVM 712 may receive the access request and determine whether the storage item identified by the request is located on the FSVM 712. If so, the FSVM 712 may process the request and send the results to the requesting user VM 714. However, if the identified storage item is located on a different FSVM 720, then the FSVM 712 may redirect the user VM 714 to the FSVM 720 on which the requested storage item is located by sending a “redirect” response referencing FSVM 720 to the user VM 714. The user VM 714 may then send the access request to FSVM 720, which may perform the requested operation for the identified storage item.
A particular virtualized file server, such as VFS 732, including the items it stores, e.g., files and folders, may be referred to herein as a VFS “instance” and/or a file system and may have an associated name, e.g., FS1, as described above. Although a VFS instance may have multiple FSVMs distributed across different host machines, with different files being stored on FSVMs, the VFS instance may present a single name space to its clients such as the user VMs. The single name space may include, for example, a set of named “shares” and each share may have an associated folder hierarchy in which files are stored. Storage items such as files and folders may have associated names and metadata such as permissions, access control information, size quota limits, file types, files sizes, and so on. As another example, the name space may be a single folder hierarchy, e.g., a single root directory that contains files and other folders. User VMs may access the data stored on a distributed VFS instance via storage access operations, such as operations to list folders and files in a specified folder, create a new file or folder, open an existing file for reading or writing, and read data from or write data to a file, as well as storage item manipulation operations to rename, delete, copy, or get details, such as metadata, of files or folders. Note that folders may also be referred to herein as “directories.”
In particular embodiments, storage items such as files and folders in a file server namespace may be accessed by clients such as user VMs by name, e.g., “\Folder-1 \File-1” and “\Folder-2\File-2” for two different files named File-1 and File-2 in the folders Folder-1 and Folder-2, respectively (where Folder-1 and Folder-2 are sub-folders of the root folder). Names that identify files in the namespace using folder names and file names may be referred to as “path names.” Client systems may access the storage items stored on the VFS instance by specifying the file names or path names, e.g., the path name “\Folder-1 \File-1”, in storage access operations. If the storage items are stored on a share (e.g., a shared drive), then the share name may be used to access the storage items, e.g., via the path name “\\Share-1 \Folder-1 \File-1” to access File-1 in folder Folder-1 on a share named Share-1.
In particular embodiments, although the VFS instance may store different folders, files, or portions thereof at different locations, e.g., on different FSVMs, the use of different FSVMs or other elements of storage pool 756 to store the folders and files may be hidden from the accessing clients. The share name is not necessarily a name of a location such as an FSVM or host machine. For example, the name Share-1 does not identify a particular FSVM on which storage items of the share are located. The share Share-1 may have portions of storage items stored on three host machines, but a user may simply access Share-1, e.g., by mapping Share-1 to a client computer, to gain access to the storage items on Share-1 as if they were located on the client computer. Names of storage items, such as file names and folder names, are similarly location-independent. Thus, although storage items, such as files and their containing folders and shares, may be stored at different locations, such as different host machines, the files may be accessed in a location-transparent manner by clients (such as the user VMs). Thus, users at client systems need not specify or know the locations of each storage item being accessed. The VFS may automatically map the file names, folder names, or full path names to the locations at which the storage items are stored. As an example and not by way of limitation, a storage item's location may be specified by the name, address, or identity of the FSVM that provides access to the storage item on the host machine on which the storage item is located. A storage item such as a file may be divided into multiple parts that may be located on different FSVMs, in which case access requests for a particular portion of the file may be automatically mapped to the location of the portion of the file based on the portion of the file being accessed (e.g., the offset from the beginning of the file and the number of bytes being accessed).
In particular embodiments, VFS 732 determines the location, e.g., FSVM, at which to store a storage item when the storage item is created. For example, a FSVM 704 may attempt to create a file or folder using a CVM 736 on the same host machine 702 as the user VM 718 that requested creation of the file, so that the CVM 736 that controls access operations to the file folder is co-located with the user VM 718. In this way, since the user VM 718 is known to be associated with the file or folder and is thus likely to access the file again, e.g., in the near future or on behalf of the same user, access operations may use local communication or short-distance communication to improve performance, e.g., by reducing access times or increasing access throughput. If there is a local CVM on the same host machine as the FSVM, the FSVM may identify it and use it by default. If there is no local CVM on the same host machine as the FSVM, a delay may be incurred for communication between the FSVM and a CVM on a different host machine. Further, the VFS 732 may also attempt to store the file on a storage device that is local to the CVM being used to create the file, such as local storage, so that storage access operations between the CVM and local storage may use local or short-distance communication.
In particular embodiments, if a CVM is unable to store the storage item in local storage of a host machine on which an FSVM resides, e.g., because local storage does not have sufficient available free space, then the file may be stored in local storage of a different host machine. In this case, the stored file is not physically local to the host machine, but storage access operations for the file are performed by the locally-associated CVM and FSVM, and the CVM may communicate with local storage on the remote host machine using a network file sharing protocol, e.g., iSCSI, SAMBA, or the like.
In particular embodiments, if a virtual machine, such as a user VM 714, CVM 736, or FSVM 704, moves from a host machine 702 to a destination host machine 708, e.g., because of resource availability changes, and data items such as files or folders associated with the VM are not locally accessible on the destination host machine 708, then data migration may be performed for the data items associated with the moved VM to migrate them to the new host machine 708, so that they are local to the moved VM on the new host machine 708. FSVMs may detect removal and addition of CVMs (as may occur, for example, when a CVM fails or is shut down) via the iSCSI protocol or other technique, such as heartbeat messages. As another example, a FSVM may determine that a particular file's location is to be changed, e.g., because a disk on which the file is stored is becoming full, because changing the file's location is likely to reduce network communication delays and therefore improve performance, or for other reasons. Upon determining that a file is to be moved, VFS 732 may change the location of the file by, for example, copying the file from its existing location(s), such as local storage 748 of a host machine 702, to its new location(s), such as local storage 750 of host machine 708 (and to or from other host machines, such as local storage 752 of host machine 716 if appropriate), and deleting the file from its existing location(s). Write operations on the file may be blocked or queued while the file is being copied, so that the copy is consistent. The VFS 732 may also redirect storage access requests for the file from an FSVM at the file's existing location to a FSVM at the file's new location.
In particular embodiments, VFS 732 includes at least three File Server Virtual Machines (FSVMs) 704, 712, 720 located on three respective host machines 702, 708, 716. To provide high-availability, there may be a maximum of one FSVM for a particular VFS instance VFS 732 per host machine in a cluster. If two FSVMs are detected on a single host machine, then one of the FSVMs may be moved to another host machine automatically, or the user (e.g., system administrator and/or file server manager) may be notified to move the FSVM to another host machine. The user and/or file server manager may move a FSVM to another host machine using an administrative interface that provides commands for starting, stopping, and moving FSVMs between host machines.
In particular embodiments, two FSVMs of different VFS instances may reside on the same host machine. If the host machine fails, the FSVMs on the host machine become unavailable, at least until the host machine recovers. Thus, if there is at most one FSVM for each VFS instance on each host machine, then at most one of the FSVMs may be lost per VFS per failed host machine. As an example, if more than one FSVM for a particular VFS instance were to reside on a host machine, and the VFS instance includes three host machines and three FSVMs, then loss of one host machine would result in loss of two-thirds of the FSVMs for the VFS instance, which would be more disruptive and more difficult to recover from than loss of one-third of the FSVMs for the VFS instance.
In particular embodiments, users, such as system administrators or other users of the user VMs, may expand the cluster of FSVMs by adding additional FSVMs. Each FSVM may be associated with at least one network address, such as an IP (Internet Protocol) address of the host machine on which the FSVM resides. There may be multiple clusters, and all FSVMs of a particular VFS instance are ordinarily in the same cluster. The VFS instance may be a member of a MICROSOFT ACTIVE DIRECTORY domain, which may provide authentication and other services such as name service.
As an example, a network share may be presented to a user VM as one or more discrete virtual disks, but each virtual disk may correspond to any part of one or more virtual or physical disks within a storage pool. Additionally or alternatively, the FSVMs may present a VFS either to the hypervisor or to user VMs of a host machine to facilitate I/O operations. The FSVMs may access the local storage via Controller/Service VMs, other storage controllers, hypervisors, or other components of the host machine. As described herein, a CVM 736 may have the ability to perform I/O operations using local storage 748 within the same host machine 702 by connecting via the network 754 to cloud storage or NAS, or by connecting via the network 754 to 750, 752 within another host machine 708, 716 (e.g., by connecting to another CVM 738, 740).
In particular embodiments, each user VM may access one or more virtual disk images stored on one or more disks of the local storage, the cloud storage, and/or the NAS. The virtual disk images may contain data used by the user VMs, such as operating system images, application software, and user data, e.g., user home folders and user profile folders. For example,
In particular embodiments, since local communication is expected to be more efficient than remote communication, the FSVMs may store storage items, such as files or folders, e.g., the virtual disk images, as block-level data on local storage of the host machine on which the user VM that is expected to access the files is located. A user VM may be expected to access particular storage items if, for example, the storage items are associated with the user VM, such as by configuration information. For example, the virtual disk image 810 may be associated with the user VM 714 by configuration information of the user VM 714. Storage items may also be associated with a user VM via the identity of a user of the user VM. For example, files and folders owned by the same user ID as the user who is logged into the user VM 714 may be associated with the user VM 714. If the storage items expected to be accessed by a user VM 714 are not stored on the same host machine 702 as the user VM 714, e.g., because of insufficient available storage capacity in local storage 748 of the host machine 702, or because the storage items are expected to be accessed to a greater degree (e.g., more frequently or by more users) by a user VM 722 on a different host machine 708, then the user VM 714 may still communicate with a local CVM 736 to access the storage items located on the remote host machine 708, and the local CVM 736 may communicate with local storage 750 on the remote host machine 708 to access the storage items located on the remote host machine 708. If the user VM 714 on a host machine 702 does not or cannot use a local CVM 736 to access the storage items located on the remote host machine 708, e.g., because the local CVM 736 has crashed or the user VM 714 has been configured to use a remote CVM 738, then communication between the user VM 714 and local storage 750 on which the storage items are stored may be via a remote CVM 738 using the network 754, and the remote CVM 738 may access local storage 750 using local communication on host machine 708. As another example, a user VM 714 on a host machine 702 may access storage items located on a disk 806 of local storage 752 on another host machine 716 via a CVM 738 on an intermediary host machine 708 using network communication between the host machines 702 and 708 and between the host machines 708 and 716.
In particular embodiments, file systems FileSystem-1A 1042 and FileSystem-2A 1040 implement the structure of files and folders for portions of the FS1 and FS2 file server instances, respectively, that are located on (e.g., served by) FileServer-VM-1 1020 on Host-1 1004. Other file systems on other host machines may implement other portions of the FS1 and FS2 file server instances. The file systems 1042 and 1040 may implement the structure of at least a portion of a file server instance by translating file system operations, such as opening a file, writing data to or reading data from the file, deleting a file, and so on, to disk I/O operations such as seeking to a portion of the disk, reading or writing an index of file information, writing data to or reading data from blocks of the disk, allocating or de-allocating the blocks, and so on. The file systems 1042, 1040 may thus store their file system data, including the structure of the folder and file hierarchy, the names of the storage items (e.g., folders and files), and the contents of the storage items on one or more storage devices, such as local storage 1028. The particular storage device or devices on which the file system data for each file system are stored may be specified by an associated file system pool (e.g., 1048 and 1050). For example, the storage device(s) on which data for FileSystem-1A 1042 and FileSystem-2A, 1040 are stored may be specified by respective file system pools FS1-Pool-1 1048 and FS2-Pool-2 1050. The storage devices for the pool may be selected from volume groups provided by CVM-1 1024, such as volume group VG1 1032 and volume group VG2 1034. Each volume group 1032, 1034 may include a group of one or more available storage devices that are present in local storage 1028 associated with (e.g., by iSCSI communication) the CVM-1 1024. The CVM-1 1024 may be associated with a local storage 1028 on the same host machine 702 as the CVM-1 1024, or with a local storage 1030 on a different host machine 1006. The CVM-1 1024 may also be associated with other types of storage, such as cloud storage, networked storage or the like. Although the examples described herein include particular host machines, virtual machines, file servers, file server instances, file server pools, CVMs, volume groups, and associations there between, any number of host machines, virtual machines, file servers, file server instances, file server pools, CVMs, volume groups, and any associations there between are possible and contemplated.
In particular embodiments, the file system pool 1048 may associate any storage device in one of the volume groups 1032, 1034 of storage devices that are available in local storage 1028 with the file system FileSystem-1A 1042. For example, the file system pool FS1-Pool-1 1048 may specify that a disk device named hd1 in the volume group VG1 1032 of local storage 1028 is a storage device for FileSystem-1A 1042 for file server FS1 on FSVM-1 1020. A file system pool FS2-Pool-2 1050 may specify a storage device FileSystem-2A 1050 for file server FS2 on FSVM-1 1020. The storage device for FileSystem-2A 1040 may be, e.g., the disk device hd1, or a different device in one of the volume groups 1032, 1034, such as a disk device named hd2 in volume group VG2 1034. Each of the file systems FileSystem-1A 1042, FileSystem-2A 1040 may be, e.g., an instance of the NTFS file system used by the WINDOWS operating system, of the UFS Unix file system, or the like. The term “file system” may also be used herein to refer to an instance of a type of file system, e.g., a particular structure of folders and files with particular names and content.
In one example, referring to
In particular embodiments, FileServer-VM-1 (abbreviated FSVM-1) 1020 on Host-1 1004 is a leader for a portion of file server instance FS1 and a portion of FS2, and is a backup for another portion of FS1 and another portion of FS2. The portion of FS1 for which FileServer-VM-1 1020 is a leader corresponds to a storage pool labeled FS1-Pool-1 1048. FileServer-VM-1 is also a leader for FS2-Pool-2 1050, and is a backup (e.g., is prepared to become a leader upon request, such as in response to a failure of another FSVM) for FS1-Pool-3 1052 and FS2-Pool-4 1054 on Host-2 1006. In particular embodiments, FileServer-VM-2 (abbreviated FSVM-2) 1022 is a leader for a portion of file server instance FS1 and a portion of FS2, and is a backup for another portion of FS1 and another portion of FS2. The portion of FS1 for which FSVM-2 1022 is a leader corresponds to a storage pool labeled FS1-Pool-3 1052. FSVM-2 1022 is also a leader for FS2-Pool-4 1054, and is a backup for FS1-Pool-1 1048 and FS2-Pool-2 1050 on Host-1 1004.
In particular embodiments, the file server instances FS1, FS2 provided by the FSVMs 1020 and 1022 may be accessed by user VMs 1008, 1010, 1012 and 1014 via a network file system protocol such as SMB, CIFS, NFS, or the like. Each FSVM 1020 and 1022 may provide what appears to client applications on user VMs 1008, 1010, 1012 and 1014 to be a single file system instance, e.g., a single namespace of shares, files and folders, for each file server instance. However, the shares, files, and folders in a file server instance such as FS1 may actually be distributed across multiple FSVMs 1020 and 1022. For example, different folders in the same file server instance may be associated with different corresponding FSVMs 1020 and 1022 and CVMs 1024 and 1026 on different host machines 1004 and 1006.
The example file server instance FS1 904 shown in
Continuing with the data request example, the associated CVM is CVM 1024, which may in turn access the storage device associated with the requested data as specified in the request, e.g., to write specified data to the storage device or read requested data from a specified location on the storage device. In this example, the associated storage device is in local storage 1028, and may be an HDD or SSD. CVM-1 1024 may access the HDD or SSD via an appropriate protocol, e.g., iSCSI, SCSI, SATA, or the like. CVM 110a may send the results of accessing local storage 1028, e.g., data that has been read, or the status of a data write operation, to CVM 1024 via, e.g., SATA, which may in turn send the results to FSVM-1 1020 via, e.g., iSCSI. FSVM-1 1020 may then send the results to user VM via SMB through the Hypervisor 1016.
Share-2 910 may be located on FSVM-2 1022, on Host-2. Network file service protocol requests from user VMs to read or write data on Share-2 may be directed to FSVM-2 1022 on Host-2 by other FSVMs. Alternatively, user VMs may send such requests directly to FSVM-2 1022 on Host-2, which may process the requests using CVM-2 1026 and local storage 1030 on Host-2 as described above for FSVM-1 1020 on Host-1.
A file server instance such as FS1 904 in
In particular embodiments, when the client 1104 requests access to Folder-3, a VFS client component executing in the user VM may use a distributed file system protocol such as MICROSOFT DFS, or the like, to send the storage access request to one or more of the FSVMs of
In particular embodiments, at step 1164, the client may send a request for a list of addresses of FSVMs to a name server 1102. The name server 1102 may be, e.g., a DNS server or other type of server, such as a MICROSOFT domain controller (not shown), that has a database of FSVM addresses. At step 1148, the name server 1102 may send a reply that contains a list of FSVM network addresses, e.g., ip-addr1, ip-addr2, and ip-addr3, which correspond to the FSVMs in this example. At step 1166, the client 1104 may send an access request to one of the network addresses, e.g., the first network address in the list (ip-addr1 in this example), requesting the contents of Folder-3 of Share-1. By selecting the first network address in the list, the particular FSVM to which the access request is sent may be varied, e.g., in a round-robin manner by enabling round-robin DNS (or the like) on the name server 1102. The access request may be, e.g., an SMB connect request, an NFS open request, and/or appropriate request(s) to traverse the hierarchy of Share-1 to reach the desired folder or file, e.g., Folder-3 in this example.
At step 1168, FileServer-VM-1 1110 may process the request received at step 1166 by searching a mapping or lookup table, such as a sharding map 1122, for the desired folder or file. The map 1122 maps stored objects, such as shares, folders, or files, to their corresponding locations, e.g., the names or addresses of FSVMs. The map 1122 may have the same contents on each host machine, with the contents on different host machines being synchronized using a distributed data store as described below. For example, the map 1122 may contain entries that map Share-1 and Folder-1 to the File Server FSVM-1 1110, and Folder-3 to the File Server FSVM-3 1112. An example map is shown in Table 1 below. While the example of
In particular embodiments, the map 1122 or 1124 may be accessible on each of the host machines. The maps may be copies of a distributed data structure that are maintained and accessed at each FSVM using a distributed data access coordinator 1126 and 1130. The distributed data access coordinator 1126 and 1130 may be implemented based on distributed locks or other storage item access operations. Alternatively, the distributed data access coordinator 1126 and 1130 may be implemented by maintaining a master copy of the maps 1122 and 1124 at a leader node such as the host machine 1108, and using distributed locks to access the master copy from each FSVM 1110 and 1112. The distributed data access coordinator 1126 and 1130 may be implemented using distributed locking, leader election, or related features provided by a centralized coordination service for maintaining configuration information, naming, providing distributed synchronization, and/or providing group services (e.g., APACHE ZOOKEEPER or other distributed coordination software). Since the map 1122 indicates that Folder-3 is located at FSVM-3 1112 on Host-3 1108, the lookup operation at step 1168 determines that Folder-3 is not located at FSVM-1 on Host-1 1106. Thus, at step 1162 the FSVM-1 1110 (or other component of the virtualized system) sends a response, e.g., a “Not Covered” DFS response, to the client 1104 indicating that the requested folder is not located at FSVM-1. At step 1160, the client 1104 sends a request to FSVM-1 for a referral to the FSVM on which Folder-3 is located. FSVM-1 uses the map 1122 to determine that Folder-3 is located at FSVM-3 on Host-3 1108, and at step 1158 returns a response, e.g., a “Redirect” DFS response, redirecting the client 1104 to FSVM-3. The client 1104 may then determine the network address for FSVM-3, which is ip-addr3 (e.g., a host name “ip-addr3.domain.name” or an IP address, 10.1.1.3). The client 1104 may determine the network address for FSVM-3 by searching a cache stored in memory of the client 1104, which may contain a mapping from FSVM-3 to ip-addr3 cached in a previous operation. If the cache does not contain a network address for FSVM-3, then at step 1150 the client 1104 may send a request to the name server 1102 to resolve the name FSVM-3. The name server may respond with the resolved address, ip-addr3, at step 1152. The client 1104 may then store the association between FSVM-3 and ip-addr3 in the client's cache.
In particular embodiments, failure of FSVMs may be detected using the centralized coordination service. For example, using the centralized coordination service, each FSVM may create a lock on the host machine on which the FSVM is located using ephemeral nodes of the centralized coordination service (which are different from host machines but may correspond to host machines). Other FSVMs may volunteer for leadership of resources of remote FSVMs on other host machines, e.g., by requesting a lock on the other host machines. The locks requested by the other nodes are not granted unless communication to the leader host machine is lost, in which case the centralized coordination service deletes the ephemeral node and grants the lock to one of the volunteer host machines and, which becomes the new leader. For example, the volunteer host machines may be ordered by the time at which the centralized coordination service received their requests, and the lock may be granted to the first host machine on the ordered list. The first host machine on the list may thus be selected as the new leader. The FSVM on the new leader has ownership of the resources that were associated with the failed leader FSVM until the failed leader FSVM is restored, at which point the restored FSVM may reclaim the local resources of the host machine on which it is located.
At step 1154, the client 1104 may send an access request to FSVM-3 1112 at ip-addr3 on Host-3 1108 requesting the contents of Folder-3 of Share-1. At step 1170, FSVM-3 1112 queries FSVM-3's copy of the map 1124 using FSVM-3's instance of the distributed data access coordinator 1130. The map 1124 indicates that Folder-3 is located on FSVM-3, so at step 1172 FSVM-3 accesses the file system 1132 to retrieve information about Folder-3 1144 and its contents (e.g., a list of files in the folder, which includes File-2 1146) that are stored on the local storage 1120. FSVM-3 may access local storage 1120 via CVM-3 1116, which provides access to local storage 1120 via a volume group 1136 that contains one or more volumes stored on one or more storage devices in local storage 1120. At step 1156, FSVM-3 may then send the information about Folder-3 and its contents to the client 1104. Optionally, FSVM-3 may retrieve the contents of File-2 and send them to the client 1104, or the client 1104 may send a subsequent request to retrieve File-2 as needed.
The computing node 1200 includes one or more communications fabric(s) 1202, which provide communications between one or more processor(s) 1204, memory 1206, local storage 1208, communications unit 1210, and/or I/O interface(s) 1212. The communications fabric(s) 1202 can be implemented with any architecture designed for passing data and/or control information between processors (such as microprocessors, communications and network processors, etc.), system memory, peripheral devices, and any other hardware components within a system. For example, the communications fabric(s) 1202 can be implemented with one or more buses.
The memory 1206 and the local storage 1208 may be computer-readable storage media. In the example of
Various computer instructions, programs, files, images, etc. may be stored in local storage 1208 and/or memory 1206 for execution by one or more of the respective processor(s) 1204 via one or more memories of memory 1206. In some examples, local storage 1208 includes a magnetic HDD 1224. Alternatively, or in addition to a magnetic hard disk drive, local storage 1208 can include the SSD 1222, a semiconductor storage device, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, or any other computer-readable storage media that is capable of storing program instructions or digital information.
The media used by local storage 1208 may also be removable. For example, a removable hard drive may be used for local storage 1208. Other examples include optical and magnetic disks, thumb drives, and smart cards that are inserted into a drive for transfer onto another computer-readable storage medium that is also part of local storage 1208.
Communications unit 1210, in some examples, provides for communications with other data processing systems or devices. For example, communications unit 1210 may include one or more network interface cards. Communications unit 310 may provide communications through the use of either or both physical and wireless communications links.
I/O interface(s) 1212 may allow for input and output of data with other devices that may be connected to computing node 1200. For example, I/O interface(s) 1212 may provide a connection to external device(s) 1218 such as a keyboard, a keypad, a touch screen, and/or some other suitable input device. External device(s) 318 can also include portable computer-readable storage media such as, for example, thumb drives, portable optical or magnetic disks, and memory cards. Software and data used to practice embodiments of the present invention can be stored on such portable computer-readable storage media and can be loaded onto and/or encoded in memory 1206 and/or local storage 1208 via I/O interface(s) 1212 in some examples. I/O interface(s) 1212 may connect to a display 1220. Display 1220 may provide a mechanism to display data to a user and may be, for example, a computer monitor.
In various examples described herein, an admin system (e.g., admin system 508 of
Data replication may be provided from a source file server to a remote file server, which may be used for failover in case of failure of the source file server. The admin system may be used to configure replication policies by, for example, selecting shares from the source file server to be replicated to the destination file server. Replication policies may further include, in various examples, selecting a replication schedule (e.g., replication frequency) for the selected shares. The source file server may be replicated by replicating each share independently based on the replication schedule. The data replication may be based on zettabyte file system (ZFS) send and receive technology using ZFS dataset snapshots. The first replication may be a full replication using a base snapshot. Subsequent replication may transfer only a data difference between the last snapshot and a new snapshot (e.g., a delta snapshot).
Replication described herein may include maintaining the standby or destination file server such that the destination file server accepts client connections and serves data over NFS and/or SMB protocols in read only. For example, the destination file server may be used to read data from the file system. However, before a failover or activation, the destination file server may not be used to write data to the file system. In case of a failure of the primary or source file server, or other failover trigger, failover may occur by updating settings of the destination file server to accept read and write requests, which may shorten recovery time when contrasted with a typical active-passive scenario. The replication methods described herein may provide failover and failback workflows to orchestrate recovery of the primary file server. In some examples, additional workflows may allow the destination file server to take over the identity of the primary file server.
The replication described herein may use a task based framework. A task framework may allow for tracking progress of work done (e.g., whether individual tasks have been started, completed, or exited with an error). Tasks may be used to handle user triggered operations that take a long time and are handled asynchronously. For example, a failover workflow may be a task. The replication described herein may use a job framework in addition to the task based framework. A job may be similar to a task, where a job represents a unit of system generated action. The job framework may allow for tracking progress of system generated periodic work. For example, replication may be a job.
Note that replicators, schedulers, and job dispatchers described herein may be software components. For example, the replicator 1314, replicator 1324, scheduler 1312, scheduler 1322, and/or job dispatcher 1316 may be implemented using executable instructions for performing the replicator, scheduler, and/or job dispatcher functions. The executable instructions may be executed by one or more processors (e.g., processors on computing nodes of the primary file server 1306 and/or secondary file server 1308) to implement the scheduler, replicator, and/or job dispatcher components.
The primary file server 1306 and the secondary file server 1308 may be used to implement and/or may be implemented by file servers and virtualized file servers described herein, such as virtualized file servers 106, 114, 122, 334, 336, 338, 408, 514, 516, 518, 614, 616, 618, and/or 732 and file servers 212, 220, 904, 906, 1042, and/or 1040. Accordingly, the primary file server 1306 and the secondary file server 1308 may include multiple host machines hosting various software to implement the file server, such as FSVMs, virtualized storage controllers, hypervisors, and the like. For example, the primary file server 1306 and the secondary file server 1308 may each include multiple host machines with FSVMs distributed across the host machines receiving file access requests for storage items of storage pools of the primary file server 1306 and the secondary file server 1308.
The admin system 1302 may be used to implement and/or may be implemented by admin systems described herein, such as admin systems 302, 508, and/or 602. The file system manager 1304 may be used to implement and/or may be implemented by file system managers described herein, such as file system managers 102, 406, 510, and/or 604. The admin system 1302 may include an instance of a supervisory process to provide a point of communication for calls coming from or to the admin system 1302 related to the primary file server 1306 and the secondary file server 1308.
The API gateway 1310 and the API gateway 1320 may run instances of the supervisory process to handle communication between FSVMs at the respective file servers and the admin system 1302. The API gateway 1310 and the API gateways 1320 may provide a single point of communication for calls coming from the admin system 1302. For example, the supervisory processes may create tasks, communicate with various components of the file servers, and performing authorizations (e.g., through AuthN and AuthZ). In some examples, where the primary file server 1306 and the secondary file server 1308 are each hosted on a plurality of host machines, the respective API gateways 1310 and 1320 may include instances distributed across the host machines of the primary file server 1306 and the secondary file server 1308. In some examples, one host machine (e.g., a leader node) may host an instance of the API gateway configured to communicate with the admin system 1302 and other host machines may host instances of the API gateway configured to communicate with the leader node. Accordingly, FSVMs hosted on various nodes of the primary file server 1306 and/or the secondary file server 1308 may send information to, and receive information from, the admin system 1302, including the file system manager 1304.
Scheduler 1312 and scheduler 1322 may be a scheduling service running on the primary file server 1306 and the secondary file server 1308, respectively. The scheduler 1312 may be a distributed scheduling service running on multiple (e.g., each) node (e.g., host machine) of a cluster hosting the primary file server 1306 and the scheduler 1322 may be a distributed scheduling service running on multiple (e.g., each) node of a cluster hosting the secondary file server 1308. The scheduler 1312 and the scheduler 1322 may be responsible for scheduling any function calls received from the admin system 1302 (e.g., from the file system manager 1304 via the API gateway) at intervals and/or at specific times and/or dates. In some examples, individual instances of the scheduler 1312 and 1322 may schedule operations for FSVMs hosted on the same host machine as the scheduler instance. For example, a replication job including snapshotting a share managed by an FSVM at a first host machine may be scheduled by a scheduler instance at that same host machine.
In some examples, the scheduler 1312 and 1322 may further include a remote procedure call (RPC) server responsible for serving RPC requests for managing replication policies, configuration, and policies at the primary file server 1306 and the secondary file server 1308, respectively. In some examples, the primary file server 1306 and the secondary file server 1308 may communicate with one another using such RPC servers. For example, requests to create, get, update, or delete policies (e.g., replication policies) may be managed by the schedulers 1312 and 1322. For example, where the scheduler 1312 receives a create, get, update, or delete request for a replication policy from the API gateway 1310, the scheduler 1312 may function to initiate a corresponding workflow at the primary file server 1306. When initiating such workflows, the scheduler 1312 may provide, to other components of the file server 1306, additional information such as identification of a source share, target file server (e.g., secondary file server 1308) IP address (or other identifier), and/or virtual machine details (e.g., identification of FSVMs at the source and/or destination file servers, and/or maps of components of the source file server to the destination file server).
Scheduler 1312 (e.g., the scheduler at the source file server) may add scheduled entities to local storage 1330 at the primary file server 1306. Local storage 1330 may refer to any storage in a storage pool of the primary file server 1306, which may include local storage devices of one or more nodes hosting FSVMs and forming primary file server 1306. Scheduled entities may be added for each policy and each schedule associated with a policy. A scheduled entity may include schedule details (e.g., a time and/or specific interval at which to make a function call) and the function call to be made according to the schedule details.
Replicator 1314 and replicator 1324 may include a primary replicator and node replicators for each node of the primary file server 1306 and the secondary file server 1308, respectively. A primary replicator may monitor for replication jobs created at the cluster (e.g., a cluster of computing nodes hosting the primary file server 1306 or the secondary file server 1308) and may assign the jobs or portions of the jobs to the node replicators. In some examples, the node replicators may register as job pools with the primary replicator, such that the primary replicator may assign jobs to individual nodes using a job based framework.
The replicator 1314 and the replicator 1324 may be responsible for carrying out replication workflows (e.g., jobs) scheduled for completion by the scheduler 1312 and 1322, respectively. For example, the replicators may take snapshots and send ZFS data streams to remote file servers. In the example shown in
Storage 1330 and storage 1332 may include different storage locations accessible at the primary file server 1306 and the secondary file server 1308, respectively. Various information and data, such as replication policies, share information for shares of the file server, mappings between the primary file server 1306 and the secondary file server 1308, details of jobs associated with various replication policies, dataset mappings, details of tasks associated with failover and failback workflows, states of jobs and policies, and the like. In various examples, the admin system 1302 may communicate with the primary file server 1306 to access information at storage 1330 and/or may communicate with the secondary file server 1308 to access information at storage 1332.
The configuration of the system 1300 is exemplary and may vary in some embodiments. For example, the admin system 1302 may communicate with additional file servers. Further, each of the admin system 1302, the primary file server 1306, and the secondary file server 1308 may host additional components, processes, and/or instances in various examples.
The first file server 1406 and the second file server 1408 may be used to implement and/or may be implemented by file servers and virtualized file servers described herein, such as virtualized file servers 106, 114, 122, 334, 336, 338, 408, 514, 516, 518, 614, 616, 618, and/or 732 and file servers 212, 220, 904, 906, 1042, 1040, 1306, and/or 1308. Accordingly, the first file server 1406 and the second file server 1408 may include multiple host machines hosting various software to implement the file server, such as FSVMs, virtualized storage controllers, and the like. The first file server 1406 and the second file server 1408 may referred to as a file server or files instance. As used herein, an instance may be a file server and/or a clustered instance of a file server.
The file system 1410 presented by the first file server and the file system 1412 presented by the second file server may be used to implement and/or may be implemented by file systems described herein, such as file systems 308, 310, 312, 314, 316, 318, 526, 528, 530, 532, 534, 536, 626, 628, 630, 632, 634, 636, 904, 1040, 1042, 1044, 1046, and/or 1132.
As shown, the shares 1418, 1420, 1422, and 1424 of the first file system 1410 correspond to shares 1426, 1428, 1430, and 1432 of the second file system 1412. However, in various examples, the first file system 1410 may include additional shares not corresponding to shares of the second file system 1412. Similarly, the second file system 1412 may include additional shares not corresponding to shares of the first file system 1410. In some examples, such additional shares may be configured for replication (e.g., backup) to other file servers.
The first file server 1406 at a first site 1402 is configured for replication to the second file server 1408 at a second site 1404. For example, shares 1418, 1420, and 1422 are associated with policies making the shares 1418, 1420, and 1422 available for read and write access at the first file server 1406. The associated policies replicate the shares 1418, 1420, and 1422 to the second file server 1408 at the second site 1404 as shares 1426, 1428, 1430, and 1432 of the second file server 1408. The shares 1418, 1420, and 1422 are configured to provide read only access at the second file server 1408. The second file server 1408 at the second site 1404 is also configured for replication to the first file server 1406 at the first site 1402. For example, share 1432 is associated with a policy making the share 1432 available for read and write access at the second file server 1408. The associated policy replicates the share 1432 to the first filer server 1406 at the first site 1402 as share 1424 of the first file server 1406. The share 1424 is configured for read only access at the first file server 1406.
With respect to shares 1418, 1420, and 1422, the first file server 1406 may be referred to as a source file server. With respect to shares 1426, 1428, and 1430, the second file server 1408 may be referred to as a target or destination file server hosting target or destination shares 1426, 1428, and 1430. As used herein, a target or destination server hosts target or destination shares, which are shares on the target or destination server where data from a source file server is copied. A target or destination file server may also be referred to as a remote file server, in various examples.
With respect to shares 1418, 1420, and 1422 of the first file server 1406 and shares 1426, 1428, and 1430 of the second file server 1408, the first file server 1406 and the second file server 1408 form an active-passive recovery environment. As used herein, an active-passive recovery environment is one where access to a primary site (e.g., the first site 1402) is read/write and access to a remote site (e.g., the second site 1404) is read-only for protocol clients. For example, the share 1432 at the second file server 1408 is read/write for clients (e.g., client 1416) accessing the share 1432 at the second file server 1408 while the corresponding share 1424 at the first file server 1406 is read-only for clients (e.g., client 1414) accessing the share 1424 at the first file server 1406. In an active-passive environment, the passive (e.g., backup) fileserver is active before full failover and accepts client connections and serves data over various protocols (e.g., NFS/SMB protocols) in read-only. Accordingly, access to the virtualized file server in case of a disaster at or failover from a primary (e.g., source) file server may be relatively quick.
In contrast to an active-passive environment, in an active-standby environment used in many backup solutions, the remote site has to be activated (e.g., a whole file server is constructed at the remote site) on failure of the source site in order to access data (e.g., storage items at the shares). An active-passive recovery environment results in quicker failover than an active-standby recovery environment, at least because the remote site is activated prior to failover. For example, the file system 1412 at the second file server 1408 is already established including the target shares 1426, 1428, and 1430 during replication of the shares 1418, 1420, and 1422 at the first file server 1406. In case of failure of the first file sever 1406, the second file server 1408 is already activated.
The first file server 1406 and the second file server 1408 may also be referred to as being in a one-way replication relationship in opposite directions. As used herein, a one-way replication relationship in opposite directions means multiple sites are writeable for different shares or targets. For example, the first file server 1406 may be writeable for shares 1418, 1420, and 1422, while the second file server 1408 may be writeable for share 1432. The first file server 1406 and the second file server 1408 are shown in a one-to-one deployment topology. As used herein, a one-to-one deployment topology is a topology where one source replicates data to only one target. In some examples, one or more shares of the first file server 1406 and/or the second file server 1408 may, instead be deployed using a one-to-many deployment topology, wherein one source replicates data to many targets. In some examples, one or more shares of the first file server 1406 and/or the second file server 1408 may be deployed using a many-to-one deployment topology, where multiple sources replicate data to a target, or a many-to-many deployment topology, where many source sites can replicate data to many targets. In some examples, the first file server 1406 and/or the second file server 1408 may be utilized in a cascaded deployment topology, where a target site for one replication relationship can also be a source site for another.
The policies associated with the shares may be configured using a file server manager (e.g., file server manager 1304) communicating with the first file server 1406 and the second file server 1408. A policy may include, for example, a policy name, a list of source shares for replication from the source file server, an identity of the target or destination file server, and/or a replication schedule. In some examples, the identity of the target or destination file server may include identification of a target share at the destination file server. Policies for shares of the first file server 1406 may be stored at the first file server 1406 (e.g., at local storage) and policies for shares of the second file server 1408 may be stored at the second file server 1408 (e.g., at local storage). In some examples, an admin system used to configure the replication policies may also store details of the policies.
The first file server 1506 and the second file server 1508 may be used to implement and/or may be implemented by file servers and virtualized file servers described herein, such as virtualized file servers 106, 114, 122, 334, 336, 338, 408, 514, 516, 518, 614, 616, 618, and/or 732 and file servers 212, 220, 904, 906, 1042, 1040, 1306, 1308, 1406 and/or 1408. Accordingly, the first file server 1506 and the second file server 1508 may include multiple host machines hosting various software to implement the file server, such as FSVMs, virtualized storage controllers, and the like.
The file system manager 1534 may be used to implement and/or may be implemented by file system managers described herein, such as file system managers 102, 406, 510, 604, and/or 1304. The file system manager 1534 may communicate with the both the first file server 1506 and the second file server 1508 to facilitate failover from the first file server 1506 to the second file server 1508. A user interface provided by the file system manager 1534 may be used to trigger failover from the first file server 1506 to the second file server 1508.
The replication process described herein may support both unplanned failovers and planned failovers. Both types of failures may be triggered by the user (e.g., an admin user). An unplanned failover may, in some examples, be triggered automatically upon detection of failure of the source file server (e.g., the first file server 1506). An unplanned failover may occur, for example, when a primary (e.g., first) site 1502 is down. The target (e.g., second) site 1504 can then be activated from the last successful snapshot per share. Clients 1514 and 1516 may then be migrated to the target site 1504 seamlessly. A planned failover may be a planned activity to change ownership of shares from the first file server 1506 to the second file server 1508. Clients 1514 and 1516 are migrated to the second file server 1508 on failover. Planned failovers may occur without data loss when the final delta replication is done as part of the planned failover workflow.
Generally, failover from the first file server 1506 to the second file server 1508 is used to mean that the second file server 1508 is serving all client requests originally directed to the first file server 1506. Failover can be a planned failover or an unplanned failover triggered through a communication to the file system manager 1534. In the case of a planned failover, a request for failover may be communicated to the file system manager 1534 prior to a scheduled failover to occur at a later time. Both unplanned and planned failovers may be triggered through user interaction with a user interface presented by the file system manager 1534 and/or an admin system. Planned failovers may generally be used, for example, to conduct maintenance, upgrades, or other operations on the first file server 1506. Unplanned failover may be used in the case of failure of the first file server 1506.
After failover from the first file server 1506 to the second file server 1508, the shares 1518, 1520, 1522, and 1524 at the first file server 1506 may be marked as read-only shares. In some examples, the shares 1518, 1520, 1522, and 1524 at the first file server 1506 may be inaccessible, and clients attempting to access the file system 1510 may be redirected to the second file server 1508. In some examples, the shares 1518, 1520, 1522, and 1524 may be configured to be inaccessible upon unplanned failover (e.g., in case of disaster at the first file server 1506). A user requesting planned failover may, in some examples, request that the shares 1518, 1520, 1522, and 1524 be configured to continue to serve read requests after failover to the second file server 1508. The shares 1526, 1528, 1530, and 1532 at the second file server 1508 may be configured to allow for both read and write requests. For example, permissions for the shares 1526, 1528, 1530, and 1532 may be changed at the file server 1508 to allow for both read and write requests by, for example, updating access information for the shares 1526, 1528, 1530, and 1532. Generally, the file system 1512 at the second file server 1508 may correspond to the file system 1510 at the first file server 1506, meaning that the shares 1526, 1528, 1530, and 1532 at the second file server 1508 correspond to the shares 1518, 1520, 1522, and 1524 of the first file server 1506.
In some examples, to complete failover from the first file server 1506 to the second file server 1508, the file system manager 1534 may communicate with an active directory and/or domain server to update domain information such that the second file server 1508 takes over for the first file server 1506. For example, upon failover, the file system manager 1534 may communicate with an active directory server or a domain server to assign an IP address of the first file server 1506 to the second file server 1508 such that requests directed to the IP address of the first file server 1506 are provided to a the second file server 1508. In some examples, such IP addresses may correspond to host machines and/or FSVMs of the first file server 1506 and/or the second file server 1508. For example, consider a failover scenario where the file server 1506 had failed over to the file server 1508. The file system manager 1534 may update a domain server and/or active directory server such that an IP address previously assigned to the file server 1506 (e.g., the IP address used to access one or more host machines of the file server 1506) is now assigned to the file server 1508 (e.g., the IP address may be used to access one or more host machines of the file server 1508). In this manner, when client 1514 requests access to share 1518 at the first file server 1506, the request may be provided to the corresponding share 1526 at the second file server 1508. Such redirection may, in various examples, be transparent or undetectable from the view of the client 1514.
Each row shown in the user interface 1600 may display details of replication policies applied to a particular file server in communication with the file server manager 1404. For example, row 1602 shows that a first protected file server is configured for replication from a source file server “LrAfsSrc” to a destination file server “LrAfsDst.” The replication is conducted in accordance with an applied policy “deptShr2P.” The user interface 1600 may also display the status of both file servers. For example, the row 1602 shows that both LrAfsScr and LrAfsDst are active (e.g., accepting read and write requests). Row 1604, shows that a second protected file server is configured for replication from a source file server “SrcDrTest” to a destination file server “DstDrTest,” where the source file server is active and the destination file server is in standby mode (e.g., shares may be accessed on a read-only basis at the destination file server). The row 1604 shows that several policies are applied to the second source file server. For example, different policies may be used for different shares of the source file server based on desired replication frequency for the shares.
The user interface 1600 may further show actions that can be initiated with respect to each protected file server. For example, through the user interface 1600, a user may trigger the file server manager 1404 to start, resume, and/or halt replication from the first source file server to the first destination file server. The user may also, through the user interface 1600, trigger a failover from the second source file server to the second destination file server.
At block 2602, the file system manager 1304 receives a replication policy for a share of a file server via an administrative user interface. In various examples, the user interface may include fields for entering information for a particular replication policy such as, for example, a policy name, a list of shares of the source file server to be protected by the policy, identity of the destination file server, target shares of the destination file server, and/or a replication schedule. For example, a user may access the admin system 1302 and/or the file system manager 1304 to configure the replication policies by selecting a list of shares from a source file server (e.g., the source file server 1306), a target file server (e.g., the destination file server 1308), and a replication frequency. Using such share based replication, an administrative user may select individual shares for replication instead of replicating a complete file server. Further, shares can be replicated at different frequencies such that, for example, higher priority shares may be backed-up frequently and lower priority shares may be backed-up less frequently, reducing the amount of backup operations when contrasted with a full file server backup.
The file system manager 1304 validates the replication policy at block 2604. Example validation checks may verify that the source and destination file servers are compatible (e.g., configured for replication, using the same protocols, have matching authentication types, and the like), that the source shares covered by the policy do not exist in another policy as a source share or a target share, that the source and target shares are reachable, and/or that there are no conflicting tasks (e.g., another policy being created or updated) which may conflict with the pending policy. In some examples, the admin system 1302 may provide error messages to a user (e.g., through the administrator interface) if a validation check is failed.
At block 2606, the file system manager 1304 communicates the replication policy to the source file server and/or the destination file server. In some examples, the file system manager 1304 may use registration information for the source file server and the destination file server to communicate with the source file server and the destination file server, respectively. For example, the file system manager 1304 may use access credentials for the first file server 1306 to communicate with and access the first file server 1306. The file system manager 1306 may also, in some examples, use information about the number and location of FSVMs in the first file server 1306 to communicate with the first file server 1306. For example, where a share of the first file server 1306 is hosted at a first host machine of the first file server 1306, the file server manager 1304 may communicate with an instance of the API gateway at the first host machine to configure the policy at the first file server 1306. Other registration information, such as IP addresses of components of the file servers, share locations, and the like may also be used by the file server manager 1304 to communicate a replication policy to the source file server and/or the destination file server.
In some examples, the file system manager 1304 may create the policy in a database of the admin system 1302 with a creation status of “in progress” before communicating the replication policy to the source file server. The file system manager 1304 may then send the policy to the source file server using a REST API request communicated to the API gateway of the source file server as a task for completion by the source file server. The file system manager 1304 and/or the admin system 1302 may periodically poll the creation task until completion. The status of the task at the admin system 1302 may remain as “in progress” until completion. In the event of task failure, the status may be changed to “failed” and the admin system 1302 may roll back to previous protection policies for the source file server. When the task succeeds, the file system manager 1304 may, in some examples, receive a source-target mapping (e.g., mapping 1334) from the source file server and may update the policy in the admin database with the source-target mapping. The task may then be marked as “successful” by the admin system 1302.
Once the file system manager 1304 communicates the replication policy to the source file server, the source file server may perform one or more tasks associated with policy creation at the source file server. For example, the scheduler 1312 at the source file server 1306 may run validation checks to determine whether the source volume group count (e.g., volume groups at the source file server 1306) matches the expected target volume group count. The source file server 1306 may send, via the API gateway 1310, details of the remote file server to the admin system 1302.
The source file server 1306 may further send a request (e.g., a RPC request) to the destination file server 1308 to create shares on the destination file server 1308 to implement the policy. For example, where a new policy specifies target shares at the destination file server 1308 that do not yet exist at the destination file server 1308, the source file server 1306 may communicate a request for share creation to the destination file server 1308. In some examples, the source file server 1306 and/or the destination file server 1308 may track creation of such shares and may report on successful creation or failure to successfully create the shares to the admin system 1302. For example, the destination file server 1308 may create shares with the requested attributes and may communicate to the source file server 1306 and/or the admin system 1302 when such shares are successfully created. In some examples, the admin system 1302 may generate an alert (e.g., through the administrative user interface) regarding the status of share creation at the destination file server 1308.
The source file server 1306 may further send a request (e.g., a RPC request) to the destination file server 1308 to generate a dataset map. The source file server 1306 may use the dataset map to create a mapping (e.g., mapping 1334) between shares of the source file server 1306 and shares of the destination file server 1308. The mapping may be referred to, in some examples, as a source target map and/or a source destination map. The mapping may further include a mapping between file server virtual machines of the source file server 1306 and file server virtual machines of the destination file server 1308. In some examples, the source file server 1306 may send a REST API communication to the destination file server 1308 after creating the mapping and the destination file server 1308 may create a reverse source target map at the destination file server 1308.
The completed policy may be stored at a location accessible to the source file server 1306 (e.g., local storage 1330), a location accessible to the destination file server 1308 (e.g., local storage 1332), at local storage of the admin system 1302, and/or at a shared storage location accessible by the source file server 1306, the destination file server 1308, and/or the admin system 1302. At the source file server 1306, storing the replication policy at local storage 1330 may trigger a watch callback for schedule entities and may add policies in memory for use by the scheduler 1312 during replication. In some examples, once the policy is created and the shares are successfully created at the destination file server 1308, the policy may be visible through the user interface of the admin system 1302. For example, user interface 1700 of
In various examples, once a replication policy is created for shares at the primary file server 1306 to be replicated to the secondary file server 1308, the primary file server 1306 may serve client read and write requests for the covered shares. Once the shares have been replicated to corresponding target shares at the secondary file server 1308, the secondary file server 1308 may serve client read requests for the covered shares using the corresponding target shares. The secondary file server 1308 may continue such read requests before failover from the primary file server 1306 to the secondary file server 1308.
In some examples, the method 2600 may further include updating a policy created at blocks 2602, 2604, and 2606. For example, a user may request, through a user interface presented by the admin system 1302, to update one or more replication policies is use by the file servers in communication with the admin system 1302. For example, user interface 2100, which provides a detailed policy view, also provides an option to edit or update the policy. Through such a user interface, the admin system 1302 may receive an updated policy name, list of shares to be protected under the policy, identity of the destination file server 1308, replication schedule, and/or other relevant policy information. In some examples, upon receiving a request to edit and/or update a policy, the admin system 1302 may send a request to the source file server 1306 and/or the destination file server 1308 to cancel any pending jobs associated with the established policy. The admin system 1302 may then run validation checks and communicate with the source file server 1306 and/or the destination file server 1308 to create the updated policy as described, for example, with respect to blocks 2602, 2604, and 2606 of the method 2600.
In some examples, the method 2600 may further include deleting a policy created at blocks 2602, 2604, and 2606. For example, a user may request, through a user interface presented by the admin system 1302, to update one or more replication policies is use by the file servers in communication with the admin system 1302. For example, user interface 2100, which provides a detailed policy view, also provides an option to delete an existing policy. Upon receipt of a request to delete a policy, the admin system 1302 may connect to the source file server 1306 to request deletion of the policy at the source file server 1306. The source file server 1306 may, in some examples, mark information in the source target map associated with the policy as “not in use” to allow for the policy to be recreated in the future, if desired, without reconstructing the source target map information associated with the policy. The source file server 1306 may further delete schedules associated with the policy, deleting schedules associated with policy in memory used by the scheduler. Further, all pending jobs associated with the policy may be cancelled. Upon successful deletion of the schedules associated with the policy and cancellation of pending jobs associated with the policy, the source file server 1306 may communicate successful deletion of the policy to the admin system 1302. The admin system 1302 may then send a notification of successful deletion to the user interface.
At block 2702, a file server accesses a replication policy for a share, where the replication policy includes a replication schedule. The replication policy may be stored locally at the source file server 1306. In some examples, the source file server 1306 may access the replication policy when triggered by the scheduler 1312 to begin replication of a share of the file server 1306.
The file server creates a snapshot of the share at block 2704. In some examples, the snapshot may be a ZFS dataset snapshot. In such examples, a first replication may be a full replication using a base snapshot. Subsequent replications may then transfer only the data difference between the previous snapshot and a new snapshot (e.g., a delta snapshot). In various examples, the replicator 1314 may create snapshots using the job framework, by scheduling a replication job 1318. The replication job may store information such as source and target file server information, share information, and dataset mapping. The replication job 1318 may, in some examples, include sub-jobs. The replication job 1318 may, for example, monitor the sub-jobs used to replicate the share. The dataset mapping of the replication job may identify one or more FSVMs of the source file server 1306 hosting at least a portion of the share to be replicated. The replication job 1318 may create sub jobs at each FSVM, instructing the FSVMs to snapshot the share. The FSVMs may then access the data corresponding to the share using, for example, file system mappings at the FSVM.
In some examples, snapshots may be associated with expiration time metadata to indicate when a snapshot may be deleted. For example, an hourly snapshot with a retention number or 24 may have an expiration time of the current time (e.g., time of snapshot)+24 hours. Accordingly, the snapshot is not deleted until the expiration time is passed. In some examples, if a previous replication job is running, the triggered replication job may be queued such that the current running replication job will create a new job upon completion. If there is already a queued job, the previous entry may be overwritten with the new snapshot.
At block 2706, the file server 1306 transmits the snapshot to a destination file server 1308. In some examples, replication may include pre-negotiation between the source file server 1306 and the destination file server 1308, which pre-negotiation may occur through direct communication and/or using the file system manager. Such pre-negotiation may determine whether the snapshot transmitted from the source file server 1306 to the destination file server 1308 is a base snapshot or an incremental replication for use on top of an existing base snapshot. Pre-negotiation may further determine a most recent common snapshot between the source file server 1306 and the destination file server 1308. Based on the pre-negotiation, the replication may be classified as a base replication or an incremental replication. In some examples, transmission of the snapshot may occur by streaming data (e.g., using gRPC) from the source file server 1306 to the destination file server 1308.
In some examples, such as where a share is distributed across multiple FSVMs, multiple streams may be used to transmit a snapshot from the source file server 1306 to the destination file server 1308. The multiple streams may be managed by sub jobs created by the replication job 1318. For example, a first FSVM hosting a first portion of the share may stream data to a corresponding second FSVM at the destination file server 1308. Meanwhile, a third FSVM at the source file server 1306 may stream data to a corresponding fourth FSVM at the destination file server 1308. In some examples, the FSVMs may further communicate with virtualized storage controllers (e.g., CVMs 1024 and/or CVMs 1026) and/or hypervisors to locate share data for replication. In such examples, the virtualized storage controllers may access specific volume groups and/or virtualized disks including share data.
Once the replication job is complete and/or all sub-jobs created by the replication job are complete, the source file server 1306 may communicate with the admin system 1302 with an updated status for the replication job. The admin system may, in some examples, display the results of the replication job, such as in user interfaces 1800 and 1900.
At block 2802, the file system manager 1304 receives a request for an unplanned failover from a first file server to a second file server. The request may be received through a user interface displayed by the admin system 1302. For example, a user may select the “failover” element of user interface 1600 to begin an unplanned failover. Other user interfaces presented by the admin system 1302 may provide alternative methods of triggering an unplanned failover. In some examples, the user may select the failed primary file server from a list of available primary file servers. Choosing a primary file server may select shares that are mapped to the standby file server (e.g., destination file server 1308).
The file system manager 1304 updates permissions for shares at a second file server at block 2804. Permissions may be, for example, adding permission to write to storage items at the second file server. Once a request for unplanned failover is received, the admin system 1302 may send a request to the destination file server 1308 through the API gateway 1320 to update permissions on the shares to fail over. At the destination file server 1308, the API gateway 1320 may communicate with instances of the replicator 1324 at various nodes of the destination file server 1308 to update permissions to the shares to make the shares available for both read and write access. As part of updating permissions, FSVMs and/or the replicator 1324 may identify the last successful snapshot of a share for access. For example, if a replication job is incomplete, the replicator 1324 may roll back the share to the last complete snapshot.
The file system manager 1304 redirects client connections to the second file server at block 2806. Clients may be redirected to the destination file server 1308 by updating domain name service mappings such that the destination file server 1308 takes over for the source file server 1306. Redirection may further include updating service principle names of the source file server 1306 to the destination file server 1308 account in the active directory. For example, IP addresses associated with the source file server 1306 may be updated to redirect to the destination file server 1308 such that client requests for the source file server 1306 are redirected to the destination file server 1308. In some examples, the file system manager 1304 may, in a failover request to the destination file server 1308, request that the destination file server 1308 (e.g., the replicator 1324 at the destination file server 1308) update such information by communicating directly with the active directory/domain server 1328.
After the unplanned failover, the backup file server (e.g., the destination file server 1308) is activated for all the shares, meaning that the shares are available for read and write access at the destination file server 1308.
At block 2902, the file system manager 1304 receives a request for planned failover from a first file server to a second file server. The request may be received through a user interface displayed by the admin system 1302. For example, a user may select the “failover” element of user interface 1600 to begin an planned failover. Other user interfaces presented by the admin system 1302 may provide alternative methods of triggering a planned failover. In some examples, the admin system 1302 may provide a user interface to schedule a planned failover for some future time. In some examples, after receiving a request for planned failover, the file system manager 1304 may cancel future replication jobs at the destination file server 1308 and/or may notify the user of replication jobs still in progress, such that the planned failover is less likely to interrupt in-progress replication jobs.
The file system manager 1304 updates policies and permissions for shares at the first file server at block 2904. Updating permissions may include, for example, making storage items for shares at the first file server 1306 read-only. The file system manager may update the policies and permissions for shares at the first file server by communicating with the first file server 1306 (e.g., through the API gateway 1310). At the source file server 1306, the API gateway 1310 may communicate with instances of the replicator 1314 at various nodes of the source file server 1306 to update permissions to the shares to make the shares available for only read access and/or to make the shares unavailable for any access, depending on user preferences and/or system configuration.
At block 2906, the file system manager 1304 updates permissions for shares at the second file server. The admin system 1302 may send a request to the destination file server 1308 through the API gateway 1320 to update permissions on the shares to fail over. At the destination file server 1308, the API gateway 1320 may communicate with instances of the replicator 1324 at various nodes of the destination file server 1308 to update permissions to the shares to make the shares available for both read and write access.
The file system manager 1304 redirects client connections to the second file server at block 2908. Clients may be redirected to the destination file server 1308 by updating domain name service mappings such that the destination file server 1308 takes over for the source file server 1306. For example, IP addresses associated with the source file server 1306 may be updated to redirect to the destination file server 1308 such that client requests for the source file server 1306 are redirected to the destination file server 1308. In some examples, the file system manager 1304 may, in a failover request to the destination file server 1308, request that the destination file server 1308 (e.g., the replicator 1324 at the destination file server 1308) update such information by communicating directly with the active directory/domain server 1328.
At block 3002, the file system manager 1304 receives a request for resuming replication from a first file server 1306. The request to resume replication may be received through a user interface displayed by the admin system 1302, such as user interface 2400 and/or user interface 2500. Other user interfaces presented by the admin system 1302 may provide alternative methods of resuming replication.
The file system manager 1304 configures replication policies at the first file server at block 3004. Configuring replication policies may include, for example, re-activating previously deactivated replication policies at the source file server 1306. In some examples, before configuring replication policies, the file system manager 1304 may reverse replication from the destination file server 1308 to the source file server 1306 to capture changes made to the storage items made during failover to the destination file server 1308. The file system manager 1304 may then continue to configure replication from the source file server 1306 to the destination file server 1308. The file system manager 1304 may configure the replication policies using one or more operations of the method 2600.
At block 3006, the file system manager 1304 updates policies and permissions for shares at a second file server. The file system manager 1304 may send a request to the destination file server 1308 through the API gateway 1320 to update permissions on the shares to fail over. At the destination file server 1308, the API gateway 1320 may communicate with instances of the replicator 1324 at various nodes of the destination file server 1308 to update permissions to the shares to make the shares available for only read access.
The file system manager 1304 redirects client connections to the first file server at block 3008. Clients may be redirected to the source file server 1306 by updating domain name service mappings such that the source file server 1306 takes over for the destination file server 1308.
While the method 3000 is described with respect to two file servers, in various examples, failback may include additional file servers. For example, a source file server may replicate some shares to a first destination file server and some shares to a second destination file server. The source file server may, accordingly, fail over to both the first destination file server and the second destination file server. Accordingly, failback may include failback from the first destination file server and the second destination file server.
The file system manager 1304 receives a request for planned failback from a second file server to a first file server at block 3102. The request for planned failback may be received through a user interface displayed by the admin system 1302. A planned failback may be similar to a planned failover. For example, the file system manager 1304 may update permissions for the share at each of the file servers and redirect clients to the first file server from the second file server.
At block 3104, the file system manager 1304 updates policies and permissions for shares at the second file server. The file system manager 1304 may send a request to the destination file server 1308 through the API gateway 1320 to update permissions on the shares to fail over. At the destination file server 1308, the API gateway 1320 may communicate with instances of the replicator 1324 at various nodes of the destination file server 1308 to update permissions to the shares to make the shares available for only read access.
The file system manager 1304 updates permissions for shares at the first file server at block 3106. The file system manager 1304 may send a request to the source file server 1306 through the API gateway 1310 to update permissions on the shares to fail over. At the source file server 1306, the API gateway 1310 may communicate with instances of the replicator 1314 at various nodes of the source file server 1306 to update permissions to the shares to make the shares available for read and write access.
At block 3108, the file system manager 1304 redirects client connections to the first file server. Clients may be redirected to the source file server 1306 by updating domain name service mappings such that the source file server 1306 takes over for the destination file server 1308.
The above methods provide for share based replication and quick failover using active-passive backup configurations. Replication and disaster recovery may facilitate share-level data replication and file-server-level disaster recover. In the event of a planned or unplanned loss of service, write access can be restored to protected shares by failing-over to a recovery site file server. Protection policies may indicate failover details, including the primary location, recovery location, and replication schedule. Rather than having a single protection policy for an entire file server, unique policies may be configured for different shares without tracking where, physically, the shares are stored within the file system.
From the foregoing it will be appreciated that, although specific embodiments have been described herein for purposes of illustration, various modifications may be made while remaining with the scope of the claimed technology.
Examples described herein may refer to various components as “coupled” or signals as being “provided to” or “received from” certain components. It is to be understood that in some examples the components are directly coupled one to another, while in other examples the components are coupled with intervening components disposed between them. Similarly, signal may be provided directly to and/or received directly from the recited components without intervening components, but also may be provided to and/or received from the certain components through intervening components.
This application claims priority to U.S. Provisional Application No. 63/260,438, entitled “File Server Managers and Systems for Managing Virtualized File Servers,” filed Aug. 19, 2021. This application claims priority to U.S. Provisional Application No. 63/264,204, entitled “Share-Based Disaster Recovery for Distributed File Server,” filed Nov. 17, 2021. The aforementioned applications are incorporated herein by reference, in their entirety, for any purpose.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5276867 | Kenley et al. | Jan 1994 | A |
| 5664144 | Yanal et al. | Sep 1997 | A |
| 5870555 | Pruett et al. | Feb 1999 | A |
| 5873085 | Enoki et al. | Feb 1999 | A |
| 5924096 | Draper et al. | Jul 1999 | A |
| 6044367 | Wolff | Mar 2000 | A |
| 6055543 | Christensen et al. | Apr 2000 | A |
| 6085234 | Pitts et al. | Jul 2000 | A |
| 6101508 | Wolff | Aug 2000 | A |
| 6212531 | Blea et al. | Apr 2001 | B1 |
| 6289356 | Hitz et al. | Sep 2001 | B1 |
| 6341340 | Tsukerman et al. | Jan 2002 | B1 |
| 6442602 | Choudhry | Aug 2002 | B1 |
| 6539381 | Prasad et al. | Mar 2003 | B1 |
| 6963914 | Breitbart et al. | Nov 2005 | B1 |
| 6968345 | Muhlestein | Nov 2005 | B1 |
| 7120631 | Vahalia et al. | Oct 2006 | B1 |
| 7159056 | Goldick | Jan 2007 | B2 |
| 7162467 | Eshleman et al. | Jan 2007 | B2 |
| 7356679 | Le et al. | Apr 2008 | B1 |
| 7366738 | Yorke et al. | Apr 2008 | B2 |
| 7409511 | Edwards et al. | Aug 2008 | B2 |
| 7606868 | Le et al. | Oct 2009 | B1 |
| 7702843 | Chen et al. | Apr 2010 | B1 |
| 7707618 | Cox et al. | Apr 2010 | B1 |
| 7725671 | Prahlad et al. | May 2010 | B2 |
| 7752492 | Armangau et al. | Jul 2010 | B1 |
| 7774391 | Le et al. | Aug 2010 | B1 |
| 7805469 | Nagaralu et al. | Sep 2010 | B1 |
| 7805511 | Panicker et al. | Sep 2010 | B1 |
| 7840533 | Prahlad et al. | Nov 2010 | B2 |
| 7890529 | Srinivasan et al. | Feb 2011 | B1 |
| 7937453 | Hayden et al. | May 2011 | B1 |
| 8095810 | Matsuzawa et al. | Jan 2012 | B2 |
| 8095931 | Chen et al. | Jan 2012 | B1 |
| 8352482 | Hansen | Jan 2013 | B2 |
| 8352608 | Keagy et al. | Jan 2013 | B1 |
| 8359594 | Davidson et al. | Jan 2013 | B1 |
| 8365167 | Beaty et al. | Jan 2013 | B2 |
| 8407448 | Hayden et al. | Mar 2013 | B1 |
| 8447728 | Prahlad et al. | May 2013 | B2 |
| 8473462 | Banerjee | Jun 2013 | B1 |
| 8484163 | Yucel et al. | Jul 2013 | B1 |
| 8484356 | Douglis et al. | Jul 2013 | B1 |
| 8539076 | Nakano et al. | Sep 2013 | B2 |
| 8543790 | Chen et al. | Sep 2013 | B2 |
| 8549518 | Aron et al. | Oct 2013 | B1 |
| 8601473 | Aron et al. | Dec 2013 | B1 |
| 8635351 | Astete et al. | Jan 2014 | B2 |
| 8646089 | Jayanthi et al. | Feb 2014 | B2 |
| 8688660 | Sivasubramanian et al. | Apr 2014 | B1 |
| 8700573 | Enko et al. | Apr 2014 | B2 |
| 8719522 | Chait et al. | May 2014 | B1 |
| 8725679 | Nair et al. | May 2014 | B2 |
| 8751515 | Xing et al. | Jun 2014 | B1 |
| 8762335 | Prahlad et al. | Jun 2014 | B2 |
| 8805951 | Faibish et al. | Aug 2014 | B1 |
| 8838923 | Prahlad et al. | Sep 2014 | B2 |
| 8850130 | Aron et al. | Sep 2014 | B1 |
| 8863124 | Aron | Oct 2014 | B1 |
| 8909753 | Nakamura et al. | Dec 2014 | B2 |
| 8914429 | Pitts | Dec 2014 | B2 |
| 8935563 | Rajaa et al. | Jan 2015 | B1 |
| 8949557 | Kamei et al. | Feb 2015 | B2 |
| 8966188 | Bardale | Feb 2015 | B1 |
| 8983952 | Zhang et al. | Mar 2015 | B1 |
| 8996783 | Huang et al. | Mar 2015 | B2 |
| 9009106 | Aron et al. | Apr 2015 | B1 |
| 9043567 | Modukuri et al. | May 2015 | B1 |
| 9060014 | Crowley | Jun 2015 | B2 |
| 9069708 | Gill et al. | Jun 2015 | B2 |
| 9152628 | Stacey et al. | Oct 2015 | B1 |
| 9154535 | Harris | Oct 2015 | B1 |
| 9165003 | Tummala et al. | Oct 2015 | B1 |
| 9201698 | Ashok et al. | Dec 2015 | B2 |
| 9201704 | Chang et al. | Dec 2015 | B2 |
| 9201887 | Earl et al. | Dec 2015 | B1 |
| 9208210 | Erofeev | Dec 2015 | B2 |
| 9213513 | Hartz et al. | Dec 2015 | B2 |
| 9244674 | Waterman et al. | Jan 2016 | B2 |
| 9244969 | Love et al. | Jan 2016 | B1 |
| 9256475 | Aron et al. | Feb 2016 | B1 |
| 9256612 | Bhatt et al. | Feb 2016 | B1 |
| 9268586 | Voccio et al. | Feb 2016 | B2 |
| 9274817 | Fan et al. | Mar 2016 | B1 |
| 9286298 | Gillett, Jr. | Mar 2016 | B1 |
| 9292327 | Von Thenen et al. | Mar 2016 | B1 |
| 9336132 | Aron et al. | May 2016 | B1 |
| 9348702 | Hsu et al. | May 2016 | B2 |
| 9405566 | Chawla et al. | Aug 2016 | B2 |
| 9411628 | Bezbaruah et al. | Aug 2016 | B2 |
| 9448887 | Ben Dayan et al. | Sep 2016 | B1 |
| 9495478 | Hendrickson et al. | Nov 2016 | B2 |
| 9497257 | Love et al. | Nov 2016 | B1 |
| 9513946 | Sevigny et al. | Dec 2016 | B2 |
| 9519596 | Coppola et al. | Dec 2016 | B2 |
| 9535907 | Stringham | Jan 2017 | B1 |
| 9563555 | Flynn et al. | Feb 2017 | B2 |
| 9571561 | Jang | Feb 2017 | B2 |
| 9619257 | Aron et al. | Apr 2017 | B1 |
| 9634990 | Lee | Apr 2017 | B2 |
| 9639428 | Boda et al. | May 2017 | B1 |
| 9652265 | Narayanasamy et al. | May 2017 | B1 |
| 9658899 | Jenkins | May 2017 | B2 |
| 9690670 | Paulzagade et al. | Jun 2017 | B1 |
| 9733958 | Cul et al. | Aug 2017 | B2 |
| 9740436 | Fiebrich-Kandler et al. | Aug 2017 | B2 |
| 9740472 | Sohi et al. | Aug 2017 | B1 |
| 9740723 | Prahlad et al. | Aug 2017 | B2 |
| 9747287 | Bhardwaj et al. | Aug 2017 | B1 |
| 9772866 | Aron et al. | Sep 2017 | B1 |
| 9832136 | Gibson | Nov 2017 | B1 |
| 9846706 | Basov et al. | Dec 2017 | B1 |
| 9853978 | Tellvik et al. | Dec 2017 | B2 |
| 9870291 | Bezbaruah et al. | Jan 2018 | B2 |
| 9886215 | Ramachandran et al. | Feb 2018 | B1 |
| 9893988 | Agarwal et al. | Feb 2018 | B2 |
| 9940154 | Ramani et al. | Apr 2018 | B2 |
| 9946573 | Mcdermott | Apr 2018 | B2 |
| 9952782 | Chandrasekaran et al. | Apr 2018 | B1 |
| 10009215 | Shorey | Jun 2018 | B1 |
| 10050862 | Nambiar et al. | Aug 2018 | B2 |
| 10083022 | Yuto et al. | Sep 2018 | B2 |
| 10084873 | Dornemann | Sep 2018 | B2 |
| 10095506 | Gopalapura Venkatesh et al. | Oct 2018 | B2 |
| 10101989 | Sinha et al. | Oct 2018 | B2 |
| 10114706 | Chougala et al. | Oct 2018 | B1 |
| 10127059 | Astete et al. | Nov 2018 | B2 |
| 10140115 | Fukui et al. | Nov 2018 | B2 |
| 10152233 | Xu et al. | Dec 2018 | B2 |
| 10210048 | Sancheti | Feb 2019 | B2 |
| 10248657 | Prahlad et al. | Apr 2019 | B2 |
| 10310953 | Mjayan et al. | Jun 2019 | B2 |
| 10311153 | Mason, Jr. et al. | Jun 2019 | B2 |
| 10367753 | Schultze et al. | Jul 2019 | B2 |
| 10394547 | Fukui et al. | Aug 2019 | B2 |
| 10419426 | Bakshan et al. | Sep 2019 | B2 |
| 10484894 | Gonzalez et al. | Nov 2019 | B2 |
| 10523592 | Byers et al. | Dec 2019 | B2 |
| 10530742 | Shah et al. | Jan 2020 | B2 |
| 10540164 | Bafna et al. | Jan 2020 | B2 |
| 10540165 | Bafna et al. | Jan 2020 | B2 |
| 10540166 | Arikatla et al. | Jan 2020 | B2 |
| 10541064 | Lee et al. | Jan 2020 | B2 |
| 10719305 | Sinha et al. | Jul 2020 | B2 |
| 10719306 | Deshmukh et al. | Jul 2020 | B2 |
| 10719307 | Kanada et al. | Jul 2020 | B2 |
| 10728090 | Deshmukh et al. | Jul 2020 | B2 |
| 10809998 | Gopalapura Venkatesh et al. | Oct 2020 | B2 |
| 10824455 | Arikatla et al. | Nov 2020 | B2 |
| 10831465 | Sharpe et al. | Nov 2020 | B2 |
| 10838708 | Sinha et al. | Nov 2020 | B2 |
| 10949192 | Gopalapura Venkatesh et al. | Mar 2021 | B2 |
| 11025626 | Todd et al. | Jun 2021 | B1 |
| 11086826 | Thummala et al. | Aug 2021 | B2 |
| 11106447 | Gupta et al. | Aug 2021 | B2 |
| 11281484 | Bafna et al. | Mar 2022 | B2 |
| 11288239 | Bafna | Mar 2022 | B2 |
| 11294777 | Venkatesh et al. | Apr 2022 | B2 |
| 11347601 | Nachiappan et al. | May 2022 | B1 |
| 20010047400 | Coates et al. | Nov 2001 | A1 |
| 20020069196 | Betros et al. | Jun 2002 | A1 |
| 20020120763 | Miloushev et al. | Aug 2002 | A1 |
| 20030014442 | Shiigi et al. | Jan 2003 | A1 |
| 20030115218 | Bobbitt | Jun 2003 | A1 |
| 20030163597 | Hellman et al. | Aug 2003 | A1 |
| 20030195942 | Muhlestein et al. | Oct 2003 | A1 |
| 20040054777 | Ackaouy et al. | Mar 2004 | A1 |
| 20040199734 | Rajamani et al. | Oct 2004 | A1 |
| 20040210591 | Hirschfeld | Oct 2004 | A1 |
| 20040225742 | Loaiza et al. | Nov 2004 | A1 |
| 20040267832 | Wong et al. | Dec 2004 | A1 |
| 20050120160 | Plouffe et al. | Jun 2005 | A1 |
| 20050120180 | Schorbach et al. | Jun 2005 | A1 |
| 20050125503 | Iyengar et al. | Jun 2005 | A1 |
| 20050193221 | Yoneyama | Sep 2005 | A1 |
| 20050193245 | Hayden et al. | Sep 2005 | A1 |
| 20050226059 | Kavuri et al. | Oct 2005 | A1 |
| 20050228798 | Shepard et al. | Oct 2005 | A1 |
| 20060010227 | Atluri | Jan 2006 | A1 |
| 20060047685 | Dearing et al. | Mar 2006 | A1 |
| 20060080445 | Chang et al. | Apr 2006 | A1 |
| 20060167921 | Grebus et al. | Jul 2006 | A1 |
| 20060206901 | Chan | Sep 2006 | A1 |
| 20060224918 | Koike | Oct 2006 | A1 |
| 20060225065 | Chandhok et al. | Oct 2006 | A1 |
| 20060271510 | Harward et al. | Nov 2006 | A1 |
| 20060271931 | Harris et al. | Nov 2006 | A1 |
| 20070022129 | Bahar et al. | Jan 2007 | A1 |
| 20070038913 | Allen et al. | Feb 2007 | A1 |
| 20070100905 | Masters et al. | May 2007 | A1 |
| 20070171921 | Wookey | Jul 2007 | A1 |
| 20070179991 | Burnett et al. | Aug 2007 | A1 |
| 20070179995 | Prahlad et al. | Aug 2007 | A1 |
| 20070300220 | Seliger et al. | Dec 2007 | A1 |
| 20080040483 | Nakatani et al. | Feb 2008 | A1 |
| 20080071997 | Loaiza et al. | Mar 2008 | A1 |
| 20080098194 | Hashimoto et al. | Apr 2008 | A1 |
| 20080104349 | Maruyama et al. | May 2008 | A1 |
| 20080104589 | Mccrory et al. | May 2008 | A1 |
| 20080114854 | Wong et al. | May 2008 | A1 |
| 20080133486 | Fitzgerald et al. | Jun 2008 | A1 |
| 20080134178 | Fitzgerald et al. | Jun 2008 | A1 |
| 20080189468 | Schmidt et al. | Aug 2008 | A1 |
| 20080201414 | Amir et al. | Aug 2008 | A1 |
| 20080201457 | London | Aug 2008 | A1 |
| 20080229142 | Anand et al. | Sep 2008 | A1 |
| 20080263113 | Krishnaiyer et al. | Oct 2008 | A1 |
| 20080270677 | Kolakowski | Oct 2008 | A1 |
| 20080320499 | Suit | Dec 2008 | A1 |
| 20080320583 | Sharma | Dec 2008 | A1 |
| 20090006801 | Shultz et al. | Jan 2009 | A1 |
| 20090100248 | Kami | Apr 2009 | A1 |
| 20090150885 | Safari et al. | Jun 2009 | A1 |
| 20090158082 | Jain et al. | Jun 2009 | A1 |
| 20090171971 | Goddard et al. | Jul 2009 | A1 |
| 20090193272 | Matsuzawa et al. | Jul 2009 | A1 |
| 20090216975 | Halperin et al. | Aug 2009 | A1 |
| 20090248870 | Kamei et al. | Oct 2009 | A1 |
| 20090249470 | Litvin et al. | Oct 2009 | A1 |
| 20090254572 | Redlich et al. | Oct 2009 | A1 |
| 20090271412 | Lacapra et al. | Oct 2009 | A1 |
| 20090287887 | Matsuki et al. | Nov 2009 | A1 |
| 20090288084 | Astete et al. | Nov 2009 | A1 |
| 20100023521 | Arcese et al. | Jan 2010 | A1 |
| 20100070725 | Prahlad et al. | Mar 2010 | A1 |
| 20100082716 | Agetsuma et al. | Apr 2010 | A1 |
| 20100082774 | Pitts | Apr 2010 | A1 |
| 20100095289 | Nguyen et al. | Apr 2010 | A1 |
| 20100138921 | Na | Jun 2010 | A1 |
| 20100174745 | Ryan et al. | Jul 2010 | A1 |
| 20100214908 | Raley | Aug 2010 | A1 |
| 20100241785 | Chen et al. | Sep 2010 | A1 |
| 20100250824 | Belay | Sep 2010 | A1 |
| 20100275205 | Nakajima | Oct 2010 | A1 |
| 20110022694 | Dalal et al. | Jan 2011 | A1 |
| 20110022695 | Dalal et al. | Jan 2011 | A1 |
| 20110022812 | Van et al. | Jan 2011 | A1 |
| 20110022883 | Hansen | Jan 2011 | A1 |
| 20110047340 | Olson et al. | Feb 2011 | A1 |
| 20110078318 | Desai et al. | Mar 2011 | A1 |
| 20110119668 | Calder et al. | May 2011 | A1 |
| 20110119763 | Wade et al. | May 2011 | A1 |
| 20110125835 | Soltis | May 2011 | A1 |
| 20110137879 | Dubey | Jun 2011 | A1 |
| 20110161299 | Prahlad et al. | Jun 2011 | A1 |
| 20110179414 | Goggin. et al. | Jul 2011 | A1 |
| 20110184993 | Chawla et al. | Jul 2011 | A1 |
| 20110185292 | Chawla et al. | Jul 2011 | A1 |
| 20110225574 | Khalidi et al. | Sep 2011 | A1 |
| 20110239213 | Aswani et al. | Sep 2011 | A1 |
| 20110251992 | Bethlehem et al. | Oct 2011 | A1 |
| 20110252208 | Ali et al. | Oct 2011 | A1 |
| 20110255538 | Srinivasan et al. | Oct 2011 | A1 |
| 20110265076 | Thorat et al. | Oct 2011 | A1 |
| 20110271279 | Pate | Nov 2011 | A1 |
| 20110276578 | Allalouf et al. | Nov 2011 | A1 |
| 20110276963 | Wu et al. | Nov 2011 | A1 |
| 20110283277 | Castillo et al. | Nov 2011 | A1 |
| 20110289561 | Ivanoy et al. | Nov 2011 | A1 |
| 20110307729 | Matsuzawa et al. | Dec 2011 | A1 |
| 20110320690 | Petersen et al. | Dec 2011 | A1 |
| 20120017114 | Timashev et al. | Jan 2012 | A1 |
| 20120023495 | Machida | Jan 2012 | A1 |
| 20120030456 | Wu et al. | Feb 2012 | A1 |
| 20120054736 | Arcese et al. | Mar 2012 | A1 |
| 20120081395 | Adi et al. | Apr 2012 | A1 |
| 20120084381 | ABadi et al. | Apr 2012 | A1 |
| 20120166866 | Rao et al. | Jun 2012 | A1 |
| 20120209983 | Bronner et al. | Aug 2012 | A1 |
| 20120233463 | Holt et al. | Sep 2012 | A1 |
| 20120254445 | Kawamoto et al. | Oct 2012 | A1 |
| 20120254567 | Umbehocker | Oct 2012 | A1 |
| 20120266162 | Baron | Oct 2012 | A1 |
| 20120272237 | Baron | Oct 2012 | A1 |
| 20120290630 | Aizman et al. | Nov 2012 | A1 |
| 20120304247 | Badger et al. | Nov 2012 | A1 |
| 20120310881 | Shadmon | Dec 2012 | A1 |
| 20120310892 | Dam et al. | Dec 2012 | A1 |
| 20120324183 | Chiruvolu et al. | Dec 2012 | A1 |
| 20130046740 | Li et al. | Feb 2013 | A1 |
| 20130047160 | Conover | Feb 2013 | A1 |
| 20130055018 | Joshi et al. | Feb 2013 | A1 |
| 20130061110 | Zvibel | Mar 2013 | A1 |
| 20130061167 | Rhodes et al. | Mar 2013 | A1 |
| 20130066930 | Kamei et al. | Mar 2013 | A1 |
| 20130117744 | Klein et al. | May 2013 | A1 |
| 20130132674 | Sundrani | May 2013 | A1 |
| 20130144921 | Nakamura et al. | Jun 2013 | A1 |
| 20130151888 | Bhattiprolu et al. | Jun 2013 | A1 |
| 20130152085 | D'Amore et al. | Jun 2013 | A1 |
| 20130185716 | Yin et al. | Jul 2013 | A1 |
| 20130198738 | Reddin et al. | Aug 2013 | A1 |
| 20130212345 | Nakajima | Aug 2013 | A1 |
| 20130227379 | Gupta et al. | Aug 2013 | A1 |
| 20130227552 | Reddin et al. | Aug 2013 | A1 |
| 20130227566 | Higuchi et al. | Aug 2013 | A1 |
| 20130232491 | Radhakrishnan et al. | Sep 2013 | A1 |
| 20130246705 | Diare | Sep 2013 | A1 |
| 20130247036 | Fujiwara | Sep 2013 | A1 |
| 20130262396 | Kripalani et al. | Oct 2013 | A1 |
| 20130283267 | Cooper et al. | Oct 2013 | A1 |
| 20130297869 | Mills et al. | Nov 2013 | A1 |
| 20130318229 | Bakre et al. | Nov 2013 | A1 |
| 20140006708 | Huynh et al. | Jan 2014 | A1 |
| 20140013398 | Hotti | Jan 2014 | A1 |
| 20140025796 | Mbhor et al. | Jan 2014 | A1 |
| 20140059392 | Ren et al. | Feb 2014 | A1 |
| 20140095544 | Eshel et al. | Apr 2014 | A1 |
| 20140095555 | Kim et al. | Apr 2014 | A1 |
| 20140095816 | Hsu et al. | Apr 2014 | A1 |
| 20140108587 | Goldberg et al. | Apr 2014 | A1 |
| 20140115182 | Sabaa et al. | Apr 2014 | A1 |
| 20140122547 | Agetsuma et al. | May 2014 | A1 |
| 20140123138 | Lee et al. | May 2014 | A1 |
| 20140146055 | Bala et al. | May 2014 | A1 |
| 20140149794 | Shetty et al. | May 2014 | A1 |
| 20140149983 | Bonilla et al. | May 2014 | A1 |
| 20140173199 | Gupta et al. | Jun 2014 | A1 |
| 20140181116 | Wang | Jun 2014 | A1 |
| 20140188808 | Wolf et al. | Jul 2014 | A1 |
| 20140189429 | Gill et al. | Jul 2014 | A1 |
| 20140189677 | Curzi et al. | Jul 2014 | A1 |
| 20140189685 | Kripalani | Jul 2014 | A1 |
| 20140189686 | Masters et al. | Jul 2014 | A1 |
| 20140196038 | Kottomtharayil et al. | Jul 2014 | A1 |
| 20140201725 | Tian et al. | Jul 2014 | A1 |
| 20140207824 | Brandwine et al. | Jul 2014 | A1 |
| 20140230024 | Uehara et al. | Aug 2014 | A1 |
| 20140237464 | Waterman et al. | Aug 2014 | A1 |
| 20140250300 | Runkis et al. | Sep 2014 | A1 |
| 20140279909 | Sudarsanam et al. | Sep 2014 | A1 |
| 20140298185 | Chen et al. | Oct 2014 | A1 |
| 20140310710 | Lubsey et al. | Oct 2014 | A1 |
| 20140359612 | D'Amato et al. | Dec 2014 | A1 |
| 20140365811 | Veiga et al. | Dec 2014 | A1 |
| 20150006707 | Malik et al. | Jan 2015 | A1 |
| 20150006788 | Liu et al. | Jan 2015 | A1 |
| 20150007180 | Sharp et al. | Jan 2015 | A1 |
| 20150026682 | Singh et al. | Jan 2015 | A1 |
| 20150032690 | Hoque et al. | Jan 2015 | A1 |
| 20150039735 | Zeyliger et al. | Feb 2015 | A1 |
| 20150039837 | Quan et al. | Feb 2015 | A1 |
| 20150081644 | Pitts | Mar 2015 | A1 |
| 20150095788 | Thiele et al. | Apr 2015 | A1 |
| 20150106802 | Ivanov et al. | Apr 2015 | A1 |
| 20150142745 | Tekade et al. | May 2015 | A1 |
| 20150142747 | Zou | May 2015 | A1 |
| 20150143164 | Veerta et al. | May 2015 | A1 |
| 20150172412 | Escriva et al. | Jun 2015 | A1 |
| 20150178019 | Hegdal et al. | Jun 2015 | A1 |
| 20150205639 | Matsumoto et al. | Jul 2015 | A1 |
| 20150213032 | Powell et al. | Jul 2015 | A1 |
| 20150215389 | Spencer | Jul 2015 | A1 |
| 20150220324 | Arcese et al. | Aug 2015 | A1 |
| 20150242291 | Chang et al. | Aug 2015 | A1 |
| 20150278046 | Zellermayer et al. | Oct 2015 | A1 |
| 20150293830 | Bhide et al. | Oct 2015 | A1 |
| 20150293896 | Runkis et al. | Oct 2015 | A1 |
| 20150301903 | Mutha et al. | Oct 2015 | A1 |
| 20150309891 | Saika | Oct 2015 | A1 |
| 20150032653 | Cui | Nov 2015 | A1 |
| 20150324217 | Shilmover et al. | Nov 2015 | A1 |
| 20150326531 | Cui et al. | Nov 2015 | A1 |
| 20150331757 | Durge et al. | Nov 2015 | A1 |
| 20150355862 | Hayes et al. | Dec 2015 | A1 |
| 20150378761 | Sevigny et al. | Dec 2015 | A1 |
| 20150378853 | Sevigny et al. | Dec 2015 | A1 |
| 20160004693 | Chen et al. | Jan 2016 | A1 |
| 20160011898 | Lee et al. | Jan 2016 | A1 |
| 20160070492 | Cherubini et al. | Mar 2016 | A1 |
| 20160077988 | Tipton et al. | Mar 2016 | A1 |
| 20160078068 | Agrawal et al. | Mar 2016 | A1 |
| 20160085480 | Chiu et al. | Mar 2016 | A1 |
| 20160085574 | Dornemann et al. | Mar 2016 | A1 |
| 20160087861 | Kuan et al. | Mar 2016 | A1 |
| 20160110214 | Vincent et al. | Apr 2016 | A1 |
| 20160110267 | Earl et al. | Apr 2016 | A1 |
| 20160124665 | Jain et al. | May 2016 | A1 |
| 20160162371 | Prabhu et al. | Jun 2016 | A1 |
| 20160171241 | Yun | Jun 2016 | A1 |
| 20160179416 | Mutha et al. | Jun 2016 | A1 |
| 20160179419 | Yamaguchi et al. | Jun 2016 | A1 |
| 20160188232 | Ramachandran et al. | Jun 2016 | A1 |
| 20160188407 | Bronnikov et al. | Jun 2016 | A1 |
| 20160202916 | Cui et al. | Jul 2016 | A1 |
| 20160203008 | Cui et al. | Jul 2016 | A1 |
| 20160216993 | Beckwith et al. | Jul 2016 | A1 |
| 20160224363 | Joy | Aug 2016 | A1 |
| 20160274926 | Narasimhamurthy et al. | Sep 2016 | A1 |
| 20160301766 | Ionescu et al. | Oct 2016 | A1 |
| 20160316003 | Snider et al. | Oct 2016 | A1 |
| 20160328226 | Arya et al. | Nov 2016 | A1 |
| 20160335108 | Ryu et al. | Nov 2016 | A1 |
| 20160335134 | Gupta et al. | Nov 2016 | A1 |
| 20160359697 | Scheib et al. | Dec 2016 | A1 |
| 20160378528 | Zamir | Dec 2016 | A1 |
| 20160378616 | Wigmore et al. | Dec 2016 | A1 |
| 20170004131 | Ben Dayan et al. | Jan 2017 | A1 |
| 20170005990 | Birger et al. | Jan 2017 | A1 |
| 20170012904 | Matzek et al. | Jan 2017 | A1 |
| 20170024152 | Bhagi et al. | Jan 2017 | A1 |
| 20170024224 | Bakke et al. | Jan 2017 | A1 |
| 20170039078 | Chen et al. | Feb 2017 | A1 |
| 20170039218 | Prahlad et al. | Feb 2017 | A1 |
| 20170048223 | Anantha Padmanaban et al. | Feb 2017 | A1 |
| 20170068469 | Shankar et al. | Mar 2017 | A1 |
| 20170075921 | Benton et al. | Mar 2017 | A1 |
| 20170090776 | Kowles | Mar 2017 | A1 |
| 20170091047 | Bangalore et al. | Mar 2017 | A1 |
| 20170109184 | Ramani et al. | Apr 2017 | A1 |
| 20170160983 | Fiske et al. | Jun 2017 | A1 |
| 20170177638 | Bhosale | Jun 2017 | A1 |
| 20170193021 | Deng et al. | Jul 2017 | A1 |
| 20170206074 | Arcese et al. | Jul 2017 | A1 |
| 20170206207 | Bondurant et al. | Jul 2017 | A1 |
| 20170220661 | Cao et al. | Aug 2017 | A1 |
| 20170228300 | Thomas et al. | Aug 2017 | A1 |
| 20170235507 | Sinha et al. | Aug 2017 | A1 |
| 20170235562 | Bafna et al. | Aug 2017 | A1 |
| 20170235563 | Bafna et al. | Aug 2017 | A1 |
| 20170235589 | Gopalapura Venkatesh et al. | Aug 2017 | A1 |
| 20170235590 | Sinha et al. | Aug 2017 | A1 |
| 20170235591 | Kanada et al. | Aug 2017 | A1 |
| 20170235653 | Arikatla et al. | Aug 2017 | A1 |
| 20170235654 | Deshmukh et al. | Aug 2017 | A1 |
| 20170235751 | Gupta et al. | Aug 2017 | A1 |
| 20170235758 | Gopalapura Venkatesh et al. | Aug 2017 | A1 |
| 20170235760 | Sharpe et al. | Aug 2017 | A1 |
| 20170235761 | Bafna et al. | Aug 2017 | A1 |
| 20170235762 | Sharpe et al. | Aug 2017 | A1 |
| 20170235763 | Gopalapura Venkatesh et al. | Aug 2017 | A1 |
| 20170235764 | Sharpe et al. | Aug 2017 | A1 |
| 20170235950 | Gopalapura Venkatesh | Aug 2017 | A1 |
| 20170242599 | Patnaik et al. | Aug 2017 | A1 |
| 20170262346 | Pradhan et al. | Sep 2017 | A1 |
| 20170264684 | Spillane et al. | Sep 2017 | A1 |
| 20170277556 | Ishi et al. | Sep 2017 | A1 |
| 20170277903 | Christodorescu | Sep 2017 | A1 |
| 20170279674 | Zhu | Sep 2017 | A1 |
| 20170286228 | Redko et al. | Oct 2017 | A1 |
| 20170302589 | Leafe et al. | Oct 2017 | A1 |
| 20170302731 | Cui | Oct 2017 | A1 |
| 20180004766 | Darling | Jan 2018 | A1 |
| 20180011766 | Lee et al. | Jan 2018 | A1 |
| 20180062993 | Wu et al. | Mar 2018 | A1 |
| 20180113623 | Sancheti | Apr 2018 | A1 |
| 20180129426 | Aron et al. | May 2018 | A1 |
| 20180143845 | Chawla et al. | May 2018 | A1 |
| 20180143880 | Dornemann | May 2018 | A1 |
| 20180145960 | Bakshan et al. | May 2018 | A1 |
| 20180157521 | Arikatla et al. | Jun 2018 | A1 |
| 20180157522 | Bafna et al. | Jun 2018 | A1 |
| 20180157561 | Venkatesh et al. | Jun 2018 | A1 |
| 20180157677 | Bafna et al. | Jun 2018 | A1 |
| 20180157752 | Arikatla et al. | Jun 2018 | A1 |
| 20180157860 | Nair et al. | Jun 2018 | A1 |
| 20180159729 | Deshmukh et al. | Jun 2018 | A1 |
| 20180159826 | Yisan et al. | Jun 2018 | A1 |
| 20180173731 | Nazari et al. | Jun 2018 | A1 |
| 20180196719 | Glass | Jul 2018 | A1 |
| 20180205787 | Ben Dayan et al. | Jul 2018 | A1 |
| 20180278602 | Koushik et al. | Sep 2018 | A1 |
| 20180332105 | Huang et al. | Nov 2018 | A1 |
| 20180357251 | Kumarasamy et al. | Dec 2018 | A1 |
| 20190026101 | Gopalapura Venkatesh et al. | Jan 2019 | A1 |
| 20190034240 | Nabi et al. | Jan 2019 | A1 |
| 20190079747 | Sinha et al. | Mar 2019 | A1 |
| 20190129808 | Acharya et al. | May 2019 | A1 |
| 20190179918 | Singh et al. | Jun 2019 | A1 |
| 20190196718 | Pai et al. | Jun 2019 | A1 |
| 20190207925 | Anantha Padmanaban et al. | Jul 2019 | A1 |
| 20190228147 | Formato et al. | Jul 2019 | A1 |
| 20190243703 | Rooney | Aug 2019 | A1 |
| 20190332683 | Thummala et al. | Oct 2019 | A1 |
| 20190339883 | Aron et al. | Nov 2019 | A1 |
| 20200007530 | Mohamad Abdul et al. | Jan 2020 | A1 |
| 20200034069 | Batra et al. | Jan 2020 | A1 |
| 20200036647 | Gupta et al. | Jan 2020 | A1 |
| 20200081704 | Bafna et al. | Mar 2020 | A1 |
| 20200081733 | Buck et al. | Mar 2020 | A1 |
| 20200106669 | Dhillon et al. | Apr 2020 | A1 |
| 20200125580 | Shao | Apr 2020 | A1 |
| 20200137157 | Joseph et al. | Apr 2020 | A1 |
| 20200193059 | Narayanswamy et al. | Jun 2020 | A1 |
| 20200274869 | Tahenakos et al. | Aug 2020 | A1 |
| 20210141630 | Sharpe et al. | May 2021 | A1 |
| 20210157690 | Wexler et al. | May 2021 | A1 |
| 20210200641 | Bafna et al. | Jul 2021 | A1 |
| 20210224233 | Bafna et al. | Jul 2021 | A1 |
| 20210247973 | Gupta et al. | Aug 2021 | A1 |
| 20210318938 | Benke | Oct 2021 | A1 |
| 20210326358 | Seelemann et al. | Oct 2021 | A1 |
| 20210334178 | Yang et al. | Oct 2021 | A1 |
| 20210342237 | Polimera et al. | Nov 2021 | A1 |
| 20210344772 | Arikatla et al. | Nov 2021 | A1 |
| 20210349859 | Bafna et al. | Nov 2021 | A1 |
| 20210365257 | Gopalapura Venkatesh et al. | Nov 2021 | A1 |
| 20210373815 | Kumar et al. | Dec 2021 | A1 |
| 20210390080 | Tripathi et al. | Dec 2021 | A1 |
| 20210397587 | Thummala et al. | Dec 2021 | A1 |
| 20210406136 | Venkatesh et al. | Dec 2021 | A1 |
| 20220004377 | Sharpe et al. | Jan 2022 | A1 |
| 20220091947 | Kothari et al. | Mar 2022 | A1 |
| 20220147342 | Sharpe et al. | May 2022 | A1 |
| 20220147495 | Sharpe et al. | May 2022 | A1 |
| 20220156107 | Bafna et al. | May 2022 | A1 |
| 20220283708 | Grunwald et al. | Sep 2022 | A1 |
| 20220292002 | Kumar et al. | Sep 2022 | A1 |
| 20230056425 | Gopalapura Venkatesh et al. | Feb 2023 | A1 |
| 20230066137 | Vijjapurapu et al. | Mar 2023 | A1 |
| 20230068262 | Bafna et al. | Mar 2023 | A1 |
| 20230101337 | Ahmad et al. | Mar 2023 | A1 |
| 20230237022 | Thomas et al. | Jul 2023 | A1 |
| 20230237170 | Thummala et al. | Jul 2023 | A1 |
| 20240045774 | Wang et al. | Feb 2024 | A1 |
| 20240070032 | Wang et al. | Feb 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 105100210 | Nov 2015 | CN |
| 110516005 | Nov 2019 | CN |
| 110519112 | Nov 2019 | CN |
| 110569269 | Dec 2019 | CN |
| 1062581 | Oct 2003 | EP |
| 1214663 | Jun 2006 | EP |
| 1979814 | Oct 2008 | EP |
| 2010050944 | May 2010 | WO |
| 2012126177 | Sep 2012 | WO |
| 2016018446 | Feb 2016 | WO |
| 2018014650 | Jan 2018 | WO |
| Entry |
|---|
| US 11,048,595 B2, 06/2021, Venkatesh et al. (withdrawn) |
| U.S. Appl. No. 18/178,400 titled “Application Level to Share Level Replication Policy Transition for File Serverdisaster Recovery Systems” filed Mar. 3, 2023. |
| U.S. Appl. No. 17/877,769 titled “Self-Service Restore (SSR) Snapshot Replication With Share-Level File System Disaster Recovery on Virtualized File Servers” filed Jul. 29, 2022. |
| “Architecture for Continuous Replication”, Commvault, May 7, 2020, pp. 1-4. |
| “DFS Namespaces and DFS Replication Overview”, Microsoft Learn, Aug. 31, 2016, pp. 9. |
| “Disaster Recovery of Workloads on AWS: Recovery in the Cloud”, AWS, Feb. 12, 2021, pp. 1-33. |
| “End User Access”, Commvault, 2019, pp. 1-4. |
| “General Share Properties”, Oracle ZFS Storage Application Administration Guide, 2013, pp. 1-5. |
| “Introducing HPE Cloud vols. Backup Chalk Talk”, HPE Technology, 2020, pp. 1-5. |
| “Neverfail User Guide”, Neverfail HybriStor v2.3 | https://neverfail.com/, 2017, pp. 1-58. |
| “Oracle ZFS Storage Appliance: How To Optimize Replication Performance”, Oracle System Handbook—ISO 7.0, Aug. 1, 2018, pp. 1-3. |
| “Quantum User Essentials”, Quantum, 2013, pp. 1-2. |
| “Replication for File Systems”, Commvault, Jan. 4, 2022, pp. 1. |
| “Replication: Remote Replication Introduction”, Oracle Sun ZFS Storage 7000 System Administration Guide, Dec. 2012, pp. 1-6. |
| “Reversing the Direction of Replication”, Oracle ZFS Storage Appliance Administration Guide, 2014, pp. 1-2. |
| “Tech TopX: AHV One Click Upgrade”, Screen captures from YouTube video clip, 13 pages, uploaded on Dec. 8, 2015 by user “Nutanix University”. Retrieved from Internet: https://www.youtube.com/watch?v=3dALdzw6qZM, Dec. 8, 2015, pp. all. |
| “Technical Overview and Best Practices”, VMware vSphere VMFS ; a VMware Technical White Paper updated for VMware vSphere 5.1, Version 3.0, Nov. 27, 2012, pp. all. |
| Jeffrey, Hemmes , et al., “Cacheable Decentralized Groups for Grid Resource Access Control”, 2006 7th IEEE/ACM International Conference on Grid Computing Department of Computer Science and Engineering, University of Notre Dame, Sep. 2006, pp. 192-199. |
| Kaam, Bas Van, “New in AOS 5.0: Nutanix Acropolis File Services”, basvankaam.com, Jan. 5, 2017, pp. all. |
| “Nutanix Files Guide”; Nutanix; Sep. 14, 2018; pp. all. |
| “Setting up and Using Acropolis File Services (AFS) on Nutanix AOS 5.0”; Virtual Dennis—Sharing Technical Tips Learned the Hard Way; Posted Dec. 30, 2016; pp. all. |
| U.S. Appl. No. 17/129,425, titled “Parallel Change File Tracking in a Distributed File Server Virtual Machine (FSVM) Architecture”, filed Dec. 21, 2020; pp. all pages of the application as filed. |
| U.S. Appl. No. 17/180,257 titled “Virtualized File Server User Views” filed Feb. 19, 2021, pp. all pages of the application as filed. |
| U.S. Appl. No. 17/169,137 titled “Virtualized File Server Data Sharing” filed Feb. 5, 2021, pp. all pages of the application as filed. |
| U.S. Appl. No. 17/364,453 titled “Virtualized Server Systems and Methods Including Domain Joining Techniques” filed Jun. 30, 2021, pp. all pages of the application as filed. |
| U.S. Appl. No. 17/302,343 titled “Disaster Recovery for Distributed File Servers, Including Metadata Fixers” filed Apr. 30, 2021, pp. all pages of the application as filed. |
| Bas van Kaam “New in AOS 5.0: Nutanix Acropolis File Services”; basvankaam.com; Jan. 5, 2017; pp. all. |
| Dell: “High Availability and Data Protection With Dell EMC Isilon Scale-Out NAS”; Jul. 2019, Dell Inc., pp. all. |
| Jay Bounds “High-Availability (HA) Pair Controller Configuration Overview and Best Practices”; NetApp; Feb. 2016; pp. all. |
| Jorge Costa “High Availability Setup Using Veritas Cluster Server and NetApp Synchronous SnapMirror—One button Failover/Failback with SnapMirror Sync and Veritas Cluster Server”; NetApp Community; Nov. 18, 2010; pp. all. |
| NetApp “Preparing Storage Systems for Snapmirror Replication”; Apr. 2005, NetApp, Inc., pp. all. |
| NetApp; “Clustered Data Ontap 8.2 File Access Management Guide for Cifs”; Feb. 2014 (year 2014); pp. all. |
| U.S. Appl. No. 17/238,001 titled “Cloning Virtualized File Servers” filed Apr. 22, 2021, pp. all pages of the application as filed. |
| Ruth, Paul “Autonomic Live Adaption of Virtual Computational Environments in a Multi-Domain Infrastructure”; 2006 IEEE International Conference on Autonomic Computing, 2006, pp. 5-14. |
| U.S. Appl. No. 17/443,009, titled “Scope-Based Distributed Lock Infrastructure for Virtualized File Server” filed Jul. 19, 2021, pp. all pages of the application as filed. |
| U.S. Appl. No. 17/448,315 titled “Virtualized File Server” filed Sep. 21, 2021, pp. all pages of the application as filed. |
| U.S. Appl. No. 17/580,555 titled “Virtualized File Server” filed Jan. 20, 2022, pp. all pages of the application as filed. |
| U.S. Appl. No. 17/581,418 titled “File Server Managers and Systems for Managing Virtualized File Servers” filed Jan. 21, 2022, pp. all pages of the application as filed. |
| U.S. Appl. No. 17/581,562 titled “Share-Based File Server Replication for Disaster Recovery” filed Jan. 21, 2022, pp. all pages of the application as filed. |
| U.S. Appl. No. 17/648,661 titled “User Interfaces for Disaster Recovery of Distributed File Servers” filed Jan. 21, 2022, pp. all pages of the application as filed. |
| U.S. Appl. No. 17/648,796 titled “Virtualized Server Systems and Methods Including Scaling of File System Virtual Machines” filed Jan. 24, 2022, pp. all pages of the application as filed. |
| U.S. Appl. No. 15/829,602 entitled “Handling Permissions for Virtualized File Servers”, filed Dec. 1, 2017, pp. all pages of the application as filed. |
| Young-Woo Jung et al. “Standard-Based Vitrual Infrastructure Resource Management for Distributed and Heterogeneous Servers”; Feb. 15, 2009; ICACT; pp. all. |
| U.S. Appl. No. 15/966,943 titled “Virtualized Server Systems and Methods Including Domain Joining Techniques” filed Apr. 30, 2018, pp. all pages of the application as filed. |
| U.S. Appl. No. 16/687,327, titled “Virtualized File Server Rolling Upgrade”, filed Nov. 19, 2019, pp. all pages of the application as filed. |
| U.S. Appl. No. 17/091,758 titled “Virtualized File Server Distribution Across Clusters”, filed Nov. 6, 2020, pp. all pages of the application as filed. |
| U.S. Appl. No. 16/942,929 titled “Method Using Access Information in a Distributed File Server Virtual Machine (FSVM) Architecture, Including Web Access”; filed Jul. 30, 2020, pp. all pages of the application as filed. |
| U.S. Appl. No. 16/944,323 titled “Actions Based on File Tagging in a Distributed File Server Virtual Machine (FSVM) Environment”, filed Jul. 31, 2020, pp. all pages of the application as filed. |
| Dell EMC; Dell EMC Isilon OneFS Operating System; Scale-out NAS to maximize the data capital and business value of your unstructured data; 2020, pp. all. |
| Dell EMC; White Paper; Dell EMC Isilon Onefs Operating System; Powering the Isilon Scale-Out Storage Platform; Dec. 2019, pp. all. |
| EMC Isilon OneFS Operating System; Powering scale-out storage for the new world of Big Data in the enterprise; www.EMC.com; captured Feb. 2020, pp. all. |
| Isilon OneFS, Version 8.0.1; Web Administration Guide; Published Oct. 2016, pp. all. |
| U.S. Appl. No. 15/833,255, entitled “Cloning Virtualized File Servers”, filed Dec. 6, 2017, pp. all pages of the application as filed. |
| U.S. Appl. No. 15/833,391, entitled “Virtualized Server Systems and Methods Including Scaling of File System Virtual Machines”, filed Dec. 6, 2017, pp. all pages of the application as filed. |
| U.S. Appl. No. 15/422,220, entitled “ Virtualized File Server” filed Feb. 1, 2017, pp. all pages of the application as filed. |
| U.S. Appl. No. 15/829,340, entitled “Configuring Network Segmentation for a Virtualization Environment”, filed Dec. 1, 2017, pp. all pages of the application as filed. |
| U.S. Appl. No. 15/829,731, entitled “Transparent Referrals for Distributed File Servers”, filed Dec. 1, 2017, , pp. all pages of the application as filed. |
| U.S. Appl. No. 15/829,781, entitled “Virtualized Server Systems and Methods Including Load Balancing for Virtualized File Servers”, filed Dec. 1, 2017, , pp. all pages of the application as filed. |
| U.S. Appl. No. 15/832,310 entitled “Disaster Recovery for Distributed File Servers, Including Metadata Fixers”, filed Dec. 5, 2017, , pp. all pages of the application as filed. |
| U.S. Appl. No. 16/140,250 titled “Virtualized File Server Data Sharing” filed Sep. 24, 2018, , pp. all pages of the application as filed. |
| U.S. Appl. No. 16/160,618 titled “Virtualized File Server Backup to Cloud” filed Oct. 15, 2018, , pp. all pages of the application as filed. |
| VMware vSphere VMFS “Technical Overview and Best Practices”, a VMware Technical White Paper updated for VMware vSphere 5.1, Version 3.0; Nov. 27, 2012, pp. all. |
| “Administering VMware vSAN—VMware vSphere 7.0”, 2015-2020, pp. 1-114. |
| “Backup vSAN 7 File Share with Veeam Backup & Replication 10”, Sysadmin Stories, https://www.sysadminstories.com/2020/06/backup-vsan-7-file-share-with-veeam.html, Jun. 2, 2020, pp. 1-7. |
| “Characteristics of a vSAN Cluster”, May 31, 2019, pp. 1-2. |
| “Designing and Sizing Virtual SAN Fault Domains”, Administering VMware Virtual SAN; VMware vSphere 6.5; vSAN 6.6; https://docs.vmware.com/en/VMware-vSphere/6.5/virtual-san-66-administration-guide.pdf, captured Aug. 20, 2021, 2017, pp. 34. |
| “Enabling or disabling SMB automatic node referrals”, NetApp https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.cdot-famg-cifs%2FGUID-AC7E8515-3A4C-4BB5-A8C8-38B565C952E0.html, Captured Sep. 19, 2019, pp. all. |
| “Guaranteeing throughput with QoS”, NetApp https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.pow-perf-mon%2FGUID-77DF9BAF-4ED7-43F6-AECE-95DFB0680D2F.html, Captured Sep. 19, 2019, pp. all. |
| “How to troubleshoot the ‘Autolocation’ feature in Clustered Data ONTAP”, NetApp. |
| https://kb.netapp.com/app/answers/answer_view/a_id/1030857/loc/en_US#_highlight, Captured Sep. 19, 2019, pp. all. |
| “How to Troubleshoot the ‘Autolocation’ feature in Clustered Data ONTAP—Results”, NetApp https://kb.netapp.com/app/results/kw/autolocation/, Captured Sep. 19, 2019, pp. all. |
| “Hybrid Cloud Storage with Cloudian HyperStore and Amazon S3”, Cloudian Inc.; www.cloudian.com, 2014, pp. all. |
| “Improving client response time by providing SMB automatic node referrals with Auto Location”, NetApp https://library.netapp.com/ecmdocs/ECMP1196891/html/GUID-0A5772A4-A6D7-4A00-AC2A-928868C5B385.html, Captured Sep. 19, 2019, pp. all. |
| “Managing Workloads”, NetApp https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.pow-perf-mon%2FGUID-13D35FC5-AF37-4BBD-8A8E-B10B41451A16.html, captured Sep. 19, 2019, pp. all. |
| “Nutanix AFS—Introduction & Steps for Setting Up”, Retrieved from https://virtual building blocks. com/2 0 1 8/01 /03/nutanix-afs-introduction-steps-for-setting-up/ (Year: 2018), Jan. 3, 2018, 1-23. |
| “Path Failover and Virtual Machines”, vSphere Storage; Update 2; VMware vSphere 7.0; VMware ESXi 7.0; vCenter Server 7.0; https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere-esxi-vcenter-server-702-storage-guide.pdf, Jun. 25, 2021, p. 238. |
| “Protect Your Data With Netapp Element Software”, Solution Brief, NetApp, 2018, pp. all. |
| “Tech TopX: AHV One Click Upgrade”, Screen captures from YouTube video clip entitled “Tech TopX: AHV One Click Upgrade,” 13 pages, uploaded on Dec. 8, 2015 by user “Nutanix University”. Retrieved from Internet: https://www.youtube.com/watch?v=3dALdzw6qZM, Dec. 8, 2015, pp. all. |
| “Understanding Multipathing and Failover”, vSphere Storage; VMware vSphere 7.0; VMware ESXI 7.0; vCenter Server 7.0 https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere-esxi-vcenter-server-702-storage-guide.pdf, Jun. 25, 2021, pp. 234-268. |
| “Virtual Disk Manager User's Guide: Virtual Disk Development Kit”, vmware.com, 2008, 1-12. |
| “VMware vCenter Server: Centrally Mananged Virtual Infrastructure Delivered with Confidence”, VMWare Datasheet; https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vCenter/vmware-vcenter-server-datasheet.pdf, captured Aug. 20, 2021, 2015, pp. 1-2. |
| “VMware VSAN 7.0 Release Notes”, VMware; https://docs.vmware.com/en/VMware-vSphere/7.0/m/vmware-vsan-70-release-notes.html, Mar. 8, 2021, pp. 1-12. |
| “VSAN 7.0 U2 Proof of Concept Guide”, VMwareStorage; https://images.core.vmware.com/sites/default/files/resource/vsan_70_u2_proof_o f_concept_guide_noindex.pdf, printed May 18, 2021, Apr. 2021, pp. 1-267. |
| “VSAN File Services Tech Note | VMware”, Aug. 2021, pp. 1-7. |
| “VSAN Health Service—File Service—File Server Health (77165)”, VMware, Knowledge Base; https://kb.vmware.com/s/article/77165, May 15, 2021, pp. 1-5. |
| “VSAN Monitoring and Troubleshooting—VMware vSphere 7.0”, https://docs.vmware.com/, Sep. 2018, pp. 1-61. |
| “VSAN Performance Graphs in the vSphere Web Client (2144493)”, Nov. 9, 2020, pp. 1-42. |
| “VSan Planning and Deployment”, Update 2 VMWare vSphere 6.7; VMware vSAN 6.7; https://docs.vmware.com/en/VMware-vSphere/6.7/vsan-673-planning- deployment-guide.pdf, Aug. 20, 2019, pp. 1-85. |
| “VSan Stretched Cluster Guide”, VMwareStorage; https://images.core.vmware.com/sites/default/files/resource/vsan_stretched_clus ter_guide_noindex.pdf, printed Jun. 24, 2021, Jun. 2020, pp. 1-62. |
| “VSphere Availability—VMware vSphere 6.7”, https://docs.vmware.com/, Jan. 11, 2019, pp. 1-105. |
| “VSphere Storage—VMware vSphere 6.7”, https://docs.vmware.com/, Jan. 4, 2021, pp. 1-382. |
| Bhardwaj, Rishi “The Wonderful World of Distributed Systems and the Art of Metadata Management”, Nutanix, Inc., https://www.nutanix.com/blog/the-wonderful-world-of-distributed-systems-and-metadata-management; captured Aug. 19, 2021, Sep. 24, 2015, pp. 1-8. |
| Birk, Ryan “How it Works: Understanding vSAN Architecture Components”, altaro.com, Feb. 28, 2018, pp. 1-10. |
| Cormac “Native File Services for vSAN 7”, CormacHogan.com, Mar. 11, 2020, pp. 1-23. |
| Feroce, Danilo “Leveraging VMware vSAM for Highly Available Management Clusters”, VMware, Inc., Version 2.9, VMware, Inc., Jan. 2018, 1-22. |
| Fojta, Tomas “Quotas and Quota Policies in VMware Cloud Director—Tom Fojta's Blog”, Nov. 6, 2020, pp. 1-4. |
| Fojta, Tomas “vSAN File Services with vCloud Director—Tom Fojta's Blog”. (wordpress.com) (“Fojta Blog”) captured Feb. 11, 2021, pp. 1-8. |
| Hogan, Cormac “New updates from Nutanix—NOS 3.0 and NX-3000”, https://cormachogan.com/2012/12/20/new-from-nutanix-Nos. 3-0-nx-3000/ Dec. 20, 2012, pp. 1-7. |
| Kemp, Erik “NetApp SolidFire SnapMirror Architecture and Configuration”, Technical Report, NetApp, Dec. 2017, pp. all. |
| Kleyman, Bill “How Cloud Computing Changes Storage Tiering”, https://www.datacenterknowledge.com, captured Jun. 4, 2019, Nov. 12, 2015, pp. all. |
| Leibovici, Andre “Nutanix One-Click Upgrade now takes care of Firmware and Hypervisor too!”, myvirtualcloud.net https://myvirtualcloud.net/nutanix-one-click-upgrade-now-takes-care-of-firmware-and-hypervisor-too/, Jul. 31, 2014, pp. 1-4. |
| Rajendran, Cedric “Working with vSAN Health Checks”, VMware vSan Virtual Blocks Blog; https://blogs.vmware.com/virtualblocks/2019/07/18/working-with-vsan-health-checks/, Jul. 18, 2019, pp. 1-6. |
| Seget, Vladan “VMware vSAN 7 now with native file services and quotas”, May 1, 2020,. |
| Seget, Vladan “VMware vSphere 7.0 and vSAN storage improvements”, Apr. 1, 2020, pp. 1-12. |
| U.S. Appl. No. 17/585,403 titled “Virtualized File Server Smart Data Ingestion” filed Jan. 27, 2022, pp. all pages of the application as filed. |
| Sturniolo, Andy “VMware vSAN File Services and Veeam”,https://www.veeam.com/blog/veeam-backup-vsan-file-services.html, Jul. 22, 2020, 1-9. |
| Poitras, Steven , “The Nutanix Bible”, https://nutanixbible.com/, Apr. 9, 2019, pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Oct. 15, 2013), from http://stevenpoitras.com/the-nutanix-bible/ (Publication date based on indicated capture date by Archive.org; first publication date unknown); pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Jan. 11, 2014), from http://stevenpoitras.com/the-nutanix-bible/ (Publication date based on indicated capture date by Archive.org; first publication date unknown); pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Jun. 20, 2014), from http://stevenpoitras.com/the-nutanix-bible/ (Publication date based on indicated capture date by Archive.org; first publication date unknown); pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Jan. 7, 2015), from http://stevenpoitras.com/the-nutanix-bible/ (Publication date based on indicated capture date by Archive.org; first publication date unknown); pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Jun. 9, 2015), from http://stevenpoitras.com/the-nutanix-bible/ (Publication date based on indicated capture date by Archive.org; first publication date unknown); pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Sep. 4, 2015), from https://nutanixbible.com/; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Jan. 12, 2016), from https://nutanixbible.com/ ; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Jun. 9, 2016), from https://nutanixbible.com/; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Jan. 3, 2017), from https://nutanixbible.com/; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Jun. 8, 2017), from https://nutanixbible.com/; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Jan. 3, 2018), from https://nutanixbible.com/; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Jun. 25, 2018), from https://nutanixbible.com/; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Jan. 8, 2019), from https://nutanixbible.com/; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Jul. 25, 2019), from https://nutanixbible.com/; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Sep. 17, 2019), from https://nutanixbible.com/; pp. all. |
| Cano, Ignacio et al. “Curator: Self-Managing Storage for Enterprise Clusters”; University of Washington; published Mar. 2017; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Mar. 2, 2020), from https://nutanixbible.com/; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Sep. 1, 2020), from https://nutanixbible.com/; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Mar. 2, 2021), from https://nutanixbible.com/; pp. all. |
| Poitras, Steven. “The Nutanix Bible” (Sep. 3, 2021), from https://nutanixbible.com/; pp. all. |
| “Common Tasks—Remote Replication”, Arcserve https://support.storagecraft.com/s/article/common-tasks-remote-replication-ox?language=en_US, Oct. 20, 2021, pp. 1-11. |
| “Storage Replica Overview”, Microsoft https://docs.microsoft.com/en-us/windows-server/storage/storage-replica/storage-replica-overview, Jul. 29, 2021, pp. 1-11. |
| “Introduction to Oracle Data Guard”, Oracle https://docs.oracle.com/en/database/oracle/oracle-database/19/sbydb/introduction-to-oracle-data-guard-concepts.html#GUID-5E73667D-4A56-445E-911F-1E99092DD8D7, pp. 1-20. |
| “Nutanix Files Guide”, Nutanix Files 3.7, Nov. 23, 2021, pp. 1-174. |
| “Server-to-Server Storage Replication with Storage Replica”, Microsoft https://docs.microsoft.com/en-us/windows-server/storage/storage-replica/server-to-server-storage-replication, Jul. 29, 2021, pp. 1-20. |
| “Nutanix-Files”, Nutanix, Inc. v7.0 https://download.nutanix.com/solutionsDocs/TN-2041-Nutanix-Files.pdf, Oct. 2021, pp. 1-89. |
| U.S. Appl. No. 18/410,903 titled “Systems and Methods for Generating Consistent Global Identifiers Within Adistributed File Server Environment Including Examples of Global Identifiersacross Domains” filed Jan. 11, 2024. |
| Carbonite Availability for Windows User's Guide Version 8.1.0, Carbonite, Inc. (United States) , Feb. 27, 2018 , pp. 1-391. |
| IBM Storwize V7000 Unified, https://www.ibm.com/docs/en/flashsystem-v7000u/1.6.2?topic=maim-best-practices-authentication-id-mapping-configurations-while-using-asynchronous-replication-remote-caching , Mar. 31, 2021 , pp. 1-3. |
| ID mapping basic concepts, https://www.ibm.com/docs/en/flashsystem-v7000u/1.6.2?topic=mapping-id-basic-concepts , Feb. 27, 2021 , pp. 1-8. |
| Number | Date | Country | |
|---|---|---|---|
| 20230056217 A1 | Feb 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 63264204 | Nov 2021 | US | |
| 63260438 | Aug 2021 | US |
