Abstract: A multi-cluster database management system includes a first cluster in a database management system of a virtual computing system, a second cluster in the database management system, a server on the first cluster, a first agent on the first cluster, and a second agent on the second cluster. The server provides a database management service to a first database stored on the first cluster via the first agent and to a second database stored on the second cluster via the second agent.

Abstract: A system and method include receiving request to create a database group, receiving selection of a database server virtual machine on which to create the database group, receiving selection of at least one database from a list of databases that are not part of another database group to add to the database group, receiving selection of a Service Level Agreement (“SLA”) and a protection schedule, and creating the database group on the database server virtual machine, including associating the database group with the SLA and the protection schedule and adding the at least one database to the database group. Each of the at least one database is protected using the same SLA and the protection schedule that is associated with the database group.

Abstract: Computer-implemented techniques for controlling virtual machine (VM) porting activities based on dynamically-calculated virtual machine predicate values. Upon receiving a command to port a subject virtual machine from a source virtualization system environment to a target virtualization system environment (wherein the source virtualization system environment and the target virtualization system environment are different), one or more match expressions that describe time of day and resource predicates conditions, under which porting operations of the subject virtual machine are to be carried out are evaluated. Based on observance of the aforementioned time of day and resource predicates, various virtual machine porting operations are either carried out (e.g., when applicable match expressions and/or predicates evaluate to TRUE), or are temporarily suspended (e.g., when the applicable match expressions and/or predicates evaluate to FALSE).

Abstract: A replication progress tracking technique is configured to present progress tracking state relating to data replicated as a recovery point (RP) from a source site to one or more target and/or remote sites over a network in a multi-site data replication environment. The progress tracking state of the replicated RP, i.e., RP replication progress, is persistently stored as a progress tracking recording at the target site independent of the source site of the replication and presented (i.e., viewed) using a well-defined, published application programming interface that is publicly callable by one or more clients of the environment.

Abstract: A scalable Internet of Things (IoT) system may include multiple instances of an IoT manager, each instance respectively configured to connect to a respective edge system of multiple edge systems. The IoT system may further include a containerized system configured to allow any instance of the IoT manager to deploy data pipelines to any edge system of the multiple edge systems in delta communications. Any instance of the IoT manager may send a change message to any edge system via a publish/subscribe notification method. In some examples, a centralized IoT manager may form a secure communication with an edge system, synchronize an object model with an edge object model for the edge system, and maintain the edge system using delta change communications. The IoT system may facilitate any instance of the IoT manager to subscribe a communication channel with an associated edge system for receiving update notification.

Abstract: Systems for high-performance computing. A storage control architecture is implemented by a plurality of nodes, where a node comprises combinations of executable containers that execute in cooperation with virtual machines running above a hypervisor. The containers run in a virtual machine above a hypervisor, and/or can be integrated directly into the operating system of a host node. Sensitive information such as credit card information may be isolated from the containers in a separate virtual machine that is configured to be threat resistant, and which can be accessed through a threat resistant interface module. One of the virtual machines of the node may be a node-specific control virtual machine that is configured to operate as a dedicated storage controller for a node. One of the virtual machines of the node may be a node-specific container service machine that is configured to provide storage-related and other support to a hosted executable container.

Abstract: In one embodiment, a system for managing communication connections in a virtualization environment includes a plurality of host machines implementing a virtualization environment, wherein each of the host machines includes a hypervisor, at least one user virtual machine (user VM), and a distributed file server that includes file server virtual machines (FSVMs) and associated local storage devices. Each FSVM and associated local storage device are local to a corresponding one of the host machines, and the FSVMs conduct I/O transactions with their associated local storage devices based on I/O requests received from the user VMs. Each of the user VMs on each host machine sends each of its representative I/O requests to an FSVM that is selected by one or more of the FSVMs for each I/O request based on a lookup table that maps a storage item referenced by the I/O request to the selected one of the FSVMs.

Abstract: A system and method includes a plurality of nodes distributed between a first cluster and a second cluster, each of the plurality of nodes storing a copy of a source database and a processor executing computer-readable instructions stored on a memory to designate a first node of the plurality of nodes as a primary node, designate remaining ones of the plurality of nodes as secondary nodes to take over from the primary node upon failure of the primary node, designate a second node of the plurality of nodes as an initial active node, backup the source database from the initial active node, automatically designate, based on a switch over policy, a third node of the plurality of nodes as a next active node upon the initial active node becoming unavailable, and continue backups of the source database from the next active node upon the initial active node becoming unavailable.

Abstract: Methods, systems, and computer program products for computer networking. Legacy policy-based routing is advanced by adding fallback-aware policy actions that are enabled within a policy-based routing regime. Upon determining that a destination specified in a subject policy is compromised, or down, or unreachable then, a fallback-aware policy action is invoked. Destinations specified in policies may refer to inserted services, wherein an inserted service can be any one of, a service process, a service virtual machine, a hardware network component, or a virtual network interface. Such inserted services might implement a logging service, or a firewall service, or other services that can process a network packet. Fallback-aware policy actions include, a PASSTHROUGH fallback action, an ALLOW fallback action, a FORWARD fallback action, and a DROP fallback action. Various techniques serve to determine whether or not a particular destination of a subject policy is deemed to be compromised, or down or unreachable.

Abstract: In one embodiment, a system for managing a virtualization environment includes a set of host machines, each of which includes a hypervisor, virtual machines, and a virtual machine controller, and a first virtualized file server configured to receive a request to access a storage item located at a second virtualized file server, determine that the storage item is designated as being accessible by other virtualized file servers, identify an FSVM of the second virtualized file server at which the storage item is located, and forward the request to the FSVM of the second virtualized file server. The storage item may be designated as being accessible by other virtualized file servers when the storage item is associated with a predetermined tag value indicating that the storage item is shared among virtualized file servers. The predetermined tag value may be stored in a sharding map in association with the storage item.

Abstract: A centralized Internet of Things (IoT) manager of an IoT system is configured generate and deploy a data pipeline application to an edge system. The centralized IoT manager is configured to receive a request for a data category and identification of a data transformation function, identify a data source of the IoT system belonging to the data category, and identify an edge system of the IoT system associated with the data source. The centralized IoT manager is further configured to generate a containerized data pipeline application based on a configuration of the edge system that is configured apply the data transformation function to input data to provide transformed data, and provide the containerized data pipeline application to the edge system.

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

Abstract: Methods, systems, and computer program products for high-performance cluster computing. Multiple components are operatively interconnected to carry out operations for high-performance RDMA I/O transfers over an RDMA NIC. A virtual machine of a virtualization environment initiates a first I/O call to an HCI storage pool controller using RDMA. Responsive to the first I/O call, a second I/O call is initiated from the HCI storage pool controller to a storage device of an HCI storage pool. The first I/O call to the HCI storage pool controller is implemented through a first virtual function of an RDMA NIC that is exposed in the user space of the virtualization environment. Prior to the first RDMA I/O call, a contiguous unit of memory to use in an RDMA I/O transfer is registered with the RDMA NIC. The contiguous unit of memory comprises memory that is registered using non-RDMA paths such as TCP or iSCSI.

Abstract: Examples of a virtualized file server that persistently stores file system event data records are described. The virtualized file server may include an audit framework with a connector publisher that is configured to publish the event data records and other information for consumption by other services using a message system. The event data records may include data related to various operations on the file system executed by the VFS. The VFS may persistently store event data records according to a data retention policy and/or until an event data record is consumed by one or more particular services.

Abstract: A technique enables recovery of failover data used to generate one or more High Frequency Snapshots (HFSs) at a source and replicated to a target for storage and recovery. The target is illustratively an intermediary repository embodied as a long-term storage service (LTSS) configured to organize and store the HFSs as recovery points (RPs) in an object store. The LTSS stores a HFS identifier (ID), a logical offset in an object of the object store storing data of the HFS, and a logical timestamp associated with each replicated HFS as a key of a segment descriptor in a key-value database configured to store metadata describing the failover data of the HFS stored as one or more objects in the object store. Upon recovery of the failover data, the technique enables identification of the HFS stored in the object store and creation of a HFS index metadata structure (B+ tree) to extract the identified HFS as a RP.

Abstract: A technique creates a compact state of snapshot metadata and associated selected snapshots that are frequently used and maintained in memory of a node of a cluster to facilitate processing of workflow operations associated with a logical entity in a disaster recovery (DR) environment. The compact state represents a minimal subset of snapshot metadata that is frequently used to perform operations in accordance with the DR workflow operations. In addition, metadata associated with the progress of the DR workflow operations processed by the node is periodically consolidated within the compact state. Illustratively, the selected frequently used snapshots of the logical entity include (i) a recently created snapshot; (ii) one or more reference snapshots; (iii) a snapshot scheduled for replication; and (iv) any snapshot that is queued for a current or future-scheduled operation.

Abstract: Examples of systems described herein provide for share-level disaster recovery on, for example, virtualized file servers by enabling additional snapshots, including self-service recovery (SSR) snapshot migration in addition to replication snapshot migration to a disaster recovery location. In examples, a disaster recovery location may receive a replication of a share of a file system, the snapshot configured for recovery of the share at the disaster recovery location. The replication snapshot may include one or more additional snapshots, each taken since a time of a previous replication snapshot. At least one of the one or more additional snapshots may include an SSR snapshot, identifiable based at least on a tag associated with a process used to create the SSR snapshot at a primary location. The at least one additional snapshot may be extracted for use by another instance of the process at the disaster recovery location.

Abstract: Methods, systems, and computer program products for expandible/contractible computing. A configurator establishes a computing environment having a storage pool formed using a common address space across storage located on multiple computing nodes. One or more instances of a first type of computing node having both a virtualization storage controller and any number of user virtual machines is situated in the computing environment. Instances of the first type of computing node are highly performant so as to handle arbitrarily large workloads. A second type of computing node having lightweight characteristics is instanced into the computing environment and interconnected to the one or more instances of the first type of computing node. The second type of computing node runs a virtualization storage controller but does not run any user virtual machines.

Abstract: Methods, systems, and computer program products for high-availability virtualized computing clusters. Components are operatively interconnected to carry out operations for maintaining high-availability configurations of such virtualized computing clusters. A virtual machine in a source computing node of a virtualized high-availability multi-node computing cluster is considered for migration in a manner that observes high-availability rules. A scheduler and/or a placement engine is configured to identify one or more feasible HA-compliant virtual machine placements. The scheduler and/or a placement engine and/or their agents are configured to respond to a virtual machine migration request by establishing a placeholder at a target computing node so as to reserve resources of the target computing node. The virtual machine is migrated from the source computing node to the target computing node using the reserved resources.

Abstract: Placement scenario optimization mechanisms for automatic placement of computing entities onto nodes of a running multi-node computing cluster. A set of failure mode parameters define a high-availability requirement of the multi-node computing cluster. In advance of a failure event, and responsive to a determination that a then-current computing entity placement does not satisfy the high-availability requirement, the cluster is analyzed and a plurality of feasible placement scenarios are generated. Optimization criteria are applied to the feasible placement scenarios such that a best choice from among the feasible placement scenarios is identified and applied to the virtual machine placements over the cluster. A change monitoring and detection facility continually observes the multi-node computing cluster to detect a change of a failure mode parameter or to detect a change to the configuration of the virtual machines.