Compaq 219700-001 - ProLiant - 1500 White Paper
  1. Manuals
  2. Brands
  3. Compaq Manuals
  4. Server
  5. 219700-001 - ProLiant - 1500
  6. White paper
Compaq 219700-001 - ProLiant - 1500 White Paper

Compaq 219700-001 - ProLiant - 1500 White Paper

Compaq backup and recovery for microsoft sql server 6.x
Hide thumbs Also See for 219700-001 - ProLiant - 1500:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual, Configuration Manual
:KLWH3DSHU
3UHSDUHG%\
'DWDEDVH(QJLQHHULQJ
&RPSDT&RPSXWHU&RUSRUDWLRQ
-XO\
¤
1997 Compaq Computer Corporation, All Rights Reserved
Doc No 444A/0797

Advertisement

Table of Contents
loading

Related Manuals for Compaq 219700-001 - ProLiant - 1500

Summary of Contents for Compaq 219700-001 - ProLiant - 1500

  • Page 1 :KLWH3DSHU 3UHSDUHG%\ 'DWDEDVH(QJLQHHULQJ &RPSDT&RPSXWHU&RUSRUDWLRQ -XO\ ¤ 1997 Compaq Computer Corporation, All Rights Reserved Doc No 444A/0797...
  • Page 2 This test is not a determination of product quality or correctness, nor does it ensure compliance with any federal, state or local requirements. Compaq does not warrant products other than its own strictly as stated in Compaq product warranties.
  • Page 3 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 3 7DEOHRI&RQWHQWV ¤ 1997 Compaq Computer Corporation, All Rights Reserved Doc No 444A/0797...
  • Page 4 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 4...

  • Page 5: Table Of Contents

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 5 /LVWRI&KDUWV Chart 1 - Data Compression Ratios and Performance..................18 Chart 2 - Throughput Variance with Block Size & Data Patterns..............21 Chart 3 - Dump to Single Tape Device ......................34 Chart 4 - Null Device Dumps : Reading Data from Disk Arrays ...............
  • Page 6 The purpose of this document is to provide the reader with information on backup and recovery technology available for and specific to the Compaq ProLiant family of servers and Microsoft SQL Server for Windows NT. It is our desire to deliver the best technical information possible on a specific topic in a timely manner and in a highly usable format.
  • Page 7 The information contained in this documents updates and adds to the information contained in the paper Compaq Backup and Recovery with Microsoft SQL Server, which was released in Oct. 1994. The additions in this paper serve mainly to inform the reader on new backup related software and hardware technologies that have appeared on the market since then.
  • Page 8 With fault tolerance implemented on the entire drive subsystem, a drive failure will not interrupt any operations and will not cause any data loss. With the Compaq SMART and SMART-2 Array controllers and the hot-pluggable drive subsystem, a failed drive can be replaced and fault tolerance restored without taking the system off-line.
  • Page 9 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 9 With disk fault tolerance installed on the transaction log volume only, and with systematic database and transaction log dumps, your data is also safe. If you have a full database dump and subsequent transaction log dumps, you can easily restore your data in case of a failed data drive.
  • Page 10 Off-line backups can take advantage of verifying the data (backup with verify) on the tape after backup. This guarantees data integrity on the tape. With Cheyenne ARCserve for Windows NT and Compaq TurboDAT AutoLoader or Compaq DLT Library, you can group tapes together to increase the capacity. Groups of tapes appear to the host as one continuous tape with an increased capacity, and the next tape in the group is automatically and transparently loaded once one tape is filled up.
  • Page 11 SQL Server-based backups in greater detail later in this document. SQL Server currently does not support the autoloading and/or cataloging capabilities of the Compaq TurboDAT AutoLoader or DLT Library. However, third party software that supports these products along with a database ‘backup agent’ for SQL Server can be used.
  • Page 12 2) isolating I/O generated by the dump activity from the transaction log and database I/O activity minimizes performance impact. Database Backup Agents are available from Compaq or Cheyenne for use with Cheyenne ARCserve, and are covered later in this paper.
  • Page 13 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 13 The recovery operation consists of restoring your data from the backup media. You will use the same utility to restore your data as you used to back it up - if you used a file based backup utility, you will use the same utility to restore your data, and if you used SQL Server to dump the database or the transaction log, you will use SQL Server to load your data.
  • Page 14 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 14 restore will fail, and you will have to use a raw data import/export tool such as SQL Transfer Manager or BCP. Even these utilities have certain limitations. See the Administrators Guide for details.
  • Page 15 In this paper we have chosen to evaluate the Compaq DLT (Digital Linear Technology) family of tape drives, which includes the 10/20-GB DLT, 15/30-GB DLT, and 35/70-GB DLT tape drives. Other, older tape technologies such as the QIC (Quarter Inch Cartridge) and DAT (Digital Audio Tape) drives are also supported by Compaq but are not discussed here.
  • Page 16 DLT Tape IIIXT (15.0-GB) DLT Tape IV (35.0-GB) The Compaq 10/20 and 15/30 DLT drives are available with either an internal or external standard SCSI (8-bit) interface. These drives can however, be connected to a Fast-Wide SCSI-2 controller with the appropriate cable, although half the bandwidth of the Wide SCSI-2 bus will remain unused. On EISA systems such as the Proliant 4500 using a Fast SCSI-2 or a Fast-Wide SCSI-2/E controller will yield the same performance.
  • Page 17 This driver should soon be available from Compaq as well. This data was incorporated from the earlier paper ‘Compaq Backup and Recovery with Microsoft SQL Server’ (1994). Although these tests did not use the same hardware and software that the rest of our document addresses, they still serve to illustrate the effects of compression.

  • Page 18: Chart 1 - Data Compression Ratios And Performance

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 18 initialized and never used pages only, and yields very high compression ratios and very high backup throughput. The “Repeated Patterns” column represents a data set with a high percentage of repeated data and unused space, thus relatively high compression ratios and high performance.
  • Page 19 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 19 tape drive writes out the current data, stops and waits for the data stream to start again. Once it does, the tape drive has to search for the end of data, reposition its write heads, and continue writing.
  • Page 20 SQL Server versions prior to 6.0 would use a hard-coded block size of 512 bytes, which had serious performance repercussions in the case of DLT tape drives. As a result, Compaq recommends that DLT drives not be used with these earlier (i.e: version 4.21x) SQL Servers. 512 byte blocks work fine for DAT and QIC...

  • Page 21: Chart 2 - Throughput Variance With Block Size & Data Patterns

    SQL Server versions prior to 6.0 would use a hard-coded block size of 512 bytes, which had serious performance repercussions in the case of DLT tape drives. As a result, Compaq recommends that DLT drives not be used with these earlier (i.e: version 4.21x) SQL Servers. 512 byte blocks work fine for DAT and QIC drives.
  • Page 22 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 22 This section will discuss the features, functional characteristics, and other considerations involved when using the native data “dump” facility provided with SQL Server. The database backup functionality built-into SQL Server 6.x is quite versatile. We will see that backup jobs can be run in a variety of ways, and that data can be archived to different types of storage.
  • Page 23 (16KB) at a time . The sequential nature of reads from the database during dumps can also benefit from read-ahead at the hardware level, such as the Compaq SMART-2 Array Controller which pre-fetches data into its on-board cache module.
  • Page 24 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 24 When the transaction log fills up and SQL Server is unable to record a checkpoint in the transaction log, you have to perform a dump of the transaction log, without making a backup copy of it, using DUMP TRAN <database>...
  • Page 25 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 25 require that a DUMP TRANSACTION WITH NO_LOG be performed followed by a full database dump the Event Manager can be asked to log a SQL Server event in response to a Performance Monitor Alert.
  • Page 26 . The best way to implement such an array is through use of a hardware RAID controller such as the Compaq Smart-2 SCSI Array controller. For the purposes of optimizing backup throughput, when using the Smart-2 array controller it is best to create a single large array spanning the two SCSI channels, rather than to create multiple arrays and extend the database across the logical volumes on the separate arrays.
  • Page 27 ARCserve for Windows NT from Cheyenne Software . The ARCserve family of products is available directly from Compaq to help form a storage management solution, and has been thoroughly tested on Compaq hardware. Thus, this section will focus specifically on ARCserve 6.0 for Windows NT, Enterprise Edition, and its ‘add-on’...
  • Page 28 Auto Changer - This option is for use with a tape autoloader or tape library such as the DLT 15- Cartridge Library from Compaq. The current version of the auto-changer is not compatible with the Raid Option however, so both cannot be used concurrently.
  • Page 29 Tape striping can be used as a way to perform unattended backups, as long as capacity requirements are met. Normally, one would use a tape library such as the Compaq DLT 15-Cartridge library for unattended backups. However, if increased performance or fault tolerance is needed along with...
  • Page 30 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 30 GigaBytes of storage in an ARCserve RAID-0 tape array. This applies to SQL Server tape stripe sets as well, which perform data striping similar to ARCserve RAID-0 arrays. ARCserve RAID-5 arrays will provide the capacity of n-1 drives, and at least 3 drives must be in the array.
  • Page 31 Compaq 15/30-GB and 35/70-GB DLT tape drives. Compaq DLT Tape Array and DLT Tape Array II cabinets. Results including Microsoft SQL Server 4.21x were covered in the previous paper, Compaq Backup and Recovery with Microsoft SQL Server (4.21x), document #250A/0894.
  • Page 32 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 32 Compaq 4.3 GB Fast-Wide SCSI-2 disk drives (7200 RPM). Compaq External Storage cabinets for Fast-Wide disk drives. The system was set up as follows: All system boot and binary files were installed on a single, internal hard drive on the integrated SCSI-2 controller.
  • Page 33 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 33 Device Controller Bus(es) - saturation of Fast-Wide SCSI-2 bus(es) (10/20 MB/sec) on 32-Bit SCSI-2 controller or Smart-2/P Array controller to which tape or disk dump devices interface. Dump Device - limited capability of tape or disk device to service write requests (1.25/2.50 MB/sec for DLT Tape drives).

  • Page 34: Chart 3 - Dump To Single Tape Device

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 34 Chart 3 - Dump to Single Tape Device Looking at the result sets, the steepest differences can be seen when comparing 35/70-GB DLT performance to 15/30-GB DLT performance: the 35/70 is almost 4x faster. This vast difference is understood when considering the hardware enhancements in the 35/70 vs.
  • Page 35 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 35 Previously, for single-device dumps all reads from the disk array occurred sequentially by one thread. Now as we add dump devices SQL Server allocates additional threads from the backup threads pool assigning one thread per dump device.

  • Page 36: Chart 4 - Null Device Dumps : Reading Data From Disk Arrays

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 36 The tests were done as striped dumps using two null devices (2 threads) for the first test, four devices (4 threads) for the second test, and six devices (6 threads) for third test. The results are shown below:...
  • Page 37 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 37 array could conceivably be used for storage of the data without an accompanying tape device . In this case a fault tolerant array would be highly recommended, preferably on a separate controller from the one containing the actual database volume.

  • Page 38: Chart 5 - Striped Dumps To Disk Arrays

    (i.e: parity can be generated for each “stripe” across all drives instead of for each write to any one drive). For a discussion on the performance implications of RAID technology, see the Configuring Compaq RAID Technology for Database Servers white paper.
  • Page 39 PCI bus usage was monitored using special Performance Monitor counters developed by Compaq, which are available through the Compaq Resource Kit for Windows NT. The PCI % utilization shown in the chart was taken as an average of the load observed between the 2 peer PCI buses.

  • Page 40: Chart 6 - Striped Dumps To 15/30 Dlt Tape Drives

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 40 Chart 6 - Striped Dumps to 15/30 DLT Tape Drives Starting with 1 drive yields the 5.00 GB/hr throughput seen before with a single drive. As Chart-6 shows, the expected increase in throughput is then seen as additional drives are added to the stripe set.

  • Page 41: Chart 7 - Striped Dumps To 35/70 Dlt Tape Drives

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 41 drives be combined with other, slower types of tape drives because this will cause the performance of the DLT drives to be reduced to that of the slowest drive in the set.
  • Page 42 See earlier section entitled Establishing Maximum Throughput at the Server. When SQL Server 6.5 database dump tests were run on previous generation (EISA-based) Compaq servers (i.e: the Proliant 4500), the maximum throughput achieved was about 25 GB/hr, due mainly to limitations imposed by EISA bus bandwidth.

  • Page 43: Chart 8 - Concurrent Dumps Of Multiple Databases To 35/70 Dlt Tape Drives

    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).
  • Page 44 SCSI ports) which resided on the primary PCI bus of the Proliant 5000. All of the DLT drives resided in Compaq DLT Tape Array cabinets (4 drives per cabinet). Each cabinet was cabled to 2 controllers (the embedded Fast-Wide SCSI-2/P controller or additional Wide-Ultra SCSI-2/P cards), so that each controller interfaced to 2 drives.

  • Page 45: Chart 9 - Database Backup To 15/30 Dlt Tape Raid Using Arcserve

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 45 Chart 9 - Database Backup to 15/30 DLT Tape RAID Using ARCserve As we can see, using the ARCserve software in conjunction with SQL Server yields excellent throughput and scalability, both with RAID-0 and RAID-5 tape arrays. The average increase in throughput when adding a tape drive to either type of array is around 4.25 GB/hr.

  • Page 46: Chart 10 - Database Backup To 35/70 Dlt Tape Raid Using Arcserve

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 46 eight DLT drives our four Pentium Pro/166 processors were almost saturated (CPU usage split between the SQL Server and ARCserve threads). This high load on the system CPU’s could cause performance...
  • Page 47 CPU use. We do however, recommend ARCserve (and its autochanger option) for implementing concurrent, unattended backup jobs to both drives inside the Compaq DLT 15-Cartridge Library Also, results of using the ARCserve products to perform concurrent backups of databases to a remote server, will be shown in the following sections.
  • Page 48 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 48 This section covers performance analysis of a different kind of backup strategy from the scenarios previously discussed. Remote backups involve backing up a database which resides on one server, by transferring data across a network interconnect to storage devices which reside on another server.
  • Page 49 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 49 2 Compaq DLT Tape Array cabinets. 1 Compaq External Storage cabinet with 5 Fast-Wide disk drives. 3 Compaq NetFlex-3 PCI 10/100 TX UTP cards. This is the primary system under test. It was set up as follows: The system boot and binary files were installed on a single internal disk drive attached to the integrated Fast-Wide SCSI-2 controller.

  • Page 50: Chart 11 - Backup Of One Server Across Single 10Baset Segment

    100Base-T repeater for the 100 Mbit tests. The 100 Mbit technology chosen was 100Base-TX. Compaq supports other 100 Mbit Ethernet technology such as 100VG-Any LAN, but this was not tested. 100Base-TX supports full-duplex mode for bi-directional throughput up to 200 Mb/s.

  • Page 51: Chart 12 - Backup Of One Server Across Single 100Basetx Segment

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 51 over 75% average usage with just one DLT, and performance gain with multiple DLT’s is minimal. Of course using RAID-5 on the tape array does give the benefit of greater data protection.
  • Page 52 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 52 network utilization, it was never seen to exceed an average of 25%. The CPU usage at both the source and destination servers is also moderate, not exceeding 10% and 16% respectively.
  • Page 53 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 53 Figure 1 – Network Layout: Backup of 4 Servers Across 4 Dedicated 10Base-T Segments At the storage server, four tape drive “groups” are set-up under ARCserve, one for each server to be backed up.

  • Page 54: Chart 13 - Concurrent Backup Of Multiple Servers Across Multiple 10Baset Segments

    It should be noted that more than four such concurrent backup jobs could feasibly be performed with the addition of still more tape drives and NICs or dual-port NICs such as the Compaq Netelligent Dual 10/100TX The concurrent backup scheme is continued here, with 100 Mbit technology. There is however, a key difference in the way the network is setup, versus the 10 Mbit tests.
  • Page 55 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 55 storage server is to avoid creating a serialization point at the storage server’s network interface while it processes incoming requests from multiple sources . The network layout is shown in Figure 2.

  • Page 56: Chart 14 - Concurrent Backup Of Multiple Servers Across Single 100Basetx Segment

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 56 Chart 14 - Concurrent Backup of Multiple Servers Across Single 100BaseTX Segment The benefits of this concurrent strategy are obvious, as greater throughput is derived from the tape server and more of the network bandwidth is utilized, for each additional database backed up from a remote system.
  • Page 57 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 57 especially in the case where a network bridge or routing device is configured in between the source and destination nodes Bridges or routers placed in between the tape backup server and the other servers can significantly degrade network backup performance.
  • Page 58 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 58 The DLT drives are Compaq’s highest performing tape backup solution, and when configured as an array with the use of SQL Server 6.x striping or ARCserve RAID Option this performance is scaled even further.

  • Page 59: Table 2 - Number Of Dlt Drives Needed For Desired Throughput

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 59 temporary disk storage can be removed by using Cheyenne ARCserve, which can ‘pull’ data from multiple database servers and sent directly to tape on the Backup server. Such remote backup jobs can be run in a sequential (back-to-back) fashion, or they can run concurrently if multiple 10-BaseT segments or a dedicated 100-BaseT segment are available.
  • Page 60 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 60 Note that the MIS manager has decided it is acceptable to restart or possibly lose backup jobs if a tape drive/cassette fails, and so ARCserve and its RAID option - along with their added costs - were not considered.
  • Page 61 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 61 This section will address considerations of performing on-line backups of a SQL Server database during user activity. Scenarios involving both the SQL Server native dump as well as the ARCserve assisted (database backup agent and RAID option) dump will be presented.

  • Page 62: Figure 3 - Sql Server Backup With Database Activity

    Finally, we measured throughput (both user transactions per second throughput and GB/hour backup throughput) during a database dump to two Compaq 15/30- GB DLT drives, with the SQL Server native striped dump as well as the ARCserve assisted dump.

  • Page 63: Table 3 - Online Dump Of Active Database With Sql Server

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 63 inaccessible, although it is actively accessed only in the first scenario. The two environments do however, result in quite different performance dynamics. The system that was used for this testing was a Proliant 5000 server with two (2) Pentium Pro/166 processors and 1 GB of RAM.

  • Page 64: Table 5 - Online Dump Of Inactive Database With Sql Server

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 64 When dumping an active database with SQL Server, the user transaction throughput significantly decreases during the dump operation: From 33% of the maximum throughput before the dump, it fell to 4% of the max at the start of the dump then gradually rose to about 16% of the max near the end of the dump.

  • Page 65: Table 6 - Online Dump Of Inactive Database With Arcserve

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 65 75% of .15 sec ~70% 75% of 0.17 sec ~80% 6.6 GB/hour Maximum Maximum Table 6 - Online Dump of Inactive Database with ARCserve Transactions Before Dump Transactions During Dump...
  • Page 66 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 66 process), or the transaction rate will suffer along with a reduction in backup throughput (with the ARCserve backup agent).
  • Page 67 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 67 Like the database itself, the transaction log can be backed up with the database still online using SQL Server dump functionality. A transaction log can be backed up as part of the database, or by itself if it resides on a separate database device.

  • Page 68: Table 7 - Max Dump Throughput For Small Arrays

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 68 common transaction log volumes (fault tolerance and number of drives) that may be implemented on an array controller, along with the approximate throughput they can be expected to deliver when...
  • Page 69 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 69 DUMP TRANSACTION SQL Server NULL 15 GB/hr SQL Server 1 15/30 DLT 6.5 GB/hr SQL Server 1 35/70 DLT 15 GB/hr SQL Server 8 15/30 6.1 GB/hr DLT’s ARCserve 8 15/30 14.8 GB/hr...
  • Page 70 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 70 16.5 GB/hr with 4 DLT drives, which exceeds the rate of the log volume. Therefore the backup time must be calculated as: [27.3 / 16.5] + [.85 / 12.5] = 1.72 hours, or about 1 hour & 43 minutes.
  • Page 71 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 71 After restoring the data pages during a load, SQL Server will reinitialize any unused pages remaining in the database. Depending on what percentage of the database remains unused, this process can consume a significant amount of the overall load time, and generates much I/O in the form of 16KB writes to the data device.

  • Page 72: Chart 15 - Load Database: Data Restore Performance Based On Disk Array Type

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 72 These results do not include any activity needed to search, replace or rewind the tapes, which would naturally prolong the restore process. Chart 15 - Load Database: Data Restore Performance based on Disk Array Type Rewind of the tapes between the restore and reinit phases of the load can be prevented by using the NOUNLOAD option.

  • Page 73: Chart 16 - Load Database: Page Reinitialization Performance Based On Disk Array Type

    Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 73 Chart 16 - Load Database: Page Reinitialization Performance based on Disk Array Type From the above results it is at once apparent that the type of data disk array does indeed have a huge impact on both phases of the database load.
  • Page 74 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 74 The page reinitialization phase of the load (chart 16) is generally faster with all types of arrays than the initial phase. Although both processes employ 16 KB writes to the data array, the reinitialization is a purely sequential operation (which translates to less head seek times on the disk drives), and does not need to fetch data from the tape drives.
  • Page 75 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 75 loaded into an empty database with 50 GB of total data space and 2 GB of total log space. The database server is a Proliant-5000 with a Smart-2/P array controller. The database is constructed across 10 disk drives configured in RAID-5, spanning both SCSIports of the Smart-2/P (5 per port).
  • Page 76 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 76 that were recorded (but not previously applied), and rolls back any transactions that were uncommitted at the time of the log dump. During the first phase of the transaction log load, SQL Server seems to restore the log in sections, by...
  • Page 77 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 77 RAID 5 data array: 1 hour, 32 minutes. This will not necessarily be the case with transaction profiles containing a much higher ratio of read (non-logged) vs. write (DML) statements, or with a system under light usage.
  • Page 78 The best way to implement such an array is through use of a hardware RAID controller such as the Compaq Smart-2 SCSI Array controller. You can increase your backup throughput by using multiple storage devices along with SQL Server striped database dumps or the ARCserve RAID option.
  • Page 79 Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 79 When estimating the amount of time needed to complete a full database dump, don’t forget to account for the size of the transaction log. If archiving the transaction log separately, the performance of the log dump will usually be slower than that of a database dump.
  • Page 80 Configuring Compaq RAID Technology for Database Servers, published in February 1994 (Document Number 267A/0294) Compaq Backup and Recovery Of Microsoft SQL Server for Windows NT, First Edition, published in October 1994 Configuration and Tuning of Microsoft SQL Server 6.5 for Windows NT on Compaq...
  • Page 81 Oracle7 Competitive Analysis UnixWare Other: Systems Management SCO UNIX Other: Other: Additional Comments: Return to: Database Engineering Compaq Computer Corporation MailCode 090803 20555 S.H. 249 Houston, Texas 77070 Compaq Backup and Recovery for Microsoft SQL Server 6.x Doc No 444A/0797...

This manual is also suitable for:

292970-001 - prosignia - 200Proliant 1000Proliant 1500Proliant 2000Proliant 4000Proliant 4500 ... Show all

Table of Contents