Proposition HP. Projet Backup Centralisé de l Université Catholique de Louvain

Transcription

1 15 Proposition HP Projet Backup Centralisé de l Université Catholique de Louvain

2 Table of contents 1. CENTRALIZED BACKUP SOLUTION PREFACE DETAILED TECHNICAL DESCRIPTION Design HP Data Protector : Short Product Overview A highly available Data Protector 5.0 cell manager Identifying potential bottlenecks, design for performance Unattended backups / Intersite cloning : Available slots HARDWARE AND SOFTWARE OFFERING : OVERVIEW General Terms and Conditions...15 Hewlett-Packard Company 2002 Page : 2 of 15

3 Limitations des responsabilités 2002 Hewlett - Packard Company; cité ci-après comme HP. Tout droits réservés. Hewlett-Packard Belgium BVBA/SPRL - - Bureaux: Rue de l Aéronef 1, 1140 Evere Restriction d utilisation et divulgation des informations et des données de cette proposition. Cette proposition est la propriété de Hewlett-Packard. Toutes les informations contenues dans le présent document sont confidentielles et ne peuvent être ni copiées ni divulguées à une tierce partie sans le consentement écrit préalable de Hewlett-Packard. Les informations et données contenues dans le présent document ne peuvent être divulguées chez la UCL qu aux employés qui sont directement impliqués dans le projet relatif à cette offre. Il est de la responsabilité de la UCL de s assurer que les employés engagés dans ce dossier soient au courant de cette clause de confidentialité et s y conforment strictement. La UCL est autorisée à utiliser les informations contenues dans ce document à des fins d évaluation uniquement. Personne de contact: Nom: Daniel Goffin Titre: Storage Sales Specialist Tel: +32 (0) Mobile: +32 (0) Nom: Philip Pauwels Titre: HP Technical Consultant Tel: philip_pauwels@hp.com Mobile: + 32 ( Hewlett-Packard Company 2002 Page : 3 of 15

4 1. CENTRALIZED BACKUP SOLUTION 1.1. PREFACE This document will describe the technical solution for centralized tape backup that the Université Catholique de Louvain would like to implement. We have made the assumption that the solution spans the Louvain-La-Neuve site. Nevertheless, the solution is highly scalable, and can be expanded to other sites (e.g. Woluwe), given an appropriate telecommunication infrastructure exists or is built to that purpose. Highlights of the solution : HP Data Protector (DP) cell manager backup manager solution. Data Protector cell manager runs as a package in a 2 node HP MC/ServiceGuard Campus Cluster. LAN-SAN backup topology. Hosts in distributed locations at LLN site are DP disk agents backing up their data over the LAN. Solution relies on the fact that appropriate Gbit-E LAN is in place or made available. The DP Cell manager and failover node act as media servers. Hewlett-Packard Company 2002 Page : 4 of 15

5 1.2. DETAILED TECHNICAL DESCRIPTION Design Hewlett-Packard Company 2002 Page : 5 of 15

6 HP Data Protector : Short Product Overview. As the central backup manager we propose the HP DataProtector (DP) data management software. DataProtector is a highly scalable, high performance Enterprise backup management application and can run on a variety of Operating System platforms as there are HP- UX, Solaris, Wintel. DataProtector s software structure is very simple : Cell Manager : Central point of administration. Can run on HP-UX, Solaris, Wintel NT4,W2K,XP Pro. Disk Agent (a.k.a. backup Agent) : Installed on every system, basically reads/writes the disks/filesystems/drive_letters/raw devices of the system. Media Agent (a.k.a. backup Device Server) : Installed on systems with have access to a tape device or tape library. Hewlett-Packard Company 2002 Page : 6 of 15

7 Tape drive license : Per tape drive used, a license is required. A distinction is made between drive license for UX, and drive license for Wintel, Netware, Linux. A drive attached to a SAN is typically a UX drive. Tape library nr-of-slots license : Per robot arm (tape library), up to 60 slots : free, slots license (up to library with 250 slots), unlimited slots license. Application Specific Online Backup agents : For a wide variety of database on-line backups so-called on-line agents exist. ORACLE, SYBASE, INFORMIX, LOTUS NOTES, SQL-Server, Exchange. Please see Product Brief for a full list. Wintel Open File Backup Agent : This agent is typically deployed in a Wintel (NT4,W2K) environment to guarantee consistent open file backups. Zero-impact backup integration : HP developed a number of application specific integrations for zero impact/ zero-downtime backup of popular database servers like SAP,ORACLE, SQL-Server, Exchange etc. Please see Product Brief for a full list. These integrations do rely on the functionality (Business Copy XP,VA, EMC Timefinder) offered by certain online disk storage platforms. From a licensing point-of-view DataProtector is a very simple product : What is typically needed in the UCL environment : A DataProtector Cell UX Manager license. This license comprises 1 UX (SAN) drive license. A nr of UX drive licenses. As MSL 5060 tape lib (60 slots) is used, no slots license is required. If more slots would be installed (Up to 4 HP MSL5060 tape libraries can be combined to form a 16drive /240 slots library), the slots license would be required. In the offer we have 2 x MSL5060 libraries, a total of 7 extra drive licenses is required. Optional : On line UX or Wintel Agents. Optional: Wintel Open File Backup Agents (1 per server, special workstation licenses available). Typically, a backup session is started from the DP Cell Manager. (Manually or through the DP scheduler. (Can be triggered by an external scheduler)). For a full overview on HP Data Protector we would like to refer to the Product Brief in appendix : XX Hewlett-Packard Company 2002 Page : 7 of 15

8 A highly available Data Protector 5.0 cell manager The HP DataProtector (DP) Cell Manager runs as a high-available package on a HP- UX 11i, MC/ServiceGuard (MC/SG) protected so-called Campus Cluster. HP MC/ServiceGuard is the proven HP clustering technology. As such the Data Protector cell manager can be run on either of the 2 cluster nodes as a package and as such provide a highly available Data Protector Cell Manager. In normal operation, each cluster node will be running the DP Cell Manager and also move LAN-SAN data traffic to and from the 4 LTO tape drives installed in the HP StorageWorks MSL5060-L1 tape library. The failover node will also act as a LAN-SAN datamover to the second MSL5060-L1. In failover mode, the failover node will run the Data Protector Cell Manager, as such guaranteeing availability for backups and restores Identifying potential bottlenecks, design for performance When designing a centralized backup architecture for adequate performance, it is important to avoid potential bottlenecks in the IO chain from the backup clients to the tape drives. Therefore we will briefly discuss the proposed architecture building blocks, where possible highlighting what assumptions were set forth to come to a high performance backup and restore environment. SAN The SAN serves the back-end connectivity to the tape and MC/SG shared storage. MC/SG : Provide access to the shared online storage HP VA7100 Virtual Arrays equipped with 93 GB usable storage. This storage is the repository of the Data Protector meta data. The meta data volumes are LVM-mirrored by the HP-UX host running the Data Protector package. Both HP-UX nodes are connected to the SAN with 2 x 2 Gb/s FC Host Bus Adapters in each host. Both disk and tape traffic are carried over these connections. Disk traffic being very limited, as only DP MetaData updates. Provide HP-UX host access to 2 x MSL5060 tape libraries (4 LTO drives) from either MC/SG cluster node. Per pair of 2 LTO drives, 1 x fiber connection is targeted. Carry the tape cloning traffic between tape libraries. The SAN is built using the latest 8 port FC switches, 2 Gb/s (200 MB/s) capable. Site UCL1 and site UCL2 are interconnected using 9/125 um Long Wave fiber connections. If distance is lower then 300m then ShortWave (50/125 um) connections could be used at 2 Gb/s speed. (500 m at 1 Gb/s speed). Note that 1 Gb/s speed is sufficient for the projected tape cloning and LVM mirroring of the DP meta data volumes. Hewlett-Packard Company 2002 Page : 8 of 15

9 LAN The LAN is assumed to have following minimal characteristics. Per local site (UCLx) a 100 Mb/s backbone exists, to which each DP client connects. To be able to get predictable and maximum backup/restore performance, a switched LAN infrastructure is assumed : As it is the idea to have multiple DP client 100 Mb/s data streams aggregate into the 1 Gb/s LAN connections of the DP HP-UX datamovers. As switched network is therefore a necessity. As a matter of fact both DP servers (remember both are DP LAN-SAN datamovers) are equipped with 2 x Gbit-E NICs and 2 x FC host bus adapters to the SAN. Note regarding the Gbit-E NICs : In the offer we have foreseen Gbit-E Fx interfaces offering a distance capability up to 550m. HP can also offer Gbit-E Tx NICs with copper interfaces. Then the distance limitation is 110m. Greater distances can of course be covered when using appropriate network switches at the backup node site UCL1 and UCL2. HP MSL5060-L1 tape libraries Both site UCL1 and UCL2 are equipped with 4 x HP LTO230 drives and 60 slots. Per MSL x HP e1200 FC-U2-SCSI routers provide the connectivity to the drives. Native tape speed of an HP LTO 230 drive is 15 MB/s. Thus, taking into account a very conservative 1.6 :1 compression ratio, 1 single LTO drive can backup 75.6 GB/hour. In other words, 4 drives can backup 4 x 86.4 GB or GB/hour. If we target a full backup volume of 2 TB per library we can state that a full backup of 2 TB (2147 GB) will take 6.2 hours. This assumes that all 4 LTO drives in 1 library can be kept streaming, or in other words that the HP-UX node has enough internal bandwidth, and enough data feed from the Gbit-E connections. HP-UX LAN-SAN datamovers : HP rp5405 Gbit-E PCI bandwidth Both backup servers actually move the backup/restore data between the LAN based DP clients and the 2 x HP-UX DP backup device servers having access to the tape drives. The proposed HP rp way 650 MHz PA8700 servers (equivalent HP 3000), provide 10 PCI slots of which 8 are independent PCI slots. 2 of these slots each have a dedicated 500 MB/s data channel. Six of these slots each have an independent 250 MB/s data channel, and an additional 2 PCI slots share 1 x 250 MB/s channel. If the 2 x Gbit-E cards would be installed in the latter 2 slots, then they would affect each others Hewlett-Packard Company 2002 Page : 9 of 15

10 performance : To avoid this we will install the Gbit-E cards, and the FC HBA in the independent channel slots offering more then enough bandwidth per IO card (Gbit-E and FC). Each server is equipped with 4GB RAM (4 GB can be increased up to 16 GB). Each server can furthermore be upgraded to a 4 way CPU. We would like to refer to an attached whitepaper : «PCI Gigabit Ethernet Performance Paper «which describes a very good characterization of the performance of a Gbit-E links of the HP L-Class (currently named rp54xx). In this whitepaper the 3 members of the L-Class (L1000, L2000, L3000) server family are used with different CPU power and clockspeed. Note that the paper was written using lower performance (CPU s) then the proposed HP5405 s. Therefore Gbit-E performance figures from the paper should extrapolated to somewhere between the performance of the L1000-2way and the L3000-4way (rp5405 as proposed is a 2 way machine but running at 650 MHz instead of 440 MHz as used in the whitepaper). The whitepaper states a performance between ~1400 Mbps and 1890 Mbps depending on what type of request (Transmit or Receive) is studied : This brings us an average of 1645 Mbps aggregated maximum performance. This is roughly 205 MB/s. When we stated earlier that 4 LTO drives can write,at a 1.6 :1 compression ratio, 24 MB/s per drive. When we know that the e1200 router FC port operates at 2 Gb/s (200 MB/s) per 2 drives where only 2 x 24 MB/s is needed. Our rp5405 FC HBAs are operating at 1 Gb/s. (2 Gb/s capable). Rp5405 PCI bandwidth is at worst 250 MB/s per FC or Gbit-E HBA. We can safely state that we have a non-blocking design Unattended backups / Intersite cloning : Available slots UCL expressed the wish to minimize tape handling. Also, to maximise data safety, the possibility of tape cloning should exist between the 2 main datacenter sites at the site of LLN, UCL1 and UCL2. DataProtector offers the possibility to clone tapes between 2 tape devices. Furthermore, DP clones a tape and then flags this tape as unappendable, meaning that on this tape, no more data can be added on the cloned copy. This is a safety measure as clone tapes are most often considered as last ditch data restore media. Given this fact, cloning is mostly done outside of the normal backup window, ensuring that the cloning of tapes is done on full media, and not interfering with the daily backup operations. Once a clone exists, it can be removed from the library. In case we would loose the source (the original) DP automatically search in the remaining tape library if it has a clone copy there, and will use it as if it was the original. Needless to say that DP also keeps track of all source and their respective clones. The HP MSL5060 offers 60 slots. It can be upgraded to 240 slots by stacking 4 x HP MSL5060. We targeted a weekly tape handling schedule : Hewlett-Packard Company 2002 Page : 10 of 15

11 Per library we target to backup 2 TB (full backup). A full backup will be done on a weekly basis, while we propose to do incremental-against-last-full backups daily. We propose to use following schedule : Mon Tue Wed Thu Fri Sat Sun Inc Inc Inc Inc Inc Full X X X X X X Clone X X X X X X Mount New Set X To target the slots capacity of each site tape library, we made following calculation : 2TB full backup tapes + clones from other site. Incremental set( 5 % data change daily). Compression ratio 1.6 :1 (160 GB on 1 LTO tape). A very rough calculation shows : 2000 GB / 160 GB = 12.5 tapes (roundup = 13) needed for full backup. Capacity needed for daily incrementals-against-last-full : Note that when we say 2 TB we use incoming data. We still use the 1.6 :1 compression ratio. 10 % change daily change against last-full-backup means a total change at the end of the week of 5 x 5 % or 25 % or 500 GB. Monday : 100 GB, easily fits on 1 tape. Tuesday : 200 GB, needs 2 tapes. Wednesday : 300 GB, needs 2 tapes. Hewlett-Packard Company 2002 Page : 11 of 15

12 Thursday : 400 GB, needs 3 tapes. Friday : 500 GB, may fit still on 3 tapes but we take 4. Total incremental tapes needed online in the lib (one week) : = 12 tapes. We need 25 tapes online (13 full + 12 incr) for a backup volume of 1 week. DataProtector allows you to do incrementals-against-last-full, or plain f<i1<i2<i3<i4<i5 incremental backups meaning that only changes are backed up against last incremental or full (first incremental after full) are taken. Repeating our incremental1 tape calculation (5 % change) we roughly would need 1 tape a day. Total online set for a week : = 18 tapes. Cloning in this matter : As stated earlier, once a clone is taken, the clone tape is considered as nonappendable. This means that each library needs enough slots to hold the tapes for daily backups, plus the clone tapes of the remote library. If we take the simple incremental schema we need 2 x 25 slots for a weeks volume of backups. The HP MSL5060 offers with it s 60 slots spare capacity for a weeks unattended operation of backups. If more capacity would be needed, additional MSL5060 can be added, not necessarily with drives installed. Total amount of tapes needed : As an example we will use above calculated tape set amounts : We will do weekly full backups. We will do weekly incr-against-last-full.(standard incremental). So we need a weekly set of 12 tapes. We will use a retention schema for the incremental backups of 2 weeks. So we need 24 tapes. We assume a retention of 4 weeks for the Full backups, so 4 Full backup sets are needed : 4 x 13 tapes = 52 tapes. Every month we keep a monthly full backup set for 1 year. (12 x 13 tapes) = 156 tapes. Total is : = 232 tapes. We need to double this amount if we consider the cloning : 232 x 2 = 464 tapes. As this only for 1 library (2 TB) : We need to double this amount as well = 928 tapes for a year worth of backups. (With monthly archival of 1 x full backup set). Hewlett-Packard Company 2002 Page : 12 of 15

13 1.3. HARDWARE AND SOFTWARE OFFERING : OVERVIEW Server related Hardware and software highlights 2 x HP9000 rp way PA MHz CPU, 4 GB RAM, 2 x 36 GB U160 drives. 2 x Gbit-E cards per server. 2 x FC cards per server. HP-UX license per server. Online JFS 3.3 per server. MirrorDisk-UX per server. APA (AutoPort Aggregation software) per server MC/ServiceGuard per server. Per rp5405 a rack (located at 2 physical sites UCL1 and UCL2). Included 3 years of software and support on hardware and software. Implementation of MC/ServiceGuard cluster. SAN related hardware. 4 x HP FC8B-EL switches with adequate SW (12) and LW(4) optical SFPs. Advanced Zoning license (4 or 1 per FC8B-EL) FC cabling, 12 x 2m 50/125um. Idea is to rack the switches together with the rp5405 servers. Hewlett-Packard Company 2002 Page : 13 of 15

14 Shared server storage 2 x HP VA7100 virtual array. 512 MB cache, 2 x 1 Gb/s FC ports, 4 x 73 GB disks. HP MSL5060-L1 tape libraries. 2 x HP MSL5060-L1 each equipped with 4 HP LTO drives/60 slots. 2 x e1200 FC-SCSI routers per MSL5060. A rack per site to contain the MSL5060. FC Cabling. HP DataProtector 5.0 software. 1 x OV Data Protector Cell Manager HP-UX LTU (1 UX drive included) 7 x OV Data Protector one Drive UNIX LTU. Optional : 1 x OV Data Protector On-line ext. UNIX LTU (included as indicative price). 1 x OV Data Protector On-line ext. Win LTU (included as indicative price). 1 x OV Data Protector open file server, LTU (included as indicative price). 3 years of software support (3Y6) per above product. Implementation of MC/ServiceGuard and Data Protector 5.0 Included in the proposal, is the implementation of the 2 node MC/SG cluster, and the DataProtector cell manager software. Hewlett-Packard Company 2002 Page : 14 of 15

15 2. GENERAL TERMS AND CONDITIONS Hewlett-Packard Company 2002 Page : 15 of 15