G06F16/166

SNAPSHOT MANAGEMENT IN DISTRIBUTED FILE SYSTEMS
20170249335 · 2017-08-31 ·

A system and method are disclosed for managing snapshots of a distributed file system. In accordance with one implementation, a list of snapshots of a file system is presented to a user, where the snapshots include one or more active snapshots and one or more inactive snapshots. A request by the user to access one of the snapshots in the list is received. In response to determining that the requested snapshot is active, the user is provided access to the requested snapshot. In response to determining that the requested snapshot is inactive, the requested snapshot is activated and the user is provided access to the requested snapshot.

System, method, and interfaces for work product management

A method includes receiving an initial electronic file where the initial electronic file is associated with a work product. The method further includes resolving, automatically, an electronic file content type associated with the initial electronic file and executing, automatically, at least one subscription program associated with the electronic file content type of the initial electronic file. The method further includes retrieving an enhanced electronic file based on a matter security level. The enhanced electronic file is associated with an indication of completion of the at least one subscription program. Another embodiment includes extracting a set of metadata from the initial electronic file and storing the set of metadata from the initial electronic file in a memory. Yet another embodiment includes populating, automatically, at least one field within a field-oriented electronic file from the set of metadata.

Method and system for collecting digital documents from a plurality of sources
11238128 · 2022-02-01 · ·

A method for collection of digital documents from a plurality of sources, the method comprising: a step to determine a collection order defining a list of documents to be collected, each document being associated with a determined source and a determined identifier, a step to generate a plurality of web pages from the collection order, each web page including a loading area associated with each digital document from said source, each loading area being adapted to automatically store a digital document in a memory of a computer management system, and a step to send a collection email to each source, each collection email sent to a source including a computer link to access the web loading page associated with said source.

Keeping Object Access on a File Store Consistent With Other File Protocols
20210397586 · 2021-12-23 ·

Techniques are provided for keeping object access on a file store consistent with other file protocols. In an example, a server that stores data in a file system receives a PUT OBJECT operation to perform, which corresponds to a target file. The server creates a temporary file and writes to the temporary file. After the writing, the server can lock the target file, rename the temporary file to the name of the target file, and unlock the target file. In another example, the server receives a GET OBJECT operation, which corresponds to a target file. The server locks the target file, reads the first file, and releases the lock on the target file. This approach can maintain consistency between object storage operations and file storage operations that are implemented by the server.

Method and Apparatus for Generating Multimedia File
20220206994 · 2022-06-30 ·

A method for generating a multimedia file includes selecting a multimedia clip according to at least one received input instruction in a process of multimedia recording, parsing the selected multimedia clip to obtain corresponding text information, generating a multimedia file according to the at least one received input instruction, and generating a file name of the multimedia file according to the text information. Accordingly, the multimedia file is generated using text information that is obtained by parsing a multimedia clip, so that a file name of the multimedia file reflects information of the multimedia file.

Method and apparatus for creating system disk snapshot of virtual machine

A method and apparatus for creating a system disk snapshot of a virtual machine comprises: receiving an instruction for creating a snapshot of a virtual machine; determining existence of a power-on state; renaming a top file in a system disk in response to the received instruction if the power-on state exists; creating a new top file in response to renaming the top file, directing dependency of the new top file to the renamed top file and opening the new top file; determining whether a preceding snapshot is created successfully; using the renamed top file as a first snapshot file if the preceding snapshot is successful; and uploading the first snapshot file to a file management server. Accordingly, when a system disk snapshot is created in a power-on state, the snapshot may be created without stopping the virtual machine, thereby reducing requirements for data back up, storage space, and network bandwidth.

Faster replay of metadata and data operations using inode number based dependency graph

Techniques are provided for replay of metadata and data operations. During initial execution of operations, identifiers of objects modified by the execution of each operation are identified and stored in association with the operations. When the operations are to be replayed (e.g., executed again, such as part of a replication operation or as part of flushing content from a cache to persistent storage), the identifiers are evaluated to determine which operations are independent with respect to one another and which operations are dependent with respect to one another. In this way, independent operations are executed in parallel and dependent operations are executed serially with respect to the operations from the dependent operations depend.

MERGING COMPOSITE IMAGES INTO A NEW FILESYSTEM NAMESPACE
20220138146 · 2022-05-05 ·

Merging a plurality of CIMs into a merged filesystem namespace includes accessing merge configuration information that identifies a plurality of backing CIMs and a merge precedence order for the backing CIMs. Based on the merge configuration information, merged metadata is generated from metadata portions of the backing CIMs. The merged metadata defines a merged filesystem namespace comprising two or more filesystem objects from the backing CIMs. The merged metadata includes at least first and second merged metadata items that each defines a corresponding filesystem object as being part of the merged filesystem namespace. Each merged metadata item corresponds to a corresponding metadata item within a corresponding metadata portion of a different backing CIM, references a data portion of its corresponding backing CIM, and is generated based on its corresponding filesystem object having no conflict with any filesystem object from any backing CIM that has a higher merge precedence.

Recovery from a clustered file system queue failure event using a modified extended attribute of a file

A computer-implemented method according to one embodiment includes, in response to a determination that a predetermined operation has been performed on an object of a first file stored on a first cluster site, storing predetermined information about the object of the first file stored on the first cluster site. The predetermined information is stored on an extended attribute of the first file stored on the first cluster site. In response to a determination that the predetermined operation is performed on an object of a first file stored on a second cluster site, the predetermined information is removed from the extended attribute of the first file stored on the first cluster site. In response to a determination that a failure event has occurred on a queue of the first cluster site, a predetermined recovery process is performed, thereby enabling fulfillment of entries of the queue of the first cluster site.

Metadata-Based Recommendations of File Names

A computing platform is configured to: (i) receive, from a first client station, a data file; (ii) obtain metadata associated with the data file; (iii) determine, based on at least a first set of metadata from the obtained metadata associated with the data file, a naming structure to use for the data file; (iv) generate, based on the determined naming structure and at least a second set of metadata from the obtained metadata, a proposed name for the data file; and (v) transmit, to a second client station, a communication identifying the proposed name and thereby cause an indication of the proposed name for the data file to be presented at a user interface of the second client station.