Abstract: Examples of systems described herein may allow users to change from an application level disaster recovery system (e.g., an application level replication policy) to a share level disaster recovery system (e.g., a share level replication policy). The change may be made such that a base snapshot need not again be taken when beginning operation under the share level replication policy—rather, the base snapshot previously taken during application level replication may be used in some examples. That base snapshot may be leveraged, an initial set of common share snapshots established, and protection maintained going forward on a share level basis.

Abstract: A replication policy management and scheduling technique of a Files service is configured for deployment in multi-site data replication environments. The technique involves policy management for data distribution and/or data consolidation (concentration) where multiple sources, e.g., file system (FS) clusters or sites, replicate the data to a central target FS site, e.g., in a spoke and hub arrangement typical of remote office/branch office environments. The technique also involves creation and configuration of a main replication policy by a customer at a central resource manager configured to interact and manage the FS sites, each of which includes one or more file server virtual machines.

Abstract: An apparatus may include one or more processors and a non-transitory, computer-readable medium including instructions which, when executed by the one or more processors, cause the one or more processors to display a user interface including an indication of a snapshot group comprising two or more snapshots and an amount of exclusive storage space used by the snapshot group, receive, via the user interface, a user selection of the snapshot group, and delete the selected snapshot group to reclaim the amount of exclusive storage space used by the snapshot group.

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: In various embodiments, one or more non-transitory computer-readable media storing program instructions that, when executed by one or more processors of an application programming interface (API) server, cause the one or more processors to perform a method comprising receiving, from a client device, a request to access a service; transmitting, to a validation server, an authorization request including an API authorization identifier; receiving, from the validation server, a validation response to the authorization request, the validation response including a validation result based on the API authorization identifier and an indicator of a level of resources to be used when performing the request; and performing the service based on the request and the validation response.

Abstract: Examples of systems described herein include a virtualized file servers. Examples of virtualized file servers described herein may support disaster recovery of the virtualized file server. Accordingly, examples of virtualized file servers may support metadata fixing procedures to update metadata in a recovery setting. Examples of virtualized file servers may support hypervisor-agnostic disaster recovery.

Abstract: A system may include a memory having computer-readable instructions stored thereon, and a processor that executes the computer-readable instructions to determine a plurality of scheduled events to be executed in a time period, determine a number of buckets in the time period based on a predetermined permissible interval, generate a plurality of buckets equal to the number of buckets in the time period, wherein each of the plurality of buckets is associated with a time interval, and schedule each of the plurality of scheduled events in one of the plurality of buckets, wherein execution of each of the plurality of scheduled events is delayed or advanced from an original scheduled time based on the predetermined permissible interval.

Abstract: In a system where a plurality of computing clouds host a plurality of tenant partitions, a method proceeds by configuring a first credentialing facility for first authentication and authorization to provide access to a first set of virtualization system entities on a first cloud infrastructure that hosts at least one of the tenant partitions, and configuring a second credentialing facility for second authentication and authorization so as to provide access to monitor and change either one or both of the first virtualization system entities and/or the second set of virtualization system entities even when the second cloud infrastructure is at least in some aspect different from the first cloud infrastructure. At least some aspects of the first set of virtualization system entities are presented in a user interface and at least some aspects of the second set of virtualization system entities are presented in the same user interface.

Abstract: A method may include monitoring, by a monitor on a first cluster, a health of an observer hosted on a second cluster, in response to determining, by the monitor, that the observer is unavailable, determining, by the monitor, whether the observer is unavailable due to a failure of an observer process, a failure of the observer VM, or a failure of the second cluster, and in response to the observer being unavailable due to the failure of the observer VM, spawning, by the monitor, a new observer VM on the second cluster, or in response to the observer being unavailable due to the failure of the second cluster, spawning, by the monitor, the new observer VM on a fourth cluster.

Abstract: Methods, systems and computer program products for hibernating a computing cluster. The present disclosure describes techniques for hibernating and resuming nodes of a computing cluster and entire computing clusters including movement of data and metadata to and from a cloud-tier storage facility (e.g., a cloud disk(s)) in an efficient manner.

Abstract: Techniques using authorization identifiers with code blocks include one or more non-transitory computer-readable media storing program instructions that, when executed by one or more processors of an authorization server, cause the one or more processors to perform a method including receiving, from an application programming interface (API) server, an authorization request, the authorization request including an API authorization identifier; determining whether the API authorization identifier is valid; and in response to determining that the API authorization identifier is valid: executing a code block in the API authorization identifier; adding an output generated by the execution of the code block to a response to the authorization request; and returning the response to the API server.

Abstract: The present disclosure provides approaches for scalable leadership election using a zero-compute witness in a multi-processing computing environment. As provided herein, a zero-compute witness serves to provide for witness functionality without requiring a running witness process at a remote location. In some embodiments, the zero-compute witness is implemented as a data structure stored on cloud storage (e.g., as a cloud storage object) and is writable using conditional write commands such as HTTP conditional writes or compare-and-swap commands (CAS). In some embodiments, the zero-compute witness is initially configured as an empty data structure that is accessible by multiple nodes in the multi-process computing environment.

Abstract: A bypassing technique bypasses an indexing service and provides a bypass data path for transferring/retrieving snapshots from a production cluster to an object store. In an embodiment, the production cluster may determine how extents of the snapshots are packed into objects of the object store and transfers the snapshots directly to the object store over the bypass data path. Once the snapshot transfer is completed, the production cluster provides location metadata as to how the snapshot extents are packed into objects to the indexing service. The indexing service is invoked to create an index of the location metadata and is not involved in the data transfer of the snapshots. In another embodiment, the production cluster identifies a snapshot to restore and queries the indexing service to compute the deltas between the snapshot to be restored and a reference snapshot. The indexing service returns a set of segments that indicates the changed delta regions between the two snapshots.

Abstract: Systems and methods for scalable tracking of objects to be replicated are disclosed. A method may include in a first time period, updating, by one or more processors, a data structure with metadata of a received object to be replicated, wherein the data structure includes a plurality of classifications of objects to be replicated based on when the objects were received, in a second time period, after the first time period, updating, by the one or more processors, the data structure to modify a classification of the object based on the object being received in the first time period, and replicating, by the one or more processors, the object based on the modified classification of the object.

Abstract: Methods, systems, and computer program products for multi-cloud shared data management. A first storage facility on a first cloud is established and a second storage facility on a second cloud established. The first cloud and the second cloud comprise at least respective first deduplication metadata and second deduplication metadata. In response to receipt of a request to store a content object comprising at least one candidate deduplication chunk, an inter-cloud deduplication protocol is initiated. The inter-cloud deduplication protocol determines whether or not a candidate deduplication chunk of a data item is already stored at either the first cloud or the second cloud. In the event that the candidate deduplication chunk of the data item deemed to have been already stored then, rather than storing a further copy of the bit sequence corresponding to the candidate deduplication chunk, instead, merely referring to the location of the already stored candidate deduplication chunk.

Abstract: A system may include a memory having computer-readable instructions stored thereon and a processor that executes the computer-readable instructions to receive, from a user, a first login credential associated with an organization on a database management service. The system may receive, from the user, a selection of the first cloud account, retrieve a second login credential for the first cloud account based on the selection, automatically log in to the first cloud account using the second login credential, receive, from the user, input to perform an operation on data in the first database on the first cloud, and transmit, to the first cloud, using the second login credential for the first cloud account, a signal to perform the operation based on the input.

Abstract: Techniques for authenticating user access to a resource and providing access to the resource include non-transitory computer-readable media storing program instructions that, when executed by one or more processors associated with a first computing device, cause the one or more processors to perform a method including receiving, from a client device, a first request for an authentication token to access a resource and identifying a second computing device through which the resource is accessible. The method further includes transmitting a second request to the second computing device for the authentication token, receiving a signed authentication token from the second computing device, wherein the authentication token is signed by the second computing device and specific to the client device, and providing the signed authentication token to the client device.

Abstract: Techniques for pre-processing metadata for faster background decisions include, in response to a metadata entry associated with storage of data in a cluster being modified, generating a summary entry corresponding to the metadata entry. The summary entry includes a subset of the information from the metadata entry. A data management action is performed based upon a scanning process that reads a plurality of summary entries corresponding to a plurality of metadata entries for data in the cluster.

Abstract: In some embodiments, a method for tuning a disaster recovery preparation system for a storage system includes determining whether the disaster recovery preparation system has not met a recovery point objective; and in response to determining that the recovery point objective is not met: determining a state of the storage system; applying a machine learning model to determine a change to one or more of a plurality of adjustable parameters of the disaster recovery preparation system based on the state of the storage system and the recovery point objective that is not met; adjusting the one or more of the plurality of adjustable parameters based on the determined change to the one or more parameters; after adjusting the one or more parameters, monitoring one or more metrics of the disaster recovery preparation system or the storage system; and updating the machine learning model based on the monitoring.

Abstract: A database management system receives a user request for provisioning a database, autonomously selects a datacenter for provisioning the database based at least on a first pre-defined rule, autonomously selects at least one cluster in the datacenter based at least on a second pre-defined rule, determines a network location of each of the at least one cluster, and provisions the database on each of the at least one cluster using the network location of each of the at least one cluster.