A file storage method, apparatus, device and a readable storage medium. The method includes: performing striping processing on a target file to obtain multiple target objects, and calculating fingerprint information of each target object; using a first target object and logical information of the target file to form a logical header object, and storing the logical header object in a storage system; using the fingerprint information of each second target object to determine whether the second target object has been stored in the storage system; and if the second target object has not been stored in the storage system, determining the second target object as a third target object and storing same in the storage system. According to the method, logical information of each file can be preserved, and files of some users can be prevented from being modified or deleted after deduplication is performed in the storage system.

Methods and systems for multi-dimensional data labeling. A structured data set having a plurality of rows is obtained, the structured data set comprising a set of data attributes, each data attribute having a data value for each of the plurality of rows of the structured data set. The structured data set is decomposed into a plurality of dimensions, each dimension defining a proper subset of the data attributes based on coherence criterion. A dimension label is obtained for each dimension of at least a portion of the plurality of rows of the structured data set and the dimension labels for a given one of the rows of the structured data set are consolidated into at least one row label for the given one of the rows.

Techniques are disclosed for managing metadata of a storage system. A storage control system receives data to be written to primary storage, and writes the received data together with metadata to a write cache. The storage control system destages the metadata from the write cache to a primary metadata structure which is configured to persistently store and index the metadata. The primary metadata structure comprises (i) a first data structure that is configured to accumulate the metadata destaged from the write cache and organize the accumulated metadata in blocks of metadata sorted by index keys, and (ii) a second data structure that is configured to receive the accumulated metadata from the first data structure, and organize the received metadata using an index structure that enables random-access to the metadata using the index keys.

The cloud hybrid application storage management system spans local data center and cloud-based storage and provides a unified view of content and administration throughout an enterprise. The system manages synchronization of storage locations, ensuring that files are replicated, uniquely identified, and protected against corruption. The system ingests digital media assets and creates instances of the assets with their own identification and rights and houses the identification and relationships in a CAR (Central Asset Registry). The system tracks the different instances of the assets in multiple storage locations using the CAR, which is a central asset registry that ties together disparate digital asset management repository systems (DAMs) and cloud-based storage archives in which the instances reside. While the invention treats and manages multiple files/instances independently, the CAR identifies them as related to each other.

Embodiments of systems and methods for the rules based distribution of managed content across heterogeneous storage distributed in a network environment are disclosed. In particular, certain embodiments may employ entity rules in association with a content management system. An entity rule may be a rule specifying a set of parameters and a destination secondary storage location. When the entity rule is evaluated by the content system, a set of content managed by the content management system responsive to the rule may be determined using the parameters of the rule. Responsive content can be determined, for example, by searching the content of the content management system based on the parameters. Responsive content may be moved from the primary storage location of the content management system to the secondary storage location specified by the entity rule.

Object service receives communication of fingerprints stream, corresponding to file segments, from file source, and identifies sequential fingerprints in fingerprints stream as fingerprints group. Object service identifies group identifier for fingerprints group, and communicates fingerprints group to deduplication service associated with group identifier range including group identifier. Deduplication service identifies fingerprints in fingerprints group which are missing from fingerprint storage, and communicates identified fingerprints to object service, which communicates request for file segments, corresponding to identified fingerprints, to file source. Deduplication service receives communication of requested segments from file source, and stores requested segments. System identifies generation identifier associated with time of communicating by object service or deduplication service and identifies generation identifier associated with another time of communicating by object service or deduplication service. If generation identifier associated with time differs from generation identifier associated with other time, object service or deduplication service restarts communication.

Methods, systems and computer program products are provided for automated runtime configuration for dataflows to automatically select or adapt a runtime environment or resources to a dataflow plan prior to execution. Metadata generated for dataflows indicates dataflow information, such as numbers and types of sources, sinks and operations, and the amount of data being consumed, processed and written. Weighted dataflow plans are created from unweighted dataflow plans based on metadata. Weights that indicate operation complexity or resource consumption are generated for data operations. A runtime environment or resources to execute a dataflow plan is/are selected based on the weighted dataflow and/or a maximum flow. Preferences may be provided to influence weighting and runtime selections.

In a multi-cloud computing environment comprising a plurality of cloud platforms with each cloud platform comprising one or more nodes, a method maintains a decentralized metadata database framework, wherein each node comprises a decentralized metadata database component operatively coupled to each other decentralized metadata database component of the framework and wherein each of at least two of the decentralized metadata database components stores a set of metadata records corresponding to protected data stored across the plurality of cloud platforms. Further, the method manages one or more access requests directed to the protected data through one or more of the decentralized metadata database components of the framework.

A method is provided that includes establishing, by an application server, a remote access session with a client device, and creating, by a file system agent running on the application server, a metadata-only virtual file system associated with the remote access session, wherein the virtual file system only comprises file metadata associated with a plurality of files residing in a local file system of the client device. The method further includes responsive to receiving, by the virtual file system, a request to access content of a file referenced by the virtual file system, redirecting the request to a file system driver implementing at least a sub-tree of the local file system of the client device.

A system for applying metadata tags based on metadata tag groups is described. The system includes a plurality of compute nodes configured to provide a plurality of computing resources for clients of a provider network and a resource tag manager for the provider network. The resource tag manager is configured to receive, from a first client of an account of the provider network, a creation request to establish a resource attribute group comprising a plurality of resource keys and a plurality of resource values, wherein respective metadata keys correspond to respective resource values. The resource tag manager may receive, from a second client of the account, an application request to apply the resource attribute group to a computing resource and apply the plurality of resource keys and the plurality of resource values to metadata maintained for the computing resource.