Patent classifications
Y10S707/99953
SYSTEMS AND METHODS FOR STORAGE MODELING AND COSTING
The present invention provides systems and methods for data storage. A hierarchical storage management architecture is presented to facilitate data management. The disclosed system provides methods for evaluating the state of stored data relative to enterprise needs by using weighted parameters that may be user defined. Also disclosed are systems and methods evaluating costing and risk management associated with stored data.
Massively Scalable Object Storage for Storing Object Replicas
An example method for storing data includes providing a plurality of physical storage pools, each storage pool including a plurality of storage nodes coupled to a network. The method also includes mapping a partition of a plurality of partitions to a set of physical storage pools, where each physical storage pool of the set of physical storage pools is located in a different availability zone, and the storage nodes within an availability zone are subject to a correlated loss of access to stored data. The method further includes receiving a data management request over the network, the data management request being associated with a data object. The method also includes identifying a first partition of the plurality of partitions corresponding to the received data management request and manipulating the data object in the physical storage pools mapped to the first partition in accordance with the data management request.
METHOD AND SYSTEM FOR CONSTRUCTING PERSISTENT MEMORY INDEX IN NON-UNIFORM MEMORY ACCESS ARCHITECTURE
A method for constructing a persistent memory index in a non-uniform memory access architecture includes: maintaining partial persistent views in a persistent memory and maintaining a global volatile view in a DRAM; an underlying persistent memory index processing a request in a foreground thread when cold data is accessed; when hot data is accessed, reading a key-value pair for a piece of hot data in the global volatile view in response to a query operation carried in the request, and in response to an insert/update/delete operation carried in the request, updating a local partial persistent view and the global volatile view; and in response to a hotspot migration, a background thread generating new partial persistent views and a new global volatile view, and recycling the partial persistent views and the global volatile view for old hot data into the underlying persistent memory index.
Method and system for constructing persistent memory index in non-uniform memory access architecture
A method for constructing a persistent memory index in a non-uniform memory access architecture includes: maintaining partial persistent views in a persistent memory and maintaining a global volatile view in a DRAM; an underlying persistent memory index processing a request in a foreground thread when cold data is accessed; when hot data is accessed, reading a key-value pair for a piece of hot data in the global volatile view in response to a query operation carried in the request, and in response to an insert/update/delete operation carried in the request, updating a local partial persistent view and the global volatile view; and in response to a hotspot migration, a background thread generating new partial persistent views and a new global volatile view, and recycling the partial persistent views and the global volatile view for old hot data into the underlying persistent memory index.
System and method of handling file metadata
A network storage system comprises data storage, one or more file system APIs, and a metadata handler. The data storage can comprise file data and associated metadata. The file system APIs can be configured to read and write file data and metadata to and from the data storage. The metadata handler can have a library of functions for handling the metadata. The library can include a metadata blob creation function and a metadata blob extraction function. The metadata blob creation function cooperates with the file system APIs to read source metadata associated with specified file data and creates and populates a metadata blob from which a substantial copy of the source metadata can be generated. The metadata blob extraction function receives at least a metadata blob, extracts information from the metadata blob, and cooperates with the file system APIs to generate destination metadata, a substantial copy of the source metadata.
Viral Engine for Network Deployment
A private network system operates over a public network to provide an asymmetric service to members with information from other members and non-members. The system includes central servers and databases connected via the public network to client systems of public network users. The users may be members who communicate with a private protocol or non-members who communicate with the public protocol. A process for the private service includes communication of information between users via the private service servers. The private service server implements the private service, which includes a viral engine for network deployment. Features of the viral engine include genetic algorithms, data mining, personalization, frictionless service setup, user maximization, and member-controlled privacy. A sample setup process and contact update wizard that include several viral engine features are described.
COPY PROCESS SUBSTITUTING COPMPRESSIBLE BIT PATTERN FOR ANY UNQUALIFIED DATA OBJECTS
A copy procedure detects qualified data objects in a body of source data, and copies the source data to a target storage unit except for unqualified data objects, which are replaced with a prescribed bit pattern. Following completion of the backup, a record is prepared indicating that all data objects exist in the specified target storage, regardless of whether each data object was replaced with a predetermined bit pattern rather than being physically written to the specified target storage. This process may, be repeated in order to perform data reclamation, effectively removing user files no longer qualifying for backup.
Automation tool for web site content language translation
A system, method and computer readable medium for providing translated web content is disclosed. The method on an information processing system includes retrieving a first content in a first language and parsing the first content into a plurality of translatable components. The method further includes generating a unique identifier for each of the plurality of translatable components of the first content and queuing the plurality of translatable components and corresponding unique identifiers for translation into a second language. The method further includes, for each of the plurality of translatable components, storing a translated component and an associated unique identifier corresponding to the translatable component, thereby storing a plurality of translated components and corresponding unique identifiers.
Viral engine for network deployment
A private network system operates over a public network to provide an asymmetric service to members with information from other members and non-members. The system includes central servers and databases connected via the public network to client systems of public network users. The users may be members who communicate with a private protocol or non-members who communicate with the public protocol. A process for the private service includes communication of information between users via the private service servers. The private service server implements the private service, which includes a viral engine for network deployment. Features of the viral engine include genetic algorithms, data mining, personalization, frictionless service setup, user maximization, and member-controlled privacy. A sample setup process and contact update wizard that include several viral engine features are described.
Copy process substituting compressible bit pattern for any unqualified data objects
A copy procedure detects qualified data objects in a body of source data, and copies the source data to a target storage unit except for unqualified data objects, which are replaced with a prescribed bit pattern. Following completion of the backup, a record is prepared indicating that all data objects exist in the specified target storage, regardless of whether each data object was replaced with a predetermined bit pattern rather than being physically written to the specified target storage. This process may, be repeated in order to perform data reclamation, effectively removing user files no longer qualifying for backup.