Abstract: A program, method and system are disclosed for managing a snapshot backup restore through a hardware snapshot interface, i.e. a hardware-driven snapshot restore, based upon a software-driven snapshot backup, e.g. created with software such as volume shadow copy service (VSS). When conventional hardware-driven snapshot restores are performed using a snapshot backup that was created using the VSS-based software such as copy services, data access issues can arise, due to the operating system assigning of a new disk signature to the disk being restored. This problem can be overcome by temporarily storing the original disk signature and then overwriting the new, incorrect disk signature after initializing the restore. This can ensure that the operating system identifies the source LUNs (and accordingly, the drive letter and mount points of the disk) using the same disk signature as before the restore.

Abstract: A program, method and system are disclosed for managing a snapshot backup restore through a hardware snapshot interface, i.e. a hardware-driven snapshot restore, based upon a software-driven snapshot backup, e.g. created with software such as volume shadow copy service (VSS). When conventional hardware-driven snapshot restores are performed using a snapshot backup that was created using the VSS-based software such as copy services, data access issues can arise, due to the operating system assigning of a new disk signature to the disk being restored. This problem can be overcome by temporarily storing the original disk signature and then overwriting the new, incorrect disk signature after initializing the restore. This can ensure that the operating system identifies the source LUNs (and accordingly, the drive letter and mount points of the disk) using the same disk signature as before the restore.

Abstract: A setup module saves disk signatures identifying cluster disks for at least one source volume to a device distinct from the cluster disks. A copy module copies data with a volume-level restore from at least one snapshot volume to the at least one source volume, overwriting the disk signatures identifying the cluster disks so that the cluster disks cannot be accessed. A reset module rewrites the saved disk signatures to the cluster disks.

Abstract: An apparatus, system, and method are disclosed for restoring cluster server data at a volume level. A setup module opens at least one source volume of a cluster server for a volume-level restore, flushes each buffer for the at least one source volume, closes the at least one source volume, disables file system checks for the cluster disks, saves disk signatures of the cluster disks, and disables device-level checks for the cluster disks. A copy module copies data with a volume-level restore from the at least one snapshot volume to the at least one source volume. A reset module rewrites the saved disk signatures to the cluster disks, re-enables the device-level checks for the cluster disks, and resets at least one volume attribute on the at least one source volume.

Abstract: Systems and methods are disclosed for providing a federated backup involving the coordination and synchronization of backup and restore operations among a plurality of hosts to ensure data consistency. A master node (backup host) acts as the initiator, coordinator, controller, and possibly as primary console for the entire backup and restore operation. All other worker application hosts and/or worker backup hosts operate as worker nodes and perform various backup and restore steps as directed by the master node. Centralized error handling aborts or recovers the entire backup operation in the event of failure on any one node. In addition, a logical view of the data is provided such that the backup can be managed as one entity, while backing up the data of each node. The backup workload may also be distributed to any other dedicated worker backup hosts (nodes) in order to minimize the impact to the production environment.

Abstract: Provided are a system, an article of manufacture, and a computer program product, wherein a first set of backup data is stored in a first computational device and a second set of backup data is stored in a second computational device. Metadata corresponding to the first set of backup data is maintained in the second computational device. The first set of backup data is reconciled with the second set of backup data based on the metadata.

Abstract: A root user identifier of a computing system is disabled. Thereafter, and in response to determining that a problem with the computing system requires root privileges to the computing system to solve, a code patch for installation on the computing system is received from a third party. The code patch is installed on the computing system, resulting in a user identifier temporarily having the root privileges to the computing system. The user identifier is different than the root user identifier is. A password for the user identifier is provided to the third party to permit the third party to solve the problem with the computing system using the root privileges, via the user identifier temporarily having the root privileges to the computing system. The code patch is computer code installable on the computing system.

Abstract: Systems and methods for managing a backup process of a database are disclosed. Typically, one or more backup logical unit numbers (LUNs) are identified in a backup management file from one or more available LUNs identified in a universe file are allocated. The backup management file comprises a plurality of data containers, each data container specifying a subset of the one or more backup LUNs capable of backing up a database comprising one or more used database LUNs. One of the plurality of the data containers are allocated for a current backup of the database as indicated in the backup management file. The backup management file is checked and updated as necessary so that the one or more backup LUNs remain available as indicated in the universe file.

Abstract: Provided are techniques for storing local versions of a data set. A first number that indicates how many local versions of the data set are to be stored in local storage given an amount of available local storage is received. It is determined whether a second number that indicates a total number of local versions of the data set that the local storage is capable of storing exceeds the first number. In response to determining that the second number exceeds the first number, the amount of local storage that is capable of storing the first number of local versions of the data set is used.

Abstract: The present invention provides a computer implemented method, data processing system, and computer program product to restore an encrypted file. A computer receives a command to restore an encrypted file, wherein the encrypted file was previously backed up. The computer identifies a user associated with the encrypted file. The computer looks up a first keystore of the user based on the user, the first keystore having an active private key. The computer determines that a public key of the encrypted file fails to match an active public key of the first keystore. The computer restores a second keystore of the user to form a restored private key, wherein the second keystore was previously backed up. The computer responsive to a determination that the public key of the encrypted file fails to match the active public key of the first keystore, decrypts the encrypted file encryption key based on the restored private key to form a file encryption key.

Abstract: Provided are a system, an article of manufacture, and a computer program product, wherein a first set of backup data is stored in a first computational device and a second set of backup data is stored in a second computational device. Metadata corresponding to the first set of backup data is maintained in the second computational device. The first set of backup data is reconciled with the second set of backup data based on the metadata.

Abstract: A first set of backup data is stored in a first computational device and a second set of backup data is stored in a second computational device. Metadata corresponding to the first set of backup data is maintained in the second computational device. The first set of backup data is reconciled with the second set of backup data based on the metadata.

Abstract: A program, method and system are disclosed for managing a snapshot backup restore through a hardware snapshot interface, i.e. a hardware-driven snapshot restore, based upon a software-driven snapshot backup, e.g. created with software such as volume shadow copy service (VSS). When conventional hardware-driven snapshot restores are performed using a snapshot backup that was created using the VSS-based software such as copy services, data access issues can arise, due to the operating system assigning of a new disk signature to the disk being restored. This problem can be overcome by temporarily storing the original disk signature and then overwriting the new, incorrect disk signature after initializing the restore. This can ensure that the operating system identifies the source LUNs (and accordingly, the drive letter and mount points of the disk) using the same disk signature as before the restore.

Abstract: An apparatus, system, and method are disclosed for restoring cluster server data at a volume level. A setup module opens at least one source volume of a cluster server for a volume-level restore, flushes each buffer for the at least one source volume, closes the at least one source volume, disables file system checks for the cluster disks, saves disk signatures of the cluster disks, and disables device-level checks for the cluster disks. A copy module copies data with a volume-level restore from the at least one snapshot volume to the at least one source volume. A reset module rewrites the saved disk signatures to the cluster disks, re-enables the device-level checks for the cluster disks, and resets at least one volume attribute on the at least one source volume.

Abstract: Capability test programs are generated implementing the capability test test cases for the components, wherein component developers use the capability test programs to test components during the development and coding of the components. Documentation is generated describing component abstract test cases incorporating information on capability test test cases. Component test programs are generated implementing the component abstract test cases for the components and utilizing capability test programs, wherein each component test program tests one component for at least one test case specified in the component abstract test case documentation for the component. The capability test programs and component test programs are stored in a shared repository. A software development program is deployed to enable the developers and testers to execute groups of component test programs in the shared repository to test the components during different phases of the development of the software product.

Abstract: A distributed backup system for a networked computer system is disclosed such that when a data backup is created, a client backup application stores backup restore information as part of the backup data which can be interpreted by the backup application and/or backup server to direct how the remainder of the backup data needs to be restored. The backup restore information may be stored (cached) in staging directory, e.g. on the local computer system. During a backup restore process, the backup application first whether the backup restore information exist in the staging directory before requesting them from the backup server. The backup restore information may be stored in a unique location within the staging directory, e.g. a timestamp-labeled subdirectory. The backup application reconciles the staging directory to eliminate backup restore information for backup data that no longer exists on the backup server.

Abstract: An apparatus, system, and method are disclosed for differential data backup using snapshot on-write data. A snapshot module maintains an on-write data structure that captures a point-in-time or temporal instance of a data set by tracking modifications to data blocks of a data set. A backup module copies the data set to a backup data storage device as a full data set backup. In addition, the backup module copies each modified data block indicated by the on-write data structure and a differential time stamp to the backup data storage device as a differential data set backup. The full data set backup and one or more differential data set backups form a plurality of temporal instances of the data set. In one embodiment, a restore module recovers a selected instance of the data set responsive to receiving a restore command by copying the full data set backup to a target data storage device.

Abstract: Systems and methods are disclosed for providing a federated backup involving the coordination and synchronization of backup and restore operations among a plurality of hosts to ensure data consistency. A master node (backup host) acts as the initiator, coordinator, controller, and possibly as primary console for the entire backup and restore operation. All other worker application hosts and/or worker backup hosts operate as worker nodes and perform various backup and restore steps as directed by the master node. Centralized error handling aborts or recovers the entire backup operation in the event of failure on any one node. In addition, a logical view of the data is provided such that the backup can be managed as one entity, while backing up the data of each node. The backup workload may also be distributed to any other dedicated worker backup hosts (nodes) in order to minimize the impact to the production environment.

Abstract: A mechanism using special properties on data containers of a snapshot backup allows the snapshot backup used for a tape backup to be excluded from the policy enforcement. In addition, reconciliation of a local (client-side) backup repository and server repository bypass the snapshot backup to ensure its validity for the backup duration. If the snapshot backup is to be retained, the data container may be brought back under the domain of policy management. The policy clause may stipulate that a snapshot cannot be recycled while it is being used for a tape backup, allowing tape backups to be prioritized over subsequent snapshot backups.

Abstract: Systems and methods for managing a backup process of a database are disclosed. Typically, one or more backup logical unit numbers (LUNs) are identified in a backup management file from one or more available LUNs identified in a universe file are allocated. The backup management file comprises a plurality of data containers, each data container specifying a subset of the one or more backup LUNs capable of backing up a database comprising one or more used database LUNs. One of the plurality of the data containers are allocated for a current backup of the database as indicated in the backup management file. The backup management file is checked and updated as necessary so that the one or more backup LUNs remain available as indicated in the universe file.