4 results about "Write once read many" patented technology

A database operating method and a fully encrypted database are disclosed. The method is executed by a read node in a write once read many database and includes: receiving a reading operation request from a user, determining that a writing operation is required for a data encryption key table in response to the reading operation request; establishing a connection with a write node and forwarding the writing operation; acquiring the data encryption key table that the write node has updated based on the writing operation; generating, based on the updated data encryption key table, a reading operation response and sending the reading operation response to the user. Thus, the present disclosure proposes a write once read many solution applicable to a fully encrypted database, which solves the problem of writing encryption key information of the read node in a distributed database scenario.

This disclosure relates to a symbolic containment firewall that evaluates and governs natural language transactions before they modify state in downstream computer systems. Incoming text is associated with a configurable domain profile and normalized, and heuristic features such as entropy, anchor coverage, omissions, and contradictions are computed. A model adapter obtains a model assisted structural stability score, and a symbolic containment engine combines the heuristic features and model score into a containment stability score and containment stability label. A decision stage selects a pass, block, or escalate action and may generate refactored text that satisfies domain profile requirements. For each transaction, the system constructs a canonical audit object that captures the input, context, analysis, and decision, computes a cryptographic seal over a deterministic representation of the audit object, and writes the sealed audit object to write once read many storage that gates downstream execution and enables later verification of containment decisions.

Write-once-read-many in cloud for file systems backed up to object storage (e.g., using a computerized tool), is enabled. For example, a system can comprise at least one processor, and at least one memory that stores executable instructions that, when executed by the at least one processor, facilitate performance of operations. The operations can comprise identifying changes to data in a file of a file system relative to a first version of an object chunk representative of the data in an object store, wherein the data is determined to comprise a defined data retention policy, copying changed data, of the data, from the file system to a second version of the object chunk, and copying unchanged data, of the data, from the first version of the object chunk to the second version of the object chunk.

A data storage management system is enhanced to accommodate, and moreover to optimize, the storing and retention of deduplicated secondary copies at write-once read-many (WORM) enabled storage platforms. Enhancements include without limitation: user interface (UI) options to enable WORM functionality for secondary storage, whether used for deduplicated or non-deduplicated secondary copies; enhancements to secondary copy (e.g., deduplication copy, backup) operations; and pruning changes. The storage manager is generally responsible for managing the creation, tracking, and deletion of secondary copies, with and without deduplication. Media agents that store secondary copies to and prune them from the WORM-enabled storage platforms also are enhanced for communicating and interoperating with both bucket-level and object-level WORM-enabled storage platforms to implement the features disclosed herein.