Article ID: 325334 - View products that this article applies to.
This article was previously published under Q325334
With striping, you can back up a database to different disks either to increase backup throughput or to distribute space usage across different disks. However, the files may or may not be evenly distributed.
SQL Server 7.0If SQL Server stripes physical devices that have different input/output (I/O) throughputs, SQL Server optimizes for speed. This means that faster devices receive more backup data that is written to disk than the slower device in the same period of time. As a result of this behavior, faster disks may run out of space and you receive following error message:
The following example demonstrates this issue. The example is based on the following hardware configuration:
BackupMedium::ReportIoError: write failure on backup device 'device name'. Operating system error 112(There is not enough space on the disk.).
Scenario 1If you run the following backup command
file Testdb_1.bak may be significantly larger than Testdb_2.bak when the backup is complete.
Scenario 2If you run the following backup command
Files Testdb_1.bak, Testdb_2.bak, and Testdb_3.bak are similar in size, while files Testdb_4.bak, Testdb_5.bak, and Testdb_6.bak are similar in size. However, files Testdb_1.bak, Testdb_2.bak, and Testdb_3.bak may be significantly larger than files Testdb_4.bak, Testdb_5.bak, and Testdb_6.bak.
In both scenarios, drive C may run out of space and the error message may appear before the backup process is complete if drive C has limited space. If you must have files evenly distributed on both disks, you must use disks that have comparable I/O throughputs.
SQL Server 2000In SQL Server 2000, regardless of the I/O throughput differences, SQL Server tries to distribute the backup data evenly to the devices. In the two scenarios that are listed in the "SQL Server 7.0" section, all files are similar in size when the backup process is complete. In this case, the slower disk may become a backup bottleneck in terms of performance. If increasing performance is your primary goal, you must avoid using the slow disk in striping and use disks with comparable throughputs instead.