Backup Compression in SQL2008 performs very well and it is easy to use. You could either use “With Compression” along with the “Backup” command or simply enable default backup compression through sp_configure by setting ‘backup compression default’ value to 1. It is very convenient for backups of large databases in our customer lab environment.
· Test to find the ideal number of backup devices to use
First database we backed up is 1.27TB in size with 12 database files (on 12 LUNs). The second database is 2.95TB in size with 76 database files across 45 LUNs. We tested backup using different number of backup files (8, 16, 26 and 32), and 16 backup devices demonstrate best performance in our environment.
The following table shows database sizes, backup execution times and total size of all backup files. The database is not page or row compressed and the backup devices are local.
|Database Size||Exec Time||Backup Size||Avg. MB/sec||# Core|
· Backup over the network (8 x 1G Ethernet, 2 files per NIC)
- Jumbo Frame helps – we used 9014.
- Set Buffer Count = 512
The backup volumes are a pair of 500GB SATA drives 7200 RPM configured as RAID 1 each. connected via 4 controllers in 16 disk shelfs.
In our test, 1.27TB is backed up over the network in 24.5 minutes (862MB/sec).
Backup operation is IO intensive. Backup compression writes less pages to disk comparing to uncompressed backup, as long as you system is not bottlenecked on CPU, backup compression should executes faster than backup without compression.
Hope you will enjoy this new SQL feature and getting even better backup performance.
Lindsey Allen, Thomas Grohser