Abstract: A device may be configured to receive, process, forward, and/or respond to one or more resource queries. For example, the device may determine whether multiple queries are satisfied by a multicast response. The device may receive a first query and a second query directed to a resource, The first and the second query may comprise a structure proxy rule identifier (sPRID). The device may determine the similarity between the two queries. For example, the similarity determination may be based on the sPRID of the two queries. The device may determine whether a response that satisfies the first query also satisfies the second query, which may be based on a response to the first query and information comprised within the sPRID of the two queries. If the response satisfies both queries, the device may multicast the response.

Abstract: A system receives a request to store a replica of a data object into any cloud storage node associated with an attribute, and then identifies a redundancy number associated with the data object. The system identifies a number of cloud storage nodes that are associated with the attribute. If the identified number of cloud storage nodes is greater than the redundancy number, the system identifies the redundancy number of cloud storage nodes as a subset of the number of cloud storage nodes, based on the data object and a unique identifier associated with each of the number of cloud storage nodes. The system stores the redundancy number of replicas into the corresponding redundancy number of cloud storage nodes.

Abstract: A device may be configured to receive, process, forward, and/or respond to one or more resource queries. For example, the device may determine whether multiple queries are satisfied by a multicast response. The device may receive a first query and a second query directed to a resource, The first and the second query may comprise a structure proxy rule identifier (sPRID). The device may determine the similarity between the two queries. For example, the similarity determination may be based on the sPRID of the two queries. The device may determine whether a response that satisfies the first query also satisfies the second query, which may be based on a response to the first query and information comprised within the sPRID of the two queries. If the response satisfies both queries, the device may multicast the response.

Abstract: Cross backup application diskless data migration is provided. Legacy data backups eligible for migration are identified in a legacy backup environment. Application specific information regarding the legacy data backups eligible for migration is received. The application specific information is filtered to indicate only legacy backup data that must be migrated representing a type of migration desired. The application specific information corresponding to the legacy backup data that must be migrated is presented as a virtual filesystem mounted within an operating system such that the application specific information is seen as live local data. A backup of the virtual filesystem mounted within the operating system is performed.

Abstract: A computer system generates snapshot backups of a virtual machine by creating a metadata snapshot and a backup snapshot. The computer system identifies a backup request for a virtual machine operating on a host computing system, initiates a backup snapshot of storage devices in use by the virtual machine, generates a metadata snapshot of a configuration of the virtual machine, and maintains the metadata snapshot in a data store.

Abstract: A method and system for automatically performing a volume group structure recovery in a virtualized server recovery environment. A first portion of a first physical volume is accessed and then stored in a temporary file. A last valid volume group backup for a volume group is retrieved. The volume group is a logical group of physical volumes that include the first physical volume. The volume group backup includes respective volume group identifiers corresponding to the physical volumes of the volume group. An existing volume group identifier is replaced with a generated random volume group identifier. Volume group identifiers in the last valid volume group backup is replaced with new volume group identifiers that were generated during a re-initializing of all physical volumes in a list of the physical volumes of the logical group. The volume group's volume group structure is restored using a backup structure stored in the temporary file.

Abstract: A technique to enable the user of storage clouds to use of a plurality of storage clouds without the user of storage clouds being aware of which data is being entrusted to which storage cloud and without sacrificing safety or ease-of-use by selecting at least one storage cloud to store an entity file storable in a cloud-utilizing terminal from among a plurality of storage clouds connected via a network to the cloud-utilizing terminal. This technique includes referencing the attributes or context of an entity file, or the attributes of a virtual folder and each attribute of a plurality of storage clouds, in response to the creation or update of the entity file in the virtual folder in the cloud-utilizing terminal, and selecting at least one storage cloud from among a plurality of storage clouds for storing the entity file so as to satisfy predefined rules.

Abstract: Systems and methods integrate disparate backup devices with a unified interface. In certain examples, a management console manages data from various backup devices, while retaining such data in its native format. The management console can display a hierarchical view the client devices and/or their data and can further provide utilities for processing the various data formats. A data structure including fields for storing both metadata common to the client device data and value-added metadata can be used to mine or process the data of the disparate client devices. The unified single platform and interface reduces the need for multiple data management products and/or customized data utilities for each individual client device and provides a single pane of glass view into data management operations. Integrating the various types of storage formats and media allows a user to retain existing storage infrastructures and further facilitates scaling to meet long-term management needs.

Abstract: A computer-implemented method for preserving individual backed-up files in accordance with legal-hold policies may include (1) providing at least one legal-hold policy that specifies the manner in which individual backed-up files that potentially relate to legal proceedings are to be preserved, (2) identifying at least one file that has been backed up, (3) identifying at least one legal purpose for preventing deletion of the backed-up file, (4) applying, in response to the identification of the legal purpose, the legal-hold policy to the backed-up file, and then (5) preserving the backed-up file in accordance with the legal-hold policy identified in the file metadata associated with the backed-up file. Various other systems, methods, and computer-readable media are also disclosed.

Abstract: Method and apparatus for evaluating a backup policy in a computer network is described. In one example, a control limit is established for each of a plurality of backup tasks in the backup policy based on a set of backup statistics. An aggregate requirement for the backup policy is computed by combining control limits for the plurality of backup tasks. The aggregate requirement is compared with aggregate capabilities of the computer network. The backup policy is evaluated based on the results of the comparison.

Abstract: Computer file storage, backup, restore and retrieval is disclosed. A method includes providing a restore file interface allowing a user to restore a plurality of files based on a plurality of filter options, the files stored on multiple local and/or remote storage devices, computing devices, servers, and clouds. A filter option selection is received from the user, and filter details may also be received from the user. An available file list may be prepared based on the filter option selection and, if received, the filter details. A user selection from the available file list may be received. The user selected files are retrieved from one or more appropriate storage devices, computing devices, servers, and clouds. The method may be performed by software executing on a computing device.

Abstract: Multitier deduplication can reduce the amount of bandwidth and storage resources used during deduplication. In certain embodiments, the system can determine if a data block is stored in a first archive data storage. If so, the system can skip the data block. If not, the system can determine if the data block is stored or identified in a second archive data storage. In various implementations, the first archive data storage can be local to the system and the second archive data storage can be a global archive that may be remote from the system. The system can create a map of a plurality of backups stored at the first archive enabling the system to quickly check multiple archives. The multitier data deduplication can filter out inactive data blocks during or before performing the deduplication process.

Abstract: A cluster network environment may comprise a plurality of nodes configured to perform various tasks, such as data I/O, storage, backup, etc. It may be advantageous to improve disaster recovery and reliability by creating backups that may be used to restore the cluster network environment and/or nodes therein. Accordingly, one or more techniques and/or systems are disclosed for restoring a cluster network environment and/or nodes therein. In particular, cluster configuration data, which may be stored in a healthy node or at a remote source, may be used to restore a node affected by an integrity loss. If the integrity loss affects the cluster network environment (e.g., a majority of healthy nodes are lost), then a new cluster network environment may be created from a healthy node or a restored healthy node. The creation of the new cluster network environment may be based at least in part on cluster configuration data.

Abstract: A method, system, and computer-readable medium for backing up and/or restoring user-specific settings for one or more IP telecommunications terminals. A backup process is initiated through a user interface of the IP telecommunications terminal. A file name and a backup file are supplied from the telecommunication terminal during a backup process. The backup file is transferred to an HTTP server and the backup file is transferred to the IP telecommunications terminal or other terminals in response to an HTTP GET message received from an IP telecommunications terminal connected to the HTTP server. Accordingly, multiple users can enjoy customized user-interfaces at multiple locations and across multiple platforms.

Abstract: Systems and methods of configuring electronic devices can include installing a first operating configuration on a first target device, running at least a first operational iteration of the first target device, saving at least a portion of a first file system resulting from the running of the at least first operational iteration of the first target device, and creating a first clone of the at least portion of the first file system at a separate host device. The first clone can be substantially identical to the corresponding at least portion of the first file system. The first clone can be evaluated via the host device. The host device can present the clone data in an integrated development environment such that a user can evaluate the clone data.

Abstract: For block level backup, a full image level backup is created of a file system from production storage at a production server to random access storage at a backup server. A mounted image is created from the full image that exposes a block level representation of the file system of the production server for read operations in a file level format. File enumeration is performed on the mounted image for files. Block level read operations are monitored while the files are being enumerated. During monitoring, blocks that are read for the read operations are marked as meta-data blocks. Blocks that are not marked as meta-data blocks are identified as data blocks. The data blocks are migrated to sequential storage, while leaving the meta-data blocks on the random access storage, wherein the data blocks form a backup image.

Abstract: Renamed directory handling for incremental file migration is described. A directory is stored in a storage device. An inode number associated with the directory in a directory table is identified. A determination is made whether the inode number equals an inode number associated with another directory in the directory table. At least one of a file and a subdirectory associated with the directory in the file system is stored into the directory in the storage device if the inode number equals the inode number associated with another directory in the directory table.

Abstract: The data transfer between data backup sites techniques include a method, a system, and/or a computer software product. In some embodiments of these techniques, the method includes determining backup data for transferring from a source data backup site to a destination data backup site based on a storage parameter, the backup data comprising data associated with a client device. The method further includes receiving a transfer parameter from the destination data backup site, the transfer parameter comprising a storage logical site available for data storage. The method further includes matching the determined backup data to the storage logical site based on a parameter selected from a group consisting of the storage parameter, and the transfer parameter. The method further includes scheduling a transfer of the determined backup data to the storage logical site based on a parameter selected from a group consisting of the storage parameter, the transfer parameter, and a schedule parameter.

Abstract: For block level backup, a full image level backup is created of a file system from production storage at a production server to random access storage at a backup server. A mounted image is created from the full image that exposes a block level representation of the file system of the production server for read operations in a file level format. File enumeration is performed on the mounted image for files. Block level read operations are monitored while the files are being enumerated. During monitoring, blocks that are read for the read operations are marked as meta-data blocks. Blocks that are not marked as meta-data blocks are identified as data blocks. The data blocks are migrated to sequential storage, while leaving the meta-data blocks on the random access storage, wherein the data blocks form a backup image.

Abstract: Pruning previously-allocated free blocks from a synthetic backup. In one example embodiment, a method of pruning previously-allocated free blocks from a synthetic backup includes identifying multiple sequential backups to be included in a synthetic backup, accessing a copy of a file system block allocation map (FSBAM) of the most recent of the multiple sequential backups that was stored with the most recent backup, identifying a set of blocks that includes the most recent block for each unique block position contained within the multiple sequential backups, pruning the set of blocks to exclude all blocks that are identified as being free in the FSBAM, storing the pruned set of blocks in the synthetic backup, and storing a copy of the FSBAM with the synthetic backup.

Abstract: This invention provides a computing system in which multiple remote copy destination sites exist and, even if a failure occurs in a copy source volume in a remote copy source site, it becomes possible in at least one remote copy destination site to establish backup in which data must be determined at a certain point in time. The computing system of this invention is characterized by, before the in-storage copy function performing in storage copy in the remote copy source site, setting the pair status of the remote copy destination volume in at least one storage system in multiple remote copy destination storage systems and the remote copy source volume to the mode for terminating remote copy and, after the in-storage copy is completed, changing the above-mentioned pair status to the mode for starting remote copy.

Abstract: A method, article of manufacture, and apparatus for efficiently backing up information are disclosed. In some embodiments, this comprises receiving data and analyzing the data. In some embodiments, the data may be manipulated. In some embodiments, the data may come from multiple sources. Chunk headers, data chunks and chunk maps are then created based on analyzing the data. Chunk headers store the data manipulation technique of the data chunk. In some embodiments, chunk headers store the size of the manipulated and un-manipulated data chunks. The chunk headers, data chunks and chunk maps are then organized into a datastream. The datastream is then stored in a storage device. In some embodiments, the received data may be discarded. In some embodiments, a chunk header is associated with a data chunk.

Abstract: PourOver is the process of replicating databases across clusters, in order to achieve real and/or near real-time database consistency between clusters (e.g., continually provide the ability to construct a consistent database on the alternate cluster that is up to date within a few minutes worth of transactions).

Abstract: A method and mobile terminal for mobile terminal environment snapshot management and backup recovery to define different working environment snapshots, and to back up and recover the environment snapshots according to the user's selection, so as to provide more flexible ways of using the mobile terminal.

Abstract: Methods, devices, and products are disclosed for recording media. An input is received via a user interface to record media. An entry is created in a recording schedule to record the media. The recording schedule is sent to a restoration server, such that the recording schedule is mirrored to the restoration server.

Abstract: Provided is a method of managing personal information in a communication system that provides a Converged Address Book (CAB) service, the method including generating, by a CAB user, a restoration request for restoring a personal document, which includes a document recognition value of a personal document stored in the CAB, current version information of the personal document, and property information instructing restoration of the personal document to a previous version of the current version, transmitting, by the CAB user, the restoration request to a server that manages the CAB through an arbitrary device, and receiving, by the CAB user, a response indicating that the personal document is restored to the previous version of the current version from the server through the arbitrary device.

Abstract: Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema.

Abstract: Improving file system reliability in storage mediums after a data corrupting event using file system journaling is described. In one embodiment, a method, which includes scanning beyond an active transactions region within the file system journal to locate additional valid transactions for replay to bring the storage medium into a consistent state; the scanning performed until an invalid transaction is reached.

Abstract: A computer-implemented method for achieving file-level data-protection operations using block-level technologies may include: 1) identifying an I/O operation directed to at least one data block on a primary storage system, 2) accessing a data-protection list that uniquely identifies files that are to be protected by a data-protection operation, 3) determining that the I/O operation is directed to at least a portion of at least one file identified on the data-protection list, and then, in response to the determination, 4) performing the data-protection operation on the I/O operation. Various additional methods, systems, and configured computer-readable media are also disclosed.

Abstract: Migrating data from an old storage device to a new storage device includes transferring the data from a first logical device on the old storage device to a second logical device on the new storage device, determining replication relationships for the first logical device, transferring the replication relationships; and transferring logical devices used for the replication relationships from the old storage device to the new storage device. The replication relationships may include a clone of the first logical device. Migrating data from an old storage device to a new storage device may also include suspending writes to the first logical storage device prior to transferring the data for the first logical storage device. The replication relationships may include at least one snapshot.

Abstract: A federated configuration management database includes a plurality of management data repositories, and a backup destination determination unit that determines backup destination management data repositories for backing up data overlapping among the plurality of management data repositories at specific management data repositories and that notifies each of the management data repositories of the data to be backed up.

Abstract: Methods and systems for managing storage of data in a cloud by receiving a request, wherein the request includes information to store data within a cloud, environment comprising a plurality of data storages coupled to each other over a network; routing the data to be stored within a specific location of storage within the cloud environment by checking for any regulatory compliance. Other embodiments are also disclosed.

Abstract: A system may present a document including a form. Forms content may be received into the form. The received forms content may be periodically and automatically saved to reduce the likelihood that received forms content is lost prior to form submission.

Abstract: An apparatus and computer-executed method for scheduling data backups may include accessing a specification for a backup job. The specification may include an identification of a data source, a start time and a target storage device to which backup data should be written. A first history of past backup jobs that specify the data source, and a second history of past backup jobs that specify the target storage device, may be identified. Using the first history, an expected size of the backup data may be computed. Using the second history, an expected rate at which the backup data may be written to the target storage device may be computed. Using the expected size, the expected rate and the start time, an expected completion time for the backup job may be computed.

Abstract: A disaster recovery technology capable of achieving the high-speed FO and correctly reading the logs even if the unit of logs written in the main site is large is provided. In the disaster recovery system comprising a main site and a sub-site, when the writing in units of a log block consisting of a plurality of log records is performed in the main site and the logs are applied in the sub-site, the log blocks are read from the sub-storage to verify the consistency, and it is determined whether the reading process conflicts with the writing process through the remote copy operation when reading the logs. Then, only the log blocks in which the reading process does not conflict with the writing process as a result of the determination are applied to the database. Thereby, the logs are applied in the sub-site independently to recover the database.

Abstract: A deduplication storage system and a backup application create a synthetic backup. Metadata instructions are provided to the deduplication storage system. Each of the metadata instructions specifies the data segment of an originating backup and a designated location of the data segment in the synthetic backup. Each of the metadata instructions are processed by locating those data sub-segments in the deduplication storage system specified by the data segment in each of the metadata instructions, and creating metadata references to each of the data sub-segments and adding the metadata references to metadata of the synthetic backup being created.

Abstract: Input backup data is deduplicated with data of a synthetic backup previously constructed by a deduplication storage system. A synthetic backup is constructed by processing metadata instructions provided by a backup application. Deduplication digests are calculated based on the data of the synthetic backup and the deduplication digests are stored in a digests index. When new backup data is processed, deduplication digests of the new data are calculated and searched in the digests index. Matching digests of previously constructed synthetic backups are located in the digests index. Each of the located matching digest references stored data are included in the synthetic backup, and the stored data is similar to the input backup data. Data matches are found in the input backup data and data in the synthetic backup.

Abstract: A method, including assigning, to each tier in a storage system comprising multiple tiers, a respective range of priority scores, and calculating a compression ratio for a file stored on one of the multiple tiers. Using the compression ratio, a priority score is calculated for the file, and the file is migrated to the tier whose assigned range of priority scores includes the calculated priority score.

Abstract: A supervisory control system includes a supervisory control target device and a supervisory control device. The supervisory control device is configured such that an attribute usage flag that indicates whether the supervisory control device supports any changes in the attributes due to adding of a function, and an attribute effectiveness flag which indicates whether the supervisory control target device supports the changes, are added, as information concerning the attributes that undergo the changes, to a definition of the instance which the supervisory control device retains. Further, the supervisory control device includes a control unit which, on a basis of data of the attribute usage flag and attribute effectiveness flag relating to the attributes undergoing the changes due to adding of a function, determines whether the supervisory control target device supports a new function or whether supervisory control based upon the new function is effective.

Abstract: An information retrieval system having: a client adapted for accessing a plurality of file sets stored on one of a plurality of file servers; a plurality of file servers configured to operate with a federated file system namespace; and a memory for storing re-direction information accessible by the client for identifying a request issued by the client for a file set at a first location in the namespace where the file set is located at a second, different location on one of the file servers and wherein the client in examining the re-direction information in the memory, re-directs the request to the second location in accordance with the re-direction information.

Abstract: The various embodiments herein include operate to identify, consolidate, and reduce redundant backup data storage. One embodiment includes storing data blocks and first signatures of data chunks of each stored data block, the first signature of each data chunk including a reference to a storage location of the data chunk within a stored data block, the stored data blocks including data blocks of previous and recent backup sessions. Some embodiments further include storing second signatures in a second signature repository, where the second signatures are calculated based on determined boundaries of the first signatures from previous backup sessions. At least one of the second signatures is calculated based on at least two first signatures, and in the range of 32 to 64 first signatures in some embodiments. Some embodiments may identify data chunks of the recent backup session present in the stored data blocks prior to the recent backup session.

Abstract: A cluster network environment may comprise a plurality of nodes configured to perform various tasks, such as data I/O, storage, backup, etc. It may be advantageous to improve disaster recovery and reliability by creating backups that may be used to restore the cluster network environment and/or nodes therein. Accordingly, one or more techniques and/or systems are disclosed for restoring a cluster network environment and/or nodes therein. In particular, cluster configuration data, which may be stored in a healthy node or at a remote source, may be used to restore a node affected by an integrity loss. If the integrity loss affects the cluster network environment (e.g., a majority of healthy nodes are lost), then a new cluster network environment may be created from a healthy node or a restored healthy node. The creation of the new cluster network environment may be based at least in part on cluster configuration data.

Abstract: A system and method for avoiding duplicate backups of data in a volume backup image. A cluster of nodes is coupled to a data storage medium configured to store data corresponding to a shared volume. A node receives a request for the backup of the shared volume. In response to this request, the node queries all other nodes in the cluster for identification of a subset of the shared volume data that should be excluded from the backup. The identified subset of the data may correspond to at least a file under control of a database application or other particular application. It may be known that this identified subset of the data will be backed up by a subsequent agent-based backup operation after the volume backup. In response to receiving all query responses, the node initiates a backup corresponding to the data in the shared volume excluding the identified subset of the data.

Abstract: Techniques are disclosed for quiescing a file system. One technique comprises freezing a file system, flushing a memory associated with the file system, and thawing the file system. One technique comprises receiving a request targeted to a file system and intercepting the request.

Abstract: A method of archiving a set of source tables in a database system. Each source table has a plurality of rows. Initially, a consistency point for the set of source tables is established. The database system creates a log record for each change (insert, modify, or delete) effected to a row of the source tables subsequent to the consistency point. Substantially all source table rows are copied to an archive (a data storage object that is external to the database system). Then the accumulated log records for the affected source tables are distilled and appended to the archive.

Abstract: Systems and methods are provided for storing and restoring digital data. In some implementations, a method is provided. The method includes identifying an encrypted source disk image to be included in a backup operation, the encrypted disk image being encrypted with a first key and generating an encrypted backup disk image, the encrypted backup disk image being encrypted with a second key protected with a randomly generated password. Other embodiments of this aspect include corresponding systems, apparatus, computer program products, and computer readable media.

Abstract: Described are systems and methods for storing a variable number of instances of data objects (e.g., 1, 2, 3, or up to N?1 instances, where N is the number of instances of the data object included in primary data) in secondary storage across a data storage network. In some examples, a system for storing a variable number of instances of data objects includes, one or more computing devices storing a set of data objects and multiple storage devices distinct from the one or more computing devices. Each of the multiple storage devices is configured to store at least a single instance of a data object. The system also includes a database configured to store information associated with the data objects. This information includes substantially unique identifiers for the data objects and, for each of the data objects, a number of instances of the data object stored on the multiple storage devices.

Abstract: A system for storing encrypted data comprises a processor and a memory. The processor is configured to receive an encrypted segment. The encrypted segment is determined by breaking a data stream, a data block, or a data file into one or more segments and encrypting each of the one or more segments. The processor is further configured to determine whether the encrypted segment has been previously stored, and in the event that the encrypted segment has not been previously stored, store the encrypted segment. The memory is coupled to the processor and configured to provide the processor with instructions.

Abstract: Provided is a computer system which is capable of backup operation with a minimum count of volumes in a remote copy environment when a disaster or the like causes a storage system to stop working normally. The computer system has a host computer, a first storage system, a second storage system, and a management computer. The first storage system contains a data volume which stores data requested by an application to be written. The second storage system contains a mirrored volume to which data stored in the data volume is copied. The computer system is characterized by being configured to receive an input of a policy about backup processing executed in backup volumes and set a configuration of the first storage system and a configuration of the second storage system under the received policy.

Abstract: Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema.