The present technology is directed to providing a backup service utilizing a bi-directional synchronization architecture. In order to support both a backup service and a bi-directional synchronization service, the present technology can utilize a special object called an anchor that only permits unidirectional synchronization. Additionally, the present technology separates the backup service from the bi-directional synchronization service. This separation includes utilizing a separate backup directory and bi-directional synchronization directory on a client device, which in turn benefits from the use of a separate instance of the synchronization service on the client device. Further, at the content management system various steps are taken to separate the backup directory from the bi-directional synchronization directory to ensure no objects from the backup directory appear in a user interface related to bi-directional synchronization, and vice versa.

Managing connectivity to synchronously replicated storage systems, including: identifying a plurality of storage systems across which a dataset is synchronously replicated; identifying a host that can issue I/O operations directed to the dataset; identifying a plurality of data communications paths between the host and the plurality of storage systems across which a dataset is synchronously replicated; identifying, from amongst the plurality of data communications paths between the host and the plurality of storage systems across which a dataset is synchronously replicated, one or more optimal paths; and issuing, to the host, an identification of the one or more optimal paths.

Datasets can be synchronized across cloud-based computer environments using computer systems. A data map can be generated for source datasets for a plurality of computing environments, respectively, and an activation function can be determined based on the data map, for simultaneously activating a new dataset of a source system from one of the plurality of computing environments. A generation ID (identification) can be shared from the source system with one or more computing environments of the plurality of the computing environments, in response to receiving the activation function. The new dataset of the source system can be replicated across the one or more computing environments. A data synchronization trigger can be activated, using a synchronization coordinator module of the computer, and the data synchronization can be completed across the plurality of computing environments.

Techniques are provided for resynchronizing a synchronous replication relationship. Asynchronous incremental transfers are performed to replicate data of a storage object to a replicated storage object. Incoming write requests, targeting the storage object, are logged into a dirty region log during a last asynchronous incremental transfer. Metadata operations, executed on the storage object, are logged into a metadata log during the last asynchronous incremental transfer. Sequence numbers are assigned to the metadata operations based upon an order of execution. The metadata operations are replicated to the replicated storage object for execution according to the sequence numbers, and the dirty regions are replicated to the replicated storage object in response to the metadata operations having been replicated to the replicated storage object. The storage object and replicated storage object are transitioned to a synchronous replication state where incoming operations are synchronously replicated to the replicated storage object.

Systems and methods for concurrent modification of content are provided. In response to a verified request received from a user content is copied to a first storage media as a first version of the content uniquely identified by a first identifier, the verified request being based on verification of the user's credentials. In response to the user editing the first version of the content, the edited copy of the content is stored in the content management system in association with a second identifier uniquely identifying the edited copy of the content as a second version of the content. In response to receiving a notification that a plurality of users no longer request access to the content stored in the content management system, the first version of the content is deleted from the first storage media.

When multiple backup database instances most recently experienced an update is determined. If a most recently updated backup database instance was updated within a defined time period of one or more other backup database instances, a source instance for cloning is selected as the backup database instance that satisfies at least one of a physical or logical proximity criteria relative to a designated database instance. If a difference in update times is greater than the defined time period, e.g., for the two most recent backup database instances, the source instance for cloning is selected to be the most recently updated backup database instance. Cloning to a target instance is performed using the selected backup database instance as a source instance as long as preparatory operations all pass. If not, the source databases are used for the cloning while still being accessible to clients.

Systems and methods are provided for synchronizing messages. The systems and methods include operations for: identifying a difference between a current state of a messaging application and a shared synchronization database, wherein the shared synchronization database is updated via a third-party application in response to the third-party application receiving, from a server, a notification related to the messaging application, the messaging application and the third-party application being implemented on a client device; retrieving information from the shared synchronization database to update the current state of the messaging application based on the identified difference; and transmitting, to the server by the messaging application, a request for content based on the update to the current state of the messaging application.

Provided herein are systems and methods for configuring replication of account object metadata. A system includes at least one hardware processor coupled to a memory and configured to decode a replication request received from a client device of a data provider. The replication request indicates at least a first account object, a source account, and a target account of the data provider. An object dependency of the at least first account object to at least a second account object of the data provider is determined. A replication of the at least first account object and the at least second account object is performed from the source account into the target account of the data provider.

A recording of a call is authenticated using a distributed transaction ledger. A call between two or more participants is recorded to generate a call recording. A record of the call recording is stored within a distributed transaction ledger. At a later time, such as in response to an access request for auditing or an authentication request, the call recording is authenticated based on information associated with the record within the distributed transaction ledger. An indication of the authentication is then output, such as for further processing or display.

Methods, computer program products, and/or systems are provided that perform the following operations: identifying a first workload being processed by a first plurality of sites in a cluster; identifying, from the first plurality of sites: (i) a first site as a primary site for the first workload, and (ii) one or more secondary sites for the first workload; identifying a communication link issue between the first site and at least one of the one or more secondary sites; splitting the cluster into sub-clusters based, at least in part, on the communication link issue, wherein the first site is included in a first sub-cluster of the sub-clusters and the at least one of the one or more secondary sites is included in a sub-cluster of the sub-clusters that is different from the first sub-cluster; and instructing the first sub-cluster to locally process the first workload.