Minimum FW required File System 5
Win2003 - x86, x64, IA64 RH 3.0, 4.0, 5.0 - x86, x64 SUSE 10 - x86 HP-UX 11.11, 11.23, 11.31 Solaris 9, 10 AIX 5.3 Tru64 5.1B OVMS 8.3 NetWare 6.5 Win2003 - x86, x64, IA64 RH 3.0, 4.0, 5.0 - x86, x64 SUSE 10 - x86 HP-UX 11.11, 11.23, 11.31 Solaris 9, 10 AIX 5.3 Tru64 5.1B OVMS 8.3 NetWare 6.5 Win2003 - x86, x64, IA64 RH 3.0, 4.0, 5.0 - x86, x64 SUSE 10 - x86 HP-UX 11.11, 11.23, 11.31 Solaris 9, 10 AIX 5.3 Tru64 5.1B OVMS 8.3 NetWare 5.1, 6.0, 6.5 Win2003 - x86, x64, IA64 RH 3.0, 4.0 - x86, x64 SUSE 10 - x86 HP-UX 11.11, 11.23, 11.31 Solaris 9, 10 AIX 5.3 Tru64 5.1B Win2003 - x86, x64, IA64 RH 4.0 - x86, x64 SUSE 10 - x86 HP-UX 11.11, 11.23, 11.31 Solaris 9, 10 Win2003 RH 4.0, SUSE 10 HP-UX 11.11, 11.31 Solaris 10 Win2003 - x86, x64, IA64 RH 3.0, 4.0, 5.0 - x86, x64 SUSE 10 - x86 HP-UX 11.11, 11.23 Solaris 9, 10 AIX 5.3
Accelerated Deduplication requires integration with backup application and data source MS Exchange (Non-MAPI) Oracle MS SQL Server NDMP VMware Lotus Domino Automigration Support

Data Protector 6.1

2003 File Backup 2003 Agent Backup 2007 File Backup 2007 Agent Backup
9, 10, 11 File Backup 9, 10, 11 RMAN Backup 4

File Backup

File Backup VMware Agent

Smart copy 6

(VLS 2.3.x code only)

Data Protector 6.0

9, 10, 11 File Backup 9, RMAN Backup 4

Data Protector 5.5

2003 File Backup 2003 Agent Backup

NetBackup 6.5

File Backup SQL 2005 Agent Backup

NetApp Filer Backup

NetBackup 6.0

NetBackup 5.1

TSM 5.5, 5.4, 5.3
NetApp Filer Backup (LAN backup only)
File Backup Agent Backup (7.0 and 8.0.1)

D2D Advanced Features

Dynamic Deduplication
Does NOT require integration

Replication

Requires separate license
D2D4112 D2D4000 D2D2500 D2D100

NOTES:

(Fibre Channel & iSCSI) (Fibre Channel & iSCSI) (iSCSI) (iSCSI)
1) See "How To Use This Document" for description of support. 2) NOT supported in the VLS300, VLS1001, VLS1002, VLS6100, VLS6500 or VLS6800. 3) Supports 6200/6600 single node series, and up to 4-nodes on multimode VLS9000/12000 systems running minimum v3.1.2 code.
4) RMAN script modifications required to enable deduplication. See HP StorageWorks Deduplication Solutions Guide for details. 5) Raw Disk deduplication is also supported for the listed file systems. 6) The initial release of Data Protector 6.1 allows customers to manage VLS automigration limited to a single drive in the physical tape library that is connected to a VLS.

Page 7 of 44

D2D Backup Systems - Operating System, ESI and TAC Partner Products (page 1 of 3)
Fb ac ku p /F U fs re du co m ve p r /U H P fs D re at st a or Pr C e ot A ec A R to C r se EM rv e C N et W IB or M ke Ti r vo li Sy St m or an ag te e c Sy M B an m ac ag an ku er te p c Ex H Ve P ec D rit at as a Pr N H et ot P B ec Fi ac le to ku Sy rE p A st xp te em m re po ss Ex Ti te B m nd ak e B er N on av e ig B N at ar et or ra Va cu ul da t B Yo rid se ge m H ite ea C d Se om H rv T m er IS Va M B ul EM ac Su tS ku C ite im R p pa et ro En na sp ig 8 ec m a t D at Fr a on So tP lu or tio IB ch ns M D ID TS ig S, ita M PA M lD Ex ic IV R pr ro S A es so rc s ft hi N D ve PM eo Sc 20 al 07 e O C ra ry cl pt e oS Se to cu Q r St re ar B ac H SM ku SG p L Fl as hN Sy et nc so rt B ac ku p Ex pr es s

in do w s TA N T R B

C PI O

ac ku p

iSCSI and SAN Support 1

D2D Backup Systems

Supported OS Windows 2008 (x86) Windows 2008 (x64) Windows 2008 (IA-64) Windows 2003 (x86) Windows 2003 (x64) Windows 2003 (IA-64) Novell OES Novell OES 9 RHEL 5 (x86)

Native Applications

Software ESI Partners

Software TAC Partners

D2D4112 3,7

(FC Connectivity)

RHEL 5 (x64) RHEL 5 (IA-64) RHEL 4 (x86) RHEL 4 (x64) RHEL 4 (IA-64) SLES 10 (x86) SLES 10 (x64) SLES 10 (IA-64) SLES 9 (x86) SLES 9 (x64) SLES 9 (IA-64) Windows 2008 (x86) Windows 2008 (x64) Windows 2008 (IA-64) Windows 2003 (x86) Windows 2003 (x64) HP-UX 11i v3 (IA-64) HP-UX 11i v3 (PA-RISC) HP-UX 11i v2 (IA-64)

Windows 2003 (IA-64)

D2D4112
HP-UX 11i v2 (PA-RISC) Novell OES RHEL 5 (x86) RHEL 5 (x64) RHEL 5 (IA-64) SLES 11 (x86) SLES 11 (x64) SLES 11 (IA-64) SLES 10 (x86) SLES 10 (x64)

(iSCSI Connectivity)

SLES 10 (IA-64)
Solaris 10 (SPARC) 1) D2D ISV by OS compatibility is explicitly listed only in the D2D section and cannot be implied from any other section of EBS Matrix. 2) Supported with Embedded iSCSI hardware or Qlogic iSCSI HBAs only 3) SAN support only with 2Gb, 4Gb and 8Gb QLogic and Emulex based FC HBAs listed in the EBS Matrix. 4) Supported with minimum Microsoft iSCSI Initiator v2.07. 5) Supported with minimum SLES 10 SP1. 6) Supported with minimum SLES 10 SP2 7) Only supported on FC fabric topologies using NPIV enabled switches or private loop topologies. 8) Supported with minimum Novell OES 2 SP1. 9) Supported with Novell OES for Linux only. 10) Supported with minimum RHEL 5 Update 4.

Page 8 of 44

D2D Backup Systems - Operating System, ESI and TAC Partner Products (page 2 of 3)

Ba ck in d ow s NT CP IO up
Supported OS Windows 2008 (x86) Windows 2008 (x64) Windows 2003 (x86)
Windows 2003 (x64) Windows 2003 (IA-64)

Windows 2000

Windows Vista (x86) Windows Vista (x64)

D2DD2D130 2

Windows XP (x86) Windows XP (x64) Novell OES 2 RHEL 5 (x86) RHEL 5 (x64) RHEL 5 (IA-64) SLES 11 ( 86) (x86) SLES 11 (x64) SLES 11 (IA-64) SLES 10 (x86) SLES 10 (x64)
NOTES: 1) D2D ISV by OS compatibility is explicitly listed only in this D2D section and cannot be implied from any other section of EBS Matrix. 2) Supported with Embedded iSCSI or Qlogic iSCSI HBAs only 3) Supported with QLogic QLA4050 PCI-X iSCSI Initiator HBA only 4) Supported with minimum Microsoft iSCSI Initiator v2.07. 5) Supported with minimum SLES 10 SP1. 6) Supported with minimum SLES 10 SP2. 7) Supported with minimum Novell OES 2 SP1. 8) Supported with Novell OES for Linux only.

Page 10 of 44

Tape Libraries/Autoloaders and Extended Solution Interoperability (ESI) Partner Products
Direct Attached and SAN Support
Enterprise Class Libraries HP Secure Key Manager ESL E-Series Ultrium 1840 FC 6 Ultrium 960 FC SDLT 600 EML E-Series Ultrium 1840 FC 6 Ultrium 960 FC Business Class Libraries MSL LTO-4 Encryption Kit Ultrium 1840

6 8, 9 4, 9

HP Data Protector

CA ARCserve

EMC NetWorker
IBM Tivoli Storage Manager

Symantec Backup Exec

Symantec Veritas NetBackup
Extended Solution Interoperability (ESI) Partners 1
(LTO-4 FC) (LTO-3 FC) (SCSI) (LTO-4 FC) (LTO-3 FC)
MSL 8096, 8048, 4048, 2024 (LTO-4 FC) (LTO-4 SCSI) (LTO-4 SAS HH) (LTO-4 SCSI HH) (LTO-3 4Gb FC) (LTO-3 FC) (LTO 3 SCSI) (LTO-3 (LTO-3 SCSI HH) (LTO-3 SAS HH) (LTO-4 SCSI) (LTO-3 SCSI) (SCSI)
Ultrium Ultrium Ultrium 1760 3,6 Ultrium 960 Ultrium 960 Ultrium 960 Ult i Ultrium 920 Ultrium 920 MSL 6000 Series Ultrium Ultrium 960 SDLT 600 Ultrium Tape Autoloaders 1/8 G2 Autoloader Ultrium Ultrium Ultrium 920 Ultrium 920 Ultrium 448 Advanced Drive and Media Features 1/8 G2 LTO-4 Encryption Kit 8, 9

- Indicates Partners with Archiving Solutions - See Page 15 for more detail. 7) Support is with the Decru DataFort FC-Series and S-Series for Tape only. 8) Support with Decru DataFort S-Series in a direct attach SCSI configuration only. 9) Please refer to Customer Advisory "c01269477" for operational details. 10) MSL 6000 Series libraries do not have library key management for the LTO4 drives. The key management must come from the backup application. 11) Requires connectivity of tape library to HP Virtual TapeServer for NonStop Systems. 12) Support is only with MSL 6026 and MSL 6030 models. 13) Refer to vendor for software application and additional hardware interoperability support. 14) Support is with the NeoScale CryptoStor Tape 700 Family only. 15) Supported with MSL4048 and MSL2024 only 16) SKM and EK are designed to provide encryption keys to LTO4 tape drives in HP tape libraries, transparent to the ISV software. Their use with all ISV software in the EBS matrix has been verified, and is fully supported.
NOTES: 1) See "How To Use This Document" for description of support. 2) Please refer to Customer Advisory "c01154679" for interoperability details. 3) Direct Attached FC only. 4) Not supported on Win2008 5) LTO4 (Ultrium 1840 and 1760) drives support AES hardware encryption. Refer to the backup/restore application vendor for LTO4 hardware encryption support details. 6) Refer to EBS Design Guide for additional info on the use of native backup commands & programs

Page 12 of 44

Advanced Library Features
Direct Attached and SAN Support Enterprise Libraries HP Secure Key Manager 5 ESL E-Series 2 Unit Cross Link 1 ESL E-Series 3-5 Unit Cross Link 1 ESL Mixed Media ESL Library Partitioning EML Library Partitioning Midrange Libraries Library Extender for the MSL G3 Family 6 MSL G3 LTO-4 Encryption Kit (EK) 4, 5 1/8 G2 Autoloader Encryption Kit (EK) 4, 5 MSL G3 Library Partitioning MSL 6000 Multi-Unit Scalability 1,2 MSL 6000 Mixed Media Support NOTES:
1) Contact your ISV for scalability support. 2) MSL multi-unit scalability is with a vertical pass-through mechanism. 3) NetWare is supported with ESL libraries in a homogeneous environment only. 4) USB Encryption Key server token for LTO-4 based Autoloaders, MSL2024, MSL4048, MSL8048 and MSL8096 libraries. 5) SKM and EK are provide encryption keys to LTO4 tape drives in HP tape libraries, transparent to the ISV software. Their use with ISV SW in the EBS matrix has been verified, and is supported. 6) The first time you install the Extender you must update the firmware in each Library individually. for future firmware updates you can update both Libraries at the same time with the Extender Firmware Package. More details at MSL Tape Library Expansion Upgrades and Options

IBM Tivoli Storage

IMPORTANT: See the Backup Application Details page for the latest supported versions of backup software.

Page 13 of 44

Backup Application Details 1
HP Data Protector Partner Device 1 Compatibility Pages Recommended Tape Driver Latest and Minimum Application Version Support HP Data Protector CA ARCserve Latest 12.12.5
IBM Tivoli Storage Manager TSM HCL Tivoli Drivers
Symantec Backup Exec Backup Exec HCL BE Drivers
Symantec Backup Exec (NetWare) Backup Exec HCL BE Drivers
Symantec Veritas NetBackup NetBackup HCL HP or NBU Drivers
Data Protector HCL Native Drivers
ARCserve HCL CABA Drivers

NetWorker HCL HP Drivers

EMC NetWorker Latest 7.5 7.5 Mininum 6.0 7.0
IBM Tivoli Storage Manager Latest 6.1 6.1
Symantec Backup Exec Latest 12.5 12.5
Symantec Backup Exec (NetWare) Latest 9.2 Mininum 9.0
Symantec Veritas NetBackup Latest 6.5 6.5 Mininum 4.5 5.0
ESL E-Series EML E-Series

Latest 6.1 6.1

Mininum 5.0 5.1

Mininum 9.0 9.0

Mininum 5.4 5.4

Mininum 9.0 10.0

VLS 12000 EVA Gateway VLS 9000 Series VLS 6000 Series 6.1 6.1 6.1 5.5 5.5 5.1 12.5 12.5

5, 7 5, 7

11.1 11.1

7.5 7.5 7.5

7.0 7.0 7.0

6.1 6.1 6.1

5.4 5.4 5.4

12.5 12.5 12.5

10.0 10.0 10.0

6.5 6.5 6.5

5.0 5.0 5.0

12.5 5, 7

11.12.12.11.5 11.5 11.5 11.5
Disk-to-Disk Backup Systems
D2D4112 Backup System (Fibre Channel) D2D4112 Backup System (iSCSI) D2D Backup Systems 4000 Series D2D Backup Systems 4000 Series D2D Backup Systems 2500 Series D2D Backup Systems 100 Series (Fibre Channel) (iSCSI) (iSCSI) (iSCSI) 6.1 6.0 6.1 6.0 6.0 6.0 6.0 6.0 5.5 5.5 5.5 5.5 12.5 12.5 12.5 12.5 6.1 6.1 7.5 7.5 7.5 7.5 7.3 7.3 7.3 7.3 6.1 6.1 6.1

5.5 5.5 5.4 5.4 5.4 5.4

12.5 12.5 12.5 12.5 12.5 12.5
12.5 12.5 12.0 12.0 12.0 11d 6.5 6.5 6.5 6.5 6.0 6.5 6.5 6.0

12.12.5

Business Class Libraries
MSL 8096, 8048 MSL 4048 MSL 2024 MSL 6000 Series 6.1 6.1 6.1 6.1 5.5 5.1 5.1 5.0 12.5 12.5

11.1 11.1 11.1 9.0

7.5 7.5 7.5 7.5

7.0 7.0 7.0 6.0

6.1 6.1 6.1 6.1

5.4 5.4 5.4 5.4

12.5 12.5 12.5 12.5

10d 2,4 10d 10d

2,4 2,4

6.5 6.5 6.5 9.2 9.0 6.5

6.0 6.0 6.0 4.5

12.12.5 5

Autoloaders
1/8 G2 Tape Autoloader (Ultrium 1760 SAS) 1/8 G2 Tape Autoloader (Ultrium 1760 SCSI) 1/8 G2 Tape Autoloader (Ultrium 920) 1/8 G2 Tape Autoloader (Ultrium 920 SAS) 1/8 G2 Tape Autoloader (Ultrium 448) 6.1 6.1 6.1 6.1 6.1 5.5 5.5 5.5 5.5 5.5 12.5 12.5 12.5 11.5 11.5 11.5 11.5 11.5 7.5 7.5 7.5 7.5 7.5 7.0 7.0 7.0 7.0 7.0 6.1 6.1

5.4 5.4 5.4 5.4 5.4

12.5 12.5 12.5 12.5 12.5

10d 3 10d 10d

9.2 9.2 9.2

9.0 9.0 9.0

6.5 6.5 6.5 6.5

6.0 6.0 6.0 6.0 6.0

11d 4 10d 3 9.9.0 6
NOTES: 1) Use the latest backup application maintenance release unless otherwise noted. Refer to the backup application vendor for specific operating system support, patches, builds, and drivers required to support HP tape automation and virtual library products. 2) Backup Exec version 10d and Device Driver Installer (DDI) version 20060615 or later are required. 3) Backup Exec version 10d and Device Driver Installer (DDI) version 20061015 or later are required. 4) Backup Exec version 11d and Device Driver Installer (DDI) version 20061215 or later are required.
5) CA ARCserve 12.0 and beyond only support Windows based media servers. 6) BENW 9.x Driver SET 2 required for Ultrium 448 1/8 G2 Autoloader support & multi-LUN support enabled on the SCSI HBA. 7) VLS models 6200, 6600, and 12000 EVA Gateway running software version 2.0.0 not currently supported with ARCserve 11.1, 11.5 or 12 running on Linux. See Customer Advisory "c01181673" for further details. 8) TSM 5.4.2 or later is required to support LTO4 tape drives. 9) Backup Exec version 12.5 and later supports Linux based media servers. 10) TSM 5.4.5 or later is required to support LTO4 drive emulation. TSM 5.5 does not currently support LTO4 drive emulation.

Page 14 of 44

Archiving Solution Partners

Software Partners

Application Atempo Time Navigator Enigma Data Solutions IDS & PARS Front Porch Digital DIVArchive Qstar HSM Quantum StorNext SGL FlashNet XenData Archive Series
Feature Advanced protection and archival solution Vendor neutral archiving solutions to preserve the value and integrity of information Content Storage Management system for digital media Provides data archive functionality and automigration High Performance Workflow and Intelligent Archiving Content storage and archive management Powerful, scalable digital archives
Link to Product Page Click Here Click Here Click Here Click Here Click Here Click Here Click Here

NOTES: 1) Refer to EBS Design Guide for configuration rules and guidelines. 2) 3rd Party adapters require HP drivers and firmware. 3) SC44Ge (416096-B21) is supported in the PCI Expansion Blade (448018-B21) 4) Third Party SCSI HBA support is for HP servers only.

4, 7 3, 8, 9 5, 6

2.72a2 5-5.30a2 5-2.10x1 5-2.10x1 2.02 9.1.3.11 9.1.7.17 9.1.7.17 1.1.0.8 1.1.0.8 1.1.0.8 2.72a2 5-5.30a2 5-2.10x1 5-2.10x1 2.02 9.1.3.11 9.1.7.17 9.1.7.17
2.72a2 5-5.30a2 5-2.10x1 5-2.10x1 2.02 9.1.3.11 9.1.7.17 9.1.7.17

2.72a2 5-5.30a2 5-2.10x1

2.02 9.1.3.11 9.1.7.17
2.72a2 5-5.30a2 5-2.10x1 5-2.10x1 2.08 9.1.3.11 9.1.7.65 9.1.7.65
2.08 9.1.3.11 9.1.7.65 9.1.7.65

2.08 9.1.3.11 9.1.7.65

5) All sp2 systems are required to run Storport.sys KB945119. Non-sp2 systems running applications othe than TSM require Storport.sys KB891793 (min) or KB916048 (recommended); systems running TSM require Storport.sys KB901371 6) Please reference ISV application installation/support documents for specific driver and patch requireme 7) See vendor website for additional details.
8) Refer to server QuickSpecs to determine which HBAs are supported. 9) Third party x86 servers supported with HP-branded adapters only. 10) Systems running TSM on WS2008 require Storport.sys KB953390. 11) ARCserve support requires MS patch KB943545.

Page 21 of 44

Windows (x86) (page 3 of 3)
Disk Array Multipath Support Windows MPIO 5 High Availability Windows (MSCS) NOTES: 1) Refer to EBS Design Guide for configuration rules and guidelines. 2) Refer to the EBS Design Guide for details on failover configurations. For Operating Systems not listed, please refer to the ISVs web page for supported High Availability configurations. 3) Not supported with TSM 5.3.x or later. 4) Support includes NAS9000 and NAS4000 platforms. 5) Windows Full-Feature MPIO failover support. Clusters sharing disk and tape on the same HBA require StorPort.

Page 22 of 44

Windows (Integrity)
Direct Attached and SAN Support Operating Systems 2 Windows Server 2003 (64-bit) Windows Server 2008 (64-bit) Servers HP Integrity Superdome and Mid-Range (rx7000-rx8000 Series, Integrity) HP Integrity Entry-Level (rx1000-rx6000 Series, Integrity) HP ProLiant c-Class BladeSystem 8Gb Fibre Channel Host Bus Adapters 1, 4 (HP Branded / 3rd Party) 81Q (AH400A) / QLogic QLE2560 (8G, PCI-e) & 82Q (AH401A) / QLogic QLE2562 (8G, PCI-e) EFI Windows Server 2003 StorPort Driver 5, 7 81E (AH402A) / Emulex LPe12000 (8G, PCI-e) & 82E (AH403A) / Emulex LPe12002 (8G, PCI-e) FW Windows Server 2003 StorPort Driver 5, 7 Windows Server 2008 StorPort Driver 5, 9 8Gb HP c-Class BladeSystem Fibre Channel Host Bus Adapters QMH2562 (451871-B21) (8G, PCI-e) for HP c-Class BladeSystem EFI Windows Server 2003 StorPort Driver 5, 7 Windows Server 2008 StorPort Driver 5, 9 LPe1205 (456972-B21) (8G, PCI-e) for HP c-Class BladeSystem FW Windows Server 2003 StorPort Driver 5, 7 Windows Server 2008 StorPort Driver 5, 9 4Gb Fibre Channel Host Bus Adapters 1, 4 (HP Branded / 3rd Party) FC2142SR (A8002A) / Emulex LPe1150 (4G, PCI-e) & FC2242SR (A8003A) / Emulex LPe11002 (4G, PCI-e) FW Windows Server 2003 StorPort Driver 5, 7 Windows Server 2008 StorPort Driver 5, 9 FC1142SR (AE311A) / QLogic QLE2460 ( , PCI-e) & AD300A / QLogic QLE2462 ( , PCI-e) ( ) g (4G, ) g (4G, ) EFI Windows Server 2003 StorPort Driver 5, 7 Windows Server 2008 StorPort Driver 5, 9 FC2143 (AD167A) / Emulex LP1150 (4G, PCI-X 2.0) & FC2243 (AD168A) / Emulex LP11002 (4G, PCI-X 2.0) FW Windows Server 2003 SCSIport Driver Windows Server 2003 StorPort Driver 5, 7 Windows Server 2008 StorPort Driver 5, 9 AB429A / Qlogic QLA2460 (4G, PCI-X 2.0) & AB379A/B / Qlogic QLA2462 (4G, PCI-X 2.0) EFI Windows Server 2003 StorPort Driver 5, 7 Windows Server 2008 StorPort Driver 5, 9 4Gb HP c-Class BladeSystem Fibre Channel Host Bus Adapters LPe1105 (403621-B21) (4G, PCI-e) for HP c-Class BladeSystem FW Windows Server 2003 StorPort Driver 5, 7 Windows Server 2008 StorPort Driver 5, 9 QMH2462 (403619-B21) (4G, PCI-e) for HP c-Class BladeSystem EFI Windows Server 2003 StorPort Driver 5, 7 Windows Server 2008 StorPort Driver 5, 9 SAS Host Bus Adapters and Controllers P700m (3Gb, PCI-e, 8 channel) SCSI Host Bus Adapters 8 A7173A (Ultra320, PCI-X, 2 channel) Disk Array Multipath Support Windows MPIO 6 High Availability Windows (MSCS)

1, 6 1, 6

IBM Tivoli Storage Manager sp2 sp2
Symantec Backup Exec sp2 sp2
Symantec Veritas NetBackup sp2 sp2 sp2

sp2 sp2 sp2

2.02 9.1.7.17 9.1.7.17 1.00a12 7-2.10x1 7-2.10x1
2.02 9.1.7.17 9.1.7.17 1.00a12 7-2.10x1 7-2.10x1 1.1.0.8 1.1.0.8 1.1.0.8
2.02 9.1.7.17 9.1.7.17 1.00a12 7-2.10x1 7-2.10x1 1.1.0.8 1.1.0.8

2.08 9.1.7.65 9.1.7.65

2.08 9.1.7.65 9.1.7.65 1.10a5 7-2.10x1 7-2.10x1
1.10a5 1, 6 7-2.10x1 Windows Server 2003 StorPort Driver 1, 7 7-2.10x1 Windows Server 2008 StorPort Driver 4, 5 (HP Branded / 3rd Party) 4Gb Fibre Channel Host Bus Adapters FC2142SR (A8002A) / Emulex LPe1150 (4G, PCI-e) & FC2242SR (A8003A) / Emulex LPe11002 (4G, PCI-e) FW 2.72a2 7-2.10x1 Windows Server 2003 StorPort Driver 1, 6 1, 7 7-2.10x1 Windows Server 2008 StorPort Driver FC1142SR (AE311A) / QLogic QLE2460 (4G, PCI-e) & FC1242SR (AE312A) / QLogic QLE2462 (4G, PCI-e) BIOS 2.02 1, 6 9.1.7.17 Windows Server 2003 StorPort Driver 1, 7 9.1.7.17 Windows Server 2008 StorPort Driver 41B (AP767A) / Brocade 415 (4G, PCI-e) & 42B (AP768A) / Brocade 425 (4G, PCI-e) BIOS Windows Server 2003 StorPort Driver 1, 7 Windows Server 2008 StorPort Driver FC2143 (AD167A) / Emulex LP1150 (4G, PCI-X 2.0) & FC2243 (AD168A) / Emulex LP11002 (4G, PCI-X 2.0) FW 2.72a2 7-2.10x1 Windows Server 2003 StorPort Driver 1, 6 1, 7 7-2.10x1 Windows Server 2008 StorPort Driver FC1143 (AB429A) / QLogic QLA2460 (4G, PCI-X 2.0) & FC1243 (AE369A) / QLogic QLA2462 (4G, PCI-X 2.0) BIOS 2.02 1, 6 9.1.7.17 Windows Server 2003 StorPort Driver 1, 7 9.1.7.17 Windows Server 2008 StorPort Driver NOTES: 1) Please reference ISV application installation/support documents for specific driver and patch requirements. 2) Please reference your ISV support matrices for supported application and operating system version compatibility. 3) Requires MS hotfix 943545 to see tape devices. 4) Refer to EBS Design Guide for configuration rules and guidelines.
2.72a2 7-2.10x1 7-2.10x1 2.02 9.1.7.17 9.1.7.17
2.72a2 7-2.10x1 7-2.10x1 2.02 9.1.7.17 9.1.7.17 1.1.0.8 1.1.0.8 1.1.0.8
2.72a2 7-2.10x1 7-2.10x1 2.02 9.1.7.17 9.1.7.17 1.1.0.8 1.1.0.8
5) 3rd Party adapters require HP drivers and firmware. 6) All non-sp2 systems running applications other than Tivoli require updated Storport.sys KB903081 (minimum) or KB916048 (recommended); systems running TSM require Storport.sys KB901371. All sp2 systems require Storport.sys KB945119. 7) Systems running Tivoli with WS2008 require Storport.sys KB953390.

Page 24 of 44

Windows (x64) (page 2 of 2)
4Gb HP c-Class BladeSystem Fibre Channel Host Bus Adapters LPe1105 (403621-B21) (4G, PCI-e) for HP c-Class BladeSystem FW Windows Server 2003 StorPort Driver 1, 6 Windows Server 2008 StorPort Driver 1, 10 QMH2462 (403619-B21) (4G, PCI-e) for HP c-Class BladeSystem BIOS Windows Server 2003 StorPort Driver 1, 6 Windows Server 2008 StorPort Driver 1, 10 SAS Host Bus Adapters and Controllers P212, P410, P411 & P700m (3Gb, PCI-e, 8 channel) SC44Ge (3Gb, PCI-e, 4 channel)

8. 9. 11 8, 9

2.72a2 7-2.10x1 7-2.10x1 2.08 9.1.7.65 9.1.7.65
SCSI Host Bus Adapters and Controllers
AH627A (HP U320e, Ultra320, PCI-e, 2 channel) 412911-B21 (HP SC11Xe, Ultra320, PCI-e, 1 channel) 374654-B21 (Ultra320, PCI-X, 1 channel) SCSI - Third Party HBAs and Integrated Controllers Adaptec 29320ALP-R (Ultra320, PCI-X, 1 channel) ATTOTech UL4D (Ultra320, PCI-X, 2 channel) ATTOTech UL5D ( (Ultra320, PCI-e, 2 channel) ) Disk Array Multipath Support Windows MPIO High Availability Windows (MSCS)
NOTES: 1) Please reference ISV support documents for specific driver and patch requirements. 2) ARCserve support requires MS patch KB943545. 3) Refer to the EBS Design Guide for details on failover configurations. For Operating Systems not listed, please refer to the ISVs web page for supported High Availability configurations. 4) Refer to EBS Design Guide for configuration rules and guidelines. 5) 3rd Party adapters require HP drivers and firmware. 6) All non-sp2 systems running applications other than Tivoli require updated Storport.sys KB903081 (minimum) or KB916048 (recommended); systems running Tivoli require Storport.sys KB901371. All sp2 systems are required to run Storport.sys KB945119. 7) See vendor website for additional details. 8) Refer to server QuickSpecs to determine which HBAs are supported 9) Third party x86 servers supported with HP-branded adapters only 10) Systems running TSM on WS2008 require Storport.sys KB953390 11) SC44Ge (416096-B21) is supported in the PCI Expansion Blade (448018-B21) 12) Third Party SCSI HBA support for HP servers only

Page 25 of 44

Linux (x86) 4 (page 1 of 2)
HP Data Protector CA ARCserve
Direct Attached and SAN Support Operating Systems 2 RHEL [AS/ES/WS] 4.0 (32-bit)
IBM Tivoli Storage Manager 8 Update 7 Update 3 SP4 SP2
RHEL [AS/ES/WS] 5.0 (32-bit) SUSE SLES 9 (32-bit) SUSE SLES 10 (32-bit) Servers HP ProLiant HP ProLiant c-Class BladeSystem HP ProLiant p-Class BladeSystem Third Party X86
Update 7 Update 2 SP4 SP2
Update 8 Update 3 SP4 SP2
Update 7 Update 3 SP4 SP2

8Gb Fibre Channel Host Bus Adapters 3, 5 (HP Branded / 3rd Party) 81Q (AK344A) / QLogic QLE2560 (8G, PCI-e) & 82Q (AJ764A) / QLogic QLE2562 (8G, PCI-e) BIOS 2.02 RHEL 4.0 driver & SUSE SLES 9 driver 8.02.11 RHEL 5.0 driver & SUSE SLES 10 driver 8.02.11 81E (AJ762A) / Emulex LPe12000 (8G, PCI-e) & 82E (AJ763A) / Emulex LPe12002 (8G, PCI-e) FW 1.00a12 RHEL 4.0 driver & SUSE SLES 9 driver 8.0.16.40 RHEL 5.0 driver & SUSE SLES 10 driver 8.2.0.22_p4 81B (AP769A) / Brocade 815 (8G, PCI-e) & 82B (AP770A) / Brocade 825 (8G, PCI-e) BIOS RHEL 5.0 driver & SUSE SLES 10 driver 8Gb HP c Class BladeSystem Fibre Channel Host Bus Adapters 3, 5 c-Class QMH2562 (451871-B21) (8G, PCI-e) for HP c-Class BladeSystem BIOS 2.08 RHEL 4.0 driver & SUSE SLES 9 driver 8.02.11 LPe1205 (456972-B21) (8G, PCI-e) for HP c-Class BladeSystem FW RHEL 5.0 driver & SUSE SLES 10 driver 1.10a5 8.2.0.22_p4
2.02 8.02.11 8.02.11 1.00a12 8.0.16.40 8.2.0.22_p4 1.1.0.8 1.1.0.8
2.02 8.02.11 8.02.11 1.00a12 8.0.16.40 8.2.0.22_p4
2.08 8.02.11 1.10a5 8.2.0.22_p4
4) EBS is not dependent on specific kernel errata levels. For required/supported kernel errata, refer to your online storage array and backup application support documentation. 5) 3rd Party adapters require HP drivers and firmware.
NOTES: 1) SAN Media server supported with CA ARCserve 11.5 & prior. Version 12 only supports backup of LAN clients 2) Please reference your ISV support matrices for supported application and operating system version compatibility. 3) Refer to EBS Design Guide for configuration rules and guidelines.
6) SLES 9 SP2 is not supported due to tape device discovery issues. 7) RHEL kernel versions include support for Oracle Enterprise Linux. 8) TSM Server 6.1 not supported. TSM Storage Agent ver 6.1 supported for RHEL5 and SLES10 only.

Page 26 of 44

Linux (x86)

(page 2 of 2)

HP Data Protector CA ARCserve 1 EMC NetWorker IBM Tivoli Storage Manager Symantec Backup Exec Symantec Veritas NetBackup
4Gb Fibre Channel Host Bus Adapters 3, 5 (HP Branded / 3rd Party) FC2142SR (A8002A) / Emulex LPe1150 (4G, PCI-e) & FC2242SR (A8003A) / Emulex LPe11002-M4 (4G, PCI-e) FW 2.72a2 RHEL 4.0 driver & SUSE SLES 9 driver 8.0.16.40 RHEL 5.0 driver & SUSE SLES 10 driver 8.2.0.22_p4 FC1142SR (AE311A) / QLogic QLE2460 (4G, PCI-e) & FC1242SR (AE312A) / QLogic QLE2462 (4G, PCI-e) BIOS 2.02 RHEL 4.0 driver & SUSE SLES 9 driver 8.02.11 RHEL 5.0 driver & SUSE SLES 10 driver 8.02.11 41B (AP767A) / Brocade 415 (4G, PCI-e) & 42B (AP768A) / Brocade 425 (4G, PCI-e) BIOS RHEL 5.0 driver & SUSE SLES 10 driver FC2143 (AD167A) / Emulex LP1150 (4G, PCI-X 2.0) & FC2243 (AD168A) / Emulex LP11002 (4G, PCI-X 2.0) FW 2.72a2 RHEL 4.0 driver & SUSE SLES 9 driver 8.0.16.40 RHEL 5.0 driver & SUSE SLES 10 driver 8.2.0.22_p4 FC1143 (AB429A) / QLogic QLA2460 (4G, PCI-X 2.0) & FC1243 (AE369A) / QLogic QLA2462 (4G, PCI-X 2.0) BIOS 2.02 RHEL 4.0 driver & SUSE SLES 9 driver 8.02.11 RHEL 5.0 driver & SUSE SLES 10 driver 8.02.11 4Gb HP c-Class BladeSystem Fibre Channel Host Bus Adapters 3, 5 LPe1105 (403621-B21) (4G, PCI-e) for HP c-Class BladeSystem FW 2.72a2 RHEL d i 4.0 driver & SUSE SLES 9 d i driver 8.0.16.40 RHEL 5.0 driver & SUSE SLES 10 driver 8.2.0.22_p1 QMH2462 (403619-B21) (4G, PCI-e) for HP c-Class BladeSystem BIOS 1.26 RHEL 4.0 driver & SUSE SLES 9 driver 8.01.07.25 RHEL 5.0 driver & SUSE SLES 10 driver 8.01.07.25 SAS Host Bus Adapters and Controllers P212, P410, P411 & P700 (3Gb, PCI-e, 8 channel) SC44Ge (3Gb, PCI-e, 4 channel) 8, 9, 10 SCSI Host Bus Adapters 8, 9 AH627A (HP U320e, Ultra320, PCI-e, 2 channel) 412911-B21 (HP SC11Xe, Ultra320, PCI-e, 1 channel) 374654-B21 (Ultra320, PCI-X, 1 channel) SCSI - Third Party HBAs and Integrated Controllers Adaptec 29320ALP-R (Ultra320, PCI-X, 1 channel) ATTOTech UL4D (Ultra320, PCI-X, 2 channel) ATTOTech UL5D (Ultra320, PCI-e, 2 channel) Disk Array Multipath Support 3 Device Mapper Emulex Multipulse (2.6 kernels only) QLogic Native Multi-Path for Linux (2.4 kernel) QLogic Native Multi-Path for Linux (2.6 kernel)

2.72a2 8.0.16.40 8.2.0.22_p4 2.02 8.02.11 8.02.11 1.1.0.8 1.1.0.8 2.72a2 8.0.16.40 8.2.0.22_p4 2.02 8.02.11 8.02.11
2.72a2 8.0.16.40 8.2.0.22_p4 2.02 8.02.11 8.02.11
2.72a2 8.0.16.40 8.2.0.22_p4 2.02 8.02.11 8.02.11 1.1.0.8 1.1.0.8
2.72a2 8.0.16.40 8.2.0.22_p1 1.26 8.01.07.25 8.01.07.25
4.3.0 2.1.9 7.07.05 8.01.07.25

4.3.0 2.2.20 8.01.07.25

4.3.0 2.2.20 7.07.05 8.01.07.25
NOTES: 1) SAN Media server supported with CA ARCserve 11.5 & prior. Ver. 12 only supports backup of LAN clients 2) Third Party SCSI HBA support is for HP servers only 5) 3rd Party adapters require HP drivers and firmware. 3) Refer to EBS Design Guide for configuration rules and guidelines. 6) SP2 for SLES 9 is not supported. 4) EBS is not dependent on specific kernel errata levels. For required/supported kernel 7) See vendor website for additional details. errata, refer to your online storage array and backup application support documentation.
8) Refer to server QuickSpecs to determine HBA supported 9) Third party x86 servers supported with HP-branded adapters only 10) SC44Ge (416096-B21) is supported in the PCI Expansion Blade (448018-B21)

Page 27 of 44

Linux (Integrity) 3,5
Direct Attached and SAN Support Operating Systems 7 RHEL [AS/ES/WS] 4.0 (64-bit) RHEL [AS/ES/WS] 5.0 (64-bit) 7, 8 SUSE SLES 9 (64-bit) SUSE SLES 10 (64-bit) Servers HP Integrity Superdome and Mid-Range (rx7000-rx8000 Series, Integrity) HP Integrity Entry-Level (rx1000-rx6000 Series, Integrity) HP ProLiant c-Class BladeSystem 4Gb Fibre Channel Host Bus Adapters 4 (HP Branded / 3rd Party) FC2142SR (A8002A) / Emulex LPe11000 (4G, PCI-e) & FC2242SR (A8003A) / Emulex LPe11002 (4G, PCI-e) FW 2.72a2 RHEL 4.0 driver & SUSE SLES 9 driver 8.0.16.40_p2 RHEL 5.0 driver & SUSE SLES 10 driver 8.2.0.22_p4 FC1142SR (AE311A) / QLogic QLE2460 (4G, PCI-e) & AD300A / QLogic QLE2462 (4G, PCI-e) EFI 2.00 RHEL 4.0 driver & SUSE SLES 9 driver 8.02.11 RHEL 5.0 driver & SUSE SLES 10 driver 8.02.11 FC2143 (AD167A) / Emulex LP1150 (4G, PCI-X 2.0) & FC2243 (AD168A) / Emulex LP11002 (4G, PCI-X 2.0) FW 2.72a2 RHEL 4.0 driver & SUSE SLES 9 driver 8.0.16.40_p2 RHEL 5.0 driver & SUSE SLES 10 driver 8.2.0.22_p4 AB429A / QLogic QLA2460 (4G, PCI-X 2.0) & AB379A / QLogic QLA2462 (4G PCI X 2 0) QL i (4G PCI X 2 0) QL i (4G, PCI-X 2.0) EFI 2.00 RHEL 4.0 driver & SUSE SLES 9 driver 8.02.11 RHEL 5.0 driver & SUSE SLES 10 driver 8.02.11 QMH2462 (4G, PCI-e) for HPc-Class BladeSystem EFI 1.09 RHEL 5.0 driver & SUSE SLES 10 driver 8.01.07.25 SAS Host Bus Adapters 6 P700m (3Gb, PCI-e, 8 channel) SC44Ge (3Gb, PCI-e, 4 channel) SCSI Host Bus Adapters 6 A7173A (Ultra320, PCI-X, 2 channel) Disk Array Multipath Support 4 Device Mapper Emulex Multipulse (2.6 kernels only) QLogic Native Multi-Path for Linux (2.4 kernel) QLogic Native Multi-Path for Linux (2.6 kernel)

4) Supported with Solaris 9 only. 5) Supported with Solaris 10 only. 6) Supported with Solaris 10 x86/x64 only.
7) Supported with Solaris 10 x64 only. (AMD64 and Intel EM64T) 8) Supported with Solaris 10 on Sun Blade platform only. 9) TSM Server and Storage Agent ver 6.1 supported for Solaris 10 only.

Page 33 of 44

Solaris (page 2 of 2)
Direct Attached and SAN Support SAS Host Bus Adapters SG-XPCI8SAS-E-Z (PCI-X) SG-XPCIE8SAS-E-Z (PCI-e) SCSI Host Bus Adapters SGXPCI1SCSILM320-Z (Ultra320, PCI-X, 1 Channel) SG-XPCIE2SCSIU320Z (Ultra320, PCI-e, 2 Channel) Disk Array Multipath Support Solaris MPxIO VERITAS DMP High Availability

VERITAS Cluster Server

NOTES: 1) Refer to EBS Design Guide for configuration rules and guidelines. 2) Refer to the EBS Design Guide for details on failover configurations. For Operating Systems not listed, please refer to the ISVs web page for supported High Availability configurations.
3) Supported with Solaris 10 only. 4) Please refer to Customer Advisory "c01536454" for required configuration details.

Page 34 of 44

Tru64 Unix
Direct Attached and SAN Support Operating Systems 2 Tru64 5.1A 5 Tru64 5.1B 5 Servers HP AlphaServer 2Gb Fibre Channel Host Bus Adapters FCA2684 / FCA2684 DC (2G, PCI-X) FW Tru64 Driver FCA2354 (2G, PCI-X) FW Tru64 Driver FCA2354 (2G, PCI-X) FW Tru64 Driver
HP Data Protector 5.1A pk6 5.1B-4

EMC NetWorker 7

Symantec Veritas NetBackup 5.1A pk6 5.1B-4

5.1A pk6 5.1B-4

1.91x6 2.17 3.93a0 2.17 1.91x6 2.17
SCSI Host Bus Adapters 6 3X-KXPEA-DB (Ultra160, PCI-X, 2 channel) Disk Array Multipath Support Tru64 Multipath High Availability 3 Tru64 (TruCluster) For the latest information on the enterprise backup strategy for HP
OpenVMS, view th strategy presentation O VMS i the t t t ti

Native

OpenVMS
For the latest information on the enterprise backup strategy for HP OpenVMS click the appropriate links below: Enterprise Backup Utilities and Products
http://h71000.www7.hp.com/openvms/storage/enterprise.html
Tape and Virtual Library Connectivity
http://h71000.www7.hp.com/openvms/storage/smstape_matrix.html

Supported Networking

HP StorageWorks Enterprise Backup Solution example configurations
Part number: 5697-6726 Second edition: May 2007
Copyright 2007 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information is provided as is without warranty of any kind and is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft, Windows, Windows NT, and Windows XP are U.S. registered trademarks of Microsoft Corporation. Oracle is a registered U.S. trademark of Oracle Corporation, Redwood City, California. UNIX is a registered trademark of The Open Group.
Enterprise Backup Solution example configurations

About this document

This guide provides example configurations for the HP StorageWorks Enterprise Backup Solution (EBS). The examples include direct attach with LAN client connectivity, as well as basic and extended Storage Area Networks (SAN). While this document does not encompass all possible EBS configurations, it should provide information to help build tape solutions to meet specific business needs. All hardware items shown in this example guide are listed in the EBS Compatibility Matrix. The HP StorageWorks Enterprise Backup Solution (EBS) Compatibility Matrix provides information for designing data protection solutions, including backup/restore and archiving, that scale from entry-level workgroups to enterprise-level data centers. It includes support for Direct Attach SCSI (DAS), Direct Attach Fibre (DAF), and Storage Area Network (SAN).

Other documentation

In addition to this guide, HP provides the following corresponding information, available via the HP website at http://www.hp.com/go/ebs: EBS Compatibility Matrix HP StorageWorks Enterprise Backup Solution Design Guide Backup application implementation guides Extended Data Protection Solutions HP StorageWorks SAN Design Reference Guide HP StorageWorks Partitioning in an EBS Environment Implementation Guide HP StorageWorks Implementing Mixed Media in HP StorageWorks ESL and MSL Tape Library Application Notes For detailed cabling instructions, see your specific HP StorageWorks or HP Server product guides. These guides are available at the following locations on the HP website: http://www.hp.com/go/tape http://www.hp.com/go/arrays http://www.hp.com/go/servers

Contents

Point-to-Point configuration, page 4 Shared tape library configuration with HP StorageWorks MSA1500 Small Business SAN configuration, page 6 Shared tape library configuration with heterogeneous servers, page 8 Multi-path to disk configuration, page 10 Disk to disk to tape configuration, page 12 Virtual tape configuration, page 14 SAN zoning configuration, page 16 Multi-Protocol Router configuration, page 17 Library partitioning configuration, page 18 Extended SAN configuration, page 19 Continuous Access configuration, page 21 Virtual Library System EVA Gateway configuration, page 23 Encryption Appliance configuration, page 25 iSCSI Virtual Library System configuration, page 27 VMware Consolidated Backup configuration, page 28

Point-to-Point configuration
Environment Typical usage Description Direct Attach SCSI (DAS) and Direct Attach Fibre (DAF) Local and network client backup. The following examples (Figures 1 and 2) represent DAS and DAF configurations. Each client transmits its data to the backup server over the LAN that then writes the data to the locally attached tape device. The tape device can be attached with either SCSI or Fibre Channel. This solution provides data protection for a large number of clients through a dedicated backup server.

Figure 1

Description, continued

Backup data flows:

Step From. Local internal disk over the LAN Backup servers To. Backup servers Direct attached tape drives

Figure 2

Shared tape library configuration with HP StorageWorks MSA1500 Small Business SAN configuration
Environment Typical usage Description Storage Area Network (SAN) Low cost business SAN array with added tape backup and restore option. The following examples (Figures 3 and 4) represent the HP StorageWorks MSA1500 configuration with a shared tape library. Each Windows server can access the MSA1500 and the tape library through a single Host Bus Adapter (HBA). Each Windows server has direct access to the tape drives within the library, and tape access is controlled by advanced features within the backup application. Sharing a tape library eliminates the need for multiple tape systems connected to each server, thereby simplifying data protection management and reducing total cost of ownership. For detailed information on the MSA1500 array, see: http://www.hp.com/go/msa.

Figure 3

Step From. MSA1500 disk array Each server To. Each SAN-based server Shared SAN-attached tape library

Figure 4

Shared tape library configuration with heterogeneous servers
Environment Typical usage Description Storage Area Network (SAN) Shared tape library across multiple servers. The following examples (Figures 5 and 6) represent a SAN configuration consisting of multiple servers with multiple operating systems, connected to multiple disk arrays and a shared tape library. Each server can access the disk arrays and the tape library through a single Host Bus Adapter (HBA). Each server has direct access to the tape drives within the library, and tape access is controlled by advanced features within the backup application. Sharing a tape library eliminates the need for multiple tape systems connected to each server, thereby simplifying data protection management and reducing total cost of ownership.

Figure 5

Step From. Each disk array Each server To. Each SAN-based server Shared SAN-attached tape library

Figure 6

Multi-path to disk configuration
Environment Typical usage Description Storage Area Network (SAN) High availability storage solution. The following examples (Figures 7 and 8) represent a shared tape library configuration (see Figure 5) with HP StorageWorks Secure Path, or other multi-pathing software, installed on each server. The multi-pathing software provides the servers with multiple access paths to disk storage, allowing backups and restores to continue in the event of a disk path failure. This solution provides 24/7 data availability in the SAN environment. NOTE: Regardless of operating system environment, multi-path to tape is not supported (only one of the two configured paths can access the tape devices at the same time).

Figure 7

Step From. Each disk array Each server To. Each SAN-based server SAN-attached tape library load, balancing the tapes between SANs

Figure 8

Disk to disk to tape configuration
Environment Typical usage Description Storage Area Network (SAN) Staging of backup data to a host-managed, low cost disk to facilitate quick restores and enable long term archival storage. The following examples (Figures 9 and 10) represent a shared tape library configuration (see Figure 5) consisting of multiple servers, primary disk storage (EVA8000), staging disk storage (MSA1500), and a tape library. The backup application backs up the primary disk data to the staging disk, allowing for quick restores of single files. Each host writes to its own file system on the low-cost array. All file transfers are controlled by backup software, and transfer to tape occurs through servers that sent data. Data on the staging disk can be archived to tape for off-site storage. This solution enhances typical recovery processes and provides data protection in a cost efficient solution.

Figure 9

Step Backup Archive to Tape From. Each disk array Each server Low cost disk array Each server To. Each SAN-based server Low cost disk array Each server SAN-attached tape library

Figure 10

Virtual tape configuration
Environment Typical usage Storage Area Network (SAN) Integration of Virtual Library Systems (disk emulating tape) into existing backup environments to facilitate quick restores and support for slow SAN clients enabling long-term, archival storage. The following examples (Figures 1 and 12) show the integration of a Virtual Library 1 System (VLS) in a SAN environment consisting of multiple servers, primary disk storage, and a tape library. The Virtual Library System uses a controller and low-cost disk to emulate a physical tape library. The backup application backs up the data to the Virtual Library System as if it were a physical tape library, allowing for quick restores of single files. When physical tapes are required for off-site storage, the data on the Virtual Library System is copied to the tape library by the backup application using an alternate server, freeing up the application host from this process. This solution allows easy integration of disk technologies into existing backup environments, requiring no unique backup application features.

Description

Figure 1 1
Step Backup From. Each disk array Each server SAN-attached virtual library system Each server (or an alternate media copy server) To. Each SAN-based server SAN-attached virtual library system Each server (or an alternate media copy server) SAN-attached tape library

Archive to Tape

Figure 12

SAN zoning configuration

Environment Typical usage Description Storage Area Network (SAN) Enable or limit access between SAN initiators and targets. This example represents a shared tape library in a zoned configuration. Zoning is a feature of the switch that creates isolated groups of connections between specific components in the SAN. Figure 13A illustrates the physical interconnection of each component in the SAN. Each zone is illustrated below, and the members of that zone are as follows: Figure 13B Port A of Windows server #1 Port A of the tape library Port B of the tape library Figure 13C Port B of Windows server #2 Port B of the disk array Figure 13D Port A of Windows server #2 Port A of the disk array Port A of the tape library The use of zoning controls the access to storage on the SAN and limits the activity that the server is exposed to on the SAN. Effective use of zoning provides security and simplifies complex SAN management.
NOTE: The dashed outlines and dashed connection lines represent the physical components and connections that are not part of the zone.
Multi-Protocol Router configuration
Environment Typical usage Description Multiple Storage Area Networks (SAN) Sharing storage devices between independent SANs. This example (Figure 14) represents a configuration consisting of independent fabrics, or SAN islands, utilizing the Multi-Protocol Router (MPR), a switch-type device. Multiple servers (highlighted with halos and members of the backup configuration) connect to their local switch within their independent fabric. Through the MPR, each server can connect to the shared tape library as if it were in the same independent fabric. This solution enables the interconnection of devices between SAN fabrics without merging those fabrics, thereby providing a more secure, flexible storage networking foundation.

Figure 14

Enterprise Backup Solution example configurations 17
Library partitioning configuration
Environment Typical usage Description
Storage Area Network (SAN) Multiple applications sharing a single tape library. This example (Figure 15) represents a configuration consisting of two independent backup applications accessing a single tape library. Utilizing the partitioning feature in the advanced version of Secure Manager for Tape Libraries and HP StorageWorks Command View TL, each backup application is presented with a logical library comprised of a subset of drives and slots of the physical library. Each application accesses its logical library independent of the other application. With tape library partitioning, multiple backup applications can share a single tape library, thereby increasing flexibility in the data center and lowering total cost of ownership. For detailed support, see HP StorageWorks Partitioning in an EBS Environment Implementation Guide at: http://www.hp.com/go/ebs.

Figure 15

Extended SAN configuration
Environment Typical usage Description Storage Area Network (SAN) Off-site backup and disaster recovery. The following examples (Figures 16 and 17) show a shared tape library configuration (see Figure 5) that uses SAN extension technologies to allow connectivity between remote sites. Data is read from the disk storage array located at site A and written to the tape storage library located at site B over the extended network link. While Fibre Channel over IP (FCIP) and Wave Division Multiplexing (WDM) allow connectivity over very long distances, Long-wave Small Formfactor Plugables (SFPs) can accommodate distances of 10-35 km. This solution illustrates a variety of SAN extension technologies, providing off-site connectivity for remote backup and disaster recovery.

Figure 16

Enterprise Backup Solution example configurations 19
Step From. Each disk array Each server To. Each SAN-based server Extended SAN-attached tape library

Figure 17

Continuous Access configuration
Environment Typical usage Description Storage Area Network (SAN) Disaster tolerance, business continuity. The following examples (Figures 18 and 19) represent a SAN configuration utilizing Continuous Access EVA, providing the ability to continuously replicate data from the disk array located at site A to the remote disk array located at site B. By creating a snapshot of the data at site B and presenting this data to a server at site B, this data can be backed up to the library at site B, thereby creating a remote backup of the data from site A. Continuous Access EVA utilizes multiple SAN extension technologies to overcome the distance limitations of a typical Fibre Channel connection. Continuous Access EVA is a complete disaster-tolerant storage solution guaranteeing data integrity if a storage system or site fails.

Figure 18

Step 3 From. Disk array on Site A Snapshot of replicated LUNs Each DR server on Site B To. Disk array on Site B Each disaster recovery (DR) server on Site B SAN-attached tape library

Figure 19

Virtual Library System EVA Gateway configuration
Environment Typical usage Storage Area Network (SAN) Integration of disk-assisted backup into existing backup environments to facilitate quick restores and support for slow SAN clients enabling long-term, archival storage. The following examples (Figures 20 and 21) show the integration of a Virtual Library System (VLS) EVA Gateway in a SAN environment, consisting of: multiple servers, primary disk storage, and a tape library. The Virtual Library System uses multiple clustered controllers and the HP Enterprise Virtual Array (EVA) to emulate large physical tape libraries. The backup application backs up the data to the Virtual Library System as if it were a physical tape library, allowing for quicker restores of single files and simultaneously restores files, even when backups are running. When physical tapes are required for off-site storage, the data on the Virtual Library System is copied to the tape library by the backup application using an alternate server, freeing up the application host from this process. This solution allows easy integration of disk technologies into existing backup environments, requiring no unique backup application features.

Figure 20

Enterprise Backup Solution example configurations 23
Step 1 Backup 4 Archive to Tape From. Primary disk array Each server SAN-zoned VLS Gateway SAN-zoned back-end EVA array SAN-zoned VLS Gateway Each server (or an alternate media copy server) To. Each SAN-based server SAN-zoned VLS Gateway SAN-zoned back-end EVA array SAN-zoned VLS Gateway Each server (or an alternate media copy server) SAN attached physical tape library

Figure 21

Encryption Appliance configuration
Environment Typical usage Description Storage Area Network (SAN) Integration of encryption tape appliances into existing backup environments to facilitate security protection of data on tape. The following examples (Figures 22 and 23) show the integration of encryption tape appliances into a SAN environment consisting of multiple servers, primary disk storage, and a tape library. The encryption appliances are zoned into the SAN to allow only the backup data to flow through the appliance. This configuration allows for easy control over which servers and tape drives are used for encryption and which are not. See http://www.hp.com/go/ebs for whitepapers on how to integrate these appliances into a SAN backup environment.

Figure 22

Step 3 From. Primary disk array Each server SAN-zoned encryption appliance To. Each SAN-based server SAN-zoned Encryption Appliance SAN-attached physical tape library

Figure 23

iSCSI Virtual Library System configuration
Environment Typical usage Description Local Area Network (iSCSI LAN) Integration of disk-assisted backup into existing backup environments to facilitate quick restores and support for slow LAN clients enabling long-term, archival storage. This example (Figure 24) shows the integration of an iSCSI Virtual Library System (VLS) into a LAN environment consisting of multiple servers, local internal disk storage, and an external physical tape drive. The iSCSI VLS allows each server to back up to its own virtual tape library over the iSCSI LAN. The backup application backs up the data to the Virtual Library System as if it were a physical tape library, allowing for quick restores of single files. When physical tapes are required for off-site storage, the data on the Virtual Library System is copied to the tape library by the backup application using an alternate server, freeing up the application host from this process. This solution allows easy integration of disk technologies into existing backup environments, requiring no unique backup application features. Backup data flows:
Step Backup Archive to Tape 3 From. Each servers Local internal disk iSCSI LAN Virtual Library Systems Alternate media copy server To. iSCSI LAN Virtual Library Systems Each server (or an alternate media copy server, if supported by backup application) Locally attached physical tape library

Figure 24

Enterprise Backup Solution example configurations 27
VMware Consolidated Backup configuration
Environment Typical usage Storage Area Network (SAN) VMware Consolidated Backup (VCB) provides a set of drivers and scripts that enable SAN backup/recovery of any running supported operating system virtual machines (VM) by one or more dedicated Microsoft Windows 2003 proxy server using an industry-standard backup agent. The following examples (Figures 25, 26, and 27) show the integration of VMware Consolidated Backup (v3.0.1) in a SAN environment consisting of multiple ESX servers (Blades), with each Blade server running 3 virtual machines: one Linux; one Windows; and one x86 Solaris, a dedicated VCB Server, primary disk storage Virtual Tape Library, and a physical tape library.

Figure 25

Figure 26 shows how the data flows for both full and incremental file level backup (for virtual machines running Microsoft Windows operating system). VCB accomplishes this over the SAN by creating a host-based snapshot of the running VM onto the same LUN that its data currently resides (there must be adequate free space), then presenting that LUN to the dedicated VCB server where the backup software is running. The backup software performs a normal full or incremental backup to a SAN-attached Virtual Tape Library or Physical Tape Library. Backup data flows:
Step From. 3 Virtual Machine File System (VM FS) Snapshot VCB server running backup application To. Host-based snapshot on same LUN SAN-based VMware Consolidated Backup server (VCB) Either a SAN-based Virtual Tape Library or Physical Tape Library

Figure 26

Enterprise Backup Solution example configurations 29
Figure 27 shows how the data flows for Image level backups (for virtual machines running any operating system). This is accomplished by make a full copy of the running Virtual Machine over the SAN onto disk space located on the dedicated VCB Backup server (there must be adequate free space). Once the full copy has completed, the backup software running on the VCB Backup server performs a normal image backup to a SAN-attached Virtual Tape Library or Physical Tape Library. Backup data flows:
Step From. Virtual Machine File System (VM FS) VCB server running backup application To. SAN-based VMware Consolidated Backup server (VCB) - FULL COPY Either a SAN-based Virtual Tape Library or Physical Tape Library

Figure 27