Compaq ProLiant 1000 Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 43

Chart 8 - Concurrent Dumps of Multiple Databases to 35/70 DLT Tape Drives

Get Compaq ProLiant 1000 PDF manuals and user guides View all Compaq ProLiant 1000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 43 highlights

Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 43 The final point above deserves further discussion. When a single database is being dumped, the dump process begins reading the data at the start of the database file and continues reading successive pages that are stored more or less contiguously on disk (even in an array). When a second database residing on the same disk or disk array begins, the disk heads will have to go back and forth between the two locations, increasing seek time and slowing performance. Thus, the only way to retain steady, sequential read paths is to isolate each database on its own volume. The only exception to this principal, is for dumping two databases residing on the same mirrored (RAID-1) volume. In this case, the Smart-2 SCSI Array controller can effectively keep the reads sequential on each set of mirrored drives by using one set to satisfy read requirements of the first dump and the other set for the second dump (known as "split seeks"). For the tests involved in this section, the system was configured as follows: A second Smart-2/P Array controller was installed in the system. A four spindle RAID-5 array was created on each SCSI-port of both controllers, providing four logical drive volumes. Four identical databases were then created, one on each drive volume. The four 35/70-GB DLT Tape drives configured across two Wide-Ultra SCSI controllers (2 drives per controller) were retained from the previous tests. Thus there will be one tape drive to receive data from each of the four databases. The controllers that will be sending data (the Smart-2 SCSI) are on the system's primary PCI bus, and the controllers that will be receiving data (the Wide-Ultra SCSI) are on the second PCI bus. This configuration is important to ensure load balancing so that PCI bus saturation will not be encountered. Using the above configuration, we performed dumps of from one to four databases simultaneously, each to its own 35/70 DLT drive, while monitoring the usual hardware usage percentages. The results are shown below: Chart 8 - Concurrent Dumps of Multiple Databases to 35/70 DLT Tape Drives The benefits of the concurrent dump strategy are quickly realized as additional databases are dumped. When dumping one database to a single drive the throughput is 18.6 GB/hr, and when dumping two 1997 Compaq Computer Corporation, All Rights Reserved Doc No 444A/0797

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
Compaq Backup and Recovery for Microsoft SQL Server 6.x
Page
43
1997 Compaq Computer Corporation, All Rights Reserved
Doc No 444A/0797
The final point above deserves further discussion.
When a single database is being dumped, the dump
process begins reading the data at the start of the database file and continues reading successive pages
that are stored more or less contiguously on disk (even in an array).
When a second database residing
on the same disk or disk array begins, the disk heads will have to go back and forth between the two
locations, increasing seek time and slowing performance.
Thus, the only way to retain steady,
sequential read paths is to
isolate each database on its own volume
. The only exception to this
principal, is for dumping two databases residing on the same mirrored (RAID-1) volume.
In this case,
the Smart-2 SCSI Array controller can effectively keep the reads sequential on each set of mirrored
drives by using one set to satisfy read requirements of the first dump and the other set for the second
dump (known as “split seeks”).
For the tests involved in this section, the system was configured as follows:
A second Smart-2/P Array controller was installed in the system.
A four spindle RAID-5 array
was created on each SCSI-port of both controllers, providing four logical drive volumes.
Four
identical databases were then created, one on each drive volume.
The four 35/70-GB DLT Tape drives configured across two Wide-Ultra SCSI controllers (2 drives
per controller) were retained from the previous tests.
Thus there will be one tape drive to receive
data from each of the four databases.
The controllers that will be sending data (the Smart-2 SCSI) are on the system’s primary PCI bus,
and the controllers that will be receiving data (the Wide-Ultra SCSI) are on the second PCI bus.
This configuration is important to ensure load balancing so that PCI bus saturation will not be
encountered.
Using the above configuration, we performed dumps of from one to four databases simultaneously,
each to its own 35/70 DLT drive, while monitoring the usual hardware usage percentages.
The results
are shown below:
Chart 8 - Concurrent Dumps of Multiple Databases to 35/70 DLT Tape Drives
The benefits of the concurrent dump strategy are quickly realized as additional databases are dumped.
When dumping one database to a single drive the throughput is 18.6 GB/hr, and when dumping two