NetBackup 6.

5 SAN Client Overview

Copyright 2009 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This document is provided for informational purposes only and is not intended as advertising. All warranties relating to the information in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice. This forward-looking indication of plans for products is preliminary and all future release dates are tentative and are subject to change. Any future release of the product or planned modifications to product capability, functionality or feature are subject to ongoing evaluation by Symantec, and may or may not be implemented and should not be considered firm commitments by Symantec, and should not be relied upon in making purchasing decisions.

Transport Technologies for > TB/hr

Teaming NICs using multiple GigE over private backup networks limited OS support, uses lots of CPU cycles for the TCPIP protocol, and hard to guarantee level of service. NetBackup is known as a LAN infrastructure test tool. 2 TB/hr requires 8 teamed GigE LAN ports (not really viable). 10 GigE LAN costly infrastructure typically used when applications need it and not for backup LAN. Limited to 8 KB packet size so it has a high OS overhead and NetBackup is not architected to get the most out of it. SAN Media Server with multiple concurrent tape drives media server footprint on application servers withTechnologies With 8KB jumbo packet support the overhead is > 32 times higher than with 256KB Competing associated NetBackup administration. Many NetBackup customers have been block transfers used by SAN Client technology.using this since 4.5. 6.5 SAN Media Server with multiple concurrent Shared Disks on Limited LTO 4 with reported 120 MB/s (0.4 TB/hr) uncompressed Platforms media server footprint on application servers and associated 0.8 TB/hr compressed (no encryption) but not on 2gbit/s FC administration plus Shared Disk administration. Windows 2003 and Solaris 9 and 10 Sparc ONLY at 6.5 release. Unconfirmed reportssmall client only footprint plus a newmanufacturers drives 6.5 SAN Client compressing and/or encrypting on some service/daemon is actually slower. future, it will likely show up on new client platforms before and PBX. In the * results of Media data and environment Media Server support exists and possibly in place will vary based upon Server support.
Symantec Confidential

Support Brown Bag March 2009

10TB in 5 Hours: Transport Technologies

Standard NetBackup Client backup over LAN
1GbE = 40 MB/s will take 69 Hours Database backup window too long.

Snapshot Client Alternate client backup

Requires additional storage (for mirrors) Would work for backups not restores Incremental backups?

SAN Media Servers

Big Media Server footprint on application servers and associated administration

NetBackup SAN Client

Speeds up to 2 TB/Hour - 10 TB in 5 Hours!! Backups over Fibre (2Gb or 4Gb) Restores over Fibre Incremental backups supported
Support Brown Bag March 2009 3

Symantec Confidential

SAN Client Overview

Introduction - What is SAN Client?
SAN Client Feature uses Fibre Channel (SAN) as a high performance alternative to a LAN to move large amounts of backup data between the NetBackup FT Client and NetBackup FT Media Server. Sends data to both disk and tape storage. Restores data from both disk and tape storage.
LAN
Catalog

Master Server
Tape Library
FT SAN Zone SAN

SAN Clients
FT Media Servers
Symantec Confidential

Disk
Support Brown Bag March 2009 4

SAN Client Overview

When to use SAN Client?
Need to perform fast backups with a high throughput rate of 2 TB/hr to disk or tape. Current SAN Media Server environments that want to leverage NetBackup disk improvements in 6.5 (treating disk as disk). Alternative to SAN Media Server with a small foot print on client. Moving backup traffic over SAN instead of LAN without requiring a Media Server install. Current SAN Media Server environments that want to reduce administration and gain master server scalability through fewer Media Servers.

Symantec Confidential

Support Brown Bag March 2009

SAN Client Terminology

FT Media Server Target mode HBA FT Pseudo Tape Device SAN Client FT Pipe FT Service Manager

FSM
LAN Catalog

Target mode HBAs

FT SAN Zone

SAN

SAN Client

ARCHIVE Python (Pseudo tape drives)

FT Media Servers
Support Brown Bag March 2009 6

Symantec Confidential

SAN Client Configuration

Appropriate OS versions Hardware SAN Zoning and Topology
SAN Client FC zone needs to be configured to allow SAN Client HBA initiator ports to see the FT Media Server target ports. A SAN Client FC zone for (theoretical max) 2Gb/s support can have > 175 MB/s per port

4Gb/s support can have > 320 MB/s per port

Licensing
SAN Client is a licensed feature Installed on EMM Server and checked by Client

If the license has expired, restores can go over lan.

Symantec Confidential

Support Brown Bag March 2009

SAN Client OS and HBA support

FT SAN Zone

SAN

Any NetBackup supported Fibre Channel HBA Initiators (Please refer to HCL)
SAN Client
AIX 5.x HP-UX 11.xx PA-RISC, IA64

Target Mode HBA QLA2340 QLA2342 QLA2344 4gBit/s QLA2460 QLA2462 QLE2460 QLE2462 QLE2464*

FT Media Server Solaris 9 SPARC Solaris 10 SPARC RHEL 4 Update 3 (x64) RHEL 4 Update 5 (x64) 6.5.1 and later RHEL 5 Update 2 (x64)* 6.5.4 RHEL 5 Update 3 (x64) * 6.5.4 Xeon 7400 SLES 9 SP3 (x64) 6.5.1

Red Hat 3.0 x86

Red Hat 4.0 x86, x64 Red Hat 5.0 x86, x64, IA64 SUSE SLES 8.0, x86 SUSE SLES 9.0 x86, x64 SUSE SLES 10 x86, x64, IA-64 Solaris 8, 9, 10 SPARC

Solaris 10 x64
Windows 2000 x86 Windows 2003 x86, x64, ia64* Windows 2008 x86, x64, ia64*

* 6.5.4GA
* 6.5.4GA limited testing, proactive Xeon 7400 support issue

Symantec Confidential

Support Brown Bag March 2009

SAN Client Configuration

Target Mode HBA identification
Each Device is uniquely identified by a values assigned in the NVRAM on the HBA. Vendor ID (1077 for QLogic) Model ID (Chip set 2312, 2422, 2432) Subsystem Vendor ID (1077 for QLogic) Subsystem Device ID (101 for QLA2432, 138 for QLE2462 etc.) *
Ex. A QLE2462 card can be identified using a 4-tuple like 1077, 2432, 1077, 138 or a 2-tuple like 1077,2432

To mark a card as target or initiator, nbhba replaces the existing SSDID with ( 8000 plus the <existing SSDID> ). The cards with the most significant bit of SSDID set are used as targets and vice versa.
Ex. A QLE2462 target mode card will have SSDID = 8138 A QLE2462 Initiator mode card will have SSDID = 138

Symantec Confidential

Support Brown Bag March 2009

SAN Client Details

Configure FT MediaSAN are Identify client / or Install SAN is started and Backup (nbhba) Devices Fibre Transportas install Registerjob Client a Server Installation Overview (nbftsrv_config)FC SAN target (bpclntcmd HBA equivalent license on FT pipes are exposed on thesanclient=1) Client mode activated Conversion to FT Media Server MasterFibreserviceserver) and StartsTransportoverstarted Fibre Client Transport services Data moved Client SAN is (and EMM the SAN SAN Devices are and Target Mode Driver registered and FT devices discovered Client
NBU Client

Master
SAN Client License Key

FSM

Media Server

SAN Client SAN Client

SAN Client Zone

FT Media Media Server Target Mode Server Driver

Target mode Initiator ports ports (backup storage)

FT Server

Initiator ports Initiator ports (storage) (SAN Client)

Client 101001 110011 Data

Beware: CLIENT_NAME required in bp.conf

Support Brown Bag March 2009 10

Symantec Confidential

SAN Client Throughput Considerations

The overall throughput rate will be slower than the slowest piece in the chain which can be the: Ability of the client to read/write to the file system or database being backed up or restored, Storage unit, System PCI I/O memory bandwidth, FC pipe transporting the data, FC topology shared bottlenecks when multiple data streams are sent through a shared element such as a Trunk or ISL.

Symantec Confidential

Support Brown Bag March 2009

11

SAN Client and Disk Architecture

Provides High Performance Backups to Disk Can be used with NetBackup Disk storage units including:
AdvancedDisk SharedDisk PureDisk OpenStorage

Backups are treated a disk backups and take advantage of the Enterprise Disk Foundation features including:
Media server load Balancing Intelligent Disk Capacity Management

Storage Lifecycle Polices

Symantec Confidential

Support Brown Bag March 2009

12

Enhancements made after NetBackup 6.5 Release

QLogic 4Gb Fibre Channel HBA support (NetBackup 6.5.2)
Higher performance, Superior scalability, Enhance Reliability

Support for Backups to Tape (NetBackup 6.5.2)

Despite the rapid growth of disk, tape is still the primary media used for backups. High end tape drive speed is fast enough to utilize the Fibre Transport performance capabilities. Need for a better alternative of a SAN Media Server

Additional FT Media Server and Client platform support

FT Media Server:
RHEL 4 Update 5 (quad core) 6.5.1 SLES 9 SP3 (quad core) 6.5.1 RHEL 5 Update 2 6.5.4

FT Client:
- SLES 10 x86, x64 and IA-64 6.5.2 - Windows 2008 x86 and x64 6.5.2 - Windows 2003/2008 ia64 6.5.4

RHEL 5 Update 3 required for Xeon 7400 parts limited testing HCL support not claimed

Symantec Confidential

Support Brown Bag March 2009

13

QLogic FC HBA Target Mode Support

The support for QLogic 24xx cards was introduced in NetBackup Release 6.5.2 The supported QLogic chip sets are
2312 (PCI-x) 2Gb used on QLA-243x cards supported in 6.5 GA and later 2422 (PCI-x) 4Gb used on QLA-246x cards support added in 6.5.2 2432 (PCI-e) 4Gb used on QLE-246x cards support added in 6.5.2

Some part numbers for supported HBAs using these are:

QLA2340 QLA2342 QLA2344 QLA2460 QLA2462 QLE2460 QLE2462

Sun, HP, Dell, and possibly others resell these QLogic HBAs with minor firmware changes to identify the OEM and our intent is to support all of these. Special mezzanine cards for blades of various manufacturers exist that will require additional testing with the blades to confirm that the combination is capable of being used in a FT Media Server configuration.

Symantec Confidential

Support Brown Bag March 2009

14

QLogic FC HBA Target Mode Support

End-of-Life Notice for 2Gb HBAs
QLogic has announced the End-of-Life (EOL) for all 2Gb OEM Fibre Channel products.

Since we now support QLA/QLE 2460 and 2462 4Gb HBAs in target mode, this will not affect SAN Client deployments.

Symantec Confidential

Support Brown Bag March 2009

15

Use case - SAN Client vs. SAN Media Server

SAN Media Server
Designed for application servers with lots of data to backup quickly Self serving only processes jobs from the local machine

Uses Operating System tape drivers and SCSI Pass Through

Does not support shared disk storage Full media server footprint

SAN Client (client end of a FC Pipe Transport)

Uses the smaller client only footprint Available on all platforms supported by SAN Media Server
Uses Operating System tape drivers and SCSI Pass Through methods to transport data to FT Pipe Servers (server side)

Client does not have to be upgraded as often as Media Server.

Symantec Confidential

Support Brown Bag March 2009

16

Existing SAN Media Server Usage

Application hosts and SAN Media Servers (Big NBU footprint) Counts significantly against the master server scalability limitations.

SAN Media server on the Application hosts (Big NetBackup footprint)

SAN

Ability to send Non-Multiplexed and Multiplexed backups of multiple streams to Tape and Disk storage media over the SAN.

Disk media with data from application hosts

Tape & Disk storage media

Symantec Confidential

Support Brown Bag March 2009

17

SAN Media Servers Replaced with SAN Clients and FT Media Servers

Application hosts and SAN Clients (Small NBU footprint) SAN Clients on the Application hosts (Small NetBackup footprint) Ability to send Non-Multiplexed and Multiplexed backups of multiple streams to Tape and Disk storage media over the SAN. Does not significantly affect Master/EMM scalability.

FT SAN Zone

SAN

FT Media Servers

Disk media with data from application hosts

Tape & Disk storage media

Symantec Confidential

Support Brown Bag March 2009

18

SAN Client Considerations

SAN Zoning and Topology
SAN Client FC zone needs to be configured to allow SAN Client HBA initiator ports to see the FT Media Server target ports. A SAN Client FC zone can have >175 MB/s per 2 gBit/s port (>350 MB/s for 4 gBit/s) continuous for the occupied backup window. ISLs or trunks between switches and between blades in director switches can be bottlenecks.

FT Media Server PCI Bus and FC Throughput

Performance will be limited by PCI slot speed. Recommend PCIexpress or PCI-X 100Mhz or higher slots for dual port target mode HBAs. Performance may be limited by the systems aggregate PCI bandwidth

SAN Client Data Source performance may be limiting factor Multiple streams are required from data base may be a limiting factor Backup Storage Unit performance agents.
Client file system and disk configuration may limit performance.
Symantec Confidential
* results will vary based upon data and environment

Support Brown Bag March 2009

20

SAN Client Design Objectives / Results High Performance Capable

* results will vary based upon data and environment

150 MB/s single stream (1/2 TB/hr on 2 gBit/s) (175 MB/s for 4 gBit/s) Data bases unlikely to supply 150 MB/s in a single stream multiple streams required. 500 MB/sec aggregate performance per FT media server (1.7 TB/hr) with 2 gBit/s, on 4 gBit/s 750 MB/s aggregate with QLA246x PCI-x 133 (1 GB/s with QLE246x PCI Express)

Broad Client platform support

Windows, Solaris, HP-UX, AIX, Linux

Lightweight client - minimal configuration and administration SAN Client has far less overhead on Master Server than SAN Media Server or any Media Server for that matter.
Support Brown Bag March 2009 21

Symantec Confidential

Sparc PCI Architecture Considerations

33 MHz Legacy PCI <132 MB/s on a single port will monopolize the entire Bus Unsupported configuration. 66 MHz Legacy PCI any 33 MHz device on the bus will down shift entire bus to 33 MHz - <132 MB/s * 2 ports will monopolize the entire Bus Unsupported configuration. SunFire T2000 is a great choice if you want to support 4 target mode ports (if it has a working on board SATA disk controller and you arent using the disks much during SAN Client data transfers). Many other Sparc machines with two 133 MHz PCI-x slots on the same bus will down shift to 100 MHz PCI-x if two 133 MHz controllers are present. Effectively limits you to two FC ports worth of I/O bandwidth. T5xxx series machines have multiple IOMMU parts and require a private Sun Patch prior to Solaris 11 (and possibly 10u7) along with an EEB prior to 6.5.4. Intel / AMD Architecture machines dont have these considerations.
Symantec Confidential

Support Brown Bag March 2009

22

SAN Client Summary

Provides High Performance Backup to Disk Can be used with NetBackup Disk storage units including:
AdvancedDisk
SharedDisk PureDisk (but dont expect high performance) OpenStorage

Backups are like any disk backups and take advantage of the Enterprise Disk Foundation features including:
Media server load Balancing

Intelligent Disk Capacity Management

Storage Lifecycle Polices

Symantec Confidential

Support Brown Bag March 2009

23

Appendix A - QLogic HBA Identification

Symantec Confidential

Support Brown Bag March 2009

24

Thank You Questions?

Copyright 2007 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This document is provided for informational purposes only and is not intended as advertising. All warranties relating to the information in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice. This forward-looking indication of plans for products is preliminary and all future release dates are tentative and are subject to change. Any future release of the product or planned modifications to product capability, functionality or feature are subject to ongoing evaluation by Symantec, and may or may not be implemented and should not be considered firm commitments by Symantec, and should not be relied upon in making purchasing decisions.

A peek under the SAN Client covers

Buffer sizing considerations are different than LAN to tape. Why SAN Media Server and Local Backups are faster. Why FT Devices arent tape devices so they can handle multiple concurrent FT Pipe transports. PCI slot and card types and measured performance characteristics.

Symantec Confidential

Support Brown Bag March 2009

26

Client - Server LAN transport

Client Process Client Process

LAN LAN

BPTM Child

BPTM Child

BPTM Parent

Data Source

bpbkar, tar, database agents

Buffer Seg 1 Buffer Seg 2

DMA

Initiator Driver Stack

Buffer Seg N

Multiplexing

control

Local Storage
Shared Storage

Shared Memory

Symantec Confidential

Support Brown Bag March 2009

27

SAN Media Server local shared memory transport

bpbkar, tar, database agents

Client Process

BPTM

Buffer Seg 1

DMA

Initiator Driver Stack

Data Source

DMA

Buffer Seg 2

Buffer Seg N control Shared Memory

Local Storage

Shared Storage

Symantec Confidential

Support Brown Bag March 2009

28

FC Pipe Transport Remotes Shared Memory

SAN Client Side

Buffer Seg 1 Buffer Seg 2

FT Media Server Side

Buffer Segment Transport Protocol
FT Pipe Connection
Buffer Seg 1 Buffer Seg 2

DMA
Buffer Seg N control Shared Memory

DMA
Buffer Seg N control

over SCSI FCP-3

Shared Memory

Symantec Confidential

Support Brown Bag March 2009

29

FSM on master

SAN Client

FT of shared memory data

PBX
Target Mode Service

FT of shared memory data

nbfdrv64

FT Media Server
CORBA connections
BPTM

Client Proces s

nbftclnt

nbftsrvr

Buffer Seg 1 Data Source

Buffer Seg 1 Buffer Seg 2

Backup
DMA
Buffer Seg 2 or

DMA

Initiator Driver Stack

bpbkar, tar, database agents

Restore Job Starts Buffer Seg N

control Shared Memory provided by nbftclnt

FT Pipe DMA
Buffer Seg N control Shared Memory provided by BPTM

6.5.2 & later

Shared Storage

Local Storage

Twice the buffers

Symantec Confidential

What you learned about tape buffers for LAN does NOT apply!
NUMBER_DATA_BUFFERS_FT
Support Brown Bag March 2009 30

FT Media Server nbfdrv64

Target Ports Max 8
tPort 0
1

luns
0

Pipes
PipeId 1

PipeId 2 PipeId 3 PipeId 4 PipeId 5 PipeId 6 PipeId 7

BPTM established

Buf Seg 0

Buf Seg 0
Buf Seg 0

Dynamic Client established

Buf Seg 0 Buf Seg 0 Buf Seg N Buf Seg 3 Buf SegBuf Control 3 Buf Control Buf Seg N Buf Seg 3 Buf Control

tPort 1

Physical FC ports
tPort 2

Buf Control
Buf Control

tPort 3
1

PipeId 16

Dynamic Open Pipe Limit = 3 (default 4*tPorts)

FATPIPE Devices
Symantec Confidential

FAT Pipe / Target Memory Pipe Buffers for open pipes Shared Devices
Support Brown Bag March 2009

31

Target Mode FC HBA considerations

PCI Bus and FC Throughput considerations Applied to FT Media Servers System PCI I/O bandwidth aggregates may limit throughput further. These tests were on an otherwise idle machines.

Ranges indicate client and server machine differences.

QLogic QLA-2340/2342/2344 (in PCI-x 100 or 133 MHz slot) 150 MB/s single backup pipe on a single port* 160 to 175 MB/s using two backup pipes on a single port

320 to 350 MB/s using two backup pipes on two ports (2342 or 2344)
PCI slot limitations on aggregate per card rates (4 ports and enough pipes) 133 MHz PCI-x slot 750 MB/s theoretical max QLA-2344 ~ 550 MB/s 100 MHz PCI-x slot 560 MB/s theoretical max QLA-2344 ~ 350 MB/s

Legacy 33 and 66 MHz PCI slots are NOT supported in production environments!
* Database backups require multiple backup jobs per port to prevent latency caused by only having one buffer at a time available for transfer.
results will vary based upon data and environment

Symantec Confidential

Support Brown Bag March 2009

32