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: 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: 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: A method and system for requesting, cross-referencing, extracting and storing historical records of data backup activity by using a software component that interfaces to a plurality of data backup software devices is disclosed. In the first aspect, a method of storing automated request-for-historical records of data backup activity schedules is disclosed. In the second aspect, a method for invoking requests through a component that interfaces to a plurality of data backup software devices is disclosed. In the third aspect, a method for receiving historical records of data backup activity from said component is disclosed. In a fourth aspect, a method for making alterations to said historical records of data backup activity is disclosed. In a fifth aspect, a method for inserting said historical records of data backup activity into a data table located in an open, relational database is disclosed.

Abstract: A checkpointing fault tolerance network architecture enables a backup computer system to be remotely located from a primary computer system. An intermediary computer system is situated between the primary computer system and the backup computer system to manage the transmission of checkpoint information to the backup VM in an efficient manner. The intermediary computer system is networked to the primary VM through a first connection and is networked to the backup VM through a second connection. The intermediary computer system identifies updated data corresponding to memory pages that have been less frequently modified by the primary VM and transmits such updated data to the backup VM through the first connection. In such manner, the intermediary computer system holds back updated data corresponding to more frequently modified memory pages, since such memory pages may be more likely to be updated again in the future.

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

Abstract: Improved backup and storage operations are disclosed for virtual computing environments using a backup proxy server to perform storage operations on one or more virtual machine disks. The proxy server can include a module that intercepts application programming interface (API) calls, for writing backup data to a first location, prior to the data arriving on the proxy disk. During the intercept process, the data can be compressed in memory pages of the proxy server and redirected to an alternative backup disk location. The proxy server can also include a differential engine that identifies changes to the virtual machine disk at the block level since the last full backup. The differential engine can advantageously leverage memory pages of the proxy server to compare differences between signatures of blocks of the last full backup with signatures of new blocks. Subsequently, only blocks with non-matching signatures are processed for backup.

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 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: An embodiment of a method of restoring data begins with a step of restoring point-in-time data from a local copy. The method concludes with a step of restoring at least a portion of an incremental difference between the point-in-time data and a desired state of the data from a remote mirror.

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: A method and apparatus for performing granular restoration from machine images stored on sequential backup media is disclosed. In one embodiment, the method for performing granular restoration from machine images stored on sequential backup media includes processing at least one machine image file to identify at least one database file and at least one data object that is arranged within the at least one database file and generating mapping information regarding the at least one data object within the at least one machine image file, wherein the at least one machine image is to be stored on the sequential backup media.

Abstract: A data processing system has a plurality of storage systems. In this system, data replication is performed at high speed and efficiency while maintaining data integrity. In addition, when failure has occurred in a configuration element, the time necessary to resume the data replication is reduced. In accordance with an instruction from first host computer, updating of replication-target data and creation of a journal are performed in a storage system A, and updating of replication data and creation of a journal are performed in a storage system B. A storage system C retrieves a journal from the storage system B in asynchronization with the updating, and performs updating of replication data. When failure has occurred in the storage system B, a journal-retrieving end is altered to the storage system, and the replication data is updated in accordance with the retrieved journal.

Abstract: A data staging system comprises an inbound staging area, data conversion logic, and a graphical user interface. The inbound staging area is configured to receive data records from a data sending computer system, including being configured to receive different versions of the same record. The inbound staging area stores the different versions of the same record pending further processing. The data conversion logic is configured to perform the further processing. The further processing reduces the number of different versions of the same record. The graphical user interface logic is configured to generate a display showing the records in the inbound staging area.

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.

Abstract: A cluster manager is configured to manage a plurality of copies of a mid-tier database as a mid-tier database cluster. The cluster manager may concurrently manage a backend database system. The cluster manager is configured to monitor for and react to failures of mid-tier database nodes. The cluster manager may react to a mid-tier database failure by, for example, assigning a new active node, creating a new standby node, creating new copies of the mid-tier databases, implementing new replication or backup schemes, reassigning the node's virtual address to another node, or relocating applications that were directly linked to the mid-tier database to another host. Each node or an associated agent may configure the cluster manager to behave in this fashion during initialization, based on common cluster configuration information. Each copy of the mid-tier database may be, for example, a memory resident database. Thus, a node must reload the entire database into memory to recover a copy of the database.

Abstract: The present invention provides systems and methods for extending media retention. Methods are provided in which a set of aging preferences are obtained. Data elements of a data set stored on storage media are evaluated against the aging preferences to determine whether each of the data elements satisfy the aging preferences. Each of the data elements that is determined to satisfy the aging preferences is aged. Aging can include freeing a portion of storage media, previously used to store a data element, for other storage usage.

Abstract: According to the present invention, policies are prepared for a plurality of resources residing in a computer system comprising a storage system for copying data from a copy source volume to a copy target volume, and an evaluation is carried out for an evaluation-target resource of the plurality of resources for determining whether or not to execute a predefined action based on the policy of this evaluation-target resource. A policy corresponding to a resource related to copying of the plurality of resources is determined based on a time period related to the copying.

Abstract: A history of locations of tenant data is maintained. The tenant data comprises data that is currently being used by the tenant and the corresponding backup data. When a tenant's data is changed from one location to another, a location and a time is stored within the history that may be accessed to determine a location of the tenant's data at a specified time. Different operations trigger a storing of a location/time within the history. Generally, an operation that changes a location of the tenant's data triggers the storing of the location within the history (e.g. upgrade of farm, move of tenant, adding a tenant, load balancing of the data, and the like). When tenant data is needed for an operation (e.g. restore), the history may be accessed to determine the location of the data.

Abstract: When performing asynchronous remote copying, whether or not a disaster has occurred at a main site is judged at a remote site; and if the disaster has occurred, recovery processing is immediately started at the remote site. When asynchronous remote copying is performed between a controller and a controller, the controller transfers remote copy target data in a storage apparatus and command information via a remote copy channel to the controller; and after receiving the remote copy target data, the controller stores the remote copy target data in a storage apparatus; and if the controller fails to receive the command information within a set time period, the controller judges that a disaster has occurred, and then outputs the judgment result to a backup center server; and the backup center server executes recovery processing based on data in the storage apparatus when the disaster has occurred.

Abstract: Backup and restoration of computer information. In one example embodiment, a method includes modifying a volume boot record of a restore volume to a first state in which at least a portion of the restore volume becomes inaccessible to a standard file system, writing restore data to the inaccessible portion of the restore volume while the volume boot record is in the first state, and restoring the volume boot record to a second state in which the inaccessible portion of the restore volume becomes accessible to the standard file system.

Abstract: Indexing functionality can be shifted to one or more backup servers in a backup system. In one implementation, a backup server can receive one or more data backups from one or more production servers. The backup server can then build or create one or more indexes at the backup server, which correspond to the contents of the one or more data backups. In one implementation, one or more management agents can also identify any appropriate components that might be needed to read the backup data at the backup server pursuant to building the one or more indexes. In either case, the one or more indexes can be used for a wide range of purposes, such as to manage data usage quotas at the one or more production servers, as well as to retrieve data from the backup server based on specific file requests.

Abstract: Projects of any type require sophisticated management software programs. In reality, these management software programs are provided by various vendors and for different professional fields. For example, scheduling programs for construction professionals, blue print programs for drafting professionals, accounting programs for cost-control professionals. In addition, there are numerous other unofficial and official documents generated by managers of different levels for reporting or track-record-keeping purposes using popular word processing programs and spread-sheet programs. Documents generated by different software programs can only be viewed under the programs they are generated under or compatible programs. This poses a problem in that there is a lack of organized control resulting in difficulty in locating and viewing documents in a timely manner.

Abstract: Subsequent to a storage operation performed on the source instance by a source component, a synchronization message is sent to a replicated component for the replicated instance. The synchronization message is stored locally in a persistent storage location associated with the source component along with an indicator representative of a time the storage operation was performed. Pursuant to receipt of the synchronization message by the replicated component, the replicated component is updated to a dirty state to indicate a lack of full synchronization between the source and replicated instances. Receipt of the synchronization message is acknowledged by the replicated component by sending a dirty state acknowledgement. If, during a subsequent recovery process, the dirty state is not yet cleared, the replicated component is deemed ineligible for participation in a full restoration operation.

Abstract: Method and apparatus for capturing data from a backup image are described. In one example, the backup image is mounted on a volume in a host computer. The backup image includes files, a first portion of which include an operating system. A database in the backup image is mounted. The database stores configuration data for use by the operating system. The configuration data includes file paths referencing at least one of the files. The file paths are re-mapped based on the volume. The data is captured from the backup image using the database as mounted and the file paths as re-mapped.

Abstract: This disclosure describes systems and methods for programmatically determining whether to perform full or partial backups. In some implementations, functionality is provided for intelligently escalating to a full backup based on one or more user-supplied escalation parameters. The escalation parameters can include a threshold of data change between backup files, which if exceeded, can result in escalation to a full backup. The escalation parameters can also include time parameters, computing resource consumption parameters, and other features that can govern full backup escalation. Additional features of the systems and methods described herein can include automatic adjustment of escalation parameters, multi-leveled backup set validation, and intelligent backup file cleanup.

Abstract: Data is processed by receiving a list of one or more file system elements in a level of a file system or a portion thereof. The list is sorted based at least in part on whether a file system element is a file or a directory. A sorted list is obtained. The file system elements in the level are backed up according to the order of the sorted list.

Abstract: A backup method for a computer system network avoids generating hashes from data that may be inaccurate due to network errors affords verification of source data written to backup media includes reading at a network client a portion of the source data from a source storage volume and generating a hash of the source data at the client. The source data and hash are transmitted to a backup server and written to the backup media. The hash is written to the backup media is associated with the backup data corresponding to the source data from which the hash was generated. Verification of the backup data is performed by reading the backup data from the backup media, generating a hash from the backup data read, and comparing that hash with the hash originally stored on the backup media.

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 technique for implementing policy-aware backup and restore capability in a tiered storage system. If a data set's contents are backed up from the tiered storage system to a backup storage system, metadata for the data set may also be backed up. Prior to the data set being restored from the backup storage system to the tiered storage system, the backed up metadata is restored and processed to determine a tier among the tiered storage pools to which the data set will be restored.

Abstract: A data processing system has a plurality of storage systems. In this system, data replication is performed at high speed and efficiency while maintaining data integrity. In addition, when failure has occurred in a configuration element, the time necessary to resume the data replication is reduced. In accordance with an instruction from first host computer, updating of replication-target data and creation of a journal are performed in a storage system A, and updating of replication data and creation of a journal are performed in a storage system B. A storage system C retrieves a journal from the storage system B in asynchronization with the updating, and performs updating of replication data. When failure has occurred in the storage system B, a journal-retrieving end is altered to the storage system, and the replication data is updated in accordance with the retrieved journal.

Abstract: A computer creates a full backup of a target volume by copying sectors of the target volume. Incremental backups are created by copying modified sectors that have changed since a preceding backup. Public accesses to a restore volume are prevented by modifying a volume boot record (VBR) of the restore volume to prevent file systems from recognizing the restore volume or by filtering public accesses while allowing private block accesses to the restore volume. Sector data are copied from the backup files to the restore volume while the public accesses are being prevented. The restore can begin, using previously created backup files, while the backup is still in process creating new incremental backups for the target volume. The restore volume is finalized after restoring the full or any number of incremental backups by restoring the VBR to indicate the restore volume is valid or stopping the filtering of public accesses.

Abstract: A backup method that uses snapshot delta views to create backups of a data collection is provided. The method comprises taking a first snapshot of the data collection, in response to determining that a previous snapshot used to create a backup does not exist; creating a backup of the data collection using the first snapshot, in response to determining that the previous snapshot does not exist; recording that the first snapshot was used as a source for the creation of a backup; and taking a second snapshot of the data collection, in response to determining that the previous snapshot that was used as a source for a backup does exist.

Abstract: A server auditing process that stores only a single up-to-date data record along with the differences relative to previous changes in the record that allow the user to move “backward in time” to recreate previous values. The auditing feature introduces a baseline database table and a difference database table for each existing database table. The baseline table stores the most recent auditing data and the differences table complements the baseline table by storing pairs in the form of attribute name and previous value. By applying difference rows to baseline data, the user is able to recreate the data as it existed at any given timestamp and at a minimal storage cost. The architecture minimizes the impact of auditing on system performance by employing an asynchronous priority queue so that task processing is deferred until the system has adequate resources and other work is not affected.

Abstract: Techniques for adjusting the frequency of data backups and initiating event-driven backups in a storage system are disclosed herein. In one embodiment, a self-adjusting backup frequency, known as a “Change Rate Objective,” is defined to conduct or delay backups for one or more volumes in the storage system on the basis of an associated policy value. The Change Rate Objective may be tied to one or more business or data activity events, such as the amount and type of data changes since a last backup. The storage system may also be tailored to conduct or delay full or incremental backups on the basis of a Change Rate Objective that measures whether a full or incremental or differential backup is more appropriate. Various data or system failures, or data or business events may also be used to adjust the retention periods of continuous data protection (CDP) data and delay a rollup of CDP data.

Abstract: Image-based data restoration restores an entire image of a volume or selective files. A restore engine receives a request to restore data from a backup image that includes a plurality of data blocks and metadata describing attributes of the data blocks. In response to the request, the restore engine determines a restore mode. If it is determined to be a logical restore mode, the restore engine restores a file by retrieving the metadata associated with the file and the data blocks that are pointed to by the metadata. If it is determined to be an image restore mode, the restore engine restores an entire image of the volume by using the data blocks in the backup image without using the metadata.

Abstract: Methods and apparatus, including computer program products, for managing data. The technique includes defining a secondary data set in a primary data set, linking the secondary data set to state information of the primary data set, transmitting the secondary data set to an external entity, receiving a modified secondary data set from the external entity and linking the modified secondary data set to a version of the primary data set stored with reference to state the information. The state information defines the state of the primary data set at the time the secondary data set is defined. The link between the modified secondary data set and the primary data set allows access by a user of a modified primary data set if the primary data set has changed with reference to the state information.

Abstract: Incremental checkpoint, for use in data replication, track the changes made to a file system after a point in time at which the incremental checkpoint is created. Data replication techniques using the incremental checkpoints may include taking a regular checkpoint of the file system and creating the first time full copy on remote node using the regular checkpoint. Changes made to the file system are then tracked in an incremental checkpoint that are stored on the remote node. The processes of taking the incremental checkpoint and storing the incremental checkpoint are iteratively performed. The first time fully copy and the incremental checkpoints may then be used for data replication, backup, continuous data protection (CDP), or the like.

Abstract: Architecture for replicating a database through log shipping. A replication service replicates data using one or more new internal application program interfaces (APIs), a replay configuration API which abstracts configuration information for each destination (or target) instance. APIs for log file management as part of the replication process are provided for opening communications for log shipping, tracking success of log shipping and closing out log shipping communications. Log shipping APIs are also provided for log truncation control. A ship control object is provided as a base class which includes an API for other components of the replication service to operate on log files when the log files are placed into a log directory. The ship control API is utilized by the replication service and for interaction with storage system log files.

Abstract: Disclosed is a method and apparatus relating generally to erasure techniques for emulating a streamed data format for non tape media capable of being used with a data storage arrangement to generate replenished user data space. The data storage arrangement comprises a host computer and a storage system in communication with the host computer, the storage system comprising at least one random access storage medium. The random access storage medium is capable of receiving data by streaming protocol and storing the data emulated in a contiguous format. The data comprises at least one data file which further comprise a plurality of records wherein each of the records comprise user data and meta data. A deletion algorithm is adapted to issue at least one deletion command capable of deleting at least one portion of the data stored on the medium up to at least a last segment of the data to create replenished storage space.

Abstract: Described are techniques and mechanisms for media data storage management. Briefly stated, a media control component monitors the usage patterns of media files on a local device. Any media files whose usage pattern falls below a given threshold is identified as a trim candidate. The media control component trims those trim candidates by eliminating data (content) from the media files. The data is eliminated from the latter portion of the media file so that the trimmed media file will continue to render properly when initially launched. If the trimmed media file is launched, the media control component retrieves the eliminated data from a content server on which is stored a library of media files.

Abstract: In certain embodiments, a tiered storage system is disclosed that provides for failover protection during data backup operations. The system can provide for an index, or catalog, for identifying and enabling restoration of backup data located on a storage device. The system further maintains a set of transaction logs generated by media agent modules that identify metadata with respect to individual data chunks of a backup file on the storage device. A copy of the catalog and transaction logs can be stored at a location accessible by each of the media agent modules. In this manner, in case of a failure of one media agent module during backup, the transaction logs and existing catalog can be used by a second media agent module to resume the backup operation without requiring a restart of the backup process.

Abstract: A priority restore agent in a data storage system generates a priority restore data set for a client computer system or device by identifying a set of active data sets and/or a set of key data sets within client system data generated by the client computer system. The priority restore agent looks at or processes file system attributes for the client system data and compares these attributes with predefined restore parameters. The restore parameters may indicate that any file that has been accessed, modified, or created within a particular period of time be included in the priority restore data set. The key data sets may be identified in a set of automated restore rules. A data protection application within the data storage system can restore data in the priority restore data set onto the client computer system after a disaster or system crash.

Abstract: Various methods and systems for using email to convey backup and restore data are disclosed. One method involves: receiving a request to perform a backup system operation; generating an email that includes data and metadata (which is associated with the data); and sending the email to an email address associated with a backup system component. The request can be a backup request, in which case the data includes data to be backed up, and the backup system component is a backup server. Alternatively, the request can be receiving a restore request. In this scenario, the data includes data to be restored, and the backup system component is a backup client.

Abstract: A method of intelligently copying recovery points from a primary storage device to a secondary storage device is presented. The decision on how to copy the recovery points depends upon the backup copy policy as well as the availability of previous backups on the secondary storage device.

Abstract: The invention relates to computer readable medium storing program code which when executed on a computer causes the computer to perform a method for creating a quick recovery volume of a primary data set used by a first computer in a backup storage system, which includes identifying a snapshot image of the primary data set generated by a snapshot application, creating the quick recovery volume of the primary data set from the snapshot image of the primary data set and controlling transfer of data from the first computer to an archival storage unit. In one embodiment, the invention provides a method for creating a quick recovery volume of a primary data set that includes creating a snapshot image of the primary data set and creating a quick recovery volume of the primary data set from the snapshot image of the primary data set. In another embodiment, the invention provides a user interface screen enabling browser style browsing and recovery of quick recovery volumes and snapshot images.

Abstract: A method and system for generating and restoring a backup image are disclosed. A server receives a request, which includes a backup path, to generate a backup image. The server generates a backup image offset map that indicates a relative location where a file is stored in the backup image before file data has been written to the backup image. The server stores the backup image offset map in a portion of the backup image on a storage device. The backup image offset map comprises an array having a number of elements equal to a number of inodes on a file system that hosts a backup path, an element of the array representing an inode on the file system, and indicates the relative location where a file that is associated with a number of the inode is stored in the backup image.

Abstract: Creating a synthetic database backup using binary logs. A full backup of a database may be stored, followed by one or more incremental backups. The one or more incremental backups may include first binary log files. A first synthetic differential backup may be created using the first binary log files. Creating the first synthetic differential backup may include translating the first binary log files into a first plurality of SQL statements. The first plurality of SQL statements may be executable to recreate the changes in the database since the full backup. Translating each of the first binary log files into the first plurality of SQL statements may be performed before performing a recovery process to decrease recovery time.

Abstract: A method and system for efficient space management for single-instance-storage volumes is provided. A backup module storing data within a collection of containers according to access locality and retention time of the data, wherein the retention time defines an amount of time the data is stored within the collection of containers before deletion of the data, and the access locality comprises an order in which the data is to be accessed is further provided. A compaction module compacting the stored data by selecting at least two containers among the collection of containers, wherein the selection is performed using a predetermined criteria that includes access locality and retention time of the data is also provided. The compaction module distributes the data among the at least two containers. The compaction criteria creates an imbalance among the containers to create more empty, full, or nearly full containers.