Abstract: An example of the present techniques receives a volume provisioning request in a storage management system. The volume provisioning request corresponds to a service level agreement (SLA) for a volume and includes a number of performance parameters for the volume. A database of historical performance data for each of a number of arrays in a storage pool is accessed. A fitness score for each array is calculated based on the performance parameters. A federation structure including a number of arrays in the storage pool to provision the volume is generated based on the fitness scores of the arrays. The volume is then provisioned based, at least in part, on the federation structure.

Abstract: Provided are a method, system, and article of manufacture wherein a primary controller receives a request from a primary host to set reservations on a primary storage and a secondary storage, wherein the primary host, the primary controller and the primary storage are at a first site, and wherein a secondary host, a secondary controller, and the secondary storage are at a second site. The primary controller sets a first reservation on the secondary storage via a storage area network coupling the secondary storage to the primary controller, wherein the setting of the first reservation causes the secondary storage to be read only for a secondary host. The primary controller sets a second reservation on the primary storage, wherein the setting of the second reservation allows the primary host to perform read and write operations on the primary storage.

Abstract: A system and method of error recovery for backup applications that utilizes error recovery logic provided in the storage controller itself are provided. With the system and method, error recovery logic is provided in the storage controller for generating and maintaining error recovery logs for one or more backup operations of one or more backup applications running on one or more host systems. The backup applications may utilize an established set of commands/API function calls to invoke the error recovery logic on the storage controller. At the initiation of the backup operation, the storage controller assigns a unique identifier to the backup operation and returns this identifier to the backup application. The backup application may then use this identifier to initiate error recovery operations or commit changes made during the backup operation via the storage controller. Thus, the storage controller offloads the burden of error recovery from the backup applications.

Abstract: Provided are a method, system, and article of manufacture wherein a primary controller receives a request from a primary host to set reservations on a primary storage and a secondary storage, wherein the primary host, the primary controller and the primary storage are at a first site, and wherein a secondary host, a secondary controller, and the secondary storage are at a second site. The primary controller sets a first reservation on the secondary storage via a storage area network coupling the secondary storage to the primary controller, wherein the setting of the first reservation causes the secondary storage to be read only for a secondary host. The primary controller sets a second reservation on the primary storage, wherein the setting of the second reservation allows the primary host to perform read and write operations on the primary storage.

Abstract: A system and method of error recovery for backup applications that utilizes error recovery logic provided in the storage controller itself are provided. With the system and method, error recovery logic is provided in the storage controller for generating and maintaining error recovery logs for one or more backup operations of one or more backup applications running on one or more host systems. The backup applications may utilize an established set of commands/API function calls to invoke the error recovery logic on the storage controller. At the initiation of the backup operation, the storage controller assigns a unique identifier to the backup operation and returns this identifier to the backup application. The backup application may then use this identifier to initiate error recovery operations or commit changes made during the backup operation via the storage controller. Thus, the storage controller offloads the burden of error recovery from the backup applications.