c00375285 Enterprise Backup Solution

8/9/2019 c00375285 Enterprise Backup Solution

1/30

HP StorageWorks

Enterprise Backup Solutionexample configurations

Part number: 5697-6726Second edition: May 2007


2/30

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 ofmerchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequentialdamages 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, ortranslated into another language without the prior written consent of Hewlett-Packard. The information is provided as is without warranty of anykind and is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statementsaccompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable fortechnical 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


3/30

Enterprise Backup Solution example configurations 3

About this documentThis guide provides example configurations for the HP StorageWorks Enterprise Backup Solution (EBS). Theexamples include direct attach with LAN client connectivity, as well as basic and extended Storage AreaNetworks (SAN). While this document does not encompass all possible EBS configurations, it shouldprovide information to help build tape solutions to meet specific business needs. All hardware items shownin this example guide are listed in the EBS Compatibility Matrix. The HP StorageWorks Enterprise BackupSolution (EBS) Compatibility Matrix provides information for designing data protection solutions, includingbackup/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 documentationIn addition to this guide, HP provides the following corresponding information, available via the HPwebsite 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 LibraryApplication Notes

For detailed cabling instructions, see your specific HP StorageWorks or HP Server product guides. Theseguides 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
http://www.hp.com/go/ebshttp://www.hp.com/go/ebs


4/30

4

Point-to-Point configuration

Figure 1

Environment Direct Attach SCSI (DAS) and Direct Attach Fibre (DAF)

Typical usage Local and network client backup.

Description The following examples (Figures1 and 2) represent DAS and DAF configurations.Each client transmits its data to the backup server over the LAN that then writes thedata 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 largenumber of clients through a dedicated backup server.


5/30


Figure 2

Description,continued

Backup data flows:

Step From... To...

1 Local internal disk over the LAN Backup servers

2 Backup servers Direct attached tape drives


6/30

6

Shared tape library configuration with HP StorageWorks MSA1500Small Business SAN configuration

Figure 3

Environment Storage Area Network (SAN)

Typical usage Low cost business SAN array with added tape backup and restore option.

Description The following examples (Figures3 and 4) represent the HP StorageWorks MSA1500configuration with a shared tape library. Each Windows server can access the

MSA1500 and the tape library through a single Host Bus Adapter (HBA). EachWindows server has direct access to the tape drives within the library, and tapeaccess is controlled by advanced features within the backup application. Sharing atape library eliminates the need for multiple tape systems connected to each server,thereby simplifying data protection management and reducing total cost ofownership.

For detailed information on the MSA1500 array, see:http://www.hp.com/go/msa.
http://www.hp.com/go/msahttp://www.hp.com/go/msa


7/30


Figure 4


Backup data flows:

Step From... To...

1 MSA1500 disk array Each SAN-based server

2 Each server Shared SAN-attached tape library


8/30

8

Shared tape library configuration with heterogeneous servers

Figure 5


Typical usage Shared tape library across multiple servers.

Description The following examples (Figures5 and 6) represent a SAN configuration consistingof multiple servers with multiple operating systems, connected to multiple disk arraysand 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 tothe tape drives within the library, and tape access is controlled by advancedfeatures within the backup application. Sharing a tape library eliminates the needfor multiple tape systems connected to each server, thereby simplifying dataprotection management and reducing total cost of ownership.


9/30


Figure 6


Backup data flows:

Step From... To...

1 Each disk array Each SAN-based server

2 Each server Shared SAN-attached tape library


10/30

10

Multi-path to disk configuration

Figure 7


Typical usage High availability storage solution.

Description The following examples (Figures7 and 8) represent a shared tape libraryconfiguration (see Figure 5) with HP StorageWorks Secure Path, or othermulti-pathing software, installed on each server. The multi-pathing software provides

the servers with multiple access paths to disk storage, allowing backups andrestores to continue in the event of a disk path failure. This solution provides 24/7data availability in the SAN environment.

NOTE: Regardless of operating system environment, multi-path to tape is notsupported (only one of the two configured paths can access the tape devices at thesame time).


11/30


Figure 8


Backup data flows:

Step From... To...


2 Each server SAN-attached tape library load, balancingthe tapes between SANs


12/30

12

Disk to disk to tape configuration

Figure 9


Typical usage Staging of backup data to a host-managed, low cost disk to facilitate quick restoresand enable long term archival storage.

Description The following examples (Figures9 and 10) represent a shared tape libraryconfiguration (see Figure 5) consisting of multiple servers, primary disk storage

(EVA8000), staging disk storage (MSA1500), and a tape library. The backupapplication backs up the primary disk data to the staging disk, allowing for quickrestores 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 occursthrough servers that sent data. Data on the staging disk can be archived to tape foroff-site storage. This solution enhances typical recovery processes and provides dataprotection in a cost efficient solution.


13/30


Figure 10


Backup data flows:

Step From... To...

Backup1 Each disk array Each SAN-based server

2 Each server Low cost disk array

Archiveto Tape

3 Low cost disk array Each server

4 Each server SAN-attached tape library


14/30

14

Virtual tape configuration

Figure 11


Typical usage Integration of Virtual Library Systems (disk emulating tape) into existing backupenvironments to facilitate quick restores and support for slow SAN clients enablinglong-term, archival storage.

Description The following examples (Figures11 and 12) show the integration of a Virtual Library

System (VLS) in a SAN environment consisting of multiple servers, primary diskstorage, and a tape library. The Virtual Library System uses a controller and low-costdisk to emulate a physical tape library. The backup application backs up the datato the Virtual Library System as if it were a physical tape library, allowing for quickrestores of single files. When physical tapes are required for off-site storage, thedata on the Virtual Library System is copied to the tape library by the backupapplication using an alternate server, freeing up the application host from thisprocess. This solution allows easy integration of disk technologies into existingbackup environments, requiring no unique backup application features.


15/30


Figure 12


Backup data flows:

Step From... To...

Backup1 Each disk array Each SAN-based server

2 Each server SAN-attached virtual library system

Archive to

Tape

3SAN-attached virtual librarysystem

Each server (or an alternate mediacopy server)

4Each server (or an alternatemedia copy server)

SAN-attached tape library


16/30

16

SAN zoning configuration

NOTE: The dashed outlines and dashed connection lines represent the physical components andconnections that are not part of the zone.


Typical usage Enable or limit access between SAN initiators and targets.

Description This example represents a shared tape library in a zoned configuration. Zoning is afeature of the switch that creates isolated groups of connections between specificcomponents 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 activitythat the server is exposed to on the SAN. Effective use of zoning provides securityand simplifies complex SAN management.


17/30


Multi-Protocol Router configuration

Figure 14

Environment Multiple Storage Area Networks (SAN)

Typical usage Sharing storage devices between independent SANs.

Description This example (Figure 14) represents a configuration consisting of independentfabrics, or SAN islands, utilizing the Multi-Protocol Router (MPR), a switch-typedevice. Multiple servers (highlighted with halos and members of the backup

configuration) connect to their local switch within their independent fabric. Throughthe MPR, each server can connect to the shared tape library as if it were in thesame independent fabric. This solution enables the interconnection of devicesbetween SAN fabrics without merging those fabrics, thereby providing a moresecure, flexible storage networking foundation.


18/30

18

Library partitioning configuration

Figure 15


Typical usage Multiple applications sharing a single tape library.

Description This example (Figure 15) represents a configuration consisting of two independent backupapplications accessing a single tape library. Utilizing the partitioning feature in theadvanced version of Secure Manager for Tape Libraries and HP StorageWorks CommandView 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 libraryindependent of the other application. With tape library partitioning, multiple backupapplications can share a single tape library, thereby increasing flexibility in the data centerand lowering total cost of ownership.

For detailed support, see HP StorageWorks Partitioning in an EBS EnvironmentImplementation Guideat: http://www.hp.com/go/ebs .


19/30


Extended SAN configuration

Figure 16


Typical usage Off-site backup and disaster recovery.

Description The following examples (Figures16 and 17) show a shared tape libraryconfiguration (see Figure 5) that uses SAN extension technologies to allowconnectivity 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 extendednetwork link. While Fibre Channel over IP (FCIP) and Wave Division Multiplexing(WDM) allow connectivity over very long distances, Long-wave Small FormfactorPlugables (SFPs) can accommodate distances of 10-35 km. This solution illustrates avariety of SAN extension technologies, providing off-site connectivity for remotebackup and disaster recovery.


20/30

20

Figure 17


Backup data flows:

Step From... To...


2 Each server Extended SAN-attached tape library


21/30


Continuous Access configuration

Figure 18


Typical usage Disaster tolerance, business continuity.

Description The following examples (Figures18 and 19) represent a SAN configuration utilizingContinuous Access EVA, providing the ability to continuously replicate data from thedisk 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 datacan be backed up to the library at site B, thereby creating a remote backup of thedata from site A. Continuous Access EVA utilizes multiple SAN extensiontechnologies to overcome the distance limitations of a typical Fibre Channelconnection. Continuous Access EVA is a complete disaster-tolerant storage solutionguaranteeing data integrity if a storage system or site fails.


22/30

22

Figure 19


Backup data flows:

Step From... To...

1 Disk array on Site A Disk array on Site B

2 Snapshot of replicated LUNs Each disaster recovery (DR) server on Site B

3 Each DR server on Site B SAN-attached tape library


23/30


Virtual Library System EVA Gateway configuration

Figure 20


Typical usage Integration of disk-assisted backup into existing backup environments to facilitatequick restores and support for slow SAN clients enabling long-term, archivalstorage.

Description The following examples (Figures20 and 21) show the integration of a Virtual

Library System (VLS) EVA Gateway in a SAN environment, consisting of: multipleservers, primary disk storage, and a tape library. The Virtual Library System usesmultiple clustered controllers and the HP Enterprise Virtual Array (EVA) to emulatelarge physical tape libraries. The backup application backs up the data to theVirtual Library System as if it were a physical tape library, allowing for quickerrestores of single files and simultaneously restores files, even when backups arerunning. When physical tapes are required for off-site storage, the data on theVirtual Library System is copied to the tape library by the backup application usingan alternate server, freeing up the application host from this process. This solutionallows easy integration of disk technologies into existing backup environments,requiring no unique backup application features.


24/30

24

Figure 21


Backup data flows:

Step From... To...

Backup

1 Primary disk array Each SAN-based server

2 Each server SAN-zoned VLS Gateway

3 SAN-zoned VLS Gateway SAN-zoned back-end EVA array

Archiveto Tape

4 SAN-zoned back-end EVA array SAN-zoned VLS Gateway5 SAN-zoned VLS Gateway Each server (or an alternate

media copy server)

6 Each server (or an alternatemedia copy server)

SAN attached physical tapelibrary


25/30


Encryption Appliance configuration

Figure 22


Typical usage Integration of encryption tape appliances into existing backup environments tofacilitate security protection of data on tape.

Description The following examples (Figures22 and 23) show the integration of encryption tapeappliances into a SAN environment consisting of multiple servers, primary disk

storage, and a tape library. The encryption appliances are zoned into the SAN toallow only the backup data to flow through the appliance. This configuration allowsfor easy control over which servers and tape drives are used for encryption andwhich are not. See http://www.hp.com/go/ebs for whitepapers on how tointegrate these appliances into a SAN backup environment.


26/30

26

Figure 23


Backup data flows:

Step From... To...

1 Primary disk array Each SAN-based server

2 Each server SAN-zoned Encryption Appliance

3 SAN-zoned encryption appliance SAN-attached physical tape library


27/30


iSCSI Virtual Library System configuration

Figure 24

Environment Local Area Network (iSCSI LAN)

Typical usage Integration of disk-assisted backup into existing backup environments to facilitatequick restores and support for slow LAN clients enabling long-term, archival storage.

Description 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 toback up to its own virtual tape library over the iSCSI LAN. The backup applicationbacks 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 foroff-site storage, the data on the Virtual Library System is copied to the tape library bythe backup application using an alternate server, freeing up the application host fromthis process. This solution allows easy integration of disk technologies into existingbackup environments, requiring no unique backup application features.

Backup data flows:

Step From... To...

Backup1 Each servers Local internal

diskiSCSI LAN Virtual Library Systems

Archive toTape

2 iSCSI LAN Virtual LibrarySystems

Each server (or an alternate mediacopy server, if supported by backupapplication)

3 Alternate media copy server Locally attached physical tape library


28/30

28

VMware Consolidated Backup configuration

Figure 25


Typical usage VMware Consolidated Backup (VCB) provides a set of drivers and scripts thatenable SAN backup/recovery of any running supported operating system virtualmachines (VM) by one or more dedicated Microsoft Windows 2003 proxy serverusing an industry-standard backup agent.

Description The following examples (Figures25, 26, and 27) show the integration of VMwareConsolidated Backup (v3.0.1) in a SAN environment consisting of multiple ESXservers (Blades), with each Blade server running 3 virtual machines: one Linux; oneWindows; and one x86 Solaris, a dedicated VCB Server, primary disk storageVirtual Tape Library, and a physical tape library.


29/30


Figure 26


Figure 26 shows how the data flows for both full and incremental file level backup(for virtual machines running Microsoft Windows operating system). VCBaccomplishes this over the SAN by creating a host-based snapshot of the runningVM onto the same LUN that its data currently resides (there must be adequate freespace), then presenting that LUN to the dedicated VCB server where the backupsoftware is running. The backup software performs a normal full or incrementalbackup to a SAN-attached Virtual Tape Library or Physical Tape Library.

Backup data flows:

Step From... To...

1 Virtual Machine File System (VMFS)

Host-based snapshot on same LUN

2 Snapshot SAN-based VMware Consolidated Backupserver (VCB)

3 VCB server running backupapplication

Either a SAN-based Virtual Tape Library orPhysical Tape Library


30/30


Figure 27 shows how the data flows for Image level backups (for virtual machinesrunning any operating system). This is accomplished by make a full copy of therunning Virtual Machine over the SAN onto disk space located on the dedicatedVCB Backup server (there must be adequate free space). Once the full copy hascompleted, the backup software running on the VCB Backup server performs anormal image backup to a SAN-attached Virtual Tape Library or Physical TapeLibrary.Backup data flows:

Step From... To...

1 Virtual Machine File System (VMFS)

SAN-based VMware Consolidated Backupserver (VCB) - FULL COPY

2 VCB server running backupapplication

Either a SAN-based Virtual Tape Library orPhysical Tape Library

Documents

c00375285 Enterprise Backup Solution