Patent ID: 12192280

DETAILED DESCRIPTION

In some data management system (DMS) architectures, the control-plane may common to multiple customers or tenants. Each customer/tenant may have a private data-plane. A data-plane may include a set of virtual machines, which may also be referred to as a node cluster (e.g., virtual machines may also be referred to as nodes), across which customer or tenant data is stored. Each node cluster includes a controller which manages the nodes of the node cluster. Separating each customer/tenant's data into separate node clusters provides fault isolation for the different customers/tenants and provides security by limiting access to data for each customer/tenant. Node clusters may be hosted externally (e.g., on Microsoft Azure). The control-plane manages tasks, such as storing backups or snapshots or performing restorations, across the multiple node clusters. The control plane may include a DMS. A single service at the control-plane may communicate tasks queued by the control-plane taskchain (also referred to as a taskchain controller) with the various node cluster controllers. The control-plane may manage thousands of node clusters, and thousands of tasks per node cluster. Use of a single additional service at the control-plane to communicate between the taskchain controller and the various node controllers, therefore, may result in high latency and may introduce a single point of failure for all of the node clusters.

Aspects of the present disclosure involve techniques for direct communication between the taskchain controller of the control plane and the multiple node clusters. In some aspects, each node cluster may include a proxy service that is directly accessible by the taskchain controller based on the network address of the proxy service. The proxy service may route communications (e.g., transmission control protocol (TCP) packets) between the taskchain controller and the nodes of the node cluster. For example, the proxy service may be deployed at the node controller for the node cluster. For a given node cluster, the taskchain controller may communicate a command to add a new node to the node controller, and the node controller may create a new node based on the command. The proxy service may route communications between the node and the taskchain controller. In some aspects, a service bus may be created for a node cluster. The service bus may be deployed onto one of the nodes of the node cluster, and may be directly accessible by the taskchain controller. After creation of a node, communications may be routed between the taskchain of the control-plane and the node via the service bus (e.g., in a queued manner). A service bus and a proxy service may coexist on the same node cluster, and the taskchain controller may communicate some tasks via the proxy service and some tasks via the service bus, for example, based on priority or traffic conditions.

FIG.1illustrates an example of a computing environment100that supports reliable and high-performance connectivity between control-planes and data-planes for a DMS in accordance with aspects of the present disclosure. The computing environment100may include a computing system105, a DMS110, and one or more computing devices115, which may be in communication with one another via a network120. The computing system105may generate, store, process, modify, or otherwise use associated data, and the DMS110may provide one or more data management services for the computing system105. For example, the DMS110may provide a data backup service, a data recovery service, a data classification service, a data transfer or replication service, one or more other data management services, or any combination thereof for data associated with the computing system105.

The network120may allow the one or more computing devices115, the computing system105, and the DMS110to communicate (e.g., exchange information) with one another. The network120may include aspects of one or more wired networks (e.g., the Internet), one or more wireless networks (e.g., cellular networks), or any combination thereof. The network120may include aspects of one or more public networks or private networks, as well as secured or unsecured networks, or any combination thereof. The network120also may include any quantity of communications links and any quantity of hubs, bridges, routers, switches, ports or other physical or logical network components.

A computing device115may be used to input information to or receive information from the computing system105, the DMS110, or both. For example, a user of the computing device115may provide user inputs via the computing device115, which may result in commands, data, or any combination thereof being communicated via the network120to the computing system105, the DMS110, or both. Additionally, or alternatively, a computing device115may output (e.g., display) data or other information received from the computing system105, the DMS110, or both. A user of a computing device115may, for example, use the computing device115to interact with one or more user interfaces (e.g., graphical user interfaces (GUIs)) to operate or otherwise interact with the computing system105, the DMS110, or both. Though one computing device115is shown inFIG.1, it is to be understood that the computing environment100may include any quantity of computing devices115.

A computing device115may be a stationary device (e.g., a desktop computer or access point) or a mobile device (e.g., a laptop computer, tablet computer, or cellular phone). In some examples, a computing device115may be a commercial computing device, such as a server or collection of servers. And in some examples, a computing device115may be a virtual device (e.g., a virtual machine). Though shown as a separate device in the example computing environment ofFIG.1, it is to be understood that in some cases a computing device115may be included in (e.g., may be a component of) the computing system105or the DMS110.

The computing system105may include one or more servers125and may provide (e.g., to the one or more computing devices115) local or remote access to applications, databases, or files stored within the computing system105. The computing system105may further include one or more data storage devices130. Though one server125and one data storage device130are shown inFIG.1, it is to be understood that the computing system105may include any quantity of servers125and any quantity of data storage devices130, which may be in communication with one another and collectively perform one or more functions ascribed herein to the server125and data storage device130.

A data storage device130may include one or more hardware storage devices operable to store data, such as one or more hard disk drives (HDDs), magnetic tape drives, solid-state drives (SSDs), storage area network (SAN) storage devices, or network-attached storage (NAS) devices. In some cases, a data storage device130may comprise a tiered data storage infrastructure (or a portion of a tiered data storage infrastructure). A tiered data storage infrastructure may allow for the movement of data across different tiers of the data storage infrastructure between higher-cost, higher-performance storage devices (e.g., SSDs and HDDs) and relatively lower-cost, lower-performance storage devices (e.g., magnetic tape drives). In some examples, a data storage device130may be a database (e.g., a relational database), and a server125may host (e.g., provide a database management system for) the database.

A server125may allow a client (e.g., a computing device115) to download information or files (e.g., executable, text, application, audio, image, or video files) from the computing system105, to upload such information or files to the computing system105, or to perform a search query related to particular information stored by the computing system105. In some examples, a server125may act as an application server or a file server. In general, a server125may refer to one or more hardware devices that act as the host in a client-server relationship or a software process that shares a resource with or performs work for one or more clients.

A server125may include a network interface140, processor145, memory150, disk155, and computing system manager160. The network interface140may enable the server125to connect to and exchange information via the network120(e.g., using one or more network protocols). The network interface140may include one or more wireless network interfaces, one or more wired network interfaces, or any combination thereof. The processor145may execute computer-readable instructions stored in the memory150in order to cause the server125to perform functions ascribed herein to the server125. The processor145may include one or more processing units, such as one or more central processing units (CPUs), one or more graphics processing units (GPUs), or any combination thereof. The memory150may comprise one or more types of memory (e.g., random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), read-only memory ((ROM), electrically erasable programmable read-only memory (EEPROM), Flash, etc.). Disk155may include one or more HDDs, one or more SSDs, or any combination thereof. Memory150and disk155may comprise hardware storage devices. The computing system manager160may manage the computing system105or aspects thereof (e.g., based on instructions stored in the memory150and executed by the processor145) to perform functions ascribed herein to the computing system105. In some examples, the network interface140, processor145, memory150, and disk155may be included in a hardware layer of a server125, and the computing system manager160may be included in a software layer of the server125. In some cases, the computing system manager160may be distributed across (e.g., implemented by) multiple servers125within the computing system105.

In some examples, the computing system105or aspects thereof may be implemented within one or more cloud computing environments, which may alternatively be referred to as cloud environments. Cloud computing may refer to Internet-based computing, wherein shared resources, software, and/or information may be provided to one or more computing devices on-demand via the Internet. A cloud environment may be provided by a cloud platform, where the cloud platform may include physical hardware components (e.g., servers) and software components (e.g., operating system) that implement the cloud environment. A cloud environment may implement the computing system105or aspects thereof through Software-as-a-Service (SaaS) or Infrastructure-as-a-Service (IaaS) services provided by the cloud environment. SaaS may refer to a software distribution model in which applications are hosted by a service provider and made available to one or more client devices over a network (e.g., to one or more computing devices115over the network120). IaaS may refer to a service in which physical computing resources are used to instantiate one or more virtual machines, the resources of which are made available to one or more client devices over a network (e.g., to one or more computing devices115over the network120).

In some examples, the computing system105or aspects thereof may implement or be implemented by one or more virtual machines. The one or more virtual machines may run various applications, such as a database server, an application server, or a web server. For example, a server125may be used to host (e.g., create, manage) one or more virtual machines, and the computing system manager160may manage a virtualized infrastructure within the computing system105and perform management operations associated with the virtualized infrastructure. The computing system manager160may manage the provisioning of virtual machines running within the virtualized infrastructure and provide an interface to a computing device115interacting with the virtualized infrastructure. For example, the computing system manager160may be or include a hypervisor and may perform various virtual machine-related tasks, such as cloning virtual machines, creating new virtual machines, monitoring the state of virtual machines, moving virtual machines between physical hosts for load balancing purposes, and facilitating backups of virtual machines. In some examples, the virtual machines, the hypervisor, or both, may virtualize and make available resources of the disk155, the memory, the processor145, the network interface140, the data storage device130, or any combination thereof in support of running the various applications. Storage resources (e.g., the disk155, the memory150, or the data storage device130) that are virtualized may be accessed by applications as a virtual disk.

The DMS110may provide one or more data management services for data associated with the computing system105and may include DMS manager190and any quantity of storage nodes185. The DMS manager190may manage operation of the DMS110, including the storage nodes185. Though illustrated as a separate entity within the DMS110, the DMS manager190may in some cases be implemented (e.g., as a software application) by one or more of the storage nodes185. In some examples, the storage nodes185may be included in a hardware layer of the DMS110, and the DMS manager190may be included in a software layer of the DMS110. In the example illustrated inFIG.1, the DMS110is separate from the computing system105but in communication with the computing system105via the network120. It is to be understood, however, that in some examples at least some aspects of the DMS110may be located within computing system105. For example, one or more servers125, one or more data storage devices130, and at least some aspects of the DMS110may be implemented within the same cloud environment or within the same data center.

Storage nodes185of the DMS110may include respective network interfaces165, processors170, memories175, and disks180. The network interfaces165may enable the storage nodes185to connect to one another, to the network120, or both. A network interface165may include one or more wireless network interfaces, one or more wired network interfaces, or any combination thereof. The processor170of a storage node185may execute computer-readable instructions stored in the memory175of the storage node185in order to cause the storage node185to perform processes described herein as performed by the storage node185. A processor170may include one or more processing units, such as one or more CPUs, one or more GPUs, or any combination thereof. The memory150may comprise one or more types of memory (e.g., RAM, SRAM, DRAM, ROM, EEPROM, Flash, etc.). A disk180may include one or more HDDs, one or more SDDs, or any combination thereof. Memories175and disks180may comprise hardware storage devices. Collectively, the storage nodes185may in some cases be referred to as a storage cluster or as a cluster of storage nodes185.

The DMS110may provide a backup and recovery service for the computing system105. For example, the DMS110may manage the extraction and storage of snapshots135associated with different point-in-time versions of one or more target computing objects within the computing system105. A snapshot135of a computing object (e.g., a virtual machine, a database, a filesystem, a virtual disk, a virtual desktop, or other type of computing system or storage system) may be a file (or set of files) that represents a state of the computing object (e.g., the data thereof) as of a particular point in time. A snapshot135may also be used to restore (e.g., recover) the corresponding computing object as of the particular point in time corresponding to the snapshot135. A computing object of which a snapshot135may be generated may be referred to as snappable. Snapshots135may be generated at different times (e.g., periodically or on some other scheduled or configured basis) in order to represent the state of the computing system105or aspects thereof as of those different times. In some examples, a snapshot135may include metadata that defines a state of the computing object as of a particular point in time. For example, a snapshot135may include metadata associated with (e.g., that defines a state of) some or all data blocks included in (e.g., stored by or otherwise included in) the computing object. Snapshots135(e.g., collectively) may capture changes in the data blocks over time. Snapshots135generated for the target computing objects within the computing system105may be stored in one or more storage locations (e.g., the disk155, memory150, the data storage device130) of the computing system105, in the alternative or in addition to being stored within the DMS110, as described below.

To obtain a snapshot135of a target computing object associated with the computing system105(e.g., of the entirety of the computing system105or some portion thereof, such as one or more databases, virtual machines, or filesystems within the computing system105), the DMS manager190may transmit a snapshot request to the computing system manager160. In response to the snapshot request, the computing system manager160may set the target computing object into a frozen state (e.g., a read-only state). Setting the target computing object into a frozen state may allow a point-in-time snapshot135of the target computing object to be stored or transferred.

In some examples, the computing system105may generate the snapshot135based on the frozen state of the computing object. For example, the computing system105may execute an agent of the DMS110(e.g., the agent may be software installed at and executed by one or more servers125), and the agent may cause the computing system105to generate the snapshot135and transfer the snapshot to the DMS110in response to the request from the DMS110. In some examples, the computing system manager160may cause the computing system105to transfer, to the DMS110, data that represents the frozen state of the target computing object, and the DMS110may generate a snapshot135of the target computing object based on the corresponding data received from the computing system105.

Once the DMS110receives, generates, or otherwise obtains a snapshot135, the DMS110may store the snapshot135at one or more of the storage nodes185. The DMS110may store a snapshot135at multiple storage nodes185, for example, for improved reliability. Additionally, or alternatively, snapshots135may be stored in some other location connected with the network120. For example, the DMS110may store more recent snapshots135at the storage nodes185, and the DMS110may transfer less recent snapshots135via the network120to a cloud environment (which may include or be separate from the computing system105) for storage at the cloud environment, a magnetic tape storage device, or another storage system separate from the DMS110.

Updates made to a target computing object that has been set into a frozen state may be written by the computing system105to a separate file (e.g., an update file) or other entity within the computing system105while the target computing object is in the frozen state. After the snapshot135(or associated data) of the target computing object has been transferred to the DMS110, the computing system manager160may release the target computing object from the frozen state, and any corresponding updates written to the separate file or other entity may be merged into the target computing object.

In response to a restore command (e.g., from a computing device115or the computing system105), the DMS110may restore a target version (e.g., corresponding to a particular point in time) of a computing object based on a corresponding snapshot135of the computing object. In some examples, the corresponding snapshot135may be used to restore the target version based on data of the computing object as stored at the computing system105(e.g., based on information included in the corresponding snapshot135and other information stored at the computing system105, the computing object may be restored to its state as of the particular point in time). Additionally, or alternatively, the corresponding snapshot135may be used to restore the data of the target version based on data of the computing object as included in one or more backup copies of the computing object (e.g., file-level backup copies or image-level backup copies). Such backup copies of the computing object may be generated in conjunction with or according to a separate schedule than the snapshots135. For example, the target version of the computing object may be restored based on the information in a snapshot135and based on information included in a backup copy of the target object generated prior to the time corresponding to the target version. Backup copies of the computing object may be stored at the DMS110(e.g., in the storage nodes185) or in some other location connected with the network120(e.g., in a cloud environment, which in some cases may be separate from the computing system105).

In some examples, the DMS110may restore the target version of the computing object and transfer the data of the restored computing object to the computing system105. And in some examples, the DMS110may transfer one or more snapshots135to the computing system105, and restoration of the target version of the computing object may occur at the computing system105(e.g., as managed by an agent of the DMS110, where the agent may be installed and operate at the computing system105).

In response to a mount command (e.g., from a computing device115or the computing system105), the DMS110may instantiate data associated with a point-in-time version of a computing object based on a snapshot135corresponding to the computing object (e.g., along with data included in a backup copy of the computing object) and the point-in-time. The DMS110may then allow the computing system105to read or modify the instantiated data (e.g., without transferring the instantiated data to the computing system). In some examples, the DMS110may instantiate (e.g., virtually mount) some or all of the data associated with the point-in-time version of the computing object for access by the computing system105, the DMS110, or the computing device115.

In some examples, the DMS110may store different types of snapshots, including for the same computing object. For example, the DMS110may store both base snapshots135and incremental snapshots135. A base snapshot135may represent the entirety of the state of the corresponding computing object as of a point in time corresponding to the base snapshot135. An incremental snapshot135may represent the changes to the state—which may be referred to as the delta—of the corresponding computing object that have occurred between an earlier or later point in time corresponding to another snapshot135(e.g., another base snapshot135or incremental snapshot135) of the computing object and the incremental snapshot135. In some cases, some incremental snapshots135may be forward-incremental snapshots135and other incremental snapshots135may be reverse-incremental snapshots135. To generate a full snapshot135of a computing object using a forward-incremental snapshot135, the information of the forward-incremental snapshot135may be combined with (e.g., applied to) the information of an earlier base snapshot135of the computing object along with the information of any intervening forward-incremental snapshots135, where the earlier base snapshot135may include a base snapshot135and one or more reverse-incremental or forward-incremental snapshots135. To generate a full snapshot135of a computing object using a reverse-incremental snapshot135, the information of the reverse-incremental snapshot135may be combined with (e.g., applied to) the information of a later base snapshot135of the computing object along with the information of any intervening reverse-incremental snapshots135.

In some examples, the DMS110may provide a data classification service, a malware detection service, a data transfer or replication service, backup verification service, or any combination thereof, among other possible data management services for data associated with the computing system105. For example, the DMS110may analyze data included in one or more computing objects of the computing system105, metadata for one or more computing objects of the computing system105, or any combination thereof, and based on such analysis, the DMS110may identify locations within the computing system105that include data of one or more target data types (e.g., sensitive data, such as data subject to privacy regulations or otherwise of particular interest) and output related information (e.g., for display to a user via a computing device115). Additionally, or alternatively, the DMS110may detect whether aspects of the computing system105have been impacted by malware (e.g., ransomware). Additionally, or alternatively, the DMS110may relocate data or create copies of data based on using one or more snapshots135to restore the associated computing object within its original location or at a new location (e.g., a new location within a different computing system105). Additionally, or alternatively, the DMS110may analyze backup data to ensure that the underlying data (e.g., user data or metadata) has not been corrupted. The DMS110may perform such data classification, malware detection, data transfer or replication, or backup verification, for example, based on data included in snapshots135or backup copies of the computing system105, rather than live contents of the computing system105, which may beneficially avoid adversely affecting (e.g., infecting, loading, etc.) the computing system105.

In the DMS110, the control-plane may be common to multiple customers/tenants. Each customer/tenant may have a private data-plane. For example, as described herein, the DMS110may transfer snapshots135via the network120to a cloud environment194. Each customer/tenant may have a private cloud environment (e.g., Microsoft Azure) which includes a node cluster195. across which customer or tenant data is stored. Each node cluster195includes a node controller196which manages the nodes197of the node cluster195. Separating each customer/tenant's data into separate node clusters195provides fault isolation for the different customers/tenants and provides security by limiting access to data for each customer/tenant. Node clusters195may be hosted externally (e.g., on Microsoft Azure). The control-plane (e.g., the DMS, and specifically the DMS manager190) manages tasks, such as storing backups or snapshots or performing restorations, across the multiple node clusters195. A single service at the control-plane may communicate tasks queued by the control-plane taskchain (also referred to as a taskchain controller) with the various node controllers196. For example, the taskchain controller may be the DMS manager190as described herein. The control-plane may manage thousands of node clusters195, and thousands of tasks per node cluster195. Use of a single additional service at the control-plane to communicate between the taskchain controller and the various node controllers196, therefore, may result in high latency and may introduce a single point of failure for all of the node clusters195.

The taskchain controller of the control plane (e.g., the DMS manager190) may directly communicate with the multiple node clusters195. In some aspects, each node cluster195may include a proxy service198that is directly accessible by the taskchain controller, based on the network address of the proxy service198. The proxy service198may route communications (e.g., TCP packets) between the taskchain controller (e.g., the DMS manager190) and the nodes197of the node cluster195. For example, the proxy service198may be deployed at the node controller196for the node cluster195. For a given node cluster195, the taskchain controller may communicate a command to add a new node197to the node controller196, and the node controller196may create a new node197based on the command. The proxy service198may route future communications between the node197and the taskchain controller. In some aspects, a service bus199may be created for a node cluster195. The service bus199may be deployed onto one of the nodes of the node cluster195, and may be directly accessible by the taskchain controller. After creation of a node195, communications may be routed between the taskchain of the control-plane and the node197via the service bus199(e.g., in a queued manner). A service bus199and a proxy service198may coexist on the same node cluster195, and the taskchain controller may communicate some tasks via the proxy service198and some tasks via the service bus199, for example, based on priority or traffic conditions.

FIG.2shows an example of a computing environment200that supports reliable and high-performance connectivity between control-planes and data-planes for a DMS in accordance with aspects of the present disclosure. The computing environment200may implement or be implemented by aspects of the computing environment100described with reference toFIG.1.

As described herein, a DMS205may be common to multiple customers/tenants. The DMS may manage data protection tasks for the multiple customers/tenants. Each customer/tenant may have a private data-plane at a cloud environment215. Each private data plane may include node cluster220(e.g., data for a first customer/tenant is stored at the node cluster220-aand data for a second customer/tenant is stored at the node cluster220-b). Each node cluster includes a node controller225(e.g., the node cluster220-aincludes a node controller225-aand the node cluster220-bincludes a node controller225-b). The node controller225manages the nodes230(e.g., virtual machines). For example, the node cluster220may be a Microsoft Azure Kubernetes Service (AKS) cluster, and the node controller225may be a AKS application programming interface (API). Customer/tenant data (e.g., backup data and snapshots) may be stored across the nodes230. Although two node clusters are shown (e.g., the node cluster220-aand the node cluster220-b), the DMS205may support thousands of node clusters for thousands of customers/tenants. The DMS205may support low-latency, high-throughput communications with the node clusters220.

A taskchain controller210at the DMS may queue data protection tasks (e.g., read and/or write operations) for the multiple node clusters220. As described herein, the taskchain controller210may establish a direct connection245with the node controller225of each node cluster (e.g., a direct connection245-awith the node controller225-aand a direct connection245-bwith the node controller225-b). For example, the direct connection245may be established based on the network address of the node controller225(e.g., when the node controller225is an API). For example, the direct connection245may be an HTTP connection. In some examples, the direct connection may be a remote procedure call (RPC) tunnel between the taskchain controller210and the node controller225. The node controller may communicate with the nodes230. DMS205may manage thousands of data protection tasks per node cluster220, and accordingly across thousands of node clusters220, the DMS205may manage millions of connections and tasks. High throughput may be demanded for small messages.

The taskchain controller210may transmit a request255via the direct connection245-ato the node controller225-ato add a node. In response to the request255, the node controller225-amay add a node (e.g., the node230-a). The node controller225-amay indicate in a control message260an identifier (e.g., a port number or a node index) for the node230-a. The taskchain controller210may identify a network address for routing a data protection task commands to the node230-a. For example, the node cluster may include a proxy service235-aat the node controller which routes data protection tasks265to nodes230based on port numbers or node indexes. The proxy service235-amay be an intermediate machine (e.g., the node controller225-a). The proxy service235-ahas access to the nodes (e.g., the node230-aand the node230-bas shown inFIG.2). In some examples, the proxy service235-amay be hosted on a machine or virtual machine other than the node controller225-a. The machine on which the proxy service235-ais hosted has access to the nodes230of the node cluster220-ain order to route data protection tasks to the nodes230. The proxy service235-amay be directly accessible by the taskchain controller210(e.g., the network address of the proxy service235-amay be known to the taskchain controller210such that the taskchain controller210can establish an HTTP connection with the proxy service235-a). For example, the taskchain controller210may establish an RPC tunnel with the node controller225-abased on the network address of the node controller225-a, and the proxy service235-amay be hosted on the node controller225-a. The data protection tasks may be communicated as TCP packets. The proxy service235-amay accept TCP packets from the taskchain controller210and routes the TCP packets to the indicated nodes230of the node cluster220-a(e.g., based on a node identifier, node index, or a port number indicated by the taskchain controller210with the TCP packets). Use of a proxy service235-amay provide a simple and low-cost solution, as a node controller225is already provided per node cluster220. Use of a proxy service235allows nodes230to remain private/transparent to the DMS205and the taskchain controller210, thereby increasing security. As the node controller can have heavy traffic conditions, at times scalability may affect the performance of a proxy service implementation.

As another example, the node cluster220-amay include a service bus240-a. The service bus240-amay be hosted on a node230of the node cluster220. The taskchain controller210may establish a direct connection250-awith the service bus240-a. For example, the node controller225-amay create the service bus240-aand transmit a control message270to the taskchain controller210which indicates the network address for the service bus240-a. The taskchain controller210may establish a direct connection250-awith the service bus240-ausing the network address for the service bus240-a(e.g., an HTTP connection). In some examples, the direct connection250-awith the service bus240-amay be an RPC tunnel between the taskchain controller210and the service bus240-a. The service bus240-amay route data protection task commands265to nodes230based on port numbers or node indexes for the respective nodes. The service bus240-amay have improved performance and scalability as compared to the proxy service235-a. The taskchain controller210may send TCP packets to the service bus240-afor relay onto the target nodes as individual messages in a queue. Deploying the service bus240-aonto a node of the node cluster220-aas compared to the node controller225-amay reduce scalability and traffic issues associated with the proxy service approach. The service bus approach exposes one of the nodes of the node cluster220-ato the taskchain controller210. Use of a node at the node cluster as a service bus240-amay involve increase resource usage as compared to the proxy service approach.

In some examples, a proxy service235-aand a service bus240-amay coexist at a node cluster220-a. For example, the taskchain controller210may route data protection tasks265-athrough the proxy service235-afor lower priority tasks that do not demand high performance or low latency and may route data protection tasks265-bthrough the service bus240-afor higher priority tasks or tasks that demand high performance or low latency. As another example, the taskchain controller210may route data protection tasks265through the proxy service235-aor through the service bus240-abased on traffic conditions at the node controller225-a(e.g., the proxy service235-amay be used for low traffic conditions at the node controller225-aand the service bus240-amay be used for high traffic conditions at the node controller225-a). In some examples, a service bus240-amay be created or terminated based on traffic conditions at the node controller225-a. In some examples, the taskchain controller210may request creation of a service bus240, for example, for routing of high priority data protection tasks or for routing of data protection tasks that demand high performance or low latency.

As described herein, the taskchain controller210may manage data protection tasks for the multiple customers/tenants of the DMS205. Accordingly, the taskchain controller210may similarly establish a direct connection245-bwith the node controller225-bof a second node cluster220-bassociated with a second customer/tenant and/or a direct connection250-bwith a service bus240-bof the second node cluster220-b. The taskchain controller210may route data protection tasks to nodes (e.g., node230-cand node230-d) of the node cluster220-bvia a proxy service235-bor a service bus240-bat the node cluster220-b.

As the service bus240uses a message oriented architecture, the service bus240-amay allow asynchronous communication between the control plane (e.g., DMS205and the taskchain controller210) and the data plane (e.g., the nodes230of the node clusters220) managed by the control plane. Asynchronous communication allows for efficient processing as neither the control node the data plane waits for the other side to respond, which may lead to improved ability to handle peak traffic and may lead to improved scalability and reliability for the DMS205. The queue solution used by the service bus240may provide message persistence, ensuring that messages are not lost in the event of a system failure. In some examples, the service bus240may report performance statistics, and accordingly the DMS205may monitor the performance of the communication between the data plane and the control plane.

Use of the service bus240or a proxy service235to route data protection tasks between the taskchain controller210and the nodes230provides the ability to maintain firewalls at the node clusters220and to maintain the private nature of the node clusters. For example, an RPC tunnel between the taskchain controller210and the node controller225or the service bus240of a node cluster does not punch a hole in the customer or tenant's firewall for the node cluster220. Use of the HTTP connection with the proxy service235or the service bus, while keeping the remaining nodes private, may increase security and customer/tenant privacy, and may ensure that authorized traffic is routed correctly while ensuring that unauthorized traffic is not allowed to flow between the control and data planes. The service bus240or a proxy service235may use built in Kubernetes mechanisms for load balancing and failover, allowing for high availability and ease of integration. The service bus240or a proxy service235may provide for load balancing by routing traffic across nodes230to ensure resource utilization across the node clusters. Deployment at the node controller or as a node of a node cluster may promote decentralization and thereby eliminate single points of failure.

FIG.3shows an example of a process flow300that supports reliable and high-performance connectivity between control-planes and data-planes for a DMS in accordance with aspects of the present disclosure. The process flow300may implement or be implemented by aspects ofFIGS.1-2. For example, the process flow300includes a DMS305, which may be an example of a DMS110or a DMS205as described herein. The DMS305may include a taskchain controller310, which may be an example of a taskchain controller210as described herein. The process flow300may include a node cluster320, which may be an example of a node cluster220as described herein. The node cluster320may include a node controller325, which may be an example of a node controller225as described herein. The node cluster320may include a node330, which may be an example of a node230as described herein. The node cluster320may include a service bus340which may be an example of a service bus240as described herein.

In the following description of the process flow300, the operations between the taskchain controller310, the node controller325, the node330, and the service bus340may be transmitted in a different order than the example order shown, or the operations performed by the taskchain controller310, the node controller325, the node330, and the service bus340may be performed in different orders or at different times. Some operations may also be omitted from the process flow300, and other operations may be added to the process flow300. The taskchain controller310may schedule data protection tasks for multiple node clusters including the node cluster320, and each node cluster may be associated with a tenant or customer of the DMS305.

At350, the taskchain controller310may establish a direct connection with the node controller325based on a network address of the node controller.

In some examples, at355, the taskchain controller310may establish a direct connection with a service bus340of the node cluster based on a network address of the service bus340. For example, the node controller325may indicate the network address of the service bus340to the taskchain controller310.

At360, the taskchain controller310may send a request to the node controller325to add a node330to the node cluster320. At365, the node controller325may add the node330to the node cluster320in response to the request. In some examples, at370, the node controller may indicate an identifier for the node330(e.g., a port, a node index, or a node identifier) that the taskchain controller310may use to identify the node in subsequent data protection task commands.

At375, the taskchain controller310may identify a network address (e.g., the network address for the node controller325or the network address for the service bus340) via which to route data protection tasks from the taskchain controller310to the node330.

In some examples, at380, the taskchain controller310may send a control message to the node controller325(e.g., to a proxy service at the node controller325) indicating for the node330to perform a data protection task. The control message may indicate an identifier for the node330(e.g., the identifier indicated at370). At385, the node controller325(e.g., a proxy service at the node controller325) may route the control message indicating to perform data management task to the node330. In some examples, the node controller325may indicate to the taskchain controller310that the node controller hosts a proxy service that may route control messages indicating for the node330to perform a data protection task to the node330.

In some examples, at390, the taskchain controller310may send a control message to the service bus340indicating for the node330to perform a data protection task. The control message may indicate an identifier for the node (e.g., the identifier indicated at370). At395, the service bus340may route the control message indicating to perform data management task to the node330.

In some examples, a proxy service at the node controller325may coexist with the service bus340. The taskchain controller310may route data protection tasks through the proxy service for lower priority tasks that do not demand high performance or low latency and may route data protection tasks through the service bus340for higher priority tasks or tasks that demand high performance or low latency. As another example, the taskchain controller310may route data protection tasks through the proxy service or through the service bus340based on traffic conditions at the node controller325(e.g., the proxy service may be used for low traffic conditions at the node controller325and the service bus340may be used for high traffic conditions at the node controller325). In some examples, a service bus240-amay be created or terminated based on traffic conditions at the node controller325). In some examples, the taskchain controller310may request creation of a service bus, for example, for routing of high priority data protection tasks or for routing of data protection tasks that demand high performance or low latency.

In some examples, the taskchain controller310may send a request to the node controller325to add the service bus340to the node cluster, for example based on identifying that a traffic load at the node controller325exceeds a threshold. In some examples, the node controller325may add the service bus340to the node cluster320based on the node controller325identifying that a traffic load at the node controller325exceeds a threshold. In some examples, the taskchain controller310may send a request to the node controller325to remove the service bus340based on identifying that the traffic load at the node controller325is below a threshold, and in response, the node controller325may terminate the service bus340. In some examples, the node controller325may terminate the service bus340in response to the node controller325identifying that the traffic load at the node controller325is below a threshold. The node controller325may indicate to the taskchain controller310when the service bus340is added to the node cluster320or terminated.

In some examples, the taskchain controller310may send a request to the node controller325to add a second node to the node cluster320. The taskchain controller310may receive, from the node controller325in response to the request, an indication of a second node identifier for the second node (e.g., a second port, a second node identifier, or a second node index). The taskchain controller310may send a control message to the node controller325or to the service bus340that indicates for the second node to perform a data protection task, and the control message may include the second node identifier. The node controller325(e.g., the proxy service) or to the service bus340may route the control message that requests the second node to perform the data protection task to the second node based on the control message including the second node identifier.

FIG.4shows a block diagram400of a system405that supports reliable and high-performance connectivity between control-planes and data-planes for a DMS in accordance with aspects of the present disclosure. In some examples, the system405may be an example of aspects of one or more components described with reference toFIG.1, such as a DMS110. The system405may include an input interface410, an output interface415, and a taskchain controller420. The system405may also include one or more processors. Each of these components may be in communication with one another (e.g., via one or more buses, communications links, communications interfaces, or any combination thereof).

The input interface410may manage input signaling for the system405. For example, the input interface410may receive input signaling (e.g., messages, packets, data, instructions, commands, or any other form of encoded information) from other systems or devices. The input interface410may send signaling corresponding to (e.g., representative of or otherwise based on) such input signaling to other components of the system405for processing. For example, the input interface410may transmit such corresponding signaling to the taskchain controller420to support reliable and high-performance connectivity between control-planes and data-planes for a DMS. In some cases, the input interface410may be a component of a network interface625as described with reference toFIG.6.

The output interface415may manage output signaling for the system405. For example, the output interface415may receive signaling from other components of the system405, such as the taskchain controller420, and may transmit such output signaling corresponding to (e.g., representative of or otherwise based on) such signaling to other systems or devices. In some cases, the output interface415may be a component of a network interface625as described with reference toFIG.6.

For example, the taskchain controller420may include a node controller connection manager425, a new node manager430, a node addressing manager435, or any combination thereof. In some examples, the taskchain controller420, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the input interface410, the output interface415, or both. For example, the taskchain controller420may receive information from the input interface410, send information to the output interface415, or be integrated in combination with the input interface410, the output interface415, or both to receive information, transmit information, or perform various other operations as described herein.

The node controller connection manager425may be configured as or otherwise support a means for establishing, at a taskchain controller of a DMS, a direct connection between the taskchain controller and a node controller of a first node cluster of a set of multiple node clusters, where the direct connection is based on a first network address of the node controller, where the set of multiple node clusters are associated with a respective set of multiple tenants of the DMS, where the taskchain controller of the DMS is operable to schedule data protection tasks for the set of multiple node clusters. The new node manager430may be configured as or otherwise support a means for sending, from the taskchain controller to the node controller via the direct connection, a request to add a node to the first node cluster. The node addressing manager435may be configured as or otherwise support a means for identifying, based on sending the request, a second network address associated with the first node cluster via which to route one or more data protection tasks from the taskchain controller to the node.

FIG.5shows a block diagram500of a taskchain controller520that supports reliable and high-performance connectivity between control-planes and data-planes for a DMS in accordance with aspects of the present disclosure. The taskchain controller520may be an example of aspects of a taskchain controller or a taskchain controller420, or both, as described herein. The taskchain controller520, or various components thereof, may be an example of means for performing various aspects of reliable and high-performance connectivity between control-planes and data-planes for a DMS as described herein. For example, the taskchain controller520may include a node controller connection manager525, a new node manager530, a node addressing manager535, a node identifier manager540, a data protection task manager545, a service bus identifier manager550, a service bus connection manager555, a service bus request manager560, a proxy service manager565, a node controller traffic manager570, a service bus termination manager575, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses, communications links, communications interfaces, or any combination thereof).

The node controller connection manager525may be configured as or otherwise support a means for establishing, at a taskchain controller of a DMS, a direct connection between the taskchain controller and a node controller of a first node cluster of a set of multiple node clusters, where the direct connection is based on a first network address of the node controller, where the set of multiple node clusters are associated with a respective set of multiple tenants of the DMS, where the taskchain controller of the DMS is operable to schedule data protection tasks for the set of multiple node clusters. The new node manager530may be configured as or otherwise support a means for sending, from the taskchain controller to the node controller via the direct connection, a request to add a node to the first node cluster. The node addressing manager535may be configured as or otherwise support a means for identifying, based on sending the request, a second network address associated with the first node cluster via which to route one or more data protection tasks from the taskchain controller to the node.

In some examples, the node identifier manager540may be configured as or otherwise support a means for receiving, at the taskchain controller from the node controller and in response to the request, an indication of an identifier for the node. In some examples, the data protection task manager545may be configured as or otherwise support a means for sending, from the taskchain controller directly to the second network address, a control message that indicates to perform a data protection task at the node, where the control message indicates the identifier for the node.

In some examples, to support sending the control message, the data protection task manager545may be configured as or otherwise support a means for sending the control message via the direct connection to a proxy service at the node controller for routing to the node based on the identifier, where the second network address is a same network address as the first network address.

In some examples, to support receiving the indication of the second network address, the service bus identifier manager550may be configured as or otherwise support a means for receiving an indication of the second network address for a second node of the first node cluster. In some examples, to support receiving the indication of the second network address, the service bus connection manager555may be configured as or otherwise support a means for establishing a second direct connection between the taskchain controller and the second node based on the second network address, where the control message is sent via the second direct connection.

In some examples, the service bus request manager560may be configured as or otherwise support a means for sending, from the taskchain controller to the node controller via the direct connection, a second request to add a service bus for the first node cluster, where reception of the indication of the second network address is responsive to the second request, and where the second node is the service bus.

In some examples, the service bus request manager560may be configured as or otherwise support a means for identifying a traffic load at the node controller exceeds a threshold, where sending the second request is based on identifying the traffic load at the node controller exceeds the threshold.

In some examples, the node controller traffic manager570may be configured as or otherwise support a means for identifying a traffic load at the node controller is below a threshold. In some examples, the service bus termination manager575may be configured as or otherwise support a means for sending, to the node controller via the direct connection, a third request to remove the service bus based on identifying the traffic load at the node controller is below the threshold. In some examples, the service bus termination manager575may be configured as or otherwise support a means for terminating the second direct connection based on identifying the traffic load at the node controller is below the threshold.

In some examples, the proxy service manager565may be configured as or otherwise support a means for receiving, at the taskchain controller from the node controller, an indication of a proxy service at the node controller via which to route the one or more data protection tasks from the taskchain controller to the node. In some examples, the data protection task manager545may be configured as or otherwise support a means for sending, from the taskchain controller to the proxy service via the direct connection, a second control message that indicates to perform a second data protection task at the node, where the second control message indicates the identifier for the node.

In some examples, the node controller traffic manager570may be configured as or otherwise support a means for identifying a traffic load at the node controller exceeds a threshold. In some examples, the data protection task manager545may be configured as or otherwise support a means for sending, from the taskchain controller to the second node via the second direct connection, a third control message that indicates to perform a third data protection task at the node, where the third control message indicates the identifier for the node.

In some examples, the new node manager530may be configured as or otherwise support a means for sending, from the taskchain controller to the node controller via the direct connection, a second request to add a second node to the first node cluster. In some examples, the node identifier manager540may be configured as or otherwise support a means for receiving, at the taskchain controller from the node controller and in response to the request, an indication of a second identifier for the second node. In some examples, the data protection task manager545may be configured as or otherwise support a means for sending, from the taskchain controller directly to the second network address, a second control message that indicates to perform a second data protection task at the second node, where the second control message indicates the identifier for the second node.

In some examples, the control message includes a transmission control protocol packet.

In some examples, the data protection task includes at least one of a write operation or a read operation.

FIG.6shows a block diagram600of a system605that supports reliable and high-performance connectivity between control-planes and data-planes for a DMS in accordance with aspects of the present disclosure. The system605may be an example of or include the components of a system405as described herein. The system605may include components for data management, including components such as a taskchain controller620, an input information610, an output information615, a network interface625, a memory630, a processor635, and a storage640. These components may be in electronic communication or otherwise coupled with each other (e.g., operatively, communicatively, functionally, electronically, electrically; via one or more buses, communications links, communications interfaces, or any combination thereof). Additionally, the components of the system605may include corresponding physical components or may be implemented as corresponding virtual components (e.g., components of one or more virtual machines). In some examples, the system605may be an example of aspects of one or more components described with reference toFIG.1, such as a DMS110.

The network interface625may enable the system605to exchange information (e.g., input information610, output information615, or both) with other systems or devices (not shown). For example, the network interface625may enable the system605to connect to a network (e.g., a network120as described herein). The network interface625may include one or more wireless network interfaces, one or more wired network interfaces, or any combination thereof. In some examples, the network interface625may be an example of may be an example of aspects of one or more components described with reference toFIG.1, such as one or more network interfaces165.

Memory630may include RAM, ROM, or both. The memory630may store computer-readable, computer-executable software including instructions that, when executed, cause the processor635to perform various functions described herein. In some cases, the memory630may contain, among other things, a basic input/output system (BIOS), which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some cases, the memory630may be an example of aspects of one or more components described with reference toFIG.1, such as one or more memories175.

The processor635may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, a field programmable gate array (FPGA), a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). The processor635may be configured to execute computer-readable instructions stored in a memory630to perform various functions (e.g., functions or tasks supporting reliable and high-performance connectivity between control-planes and data-planes for a DMS). Though a single processor635is depicted in the example ofFIG.6, it is to be understood that the system605may include any quantity of one or more of processors635and that a group of processors635may collectively perform one or more functions ascribed herein to a processor, such as the processor635. In some cases, the processor635may be an example of aspects of one or more components described with reference toFIG.1, such as one or more processors170.

Storage640may be configured to store data that is generated, processed, stored, or otherwise used by the system605. In some cases, the storage640may include one or more HDDs, one or more SDDs, or both. In some examples, the storage640may be an example of a single database, a distributed database, multiple distributed databases, a data store, a data lake, or an emergency backup database. In some examples, the storage640may be an example of one or more components described with reference toFIG.1, such as one or more network disks180.

For example, the taskchain controller620may be configured as or otherwise support a means for establishing, at a taskchain controller of a DMS, a direct connection between the taskchain controller and a node controller of a first node cluster of a set of multiple node clusters, where the direct connection is based on a first network address of the node controller, where the set of multiple node clusters are associated with a respective set of multiple tenants of the DMS, where the taskchain controller of the DMS is operable to schedule data protection tasks for the set of multiple node clusters. The taskchain controller620may be configured as or otherwise support a means for sending, from the taskchain controller to the node controller via the direct connection, a request to add a node to the first node cluster. The taskchain controller620may be configured as or otherwise support a means for identifying, based on sending the request, a second network address associated with the first node cluster via which to route one or more data protection tasks from the taskchain controller to the node.

By including or configuring the taskchain controller620in accordance with examples as described herein, the system605may support techniques for reliable and high-performance connectivity between control-planes and data-planes for a DMS, which may provide one or more benefits such as, for example, improved reliability, reduced latency, improved scalability, and improved security, among other possibilities.

FIG.7shows a flowchart illustrating a method700that supports reliable and high-performance connectivity between control-planes and data-planes for a DMS in accordance with aspects of the present disclosure. The operations of the method700may be implemented by a DMS or its components as described herein. For example, the operations of the method700may be performed by a DMS as described with reference toFIGS.1through6. In some examples, a DMS may execute a set of instructions to control the functional elements of the DMS to perform the described functions. Additionally, or alternatively, the DMS may perform aspects of the described functions using special-purpose hardware.

At705, the method may include establishing, at a taskchain controller of a DMS, a direct connection between the taskchain controller and a node controller of a first node cluster of a set of multiple node clusters, where the direct connection is based on a first network address of the node controller, where the set of multiple node clusters are associated with a respective set of multiple tenants of the DMS, where the taskchain controller of the DMS is operable to schedule data protection tasks for the set of multiple node clusters. The operations of block705may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of705may be performed by a node controller connection manager525as described with reference toFIG.5.

At710, the method may include sending, from the taskchain controller to the node controller via the direct connection, a request to add a node to the first node cluster. The operations of block710may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of710may be performed by a new node manager530as described with reference toFIG.5.

At715, the method may include identifying, based on sending the request, a second network address associated with the first node cluster via which to route one or more data protection tasks from the taskchain controller to the node. The operations of block715may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of715may be performed by a node addressing manager535as described with reference toFIG.5.

FIG.8shows a flowchart illustrating a method800that supports reliable and high-performance connectivity between control-planes and data-planes for a DMS in accordance with aspects of the present disclosure. The operations of the method800may be implemented by a DMS or its components as described herein. For example, the operations of the method800may be performed by a DMS as described with reference toFIGS.1through6. In some examples, a DMS may execute a set of instructions to control the functional elements of the DMS to perform the described functions. Additionally, or alternatively, the DMS may perform aspects of the described functions using special-purpose hardware.

At805, the method may include establishing, at a taskchain controller of a DMS, a direct connection between the taskchain controller and a node controller of a first node cluster of a set of multiple node clusters, where the direct connection is based on a first network address of the node controller, where the set of multiple node clusters are associated with a respective set of multiple tenants of the DMS, where the taskchain controller of the DMS is operable to schedule data protection tasks for the set of multiple node clusters. The operations of block805may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of805may be performed by a node controller connection manager525as described with reference toFIG.5.

At810, the method may include sending, from the taskchain controller to the node controller via the direct connection, a request to add a node to the first node cluster. The operations of block810may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of810may be performed by a new node manager530as described with reference toFIG.5.

At815, the method may include identifying, based on sending the request, a second network address associated with the first node cluster via which to route one or more data protection tasks from the taskchain controller to the node. The operations of block815may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of815may be performed by a node addressing manager535as described with reference toFIG.5.

At820, the method may include receiving, at the taskchain controller from the node controller and in response to the request, an indication of an identifier for the node. The operations of block820may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of820may be performed by a node identifier manager540as described with reference toFIG.5.

At825, the method may include sending, from the taskchain controller directly to the second network address, a control message that indicates to perform a data protection task at the node, where the control message indicates the identifier for the node. The operations of block825may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of825may be performed by a data protection task manager545as described with reference toFIG.5.

FIG.9shows a flowchart illustrating a method900that supports reliable and high-performance connectivity between control-planes and data-planes for a DMS in accordance with aspects of the present disclosure. The operations of the method900may be implemented by a DMS or its components as described herein. For example, the operations of the method900may be performed by a DMS as described with reference toFIGS.1through6. In some examples, a DMS may execute a set of instructions to control the functional elements of the DMS to perform the described functions. Additionally, or alternatively, the DMS may perform aspects of the described functions using special-purpose hardware.

At905, the method may include establishing, at a taskchain controller of a DMS, a direct connection between the taskchain controller and a node controller of a first node cluster of a set of multiple node clusters, where the direct connection is based on a first network address of the node controller, where the set of multiple node clusters are associated with a respective set of multiple tenants of the DMS, where the taskchain controller of the DMS is operable to schedule data protection tasks for the set of multiple node clusters. The operations of block905may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of905may be performed by a node controller connection manager525as described with reference toFIG.5.

At910, the method may include sending, from the taskchain controller to the node controller via the direct connection, a request to add a node to the first node cluster. The operations of block910may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of910may be performed by a new node manager530as described with reference toFIG.5.

At915, the method may include identifying, based on sending the request, a second network address associated with the first node cluster via which to route one or more data protection tasks from the taskchain controller to the node. The operations of block915may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of915may be performed by a node addressing manager535as described with reference toFIG.5.

At920, the method may include receiving, at the taskchain controller from the node controller and in response to the request, an indication of an identifier for the node. The operations of block920may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of920may be performed by a node identifier manager540as described with reference toFIG.5.

At925, the method may include sending, from the taskchain controller directly to the second network address, a control message that indicates to perform a data protection task at the node, where the control message indicates the identifier for the node. The operations of block925may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of925may be performed by a data protection task manager545as described with reference toFIG.5.

At930, the method may include sending the control message via the direct connection to a proxy service at the node controller for routing to the node based on the identifier, where the second network address is a same network address as the first network address. The operations of block930may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of930may be performed by a data protection task manager545as described with reference toFIG.5.

FIG.10shows a flowchart illustrating a method1000that supports reliable and high-performance connectivity between control-planes and data-planes for a DMS in accordance with aspects of the present disclosure. The operations of the method1000may be implemented by a DMS or its components as described herein. For example, the operations of the method1000may be performed by a DMS as described with reference toFIGS.1through6. In some examples, a DMS may execute a set of instructions to control the functional elements of the DMS to perform the described functions. Additionally, or alternatively, the DMS may perform aspects of the described functions using special-purpose hardware.

At1005, the method may include establishing, at a taskchain controller of a DMS, a direct connection between the taskchain controller and a node controller of a first node cluster of a set of multiple node clusters, where the direct connection is based on a first network address of the node controller, where the set of multiple node clusters are associated with a respective set of multiple tenants of the DMS, where the taskchain controller of the DMS is operable to schedule data protection tasks for the set of multiple node clusters. The operations of block1005may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1005may be performed by a node controller connection manager525as described with reference toFIG.5.

At1010, the method may include sending, from the taskchain controller to the node controller via the direct connection, a request to add a node to the first node cluster. The operations of block1010may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1010may be performed by a new node manager530as described with reference toFIG.5.

At1015, the method may include identifying, based on sending the request, a second network address associated with the first node cluster via which to route one or more data protection tasks from the taskchain controller to the node. The operations of block1015may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1015may be performed by a node addressing manager535as described with reference toFIG.5.

At1020, the method may include receiving an indication of the second network address for a second node of the first node cluster. The operations of block1020may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1020may be performed by a service bus identifier manager550as described with reference toFIG.5.

At1025, the method may include establishing a second direct connection between the taskchain controller and the second node based on the second network address. The operations of block1025may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1025may be performed by a service bus connection manager555as described with reference toFIG.5.

At1030, the method may include receiving, at the taskchain controller from the node controller and in response to the request, an indication of an identifier for the node. The operations of block1030may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1030may be performed by a node identifier manager540as described with reference toFIG.5.

At1035, the method may include sending, from the taskchain controller directly to the second network address, a control message that indicates to perform a data protection task at the node, where the control message indicates the identifier for the node, where the control message is sent via the second direct connection. The operations of block1035may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1035may be performed by a data protection task manager545as described with reference toFIG.5.

A method is described. The method may include establishing, at a taskchain controller of a DMS, a direct connection between the taskchain controller and a node controller of a first node cluster of a set of multiple node clusters, where the direct connection is based on a first network address of the node controller, where the set of multiple node clusters are associated with a respective set of multiple tenants of the DMS, where the taskchain controller of the DMS is operable to schedule data protection tasks for the set of multiple node clusters, sending, from the taskchain controller to the node controller via the direct connection, a request to add a node to the first node cluster, and identifying, based on sending the request, a second network address associated with the first node cluster via which to route one or more data protection tasks from the taskchain controller to the node.

An apparatus is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to establish, at a taskchain controller of a DMS, a direct connection between the taskchain controller and a node controller of a first node cluster of a set of multiple node clusters, where the direct connection is based on a first network address of the node controller, where the set of multiple node clusters are associated with a respective set of multiple tenants of the DMS, where the taskchain controller of the DMS is operable to schedule data protection tasks for the set of multiple node clusters, send, from the taskchain controller to the node controller via the direct connection, a request to add a node to the first node cluster, and identifying, based on sending the request, a second network address associated with the first node cluster via which to route one or more data protection tasks from the taskchain controller to the node.

Another apparatus is described. The apparatus may include means for establishing, at a taskchain controller of a DMS, a direct connection between the taskchain controller and a node controller of a first node cluster of a set of multiple node clusters, where the direct connection is based on a first network address of the node controller, where the set of multiple node clusters are associated with a respective set of multiple tenants of the DMS, where the taskchain controller of the DMS is operable to schedule data protection tasks for the set of multiple node clusters, means for sending, from the taskchain controller to the node controller via the direct connection, a request to add a node to the first node cluster, and means for identifying, based on sending the request, a second network address associated with the first node cluster via which to route one or more data protection tasks from the taskchain controller to the node.

A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to establish, at a taskchain controller of a DMS, a direct connection between the taskchain controller and a node controller of a first node cluster of a set of multiple node clusters, where the direct connection is based on a first network address of the node controller, where the set of multiple node clusters are associated with a respective set of multiple tenants of the DMS, where the taskchain controller of the DMS is operable to schedule data protection tasks for the set of multiple node clusters, send, from the taskchain controller to the node controller via the direct connection, a request to add a node to the first node cluster, and identifying, based on sending the request, a second network address associated with the first node cluster via which to route one or more data protection tasks from the taskchain controller to the node.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, at the taskchain controller from the node controller and in response to the request, an indication of an identifier for the node and sending, from the taskchain controller directly to the second network address, a control message that indicates to perform a data protection task at the node, where the control message indicates the identifier for the node.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, sending the control message may include operations, features, means, or instructions for sending the control message via the direct connection to a proxy service at the node controller for routing to the node based on the identifier, where the second network address may be a same network address as the first network address.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, receiving the indication of the second network address may include operations, features, means, or instructions for receiving an indication of the second network address for a second node of the first node cluster and establishing a second direct connection between the taskchain controller and the second node based on the second network address, where the control message may be sent via the second direct connection.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for sending, from the taskchain controller to the node controller via the direct connection, a second request to add a service bus for the first node cluster, where reception of the indication of the second network address may be responsive to the second request, and where the second node may be the service bus.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying a traffic load at the node controller exceeds a threshold, where sending the second request may be based on identifying the traffic load at the node controller exceeds the threshold.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying a traffic load at the node controller may be below a threshold, sending, to the node controller via the direct connection, a third request to remove the service bus based on identifying the traffic load at the node controller may be below the threshold, and terminating the second direct connection based on identifying the traffic load at the node controller may be below the threshold.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, at the taskchain controller from the node controller, an indication of a proxy service at the node controller via which to route the one or more data protection tasks from the taskchain controller to the node and sending, from the taskchain controller to the proxy service via the direct connection, a second control message that indicates to perform a second data protection task at the node, where the second control message indicates the identifier for the node.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying a traffic load at the node controller exceeds a threshold and sending, from the taskchain controller to the second node via the second direct connection, a third control message that indicates to perform a third data protection task at the node, where the third control message indicates the identifier for the node.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for sending, from the taskchain controller to the node controller via the direct connection, a second request to add a second node to the first node cluster, receiving, at the taskchain controller from the node controller and in response to the request, an indication of a second identifier for the second node, and sending, from the taskchain controller directly to the second network address, a second control message that indicates to perform a second data protection task at the second node, where the second control message indicates the identifier for the second node.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the control message includes a transmission control protocol packet.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the data protection task includes at least one of a write operation or a read operation.

It should be noted that the methods described above describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more of the methods may be combined.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “exemplary” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Further, a system as used herein may be a collection of devices, a single device, or aspects within a single device.

Also, as used herein, including in the claims, “or” as used in a list of items (for example, a list of items prefaced by a phrase such as “at least one of” or “one or more of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an exemplary step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can comprise RAM, ROM, EEPROM) compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

The description herein is provided to enable a person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.