Abstract: In a method used for maximizing performance of a storage system, saturation points of the storage system for I/O requests of different types and sizes are identified. Normalized tokens are determined based on the saturation points. Unique numbers of normalized tokens are associated with the I/O requests of different types and sizes. A number of normalized tokens for a queue depth limit of a storage device is determined. From the queue depth limit, normalized tokens are allocated to each node in the storage device. I/O requests are processed according to the allocations of normalized tokens.

Abstract: In a method used for maximizing performance of a storage system, saturation points of the storage system for I/O requests of different types and sizes are identified. Normalized tokens are determined based on the saturation points. Unique numbers of normalized tokens are associated with the I/O requests of different types and sizes. A number of normalized tokens for a queue depth limit of a storage device is determined. From the queue depth limit, normalized tokens are allocated to each node in the storage device. I/O requests are processed according to the allocations of normalized tokens.

Abstract: In a method used for maximizing performance of a storage system, saturation points of the storage system for I/O requests of different types and sizes are identified. Normalized tokens are determined based on the saturation points. Unique numbers of normalized tokens are associated with the I/O requests of different types and sizes. A number of normalized tokens for a queue depth limit of a storage device is determined. From the queue depth limit, normalized tokens are allocated to each node in the storage device. I/O requests are processed according to the allocations of normalized tokens.

Abstract: In one embodiment, a method includes receiving an input/output (I/O) request for data that starts or ends at a location other than a physical sector boundary of the device. The method further includes reading, starting at a first physical sector boundary before a beginning location specified in the I/O request and ending at a second physical sector boundary after an ending location specified in the request.

Abstract: In one embodiment, a method includes receiving an input/output (I/O) request for data that starts or ends at a location other than a physical sector boundary of the device. The method further includes reading, starting at a first physical sector boundary before a beginning location specified in the I/O request and ending at a second physical sector boundary after an ending location specified in the request.

Abstract: A system and method for updating file archive bits in a data storage arrangement that performs snapshot backup operations is provided. The snapshot container is a read-write container that can receive archive bit backup write data from the file system and associated file system. Snapshot container files in which archive bits have been cleared, indicating a backup, are checked. These files' counterparts in the snapshotted container are located. Where the snapshotted files have had archive bits cleared, they are passed over. Where snapshotted files have set archive bits, the file data parameters for respective snapshot and snapshotted files are compared. If the file data parameters therebetween are the same, then the respective snapshotted file archive bit is cleared confirming backup status. Where the file data parameters differ, the set archive bit for the snapshotted file is retained, indicating un-backed-up current version in the snapshotted container.

Abstract: A system and method for enabling a snapshot container generated in a copy-on-write backup process to function in the presence of a data-handling system (e.g. a file system) that writes data to the backup disk is provided. The snapshot container, which is read-by and written-to by the system backup application is configured as a read-write container with associated driver. The write data from the backup application is provided to, and stored in the snapshot information container that also receives and stores data from the original read-write container in the manner of a backing store container. Data in the snapshot information container is selectively mapped container as a source, or to backup information container as a source, denoting a backup application write, based upon a bit-map associated with the snapshot driver arrangement.