Patent classifications
G06F16/275
Deduplicated data distribution techniques
In connection with a data distribution architecture, client-side “deduplication” techniques may be utilized for data transfers occurring among various file system nodes. In some examples, these deduplication techniques involve fingerprinting file system elements that are being shared and transferred, and dividing each file into separate units referred to as “blocks” or “chunks.” These separate units may be used for independently rebuilding a file from local and remote collections, storage locations, or sources. The deduplication techniques may be applied to data transfers to prevent unnecessary data transfers, and to reduce the amount of bandwidth, processing power, and memory used to synchronize and transfer data among the file system nodes. The described deduplication concepts may also be applied for purposes of efficient file replication, data transfers, and file system events occurring within and among networks and file system nodes.
BLOCKCHAIN STRUCTURE FOR EFFICIENT SEARCHING
A determination is made that an event associated with a composite blockchain is a primary event or a secondary event. The composite blockchain comprises a primary blockchain and a first level sub-blockchain. In response to determining that the event is the primary event, a new block is dynamically added to the end of the primary blockchain. In response to determining that the event is the secondary event, the first level sub-blockchain is dynamically created. Dynamically creating the first sub-level blockchain comprises dynamically creating a first block in the first sub-level blockchain. This creates a branched blockchain that can be used for efficient searching.
Processing transactions in a synchronized replication system
Embodiments of the present disclosure provide a method, a computer program product and apparatus for processing transactions in a synchronized replication system, wherein the method comprises, at a source site in the synchronized replication system: serializing commits of transactions in the synchronized replication system so that only one of the transactions can be committed at the same time; in response to initiating the commit of the one transaction, generating a log for each of transactions that are ongoing in the synchronized replication system, so as to record impact of all operations of a respective transaction on the synchronized replication system; marking transactions for which the logs have been generated; and completing commits of the marked transactions.
File system warnings application programing interface (API)
The present technology pertains to a organization directory hosted by a synchronized content management system. The corporate directory can provide access to user accounts for all members of the organization to all content items in the organization directory on the respective file systems of the members' client devices. Members can reach any content item at the same path as other members relative to the organization directory root on their respective client device. In some embodiments novel access permissions are granted to maintain path consistency.
Information processing apparatus and non-transitory computer readable medium storing information processing program
An information processing apparatus includes a transfer part that, in a case where an authentication process for connecting to a preset first storage area fails and transfer of a document processed in accordance with a preset process procedure to the first storage area fails, transfers the document to a second storage area, and in a case where the authentication process succeeds after the document is transferred to the second storage area, transfers the document stored in the second storage area to the first storage area.
Dependency aware parallel splitting of operations
Techniques are provided for dependency aware parallel splitting of operations. For example, a count of pending data operations being executed by a first node and replicated in parallel to a second node are tracked. A metadata operation is executed at the first node based upon the count being less than a threshold (e.g., the count being zero). A first list of affected inodes modified by the metadata operation is identified. A dependency of the metadata operation with respect to pending metadata operations replicated to the second node is determined. The metadata operation is dispatched to the second node based upon the dependency indicating that the metadata operation is independent of the pending metadata operations.
DEDUPLICATED DATA DISTRIBUTION TECHNIQUES
In connection with a data distribution architecture, client-side “deduplication” techniques may be utilized for data transfers occurring among various file system nodes. In some examples, these deduplication techniques involve fingerprinting file system elements that are being shared and transferred, and dividing each file into separate units referred to as “blocks” or “chunks.” These separate units may be used for independently rebuilding a file from local and remote collections, storage locations, or sources. The deduplication techniques may be applied to data transfers to prevent unnecessary data transfers, and to reduce the amount of bandwidth, processing power, and memory used to synchronize and transfer data among the file system nodes. The described deduplication concepts may also be applied for purposes of efficient file replication, data transfers, and file system events occurring within and among networks and file system nodes.
Mechanism for synchronization of hierarchical data between a mobile device and multi tenant database
Techniques and structures to synchronize hierarchical data, comprising. A conflict between data stored at a computing device and data stored at a service provider database is detected. A synchronization operation is performed to synchronize a plurality of objects within the hierarchical entity data stored at the computing device with hierarchical entity data stored at the service provider database.
Native persistent store support for blockchains
Distributed ledgered data is stored within a distributed persistent storage system comprising multiple persistent storage systems as distributed ledgered participants. In various embodiments, the distributed ledgered data is maintained using the native capabilities of a persistent storage system. The distributed ledgered data is replicated as persistent data objects in a “ledgered repository of objects” that are replicated at each of the persistent storage systems. Changes at one persistent storage system are recorded within a block in a distributed blockchain that is distributed across each of the other distributed ledgered participants. The other distributed ledgered participants read the changes from the blockchain and apply the changes to the respective replicas at each of the other distributed ledgered participants. Hence, this approach is referred to as blockchain apply. Blockchain apply may be used to replicate the repository objects of various forms of PSSs. In a DBMS, a repository of objects is a table, where each record or row is an object in the repository. In a file system, a repository of objects is a directory, where each directory and file therein is an object in the repository. In a document storage system (DOCS), a repository of objects is a collection of documents, where each document is an object in the repository.
Methods, systems and computer program products for data synchronization in industrial plants
The present invention provides methods, systems and computer program products that enable the optimized synchronization of data between mobile client devices assigned to field operators in an industrial plant and a centralized repository for plant data. The invention optimizes synchronization of data between mobile client devices assigned to field operators in an industrial plant and a centralized repository for plant data by selecting a reduced set of data records associated with a field operator, for data synchronization based on one or more of a set of data record selection parameters, and a set of version synchronization rules to ensure that only data records that are relevant to a field operator's foreseeable activities in a shift are downloaded to the field operator's mobile client device.