HP ProLiant 4000 Compaq Backup and Recovery for Microsoft SQL Server 6.X
HP ProLiant 4000 Manual
View all HP ProLiant 4000 manuals
Add to My Manuals
Save this manual to your list of manuals |
HP ProLiant 4000 manual content summary:
- HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 1
1997 Compaq Computer Corporation, All Rights Reserved Doc No 444A/0797 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 2
Insight Manager, Fastart Registered U.S. Patent and Trademark Office. ProSignia, ProLiant and QVision are trademarks of the Compaq Computer Corporation. Microsoft, Windows, Windows NT, Windows NT Advanced Server, SQL Server for Windows NT are trademarks and/or registered trademarks of Microsoft - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 3
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 3 1997 Compaq Computer Corporation, All Rights Reserved Doc No 444A/0797 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 4
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 4 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 5
Page Reinitialization Performance based on Disk Array Type 73 Table 1 - Tape Cartridge Support Matrix ...15 Table 2 - Number of DLT Drives Needed for Desired Throughput 59 Table 3 - Online Dump of Active Database with SQL Server 63 Table 4 - Online Dump of Active Database with ARCserve 63 Table - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 6
of data archival has led to the emergence of powerful and rather versatile new backup products. We have attempted to make this document as comprehensive as possible to meet the needs of all Compaq customers who manage SQL Server environments on our hardware products. The customer who is beginning - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 7
6.x 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 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 8
failure, software component failure, power loss, etc. SQL Server provides this automatic data protection Server. More detailed information about transaction logging can be found in the Microsoft SQL Server manuals not cause any data loss. With the Compaq SMART and SMART-2 Array controllers and the - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 9
procedures in various failure scenarios, refer to the SQL Server Administrator's Guide. Your ability to recover your data depends entirely on utilities while SQL Server is running. 6 This document will provide a performance analysis of online backups only. 1997 Compaq Computer Corporation, All - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 10
the tape. With Cheyenne ARCserve for Windows NT and Compaq TurboDAT AutoLoader or Compaq DLT Library, you can group tapes together to increase the device files on 'raw' (unformatted) partitions is supported by both Windows NT and SQL Server to enhance I/O performance by bypassing the file system. - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 11
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 your needs, along with techniques outlined in the System Administrator's Guide, will help you determine a plan that is best for you. You - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 12
on another server. This device can consist of a hard disk drive or a rewritable optical disk drive. SQL Server does not support direct Server Executive service or third party software. Refer to the System Administrator's Guide are available from Compaq or Cheyenne for use with Cheyenne ARCserve, and - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 13
to test your backup AND recovery strategy! More details on various SQL Server-based recovery scenarios, load requirements and other considerations can be found in the System Administrator's Guide or the manuals available with your backup software. We will analyze some considerations and performance - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - 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.12 12 Even these utilities have certain limitations. See the Administrators Guide for details. - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 15
large, mission critical databases like those found in many SQL Server environments. Table 1 summarizes the tape cartridge support of tape drives evaluated in this document: Table 1 - Tape Cartridge Support Matrix Tape Drive Tape Cartridge(s) Supported Compaq 10/20-GB DLT Drive DLT Tape III (10 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 16
the appropriate cables. Compaq also provides DLT Tape Array cabinets which support up to four Server cannot interface with the drive by itself. When operating in a Microsoft Windows NT 3.51 or 4.0 environment, the Compaq 10/20-GB and 15/30-GB DLT drives use the Digital TZ86, TZ87, DLT2000 driver - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 17
Compaq SCSI-2 controller such as the integrated controllers found on Proliant and ProSignia servers, make sure that the Compaq 32-Bit SCSI-2 Controllers driver (CPQ32FS2.SYS) is installed from the Compaq manually de-selecting the compression option on the drive, or using tape software that supports - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 18
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 18 initialized and never used pages only, and compression can sometimes be faster than hardware data compression, since it can utilize a more powerful and faster system processor (depends on the processor type, of course), and because it - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 19
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 19 tape drive writes out the current data, To achieve optimal backup throughput in this case, make sure you have plenty of CPU power (a higher speed Pentium or Pentium Pro processor, or dual processors if the compression algorithm is - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 20
query the tape driver with the appropriate API call to determine the kind of tape drive before attempting to set the block size. SQL Server 6.0 does 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 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 21
Compaq Backup and Recovery for Microsoft SQL Server 6.x Chart 2 - Throughput Variance with Block Size & Data Patterns Page 21 The above discussion is relevant to the subject of this paper in helping to explain performance differences that may be seen between versions of SQL Server. The blocking - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 22
transfers take place. These larger I/O sizes allow SQL Server 6.x to more efficiently drive powerful hardware storage technologies such as disk arrays, Wide SCSI SQL Server dump process either locally or across the network. In addition to named pipe dumps, SQL Server 6.x continues to support dumps - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 23
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. During a dump, SQL Server reads the data pages into in-memory buffers; with one buffer being allocated per backup thread - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 24
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 24 When the transaction log fills up and SQL Server backup. Refer to the System Administrator's Guide for more details and important considerations regarding use Executive The SQL Executive Service in SQL Server 6.x includes several ' - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 25
done which requires a subsequent database dump to preserve the usability of future transaction log dumps. For more information on this subject, refer to the SQL Server Administrator's Companion. 1997 Compaq Computer Corporation, All Rights Reserved Doc No 444A/0797 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 26
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 26 of pages reported as dumped in the SQL Server error log (or Windows NT Application event log)33, then multiply this number by '2048'. The time required to perform the dump can most accurately be acquired from the SQL Server error log - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 27
to carry out online backup of SQL Server databases. ARCserve 6.0 Enterprise is a powerful storage management product that offers a rich supports up to 8 tape drives per server. 35 Cheyenne Software, Inc. is now a wholly owned subsidiary of Computer Associates International, Inc. 1997 Compaq - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 28
native SQL Server product. Auto Changer - This option is for use with a tape autoloader or tape library such as the DLT 15Cartridge Library from Compaq. The current SQL Server 6.x Task Manager, part of the SQL Executive service, provides a more limited scheduling scheme for native SQL Server backup - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 29
Server dump operations directly to tape will no longer work once the Windows NT supplied driver becomes unavailable. For more information on ARCserve 6.0 or its Option software, please refer to the User Guide a tape library such as the Compaq DLT 15-Cartridge library for unattended - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - 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, - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 31
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 31 In this section of the document, the performance aspects of various backup and recovery methods are analyzed, and some guidelines provided to help you choose the best method for your environment. We have focused our efforts on the - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 32
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 database volume. Disks - insufficient spindles in database volume to service required number of read requests from application. Software - serialization - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 33
service write requests (1.25/2.50 MB/sec49 for DLT Tape drives). Intermediate (Link): Network - insufficient bandwidth (1.25/12.5 MB/sec50) in the network cable. NIC Cards - limited capability of network controllers (at server 1997 Compaq Computer Corporation, All Rights Reserved Doc No 444A/0797 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 34
Compaq Backup and Recovery for Microsoft SQL Server 6.x Chart 3 - Dump to Single Tape Device Page 34 size (please see the earlier section entitled Block Size). The larger read/write blocks specified by SQL Server 6.5 allow the DLT to record the data at a much faster rate - especially in the case - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 35
the two SCSI channels (or 'SCSI-ports') on both of the Smart-2 controllers was supplied with four Fast-Wide SCSI-2 disk drives. Four drives were found to be sufficient to The 'diskdump' device in SQL Server is a 'null' device. 1997 Compaq Computer Corporation, All Rights Reserved Doc No 444A/0797 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 36
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 36 The tests were done as striped dumps the case in the following sections, where striped dumps are done to various hardware storage devices. SQL Server allows the use of "disk dump devices" for backup purposes, as well as tape. The - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 37
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 37 array could conceivably be used for throughput may be limited by the PCI bus bandwidth. 60 The on-board controller cache was manually configured for 100% write caching (vs. read-ahead) using the Array Configuration Utility. However - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 38
Compaq Backup and Recovery for Microsoft SQL Server 6.x Chart 5 - Striped Dumps to Disk Arrays Page 38 As expected, performance increases as the drive). For a discussion on the performance implications of RAID technology, see the Configuring Compaq RAID Technology for Database Servers white paper. - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 39
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 39 goes up almost 50% to 47 to multiple 15/30-GB DLT63 tape drives, using the tape drive striping functionality of the SQL Server dump database process. For these types of dumps to multiple tape drives, the following considerations were - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 40
Compaq Backup and Recovery for Microsoft SQL Server 6.x Chart 6 - Striped Dumps to 15/30 DLT Tape a single system for this type of backup activity. Production environments that wish to use the SQL Server dump but that require a backup rate 30GB/hr or greater to meet their time constraints, should - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 41
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 41 drives be combined with other, slower in your database can affect the performance numbers seen when dumping to tape drives supporting hardware compression. We have found however, that performance differences due to compression become - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 42
go through numerous software layers as well (operating system, tape driver, miniport driver, etc), any one or a combination of which could introduce Throughput at the Server. 67 When SQL Server 6.5 database dump tests were run on previous generation (EISA-based) Compaq servers (i.e: the Proliant - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 43
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 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 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 44
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 44 databases to two different drives the combined database on the system. The ARCserve applications act as a 'go-between' from SQL Server to the tape subsystem. For these types of operations utilizing ARCserve to backup databases to - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 45
the named pipes mechanism allows the ARCserve backup agent to process the incoming data and send it out to tape faster than the native SQL Server process can. However, this mechanism also demands much more CPU power; with 1997 Compaq Computer Corporation, All Rights Reserved Doc No 444A/0797 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 46
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 degradation to other application - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 47
in a RAID-5 tape array. Note however, that a system with more powerful processors than our four Pentium-Pro/166 modules, could conceivably yield better Compaq DLT 15-Cartridge Library69. Also, results of using the ARCserve products to perform concurrent backups of databases to a remote server - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 48
Compaq 35/70-GB DLT tape drive. 70 Alternatively, the name of the remote share can be added to the "NullSessionShares" registry key under the path \\HKEY_LOCAL_MACHINE->CurrentControlSet->Services->LanmanServer->Parameters. For more information on setting up a network dump device, see the SQL Server - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 49
written out from memory to peripherals on PCI bus 2). Database Server: Compaq Proliant 5000 Server with 4 P6/166 processor boards. 1 Compaq SMART-2 Array PCI controller (C875). 1 Compaq External Storage cabinet with 5 Fast-Wide disk drives. 1 Compaq NetFlex-3 PCI 10/100 TX UTP card. This was - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 50
selected was TCP/IP. Networking hardware included: Compaq NetFlex-3 and Netelligent network interface cards. Compaq Netelligent 10Base-T Repeater. Compaq Netelligent 100Base-TX Repeater. CAT 5 UTP cables (supports both 10 Mbs & 100 Mbs). Both servers were cabled to the 10Base-T repeater for the - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 51
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 51 over 75% average usage with just this oversimplified prediction, as shown by the below chart: Chart 12 - Backup of One Server Across Single 100BaseTX Segment Comparing Chart-12 to Chart-9, the throughput seen while backing up data - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - 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 5000 systems are more powerful than the Proliant 2500's, for the purposes of these tests they - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - 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. Each drive group contains only a - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 54
ratio between systems to be backed up vs. network cards in the storage server, although all data transfers occur over the same wire. The reason for having more than one NIC on the 74 Our configuration did not include performance testing with the Compaq Netelligent Dual 10/100TX PCI UTP controller. - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 55
More than 2 RAID-5 arrays could not be configured as ARCserve supports only 8 drives and each RAID-5 array requires at least 3 server to receive data from up to 4 other servers. 76 The PCI % usage shown in the chart was taken as an average of the load observed between the 2 peer-buses. 1997 Compaq - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 56
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 transferred into the server and written out - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 57
bridge or routing device is configured in between the source and destination nodes77. 77 Bridges or routers placed in between the tape backup server and the other servers can significantly degrade network backup performance. 1997 Compaq Computer Corporation, All Rights Reserved Doc No 444A/0797 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 58
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. By adding enough of the drives - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 59
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) - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 60
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 60 Note that the MIS manager has the database backup, then the DLT 15-Cartridge Library along with ARCserve (and its autochanger support) may have provided a better solution, allowing for unattended backups with even more capacity so - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - 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 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 62
Finally, we measured throughput (both user transactions per second throughput and GB/hour backup throughput) during a database dump to two Compaq 15/30GB DLT drives, with the SQL Server native striped dump as well as the ARCserve assisted dump. During each of the phases we also noted changes in the - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 63
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 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 64
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 64 When dumping an active database with SQL Server, the user OLTP-type environment with numerous read/write transactions. A Decision Support-type environment involving large read-only queries may behave differently since reads are - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 65
fact that we have isolated our two databases on separate disk arrays helps to produce this situation - I/O requests from the backup job do service all threads and I/O is separated. If CPU usage becomes high however, the backup throughput will suffer (with the SQL Server dump 1997 Compaq Computer - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - 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). - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - 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 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 68
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 68 common transaction log volumes (fault and in fact went down - when a striped dump was done to multiple DLT drives! The SQL Server Dump Transaction process does not seem to be able to keep the tape drives streaming for a striped - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 69
Compaq Backup and Recovery for Microsoft SQL Server 6.x DUMP TRANSACTION SQL Server NULL SQL Server 1 15/30 DLT SQL Server 1 35/70 DLT SQL Server 8 15/30 DLT's ARCserve 8 15/30 DLT's NO TRUNCATE option SQL Server NULL SQL Server 1 15/30 DLT SQL Server 1 35/70 DLT SQL Server to help in this - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 70
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 70 16.5 GB/hr with 4 DLT drives, created, with respect to device allocation. When recovering a database from a database dump and a series of subsequent transaction log dumps, all dump images must be loaded in sequence and successfully. If - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - 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 considerations can be found in the Microsoft SQL Server manuals and the Microsoft SQL Server, Backup and Recovery Guidelines document, available from - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 72
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 72 These results do not include any activity needed to search, replace or rewind89 the tapes, which would naturally prolong the restore process. Chart - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 73
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 73 Chart 16 - Load Database: Page 8 15/30-GB DLT's (11.5 GB/hr). Interestingly, using the ARCserve Backup Agent for SQL Server with 8 DLT drives yielded significantly better restore performance to the RAID-5 array: 16.6 GB/hr with 14 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 74
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 74 The page reinitialization phase of the GB) should be obtained using one of the methods discussed in 'Online Backup Considerations with SQL Server Dump'. Time (in hrs) can then be estimated using the above formulae. Note that if the - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - 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 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - 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, - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - 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 necessary Re-creation of the database devices and the database itself, if necessary. 1997 Compaq Computer Corporation, All Rights Reserved Doc No 444A/0797 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 78
with Microsoft SQL Server for Windows NT and Compaq server products. We have limitations, and a careful analysis of your requirements will help you determine the best method. The performance of off- it is important to ensure adequate CPU power or else the backup throuhput will suffer and possibly - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 79
Compaq Backup and Recovery for Microsoft SQL Server 6.x Page 79 13. When estimating the amount of time needed Form on the next page and return it to us at your earliest convenience. This will help us tailor the future information products to your needs, and will enable us to make future revisions - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 80
Houston, Texas 77070 Main (281) 370-0670 http://www.compaq.com/ 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 - HP ProLiant 4000 | Compaq Backup and Recovery for Microsoft SQL Server 6.X - Page 81
related new information products. Your effort will help us improve the quality of the future Server Sybase System 10 Oracle7 Other: Processing Type On-Line Transaction Processing Decision Support Server Sybase System 10 Oracle7 Other: Additional Comments: Return to: Database Engineering Compaq
1997 Compaq Computer Corporation, All Rights Reserved
Doc No 444A/0797