A system for facilitating upload file optimization via transaction transformation. A request is received for an operation to upload a file to the cloud. The system bypasses a transaction processing (sub)system and attempts to upload the file to a staging area of the cloud. When the upload transaction is ready to be executed, the system determines an upload status of the file. The system transfers the file from the staging area to an intended destination if the file has been uploaded to the staging area. If the file is not yet uploaded to the staging area, the system determines if an upload operation failed. If an upload operation did not fail, the system waits for the upload to finish prior to transferring the file to the intended destination. If the upload operation did fail, the system uploads the file to the intended destination. Once the file is transferred to the intended destination, the transaction may be marked as complete in the journal.
A method of managing file permissions in a remote file storage system includes defining permissions for the remote file storage system and controlling access to objects on the remote file storage system according to the permissions of the remote file storage system. The permissions are transferred to a client file storage system remote from the remote file storage system, and access to objects on the client file storage system is controlled according to the permissions of the remote file storage system. A remote file storage system includes a permissions file generator operative to generate a permissions file, which is transmitted to a client file storage system for enforcement at the client file storage system.
A novel system for performing valuations of file system objects include a processor configured to execute code and memory configured to store data and the code. The code includes an accumulator configured to accumulate secondary data associated with said file system objects, a data aggregator configured to arrange the secondary data in the memory, and a value generator configured to generate an object value indicative of the value of at least one of the file system objects to a particular entity. In a particular embodiment, the value generator creates a record in a valuation database to associate the object value with the at least one of the file system objects.
A system and methods for enhancing content collaboration by conflict detection and resolution. A hybrid cloud cache receives a request from a client to upload an object to the cloud. The hybrid cloud cache may perform an internal lookup to find the latest version of the object known to it. This lookup may return a local identifier or a cloud identifier. The cache may compare a client-provided identifier to the local identifier or to the cloud identifier that is mapped to the local identifier to determine if the client-provided identifier refers to the latest uploaded version of the object. The system may determine that a conflict exists if the client-provided identifier does not match either identifier. The system may generate an alternate name for the object and upload the renamed object to the cloud from the hybrid cloud cache.
A system and methods for presenting a hybrid cloud cache as a file system. The system implements a set of standard file system command line interfaces that present the objects stored by the hybrid cloud cache to users of the system as if the users were viewing and interacting with a traditional file system. The system provides an interactive shell to the users to view the contents of the hybrid cloud cache. The system may be configured to operate on a live instance as well as on an on-disk structure of the hybrid cloud cache. The system may provide the ability to present partially cached cloud data as a file system via the interactive shell for the purposes of development, support, and troubleshooting.
A system for handling Implicit transactions in a hybrid cloud cache. The hybrid cloud cache maintains folders in a metadata file system that includes a hierarchy of cached folders, and maintains a meta-file containing metadata of files and folders. The system obtains a meta-file from a cloud platform and compares that to a meta-file obtained from the hybrid cloud cache. An object associated with an Implicit metadata transaction is transferred to an internal namespace of the hybrid cloud cache if the comparison indicates that certain conditions are met. The system may perform a bottom-up traversal of the namespace and may abort the traversal if an outstanding explicit transaction for the object is present or the object exists in the cloud platform. An object may be moved to a temporary storage location if there is no explicit transaction on it and the object does not exist in the cloud platform.
H04L 67/1097 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau pour le stockage distribué de données dans des réseaux, p.ex. dispositions de transport pour le système de fichiers réseau [NFS], réseaux de stockage [SAN] ou stockage en réseau [NAS]
G06F 16/22 - Indexation; Structures de données à cet effet; Structures de stockage
H04L 67/568 - Stockage temporaire des données à un stade intermédiaire, p.ex. par mise en antémémoire
7.
SYSTEM AND METHODS FOR EFFECTIVELY ADDRESSING FAST-PRODUCER AND SLOW-CONSUMER PROBLEM FOR PERSISTENT HYBRID CLOUD CACHES
A system for effectively addressing the fast-producer and slow-consumer problem for persistent hybrid cloud caches. In particular, the system and associated methods ensure the integrity of data stored by persistent caches by utilizing a plurality of journals, including a user journal and a cloud journal. The user journal records operations conducted by users of the system in records. Before the records are transferred to a cloud storage system, the records are transferred to the cloud journal, which may be configured to be larger than the user journal. Once a record is transferred from the user journal to the cloud journal, the record may be released from the user journal, thereby increasing capacity of the user journal for subsequent operations to be recorded. Each record may then be transferred to the cloud storage system from the cloud journal, which may then cause each record to be released from the cloud journal.
G06F 16/17 - Systèmes de fichiers; Serveurs de fichiers - Détails d’autres fonctions de systèmes de fichiers
H04L 67/1097 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau pour le stockage distribué de données dans des réseaux, p.ex. dispositions de transport pour le système de fichiers réseau [NFS], réseaux de stockage [SAN] ou stockage en réseau [NAS]
H04L 67/06 - Protocoles spécialement adaptés au transfert de fichiers, p.ex. protocole de transfert de fichier [FTP]
8.
System and Method for Sensitive Content Analysis Prioritization Based on File Metadata
Example systems and methods for efficient data governance are disclosed. Metadata associated with file objects is analyzed to estimate, for each file object, the likelihood that the file object includes sensitive data. The estimates are used to prioritize the file objects for analysis of the file objects' content to determine the whether the file objects include data deemed to be of a sensitive nature. In cloud-based systems/methods the estimates are also used to prioritize the file objects for transfer from a remote file storage system to the cloud-based system for analysis of content. The disclosed systems and methods significantly reduce the time required to identify sensitive file content in a large number of file objects.
A system for facilitating upload file optimization via transaction transformation. A request is received for an operation to upload a file to the cloud. The system bypasses a transaction processing (sub)system and attempts to upload the file to a staging area of the cloud. When the upload transaction is ready to be executed, the system determines an upload status of the file. The system transfers the file from the staging area to an intended destination if the file has been uploaded to the staging area. If the file is not yet uploaded to the staging area, the system determines if an upload operation failed. If an upload operation did not fail, the system waits for the upload to finish prior to transferring the file to the intended destination. If the upload operation did fail, the system uploads the file to the intended destination.
A method for providing access to objects associated with a particular client in a cloud storage system is disclosed. The method includes the steps of establishing a connection with a user, providing a client namespace associated with the client to the user, where the client namespace represents objects stored on the cloud storage system and objects stored on a private storage system apart from the cloud storage system, receiving a request from the user to access an object stored on the private storage system, and providing information to the user to facilitate access to the object stored on the private storage system by said user. Other systems and methods are also disclosed. Important advantages of the present invention are facilitated by separating the logic for user access (control plane) from the actual storage (Storage plane). Private file system access can still be managed from the cloud, while keeping the client data private.
G06F 16/27 - Réplication, distribution ou synchronisation de données entre bases de données ou dans un système de bases de données distribuées; Architectures de systèmes de bases de données distribuées à cet effet
G06F 15/173 - Communication entre processeurs utilisant un réseau d'interconnexion, p.ex. matriciel, de réarrangement, pyramidal, en étoile ou ramifié
11.
Systems and Methods for Uploading Streamed Objects to a Cloud Storage System
Methods in a cloud object store facilitate strong data encryption, customer-management of object (encryption) keys, reductions in latency, globally-distributed object storage, and handling of streamed uploads. A method for encrypting objects stored in a cloud includes encrypting each object with a unique encryption (object) key. The plaintext object keys are generated in advance of uploads. The plaintext object keys can be stored in an object database in the cloud. Alternatively, the plaintext object keys can be provided to a customer's HSM, encrypted, and returned to the cloud, such that encrypted object keys, encrypted by the customer, are stored in the cloud. The cloud can alternatively encrypt the customer's object keys with a master key for the customer, which is then encrypted by the customer's HSM before being stored in the cloud. Proxies are also deployed for efficiently communicating with customer security modules.
G06F 21/62 - Protection de l’accès à des données via une plate-forme, p.ex. par clés ou règles de contrôle de l’accès
H04L 9/32 - Dispositions pour les communications secrètes ou protégées; Protocoles réseaux de sécurité comprenant des moyens pour vérifier l'identité ou l'autorisation d'un utilisateur du système
H04L 67/10 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau
G06F 16/174 - Systèmes de fichiers; Serveurs de fichiers - Détails d’autres fonctions de systèmes de fichiers Élimination de redondances par le système de fichiers
H04L 67/1097 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau pour le stockage distribué de données dans des réseaux, p.ex. dispositions de transport pour le système de fichiers réseau [NFS], réseaux de stockage [SAN] ou stockage en réseau [NAS]
A system for resolving transient and localized errors in a hybrid cloud cache. The system may include a subsystem within a hybrid cloud cache that provides a way to handle errors associated with uploading files or folders to a cloud. The subsystem may be used to recover files and folders created by a user that could not be pushed to the cloud, while also ensuring that metadata and data are not lost. The subsystem may work with the transaction processing subsystem of the hybrid cloud cache to facilitate the release of transactions associated with the files and folders that could not be pushed to the cloud. By doing so, the subsystem assists in unblocking subsequent transactions or user operations and allows the hybrid cloud cache to upload files and folders to the cloud without interruption.
G06F 11/14 - Détection ou correction d'erreur dans les données par redondance dans les opérations, p.ex. en utilisant différentes séquences d'opérations aboutissant au même résultat
G06F 16/16 - Opérations sur les fichiers ou les dossiers, p.ex. détails des interfaces utilisateur spécialement adaptées aux systèmes de fichiers
A method for synchronizing a local file system (LFS) and a remote (cloud) file system (RFS) includes the step of storing events indicative of differences between the LFS and the RFS, where the events are associated with file system objects of the LFS and RFS. The method further includes the steps of prioritizing the events, generating file system operations for the events based at least in part on the prioritization of the events, and performing at least some of the file system operations to synchronize the LFS and RFS. Prioritizing the events includes defining a plurality of service classes (e.g., based on type of event, event attribute, etc.), assigning a priority to each of the service classes, and assigning each event to one of said service classes. Systems are also described. The invention allocates limited synchronization resources based on a predefined policy to synchronize important file system objects sooner.
G06F 16/178 - Techniques de synchronisation des fichiers dans les systèmes de fichiers
H04L 67/1095 - Réplication ou mise en miroir des données, p.ex. l’ordonnancement ou le transport pour la synchronisation des données entre les nœuds du réseau
G06F 16/16 - Opérations sur les fichiers ou les dossiers, p.ex. détails des interfaces utilisateur spécialement adaptées aux systèmes de fichiers
G06F 16/176 - Support d’accès partagé aux fichiers; Support de partage de fichiers
14.
System and Method for Event-Based Synchronization of Remote and Local File Systems
A method for synchronizing a file system (FS) and a remote file system (RFS) includes monitoring the FS for FS events, generating FS event records, receiving RFS event records of RFS events, generating file system operations (FSOs) based on the FS and RFS event records, and communicating the FSOs to the FS and RFS to synchronize them. A method for generating the FSOs includes accessing a plurality of FS and/or RFS event records, processing the accessed records to generate processed event records, generating the FSOs based on the processed event records, and outputting the FSOs to cause synchronization of the FS and RFS. Systems are also described. The invention facilitates event-based, steady-state synchronization of local and remote file systems.
A system for effectively addressing the fast-producer and slow-consumer problem for persistent hybrid cloud caches. In particular, the system and associated methods ensure the integrity of data stored by persistent caches by utilizing a plurality of journals, including a user journal and a cloud journal. The user journal records operations conducted by users of the system in records. Before the records are transferred to a cloud storage system, the records are transferred to the cloud journal, which may he configured to he larger than the user journal. Once a record is transferred from the user journal to the cloud journal, the record may be released from the user journal, thereby increasing capacity of the user journal for subsequent operations to be recorded. Each record may then be transferred to the cloud storage system from the cloud journal, which may then cause each record to be released from the cloud journal.
H04L 67/568 - Stockage temporaire des données à un stade intermédiaire, p.ex. par mise en antémémoire
H04L 67/1097 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau pour le stockage distribué de données dans des réseaux, p.ex. dispositions de transport pour le système de fichiers réseau [NFS], réseaux de stockage [SAN] ou stockage en réseau [NAS]
G06F 16/17 - Systèmes de fichiers; Serveurs de fichiers - Détails d’autres fonctions de systèmes de fichiers
H04L 67/06 - Protocoles spécialement adaptés au transfert de fichiers, p.ex. protocole de transfert de fichier [FTP]
A system for handling Implicit transactions in a hybrid cloud cache. The hybrid cloud cache maintains folders in a metadata file system that includes a hierarchy of cached folders, and maintains a meta-file containing metadata of files and folders. The system obtains a meta-file from a cloud platform and compares that to a meta-file obtained from the hybrid cloud cache. An object associated with an Implicit metadata transaction is transferred to an internal namespace of the hybrid cloud cache if the comparison indicates that certain conditions are met. The system may perform a bottom-up traversal of the namespace and may abort the traversal if an outstanding explicit transaction for the object is present or the object exists in the cloud platform. An object may be moved to a temporary storage location if there is no explicit transaction on it and the object does not exist in the cloud platform.
H04L 67/1097 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau pour le stockage distribué de données dans des réseaux, p.ex. dispositions de transport pour le système de fichiers réseau [NFS], réseaux de stockage [SAN] ou stockage en réseau [NAS]
G06F 16/22 - Indexation; Structures de données à cet effet; Structures de stockage
H04L 67/568 - Stockage temporaire des données à un stade intermédiaire, p.ex. par mise en antémémoire
17.
System and method for sensitive content analysis prioritization based on file metadata
Example systems and methods for efficient data governance are disclosed. Metadata associated with file objects is analyzed to estimate, for each file object, likelihood that the file object includes sensitive data. The estimates are used to prioritize the file objects for analysis of the file objects’ content to determine the objects include data deemed to be of a sensitive nature. In cloud-based systems/methods the estimates are also used to prioritize the file objects for transfer from a remote file storage system to the cloud-based system for analysis of content. The disclosed systems and methods significantly reduce the time required to identify sensitive file content in a large number of file objects.
Systems and methods for serving subject access requests (SARs) are disclosed. A network connection is established with a user. An SAR, including at least one piece of personal data corresponding to an entity associated with said user, is received from the user via the network connection. Text data is extracted from a plurality of data objects, the data objects including personal data associated with the user. The text data is then processed to identify instances of names and instances of personal data within the text data. Associations are generated between identified names and identified personal data. A subset of the identified personal data that corresponds to the entity is identified based on the associations. A response to the SAR is provided, based at least in part on the identified personal data corresponding to the entity.
Cloud storage systems and methods are described for providing event-based user state synchronization among the various cloud elements. A global user directory is maintained on a remote cloud storage system. The global user directory includes a plurality of global user definitions associated with a plurality of user accounts, where each of the user accounts has access to at least one of a remote file system hosted by the remote cloud storage system and a local file system hosted by a local cloud storage system. As global user definition are altered on the remote cloud storage system, user events are generated and communicated to the local cloud storage system, where they are applied to synchronize the local user definitions with the global user definitions. The invention facilitates centralized control of user definitions, near real-time event delivery to local cloud storage systems, and separation of authentication processes from customers' active directory services.
G06F 16/27 - Réplication, distribution ou synchronisation de données entre bases de données ou dans un système de bases de données distribuées; Architectures de systèmes de bases de données distribuées à cet effet
G06F 21/45 - Structures ou outils d’administration de l’authentification
20.
System and method for resolving transient and localized errors in a hybrid cloud cache
A system for resolving transient and localized errors in a hybrid cloud cache. The system may include a subsystem within a hybrid cloud cache that provides a way to handle errors associated with uploading files or folders to a cloud. The subsystem may be used to recover files and folders created by a user that could not be pushed to the cloud, while also ensuring that metadata and data are not lost. The subsystem may work with the transaction processing subsystem of the hybrid cloud cache to facilitate the release of transactions associated with the files and folders that could not be pushed to the cloud. By doing so, the subsystem assists in unblocking subsequent transactions or user operations and allows the hybrid cloud cache to upload files and folders to the cloud without interruption.
G06F 11/00 - Détection d'erreurs; Correction d'erreurs; Contrôle de fonctionnement
G06F 11/14 - Détection ou correction d'erreur dans les données par redondance dans les opérations, p.ex. en utilisant différentes séquences d'opérations aboutissant au même résultat
G06F 16/16 - Opérations sur les fichiers ou les dossiers, p.ex. détails des interfaces utilisateur spécialement adaptées aux systèmes de fichiers
A cloud-based data governance system includes a processing unit, a network adapter, and memory for storing data and code. The network adapter establishes a connection with a remote data storage system associated with a remote file system over a wide-area network (WAN). The code includes and event collection interface, a data governance service, and an enforcement service. The event collection interface is configured to capture an event from the remote data storage system. The event is indicative of a file system operation executed on a data object of the remote file system. The data governance service is configured to receive the event from the event collection interface and to process the event to determine whether the file system operation conflicts with a governance policy of the data governance system. The enforcement service executes a set of remediation actions, if the file system operation does conflict with the governance policy.
A system and methods for presenting a hybrid cloud cache as a file system. The system implements a set of standard file system command line interfaces that present the objects stored by the hybrid cloud cache to users of the system as if the users were viewing and interacting with a traditional file system. The system provides an interactive shell to the users to view the contents of the hybrid cloud cache. The system may be configured to operate on a live instance as well as on an on-disk structure of the hybrid cloud cache. The system may provide the ability to present partially cached cloud data as a file system via the interactive shell for the purposes of development, support, and troubleshooting.
A system and methods for grouping and executing transactions concurrently while ensuring hybrid cloud cache integrity and consistency. The system identifies upload operations in a journal and associates each such operation with an upload transaction. The upload operations may be grouped into a group of concurrently executed upload operations. If an upload transaction finishes uploading a file and there is a most recent older upload transaction having a pending upload, then the system adds the completed transaction and a dependency queue associated with that transaction to a dependency queue of the most recent older upload transaction. If the current upload transaction finishes the upload operation and the transaction has an oldest transaction identifier of the group, then the system adds a PUSHDONE record for that transaction to a hybrid cloud cache journal along with a PUSHDONE record for the other transactions depending on that completed transaction.
A method for providing access to objects associated with a particular client in a cloud storage system is disclosed. The method includes the steps of establishing a connection with a user, providing a client namespace associated with the client to the user, where the client namespace represents objects stored on the cloud storage system and objects stored on a private storage system apart from the cloud storage system, receiving a request from the user to access an object stored on the private storage system, and providing information to the user to facilitate access to the object stored on the private storage system by said user. Other systems and methods are also disclosed. Important advantages of the present invention are facilitated by separating the logic for user access (control plane) from the actual storage (Storage plane). Private file system access can still be managed from the cloud, while keeping the client data private.
G06F 16/27 - Réplication, distribution ou synchronisation de données entre bases de données ou dans un système de bases de données distribuées; Architectures de systèmes de bases de données distribuées à cet effet
Systems and methods for serving subject access requests (SARs) are disclosed. A network connection is established with a user. An SAR, including at least one piece of personal data corresponding to an entity associated with said user, is received from the user via the network connection. Text data is extracted from a plurality of data objects, the data objects including personal data associated with the user. The text data is then processed to identify instances of names and instances of personal data within the text data. Associations are generated between identified names and identified personal data. A subset of the identified personal data that corresponds to the entity is identified based on the associations. A response to the SAR is provided, based at least in part on the identified personal data corresponding to the entity.
A novel method for restarting a steady-state synchronization process includes persisting synchronization data in non-volatile memory before restarting, and utilizing the persisted synchronization data to restart the synchronization where the prior steady-state synchronization process left off. In a particular embodiment, the synchronization data is indicative of a particular point of the synchronization process and is utilized to begin synchronizing from that point after the service is restarted. In a more particular embodiment, the synchronization data is a particular operation of a sequence of operations performed as part of the synchronization. In another particular embodiment, operations associated with a batch are applied before stopping the synchronization.
G06F 16/27 - Réplication, distribution ou synchronisation de données entre bases de données ou dans un système de bases de données distribuées; Architectures de systèmes de bases de données distribuées à cet effet
G06F 16/11 - Administration des systèmes de fichiers, p.ex. détails de l’archivage ou d’instantanés
G06F 16/176 - Support d’accès partagé aux fichiers; Support de partage de fichiers
G06F 16/17 - Systèmes de fichiers; Serveurs de fichiers - Détails d’autres fonctions de systèmes de fichiers
27.
Flexible permission management framework for cloud attached file systems
A method of managing file permissions in a remote file storage system includes defining permissions for the remote file storage system and controlling access to objects on the remote file storage system according to the permissions of the remote file storage system. The permissions are transferred to a client file storage system remote from the remote file storage system, and access to objects on the client file storage system is controlled according to the permissions of the remote file storage system. A remote file storage system includes a permissions file generator operative to generate a permissions file, which is transmitted to a client file storage system for enforcement at the client file storage system.
A method for facilitating synchronization of a remote file system (RFS) and a local file system (LFS) includes maintaining a global revision identifier associated with the RFS, where the global revision identifier has a variable state, and responsive to the RFS being modified, updating metadata associated with one or more of the file system objects of the RFS based on a state of the global revision identifier. More particularly, the method includes updating the global revision identifier to a new state in response to the RFS modification and then updating the metadata of the folder(s) associated with the RFS modification. The RFS metadata is partitioned by folder and file to facilitate efficient searching based on a requested namespace view. Another method utilizes prior revision identifiers stored in the LFS to limit the RFS metadata returned to the local cloud during a rescan, by excluding the data set that has not changed, which improves the efficiency of the rescan synchronization.
A method for synchronizing a file system (FS) and a remote file system (RFS) includes monitoring the FS for FS events, generating FS event records, receiving RFS event records of RFS events, generating file system operations (FSOs) based on the FS and RFS event records, and communicating the FSOs to the FS and RFS to synchronize them. A method for generating the FSOs includes accessing a plurality of FS and/or RFS event records, processing the accessed records to generate processed event records, generating the FSOs based on the processed event records, and outputting the FSOs to cause synchronization of the FS and RFS. Systems are also described. The invention facilitates event-based, steady-state synchronization of local and remote file systems.
A method for synchronizing a local file system (LFS) and a remote (cloud) file system (RFS) includes the step of storing events indicative of differences between the LFS and the RFS, where the events are associated with file system objects of the LFS and RFS. The method further includes the steps of prioritizing the events, generating file system operations for the events based at least in part on the prioritization of the events, and performing at least some of the file system operations to synchronize the LFS and RFS. Prioritizing the events includes defining a plurality of service classes (e.g., based on type of event, event attribute, etc.), assigning a priority to each of the service classes, and assigning each event to one of said service classes. Systems are also described. The invention allocates limited synchronization resources based on a predefined policy to synchronize important file system objects sooner.
G06F 16/178 - Techniques de synchronisation des fichiers dans les systèmes de fichiers
H04L 67/1095 - Réplication ou mise en miroir des données, p.ex. l’ordonnancement ou le transport pour la synchronisation des données entre les nœuds du réseau
G06F 16/16 - Opérations sur les fichiers ou les dossiers, p.ex. détails des interfaces utilisateur spécialement adaptées aux systèmes de fichiers
G06F 16/176 - Support d’accès partagé aux fichiers; Support de partage de fichiers
31.
System and method for determining value of digital content
A novel system for performing valuations of file system objects include a processor configured to execute code and memory configured to store data and the code. The code includes an accumulator configured to accumulate secondary data associated with said file system objects, a data aggregator configured to arrange the secondary data in the memory, and a value generator configured to generate an object value indicative of the value of at least one of the file system objects to a particular entity. In a particular embodiment, the value generator creates a record in a valuation database to associate the object value with the at least one of the file system objects.
G06Q 50/00 - Systèmes ou procédés spécialement adaptés à un secteur particulier d’activité économique, p.ex. aux services d’utilité publique ou au tourisme
G06F 16/00 - Recherche d’informations; Structures de bases de données à cet effet; Structures de systèmes de fichiers à cet effet
G06Q 30/02 - Marketing; Estimation ou détermination des prix; Collecte de fonds
G06Q 50/18 - Services juridiques; Maniement de documents juridiques
G06F 16/14 - Systèmes de fichiers; Serveurs de fichiers - Détails de la recherche de fichiers basée sur les métadonnées des fichiers
G06F 16/17 - Systèmes de fichiers; Serveurs de fichiers - Détails d’autres fonctions de systèmes de fichiers
G06F 16/11 - Administration des systèmes de fichiers, p.ex. détails de l’archivage ou d’instantanés
G06F 16/28 - Bases de données caractérisées par leurs modèles, p.ex. des modèles relationnels ou objet
32.
System and method for synchronizing file systems with large namespaces
A method for facilitating synchronization of a remote file system (RFS) and a local file system (LFS) includes maintaining a global revision identifier associated with the RFS, where the global revision identifier has a variable state, and responsive to the RFS being modified, updating metadata associated with one or more of the file system objects of the RFS based on a state of the global revision identifier. More particularly, the method includes updating the global revision identifier to a new state in response to the RFS modification and then updating the metadata of the folder(s) associated with the RFS modification. The RFS metadata is partitioned by folder and file to facilitate efficient searching based on a requested namespace view. Another method utilizes prior revision identifiers stored in the LFS to limit the RFS metadata returned to the local cloud during a rescan, by excluding the data set that has not changed, which improves the efficiency of the rescan synchronization.
The invention prevents improper deletes of file system objects during rescan synchronizations of local and remote (cloud) file systems. File and folder deletes are validated (confirmed) during a rescan synchronization using events generated for a steady state synchronization process. Any improper deletes are fenced and not allowed to proceed during synchronization. A method for synchronizing local (LFS) and remote (RFS) file systems includes monitoring the LFS for changes, generating a first set of events as part of a first synchronization routine (e.g., a steady state synchronization routine), generating a second set of events as part of a second (rescan) synchronization routine, validating selected events of the second set with events of the first set to determine whether each of the selected events of the second set is valid or invalid, and synchronizing the file systems based on the events of the second set excluding those that have been invalidated. Storage systems are also disclosed.
brevets
