Abstract: A system, method, and medium for performing incremental backups of a Microsoft SQL server database. A snapshot of the database is created, and then a map identifying the changed extents is retrieved from the snapshot. The changed extents are then retrieved from the snapshot and stored in a backup storage device. For a restore operation, a full database backup file is written to a storage device and then the changed extents from a stored incremental backup file may be merged with the full backup file. Next, the database server is notified of the reconstructed file and then the reconstructed file is mounted by the database server as a live instance of the database.

Abstract: A data access layer operable to manage data requests from one or more software applications is provided. The data access layer includes a query processor, a metadata repository, a transaction data store, and an exception handler. The query processor manages transaction processing of data requests between applications, such as commercial-off-the-shelf software applications, and data stores. The metadata repository maintains a logical data model related to the data to provide instructions regarding handling the data requests from the application. The transaction data store maintains transaction information. A data warehouse may be updated along with the data stores by publication and subscription of data updates. When an error related to processing the one of the data requests is detected, the exception handler uses the transaction information to return any of the data to its previous state using compensating transactions.

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: Techniques for providing a differential backup from a storage image are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for providing a differential backup from a storage image comprising identifying one or more dirty blocks in a storage image, creating a differential backup data structure, and transmitting the one or more dirty blocks to a data management process utilizing the differential backup data structure to provide a differential backup.

Abstract: Various embodiments of a system and method for restoring a file are described herein. A previous version of the file may be split into segments and backed up to a server computer system. In response to a subsequent request to restore the file to the previous version, the current segments of the file may be compared to the backup segments stored on the server computer system. The segments that have changed may be retrieved from the server computer system and used to restore the corresponding segments of the current version of the file to their previous states. Segments that have not changed do not need to be transferred across the network from the server computer system. In further embodiments, one or more of the segments that have changed may be obtained locally from other files, thus further reducing the amount of data transferred across the network.

Abstract: The present disclosure provides a method and apparatus for backing up a subversion repository. In one embodiment, a method of backing up a subversion repository wherein a version attribute of a backup repository is preset and identifies a latest version of the backup repository, the method comprises: synchronizing the backup repository based on the version attribute of the backup repository; in an event of successful synchronization, updating the version attribute of the backup repository with an identification of a synchronized version; and in an event of unsuccessful synchronization, determining that a current version to be a non-synchronizable version, backing up an original repository by duplicating a copy of the original repository, and updating the version attribute of the backup repository with an identifier of the non-synchronizable version.

Abstract: Computer-implemented methods, systems, and computer-readable media for performing optimized backups of multiple volumes are disclosed. In one example, an exemplary method for performing such a task may comprise: 1) identifying a plurality of volumes, 2) prior to backing up the plurality of volumes, obtaining information that indicates that at least one volume within the plurality of volumes comprises at least one shared region of memory that is identical to a region of memory on at least one other volume within the plurality of volumes, and 3) when creating backups of the plurality of volumes, backing up each shared region of memory a single time so that the backups of the plurality of volumes share a single copy of each shared region of memory.

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 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: A method for fast incremental replication of a file system. The method includes, at a data storage level, tracking file system status for a plurality of files by using a data structure inside respective inodes for the plurality of files, and at a file system level, tracking file system status for a plurality of files by using a file system mask structure. For all files present in a backup, a catalogue of the file path name and inode number is maintained on a source file system. During incremental backup, a source file system data structure enumerating a plurality of modified inodes is consulted. For inodes that have not been marked as removed or created, the file system mask structure that tracks modified portions is consulted to obtain a file incremental change and inodes. The method further includes performing incremental backup using the inodes that have been modified and appended.

Abstract: Embodiments of the invention relate to creating an operating system and file system independent incremental data backup. A first data backup of a source system and second version of the data on the source system is received. A second data backup of the second version of the data is created by determining differences between the first data backup and the second version of the data. Each portion of the second version of the data that is the same as a portion of the first data backup is referenced in the second data backup. Each portion of the second version of the data that is different than all portions of the first data backup is included in the second data backup. The second data backup is appended to the first data backup to create an incremental data backup.

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: A method and a system for backing up terminal data are disclosed. The scheme is used for solving technical problems that existing ways for backing up terminal data have a low duplicating efficiency and resources are wasted seriously. The scheme creates a terminal index table to maintain data information in a terminal device; when the terminal device newly creates or modifies data contents, information of the index items in the terminal index table and corresponding data contents are sent to a network server; the network server also creates a server index table corresponding to the terminal index table, and the network server stores or deletes data contents of the terminal device according to information such as types and numbers of index items. The scheme can back up terminal data rapidly and simplifies the check procedure, thereby saving memory resources of the terminal device and improving backup efficiency.

Abstract: A method is disclosed for reliably updating a data group in a read-before-write data replication environment. The method reliably updates the data group by receiving an updated data group sent from a first storage medium to a second storage medium, comparing the updated data group with a previous data group previously existing on the second storage medium and writing the updated data group to the second storage medium. The read-before-write and differencing method disclosed maintain reliability by storing multiple copies of changes made to the second storage medium during and after the write process.

Abstract: A flashcopy of a source storage volume to a target storage volume is initiated. The content of the source storage volume is stored on the target storage volume in a space efficient manner. The space requirement of the stored content on the target storage volume is monitored. The flashcopy is terminated when the space requirement reaches a predetermined level. The stored content on the target storage volume is copied to a backup storage medium. A new flashcopy of the source storage volume is initiated.

Abstract: A flashcopy of a source storage volume to a target storage volume is initiated. The content of the source storage volume is stored on the target storage volume in a space efficient manner. The space requirement of the stored content on the target storage volume is monitored. The flashcopy is terminated when the space requirement reaches a predetermined level. The stored content on the target storage volume is copied to a backup storage medium. A new flashcopy of the source storage volume is initiated.

Abstract: A method for fast incremental replication of a file system. The method includes, at a data storage level, tracking file system status for a plurality of files by using a data structure inside respective inodes for the plurality of files, and at a file system level, tracking file system status for a plurality of files by using a file system mask structure. For all files present in a backup, a catalogue of the file path name and inode number is maintained on a source file system. During incremental backup, a source file system data structure enumerating a plurality of modified inodes is consulted. For inodes that have not been marked as removed or created, the file system mask structure that tracks modified portions is consulted to obtain a file incremental change and inodes. The method further includes performing incremental backup using the inodes that have been modified and appended.

Abstract: Reclaiming data space by rewriting metadata is disclosed. It is determined that fewer than all of the previous version data included in a write is required to be retained, e.g., beyond a continuous data protection window. A metadata record associated with the write is modified to point only to those blocks in which previous version data that is still required to be retained is stored. Other blocks become eligible for reclamation.

Abstract: Methods and computer readable media for restoring a database. In a method, a backup of a subset of a database is created, where the subset includes a filegroup and database metadata describing the filegroup. The database is then restored using the database subset. In a computer-readable medium, a first data field contains data representing a database subset having at least one of a plurality of filegroups. A second data field contains data representing database metadata that describes the filegroup. In another method, archived database metadata and an archived filegroup that is one of a plurality of filegroups is accessed, and the filegroup is brought online using the database metadata.

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: Methods and systems for allowing the backing-up of electronic data, its accessibility in times of need, and the ability to restore this data without denying user access to it while the restoration occurs. Also, the data may continue to be backed-up while it is being restored. One method allows for the removal of duplicated data from within the on or off-site copy and subsequent incremental on or off-site-site copies of the data. In this way, the amount of bandwidth and storage required may be reduced. For example, if there are two sets of files required to run two applications and some or all of these files are identical then only one copy need be made and sent and stored. This also applies where the on-site appliance is connected to more than one client server, such that data which is common to the client servers may only be copied once.

Abstract: A method for maintaining local and remote backups of a target file on a local device. The method includes identifying the target file to be backed up; modifying a first backup data structure on a local backup apparatus to backup the target file; and modifying a second backup data structure in a remote backup system to backup the target file.

Abstract: A method and mechanism for performing data backups in a computing system. A “delta” catalog is utilized for the maintenance of data backups. The delta catalog includes a backed up object table and an extent map. For a given backup, the backed up object table update stores entries which identify only those objects backed up during that backup. The backed up object table is further configured to store entries which identify objects which were deleted between the time of a prior backup procedure and a current backup procedure. The extent map is configured identify all objects present in the system at the time of a particular backup. The extent map identifies the objects which were present as one or more sequences of entries in the backed up object table.

Abstract: A method for maintaining incremental backups of a file. The method includes identifying a target file to be backed up. The method also includes comparing the target file to a one or more previously backed up files, in order to identify differences of the target file from a corresponding previously backed up file. The method also includes generating a delta version of the target file that records the identified differences from the previously backed up file.

Abstract: A computer system configured to store a plurality of files, and a data file, which includes inode and migration or purge information associated with the files. The computer system searches the data file to identify files that are candidates for migration or purge. A plurality of pathnames associated with the files is stored in the data file or a separate data file, and the computer system obtains the pathnames of candidate files from the data file (or separate data file). When candidate files are identified, their inodes are used to look up their pathnames in the plurality of pathnames. The data file may include information about whether a file has been modified and its time of last access. To determine whether a file is a candidate for migration, its entry in the data file is checked to determine whether it has been modified. If it has, it is identified as a migration candidate.

Abstract: In general, the invention relates to a method for migrating a source file system residing on a source server to a destination server. The method includes sending a first snapshot of the source file system from the source server to the destination server and creating, using the first snapshot, a migrated file system on the destination server. The method further includes sequentially sending, to the destination server, a set of snapshot deltas including modifications to the source file system, updating the migrated file system using the set of snapshot deltas, determining that a freeze threshold is exceeded, freezing the source file system, sending a final snapshot delta from the source server to the destination server, updating the migrated file system using the final snapshot delta, creating a file system husk referencing the migrated file system, and thawing the source file system and the migrated file system.

Abstract: An approach that allows for replicating data sets that have different attributes. A logical copy operation may not be possible from a source data set to a target data set due to differences between their respective attributes. The source data set may have obsolete attributes that prevent a logical copy to a target data set with supported attributes. The presented solution may involve allocating an intermediate data set with the same attributes as the source data set. The intermediate data set may be allocated with the same obsolete attributes as the source data set. The approach may also involve executing a logical copy operation from the source data set to the intermediate data set. A standard copy operation that reformats the data may be executed on the intermediate data set to the target data set.

Abstract: Persistent data of virtual machines are migrated between and across data stores using a method that provides for a bounded disk size, low performance overhead, arbitrarily low downtimes, atomic switch-over, and ability to build optimizations based around block level heuristics. The method includes the steps of copying the persistent data at the source data store to the destination data store, updating a bitmap data structure during the copying step to indicate which blocks of the persistent data have been modified during the copying step, identifying the blocks that have been modified during the copying step using the bitmap data structure, and copying the identified blocks to the destination data store. The method may further include the step of determining that the number of the identified blocks is below a predetermined threshold and suspending the virtual machine prior to the second copying step.

Abstract: Systems and methods are provided for storing and restoring digital data. In some implementations, a method is provided. The method includes identifying an item for segmented backup according to one or more specified criteria, and performing a first backup of the item including separating the item into a plurality of first parts prior to backing up the data and including separately storing each part. Other embodiments of this aspect include corresponding systems, apparatus, computer program products, and computer readable media.

Abstract: A hash-optimized backup system and method takes data blocks and generates a probabilistically unique digital fingerprint of the content of each data block using a substantially collision-free algorithm. The process compares the generated fingerprint to a database of stored fingerprints and, if the generated fingerprint matches a stored fingerprint, the data block is determined to already have been backed up, and therefore does not need to be backed up again. Only if the generated fingerprint does not match a stored fingerprint is the data block backed up, at which point the generated fingerprint is added to the database of stored fingerprints. Because the algorithm is substantially collision-free, there is no need to compare actual data content if there is a hash-value match. The process can also be used to audit software license compliance, inventory software, and detect computer-file tampering such as viruses and malware.

Abstract: The invention provides a process for performing automatic backups of a user's data contained in the local drives of at lest one computer of a local area network by means of a Residential Gateway, which is in turn connected to a provider's Backup Server.

Abstract: According to embodiments described herein, a backup server maintains backup data for a set of data, which includes data for a first block and a second block. Backup data for the first and second block include backup data for a plurality of versions of the first and second block. A distinct watermark is stored for each version of the first block and each version of the second block. In response to a request to perform a restoration operation on the set of data, a particular version of the first block and a particular version of the second block are selected to use in the restoration operation by comparing a restoration target with the watermarks of the version of the first block and second block. The selected version of the first block has a different watermark than the selected version of the second block.

Abstract: An incremental backup service may be configured to backup structured files and unstructured files on a client system. A filter driver 130 may be configured to monitor write operations on the client system and log changed cluster address information for structured files. The backup service may backup changed clusters of structured files to a backup storage device. For each of the unstructured files, the backup service may compare the file size to a threshold size. If the unstructured file is smaller than the threshold size, the backup service may backup the entire unstructured file. If the file size is larger than the threshold size, the backup service may determine the ratio of changed clusters to unchanged clusters. If the ratio is below a ratio threshold, the backup service may backup the changed clusters. If the ratio is above the ratio threshold, the backup service may backup the entire file.

Abstract: Provided are techniques for, in response to establishing each incremental virtual copy from a source to a target, creating a target change recording structure for the target. While performing destage to a source data block at the source, it is determined that there is at least one incremental virtual copy target for this source data block. For each incremental virtual copy relationship where the source data block is newer than the incremental virtual copy relationship and an indicator is set in a target inheritance structure on the target for a corresponding target data block, the source data block is copied to each corresponding target data block, and an indicator is set in each target change recording structure on each target for the target data block corresponding to the source data block being destaged.

Abstract: A method for using a change-recording feature to perform more effective backups includes generating an initial point-in-time copy of source data residing in a storage device. The method may then perform an initial backup of the initial point-in-time copy. As changes are made to the source data, the method may record changes made to the source data after the initial point-in-time copy is generated. These changes may be stored as incremental change data. At some point, the initial point-in-time copy may be updated using the incremental change data. In order to perform an incremental backup of the updated point-in-time copy, the method may query the incremental change data to determine which changes were used to update the point-in-time copy. The method may then perform an incremental backup of the updated point-in-time copy by backing up the changes designated in the incremental change data.

Abstract: A method and apparatus for providing point-in-time consistent backup images while reducing a computing overhead associated with copy-on-write operations for snapshot images is described. In one embodiment, the method comprises processing at least one data block that is inconsistent with a backup image; and updating the backup image with the at least one inconsistent data block from a snapshot image, wherein the snapshot image is created after a backup process, wherein the updated backup image is point in time consistent.

Abstract: Provided are techniques for, in response to establishing each incremental virtual copy from a source to a target, creating a target change recording structure for the target. While performing destage to a source data block at the source, it is determined that there is at least one incremental virtual copy target for this source data block. For each incremental virtual copy relationship where the source data block is newer than the incremental virtual copy relationship and an indicator is set in a target inheritance structure on the target for a corresponding target data block, the source data block is copied to each corresponding target data block, and an indicator is set in each target change recording structure on each target for the target data block corresponding to the source data block being destaged.

Abstract: A technique for restoring file systems by applying full and incremental backups together while streaming them from multiple devices provides a faster system restore from a full backup where incremental backups must also be applied. A first storage device streams the full backup while at least one second storage device streams at least one incremental backup. As files are detected in the incremental backup, they are written instead of the corresponding file in the full backup. Incremental backups can be pre-merged to reduce their number to one less than a number of storage devices available to stream the backups, so that the full backup can be streamed along with the pre-merged incremental backup(s) to restore the file system.

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: Systems and methods are provided for storing and restoring digital data. In some implementations, a method is provided. The method includes initiating a backup operation of data including a plurality of items, interrupting the backup operation, where interrupting occurs after a portion of the data has been completed, receiving an input to resume the backup operation, identifying a previously completed portion of the backup data, and performing a backup of a remaining uncompleted portion of the backup data. Other embodiments of this aspect include corresponding systems, apparatus, computer program products, and computer readable media.

Abstract: A management method and management apparatus that can prevent deterioration of response performance of an entire system is suggested.

Abstract: Described herein are a system and method for remote mirroring/copying data and metadata sets from a local node to a remote node that reduces the number of metadata sets that are mirrored. In some embodiments, the local node may coalesce metadata sets into metadata chains, each metadata chain comprising a grouping of two or more metadata sets. In some instances, a “representative” metadata set of a metadata chain may be selected for sending to the remote node for storing, wherein the other metadata sets of the metadata chain are not sent to the remote node. In these embodiments, the selected metadata set may represent all the metadata sets in the chain and be the only metadata set in the chain that is transmitted and stored to the remote node. As such, the network congestion between the local and remote nodes may be reduced.

Abstract: Tracking files which have been processed by a backup/restore operation. A request to perform a backup/restore operation for files on a target computer may be received at the target computer. The request may be received from a server computer. Information regarding which files on the target computer have been processed by the backup/restore operation may be maintained by the target computer. The information may be configured to be used for restart of the backup/restore operation at a requested file. Maintaining the information may include storing file identifiers into a data structure on the target computer corresponding to files that have processed by the backup/restore operation.

Abstract: A hash-optimized backup system and method takes data blocks and generates a probabilistically unique digital fingerprint of the content of each data block using a substantially collision-free algorithm. The process compares the generated fingerprint to a database of stored fingerprints and, if the generated fingerprint matches a stored fingerprint, the data block is determined to already have been backed up, and therefore does not need to be backed up again. Only if the generated fingerprint does not match a stored fingerprint is the data block backed up, at which point the generated fingerprint is added to the database of stored fingerprints. Because the algorithm is substantially collision-free, there is no need to compare actual data content if there is a hash-value match. The process can also be used to audit software license compliance, inventory software, and detect computer-file tampering such as viruses and malware.

Abstract: A technique for restoring file systems by applying full and incremental backups together while streaming them from multiple devices provides a faster system restore from a full backup where incremental backups must also be applied. A first storage device streams the full backup while at least one second storage device streams at least one incremental backup. As files are detected in the incremental backup, they are written instead of the corresponding file in the full backup. Incremental backups can be pre-merged to reduce their number to one less than a number of storage devices available to stream the backups, so that the full backup can be streamed along with the pre-merged incremental backup(s) to restore the file system.

Abstract: Provided are systems and methods for use in data archiving. In one arrangement, compression techniques are provided wherein an earlier version of a data set (e.g., file folder, etc) is utilized as a dictionary of a compression engine to compress a subsequent version of the data set. This compression identifies changes between data sets and allows for storing these differences without duplicating many common portions of the data sets. For a given version of a data set, new information is stored along with metadata used to reconstruct the version from each individual segment saved at different points in time. In this regard, the earlier data set and one or more references to stored segments of a subsequent data set may be utilized to reconstruct the subsequent data set.

Abstract: Provided are a method, system, and article of manufacture for maintaining information of a relationship of target volumes comprising logical copies of a source volume. Information is maintained on a source volume having a plurality of data units and a plurality of target volumes created at different points-in-time maintaining a logical copy of the data units in the source volume for the different points-in-time. A source downstream pointer is generated for each data unit in the source volume to point to a corresponding data unit in a first target volume. For each target volume data unit whose data is maintained in the source volume or another one of the target volumes, a first upstream pointer is generated indicating one of the source and target volumes from which the target volume data unit inherits data.

Abstract: A method is disclosed for establishing an agency relationship to perform delegated computing tasks. The method provides for initiation of the agency relationship, establishment of credentials to perform a delegated computing task, and performance of the delegated computing task. Benefits of establishing an agency relationship in a computing environment include improved security, efficiency, and reliability in performing delegated computing tasks.

Abstract: Query processing statistics are logged in a multi-database system containing a plurality of system databases. A plurality of query log entries generated using information regarding the execution of a plurality of queries are temporarily stored in a database query log (DBQL). The information is received from a plurality of system databases. Each query log entry is generated using information regarding execution of one query by the plurality of system databases. Each query log entry includes a field identifying a system database that was the source of the information in that entry. An express request is created upon occurrence of a triggering event. The express request contains a subset of the query log entries temporarily stored in the DBQL cache. The created express request is transmitted to a plurality of system databases and the contents of the transmitted express request are stored in each of plurality of system databases to which it was transmitted.