Patent application number | Description | Published |
20090249005 | SYSTEM AND METHOD FOR PROVIDING A BACKUP/RESTORE INTERFACE FOR THIRD PARTY HSM CLIENTS - A method for performing a backup of a stub object located on a file system managed by a hierarchical storage manager configured to migrate data objects from the file system to a migration storage pool is provided. The stub object includes information for recalling a migrated data object. The method comprises determining whether a backup copy of the migrated data object is stored in a backup storage pool if the backup is performed in an incremental backup operation; directing the hierarchical storage manager to recall the migrated data object to the file system if the backup copy of the migrated data object is not stored in the backup storage pool or if the backup is performed in a selective backup operation; creating the backup copy of the migrated data object if the migrated data object is recalled; storing the backup copy of the migrated data object in the backup storage pool if the migrated data object is recalled; creating a backup copy of the stub object if the migrated data object is not recalled; storing the backup copy of the stub object from the file system in the backup storage pool if the migrated data object is not recalled; and logically grouping the backup copy of the migrated data object with the backup copy of the stub object in the backup storage pool such that the backup copy of the migrated data object cannot be deleted from the backup storage pool unless the backup copy of the stub object does not exist in the backup storage pool if the migrated data object is not recalled. | 10-01-2009 |
20110016095 | Integrated Approach for Deduplicating Data in a Distributed Environment that Involves a Source and a Target - One aspect of the present invention includes a configuration of a storage management system that enables the performance of deduplication activities at both the client (source) and at the server (target) locations. The location of deduplication operations can then be optimized based on system conditions or predefined policies. In one embodiment, seamless switching of deduplication activities between the client and the server is enabled by utilizing uniform deduplication process algorithms and accessing the same deduplication index (containing information on the hashed data chunks). Additionally, any data transformations on the chunks are performed subsequent to identification of the data chunks. Accordingly, with use of this storage configuration, the storage system can find and utilize matching chunks generated with either client- or server-side deduplication. | 01-20-2011 |
20110040732 | APPROACH FOR SECURING DISTRIBUTED DEDUPLICATION SOFTWARE - The various embodiments of the present invention include techniques for securing the use of data deduplication activities occurring in a source-deduplicating storage management system. These techniques are intended to prevent fake data backup, target data contamination, and data spoofing attacks initiated by a source. In one embodiment, one technique includes limiting chunk querying to authorized users. Another technique provides detection of attacks and unauthorized access to keys within the target system. Additional techniques include the combination of validating the existence of data from the source by validating the data chunk, validating a data sample of the data chunk, or validating a hash value of the data chunk. A further embodiment involves the use of policies to provide authorization levels for chunk sharing and linking within the target. These techniques separately and in combination provide a comprehensive strategy to avoid unauthorized access to data within the target storage system. | 02-17-2011 |
20110047537 | Updating client node of computing system - During execution of an existing scheduling computer program on a client node, an update computer program and a self-describing automatic installation package are downloaded to the client node from a logical depot node implemented on an existing management server. Therefore, advantageously, no physical depot node or other additional computing device is needed for the client node to update itself. Execution of the update computer program is spawned on the client node from the existing scheduling computer program. As such, the update computer program inherits root access to the client node and security credentials to the management server from the scheduling computer program—advantageously, then, a user does not have to perform any laborious configuration of the client node in order to update the node. The client node ultimately updates itself using the self-describing automatic installation package, which includes all the information needed for the client node to update itself. | 02-24-2011 |
20110145196 | SYSTEM AND METHOD FOR PROVIDING A BACKUP/RESTORE INTERFACE FOR THIRD PARTY HSM CLIENTS - Performing a backup of a stub object located on a file system managed by a hierarchical storage manager configured to migrate data objects from the file system to a migration storage pool. The stub object includes information for recalling a migrated data object and is configured to determine whether a backup copy of the migrated data object is stored in a backup storage pool if the backup is performed in an incremental backup operation. The backup further includes directing the hierarchical storage manager to recall the migrated data object to the file system if the backup copy of the migrated data object is not stored in the backup storage pool or if the backup is performed in a selective backup operation. The backup additionally includes storing a backup copy of the migrated data object in the backup storage pool if the migrated data object is recalled. | 06-16-2011 |
20120089572 | AUTOMATED AND SELF-ADJUSTING DATA PROTECTION DRIVEN BY BUSINESS AND DATA ACTIVITY EVENTS - 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. | 04-12-2012 |
20130166511 | DETERMINING AN OVERALL ASSESSMENT OF A LIKELIHOOD OF A BACKUP SET RESULTING IN A SUCCESSFUL RESTORE - A point-in-time backup image is selected from a plurality of backup images of an image on a source computer system to be applied to the target computer system. A first assessment value is associated with an extent to which critical files and recovery metadata are included in the selected backup based on an include list of critical files and recovery metadata to include in the backup. A second assessment value comprises a backup status of the critical files and the recovery metadata. A third assessment value is indicative of an extent to which the selected backup satisfies requirements of a retention policy. A fourth assessment value is indicative of an extent to which computational resources and device drivers in the target computer system are compatible. An overall assessment value for the selected backup image is determined based on the determined first, second, third, and fourth assessment values. | 06-27-2013 |
20130166521 | DETERMINING WHETHER A SELECTED BACKUP SET SATISFIES A RETENTION POLICY - Provided are computer program product, system, and method for assessing a backup image comprising a backup of a source computer system to recover to a target computer system. A point-in-time backup image is selected from a plurality of backup images taken of an image on the source computer system, wherein the selected backup is to be applied to the target computer system. A determination is made from a plurality of retention policies applicable to files included in the source computer system a most restrictive retention policy. A determination is made as to whether the selected backup image satisfies the most restrictive retention policy. A retention status of the backup image is set based on whether the determined version of the selected backup satisfies the most restrictive retention policy. The retention status is presented for use in determining whether to use the selected backup image. | 06-27-2013 |