Abstract: 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.

Abstract: Provided are a computer program product, system, and method for using a metadata image of a file system and archive instance to restore files in the file system. A metadata image of the file system for a point-in-time backup as of a point-in-time includes information on files and directories in the file system as of the point-in-time and an archive instance including a copy of database records in the backup database for the files in the point-in-time backup. A restore request is received. A file representation is created of each file to restore in the directory structure of the file system from the metadata image, wherein at least one of the created file representations indicates that the file is stored off-line and has an external identifier used to access information on the file in the database records in the archive instance for the point-in-time backup.

Abstract: Provided are a computer program product, system, and method for using a metadata image of a file system and archive instance to backup files in the file system. A point-in-time backup is performed of files in the file system as of a point-in-time. A metadata image includes information on files and directories in the file system as of the point-in-time. Files in the point-in-time backup are backed up to a backup storage. A backup database has records on the files backed-up from the file system. Each record in the backup database has a unique identifier for each backed-up file and a location of the backed-up file in the backup storage. An archive instance is generated including a copy of the database records for the files in the point-in-time backup. The metadata image and the archive instance are associated for the point-in-time backup.

Abstract: Provided are a computer program product, system, and method for encrypting data objects to back-up to a server. A client private key is intended to be maintained only by the client. A data object of chunks to store at the server is generated. A first portion of the chunks in the data object is encrypted with the client private key and the first portion of the chunks in the data object encrypted with the client private key are sent to the server to store. A second portion of the chunks in the data object not encrypted with the client private key are sent to the server to store.

Abstract: Provided are a computer program product, system, and method for encrypting data objects to back-up to a server. A client private key is intended to be maintained only by the client. A data object of chunks to store at the server is generated. A first portion of the chunks in the data object is encrypted with the client private key and the first portion of the chunks in the data object encrypted with the client private key are sent to the server to store. A second portion of the chunks in the data object not encrypted with the client private key are sent to the server to store.

Abstract: Provided are a computer program product, system, and method for using a metadata image of a file system and archive instance to backup files in the file system. A point-in-time backup is performed of files in the file system as of a point-in-time. A metadata image includes information on files and directories in the file system as of the point-in-time. Files in the point-in-time backup are backed up to a backup storage. A backup database has records on the files backed-up from the file system. Each record in the backup database has a unique identifier for each backed-up file and a location of the backed-up file in the backup storage. An archive instance is generated including a copy of the database records for the files in the point-in-time backup. The metadata image and the archive instance are associated for the point-in-time backup.

Abstract: Provided are a computer program product, system, and method for using a metadata image of a file system and archive instance to restore files in the file system. A metadata image of the file system for a point-in-time backup as of a point-in-time includes information on files and directories in the file system as of the point-in-time and an archive instance including a copy of database records in the backup database for the files in the point-in-time backup. A restore request is received. A file representation is created of each file to restore in the directory structure of the file system from the metadata image, wherein at least one of the created file representations indicates that the file is stored off-line and has an external identifier used to access information on the file in the database records in the archive instance for the point-in-time backup.

Abstract: 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.

Abstract: Various embodiments are provided for facilitation of data retention using logical objects. Following an operation creating a redundant copy of the data performed on a scheduled interval, a logical object containing a number of managed file versions, represented by a number of member objects for a recovery point, is created. The logical object is assigned a policy of a data retention policy construct associated with the recovery point. The logical object is adapted for reassignment between policies of the data retention policy construct associated with various recovery points. During the reassignment, the plurality of member objects representing the plurality of managed file versions are logically retained instead of performing a data copy operation to associate the plurality of managed file versions with another recovery point.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Provided are a computer program product, system, and method for encrypting data objects to back-up to a server. A client private key is intended to be maintained only by the client. A data object of chunks to store at the server is generated. A first portion of the chunks in the data object is encrypted with the client private key and the first portion of the chunks in the data object encrypted with the client private key are sent to the server to store. A second portion of the chunks in the data object not encrypted with the client private key are sent to the server to store.

Abstract: Provided are a computer program product, system, and method for encrypting data objects to back-up to a server. A client private key is intended to be maintained only by the client. A data object of chunks to store at the server is generated. A first portion of the chunks in the data object is encrypted with the client private key and the first portion of the chunks in the data object encrypted with the client private key are sent to the server to store. A second portion of the chunks in the data object not encrypted with the client private key are sent to the server to store.

Abstract: An angiographic injector system and a method of controllably delivering medical fluid to a patient from an angiographic injector system are disclosed. A multiple processor control system is used to actively control the injection process and to monitor sensed functions of the system. The multiple processors provide dual redundancy safety circuits for critical control functions such as syringe motor drive speed and current. A motor/servo-amplifier nested control function is also disclosed. A unique method and apparatus are disclosed for establishing injection parameter default values just prior to an injection procedure that are based on physiological values of the patient to be treated. The injector system uses an interactive display panel that presents sequenced set-up screens to the user and which enables the user to select injection procedures, parameters and other modes of operation directly through the interactive panel.

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: Various embodiments are provided for facilitation of data retention using logical objects. Following an operation creating a redundant copy of the data performed on a scheduled interval, a logical object containing a number of managed file versions, represented by a number of member objects for a recovery point, is created. The logical object is assigned a policy of a data retention policy construct associated with the recovery point. The logical object is adapted for reassignment between policies of the data retention policy construct associated with various recovery points. During the reassignment, the plurality of member objects representing the plurality of managed file versions are logically retained instead of performing a data copy operation to associate the plurality of managed file versions with another recovery point.

Abstract: Various embodiments are provided for facilitation of data retention using logical objects. Following an operation creating a redundant copy of the data performed on a scheduled interval, a logical object containing a number of managed file versions, represented by a number of member objects for a recovery point, is created. The logical object is assigned a policy of a data retention policy construct associated with the recovery point. The logical object is adapted for reassignment between policies of the data retention policy construct associated with various recovery points. During the reassignment, the plurality of member objects representing the plurality of managed file versions are logically retained instead of performing a data copy operation to associate the plurality of managed file versions with another recovery point.

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.