Techniques for generating a crash-consistent clone of file(s) stored by a distributed file system are described herein. To generate the crash-consistent clone, a coordinator node may identify multiple nodes (e.g., at least a first node and a second node) of the distributed file system that are storing different portions of data of the file. The coordinator node may then send a first command to the multiple nodes to cause each of the multiple nodes to quiesce the file and clone the different portions of the data to generate the crash-consistent clone of the file. The coordinator node may then receive, from the multiple nodes, a status associated with generating the crash-consistent clone of the file. Based at least in part on the status, the coordinator node may send a second command to the multiple nodes to cause each of the multiple nodes to unquiesce the file.

Modifying a clone image of a dataset, including: generating, based on metadata describing one or more updates to a dataset, a tracking copy of replica data on a target data repository; generating, after receiving an indication to begin accepting modifications to the tracking copy of the replica data, a cloned image of the dataset that is modifiable without modifying the tracking copy of the replica data; and responsive to a storage operation directed to the target data repository, modifying the cloned image of the dataset without modifying the tracking copy of the replica data.

Provided are techniques for role reversal of primary and secondary sites with minimal replication delay. During a backup phase, an Input/Output (I/O) operation selected from a group comprising a create operation and a rename operation is received with one or more local attributes of a local file. The I/O operation is processed to generate one or more remote attributes. The one or more local attributes are stored with the one or more remote attributes. During a reversed phase, a write operation for the remote file is processed, and, the write operation is sent to the primary replication system with the one or more local attributes, where the primary replication system uses a local file handle in the one or more local attributes to access the local file for processing the write operation to sync the local file with the remote file.

Provided are techniques for role reversal of primary and secondary sites with minimal replication delay. During a backup phase, an Input/Output (I/O) operation selected from a group comprising a create operation and a rename operation is received with one or more local attributes of a local file. The I/O operation is processed to generate one or more remote attributes. The one or more local attributes are stored with the one or more remote attributes. During a reversed phase, a write operation for the remote file is processed, and, the write operation is sent to the primary replication system with the one or more local attributes, where the primary replication system uses a local file handle in the one or more local attributes to access the local file for processing the write operation to sync the local file with the remote file.

The present disclosure describes systems and methods for aggregation and management of cloud storage among a plurality of providers. In a first aspect, the invention is directed to file distribution and management across multiple cloud services via a storage manager. The storage manager may aggregate third-party cloud storage provider accounts into a single cloud storage space and load balance files among the third party-accounts as necessary. In one implementation, the storage manager may act as an intermediary, and files may be transferred by the client to the storage manager, which may select and forward the files to a third-party storage provider. File retrieval may be performed similarly, with the client requesting a file from the intermediary storage manager, which may retrieve the file from the corresponding third-party storage provider and forward the file to the client device.

The present disclosure describes systems and methods for aggregation and management of cloud storage among a plurality of providers. In a first aspect, the invention is directed to file distribution and management across multiple cloud services via a storage manager. The storage manager may aggregate third-party cloud storage provider accounts into a single cloud storage space and load balance files among the third party-accounts as necessary. In one implementation, the storage manager may act as an intermediary, and files may be transferred by the client to the storage manager, which may select and forward the files to a third-party storage provider. File retrieval may be performed similarly, with the client requesting a file from the intermediary storage manager, which may retrieve the file from the corresponding third-party storage provider and forward the file to the client device.

The present disclosure relates to processing operations configured for intelligent management of a synchronization interval usable to synchronize data for an application/service between local data storage and distributed data storage. A classification prediction for a synchronization interval may be generated that is used as prediction for modifying the synchronization interval when a plurality of computing devices, linked to one or more user accounts, are used to access content. For instance, a suggestion is made as to whether a synchronization interval should be made faster, slower or even remain unchanged when a user account is accessing content. This may occur based on analysis of contextual factors described herein, thereby enabling a synchronization prediction component to make a best possible prediction for setting a synchronization interval. Artificial intelligence processing may be trained to generate the classification prediction for a synchronization interval. The classification prediction is utilized to manage modification of synchronization interval.

Embodiments are directed to synchronizing files between client devices utilizing different file systems with different filename restrictions. Generally speaking, a server of a cloud-based storage environment can, upon generation of a file or receiving a file from a first client device, detect any “illegal” characters therein, i.e., characters that are predefined by a file system of a second client device of the environment as being impermissible for use in a filename, and substitute a replacement character for those illegal characters. This replacement character can comprise a character that is permissible by the file system of both the first and second client devices, thereby allowing synchronization and access. Additionally, the server(s) can identify the original filename from the first client device and substitute the replacement characters back to the original filename when the file is being accessed by or synchronized with the first client device.

Embodiments are directed to synchronizing files between client devices utilizing different file systems with different filename restrictions. Generally speaking, a server of a cloud-based storage environment can, upon generation of a file or receiving a file from a first client device, detect any “illegal” characters therein, i.e., characters that are predefined by a file system of a second client device of the environment as being impermissible for use in a filename, and substitute a replacement character for those illegal characters. This replacement character can comprise a character that is permissible by the file system of both the first and second client devices, thereby allowing synchronization and access. Additionally, the server(s) can identify the original filename from the first client device and substitute the replacement characters back to the original filename when the file is being accessed by or synchronized with the first client device.

One embodiment of a system comprises a client device and a remote content management system. The client device comprises a synchronization manager that maintains a remote virtual model that models a synchronization state of a remote peer resource at the content management system and a local virtual model that models a synchronization state of a local peer resource in the local file system. The synchronization manager determines that the remote peer resource and local peer resource are out of sync based on a comparison of the remote virtual model and the local virtual model and synchronizes changes from the local cache to the content management system to update the remote peer resource or synchronizes changes from the content management system to update the local peer resource.