protectier on ibm iiseries.homestead.com/files/2011_may_protectier.pdf · – protectier has been...

© 2011 IBM Corporation

™

Bob FrenchDynamix Group, Inc.

[email protected]

ProtecTIER on IBM iMay,2011


®

2

™

Agenda – ProtecTIER on IBM i• Product Overview

– What does it do?– Deduplication Algorithms– Product Family– ProtecTIER on IBM i – where it fits– ProtecTIER on IBM i – how it attaches– ProtecTIER on IBM i - sizing– Next Steps


®

3

™

ProtecTIERProduct Overview


®

4

™

1. Data-agnostic factoring of up to 25 times or more2. Unmatched performance up to 1000 MB/s or more3. Unequaled scalability: up to 1 PB physical data4. Enterprise-class data-integrity: Not hash-based5. Simple, non-disruptive deployment6. Supported in most hardware and software

environments

No other dedupe technology meets all these criteria!

ProtecTIER Vision and Design Criteria


®

5

™

OhioProtecTIER IBM i

What does ProtecTIER do?

Local Saves to Virtual Tape with

De-dup

IBM i ProtecTIER

New York

IP Replication

Minimized bandwidth since data is de-dup’d

before sending

TS3500Optional

duplication to physical

tape

(at local or remote site)

Disk

Virtual Tapes C

A

B

C

AA

BB

AWhat is

DeDuplication?

C

A

B

C

AA

BB

A C

A

B

C

A B

B

A

A


®

6

™

Repository

IBM i Servers

SAN SwitchTS7650G

HyperFactor

MemoryResident Index

“Filtered” data

Existing Data

New Data Stream

Disk Arrays

Hyperfactor Deduplication in Action


®

7

™

Deduplication Algorithms - Types

Text

Content Aware ProtecTIER HyperFactorHash Based

• Assumes the best candidate to de-dup against is an object with similar attributes (eg file name, file type)

• De-dup ratios are lower since even a tiny difference within the boundary causes the match to fail

• Sepaton

Hash Value Pointer

• Hash table grows as more backup data is stored

• As the repository fills, backup speeds decrease since it takes longer to check the bigger table

• Eventually the Hash Table can’t fit in memory and backup speeds decrease seriously

• Hence this algorithm is only suited to smaller devices: it doesn’t scale well

• Data Domain, FalconStor

• Very fast algorithm since it processes backup stream to find possible matches then offloads work to disk to confirm the match

• Algorithm can index 1 PB of physical disk using a 4 GB index that fits in memory, hence no performance degradation as the repository grows

• Hence scalable for large repositories


®

8

™Production Customers Deployment Results


®

9

™

Deduplication Algorithms – Post vs Inline

• Backups run first without de-dup

• Separate de-dup algorithm runs thereafter

• Requires extra disk space to hold the interim full-sized copy of the backup

• Used when the de-dup algorithm is not fast enough to run inline

Inline De-Duplication (eg HyperFactor)Post Processing Deduplication

• De-dup runs as part of backup process

• Uses less disk

• Once save is done, the entire process is done

• Only possible with a fast de-dup algorithm like ProtecTIER HyperFactor


®

10

™

Approach Index Read I/O TB to process datastream

HyperFactor 0 10

Hash Inline > 1 Billion* 0

Hash Post > 1 Billion 20

Content Aware ~10 Million 30

Combined Disk Index I/O Activity for 10 TB

* This can be hosted in memory if the mapped area is small. When dealing with a 10 TB payload this is not likely.

10


®

11

™

Highest Performance

Largest Capacity

High Availability

Better Performance

Larger Capacity

Scalable

Better Performance

Larger Capacity

Scalable

Good Performance

Highly Scalable

Low cost

Highest Performance

Largest Capacity

Highest Performance

Largest Capacity

IBM TS7600 ProtecTIER® Deduplication Family

High Performance

High Capacity

Flexible Storage

Highest Performance

Largest Capacity

High Availability

Good Performance

Entry Capacity

Very Low cost

1 TB = decimal TB = 1,000,000,000,000 bytes or 1,000 GB (i.e. 10^12 bytes)1 TiB = binary TB = 1,099,511,627,776 bytes or 1,024 GiB (i.e. 2^40 bytes)

Single Node

Up to 85 MB/sec

5.9 TB (5.5 TiB) useable

Single Node

Up to 85 MB/sec

4.4 TB (4.0 TiB) useable

Single Node

Up to 500 MB/sec

36 TB (31.5 TiB) useable

Active-Active Cluster

Up to 500 MB/sec


Single Node

Up to 100 MB/sec


Single Node

Up to 250 MB/sec


Single Node

Up to 900 MB/sec

1 PB useable

Active-Active Cluster

Up to 1500 MB/sec

1 PB useable

Nominal Space Available = “useable” space * HyperFactor Ratio

New in July 2010


®

12

™

Notes:

(1) IBM i has a max of 32 drives in a virtual library attached to a given server, and 92 drives total in a virtual library

(2) IBM i has a max of 4096 cartridge locations in each library (slots + drives + IO slots + grippers)

TS7610 Appliance TS7650 Appliance TS7650 Gateway

# nodes 1 1-2 1-2

Max Throughput 80 MB/sec 100, 250, 500 MB/sec

Up to 1500 MB/secwith 2 nodes

Repository (Physical) 4.4 or 5.9 TB 7, 18, 36 TB Up to 1 PB

Max # Virtual Libraries 4 12 16

Max # Virtual Drives (1) 64 256 256

Max # Virtual Cartridges (2) 8,192 128,000 500,000

Replication – Max Spokes per Hub

4 if TS7610 is the hub12 if TS7650 is the hub

12 12

TS7610 ApplianceTS7650 Appliance TS7650 Gateway

ProtecTIER Details LTO-2 & LTO-3 Emulation


®

13

™

Customer Profile for each Appliance Configuration Ideal Customer for 7TB ProtecTIER Appliance

1 TB or less incremental backups per day 1-3 TBs full backups each week Experiencing average data growth Needs a cost effective solution

Ideal Customer for 18TB ProtecTIER Appliance 3 TBs or less incremental backups per day

3-6 TBs full backups each week Experiencing rapid data growth

Needs good performance to meet backup window

Ideal Customer for 36TB ProtecTIER Appliance 5 TBs or less incremental backups per day

5-12 TBs full backups each week Additional growth expected

Meeting the Backup window is an issue - higher performance needed

* Note: These general guidelines are based on the backup workload that best fits each appliance configurationPlease use Capacity Planning Tool to accurately size a solution to meet customer’s specific requirements


®

14

™

IBM’s LTO Technology Roadmap


®

15

™

ProtecTIERFor IBM i


®

16

™

ProtecTIER on IBM i – Where does it fit?

IBM i ProtecTIER

Our Niche – ProtecTIER IP Replication

IBM iProtecTIER

For customers who are moving their tapes offsite via truck today and would like a safer, more automated solution

Note: If the customer already has an HA/DR solution that replicates his data to his remote site, then that will likely provide a more economical solution for remote tape:

• IBM i Software-based Replication (eg iCluster, MIMIX, Visions, iTera, etc)• External Disk Copy Services• IBM i Geographic Mirroring (formerly Cross Site Mirorring or XSM)

For customers where a tape cartridge is much bigger than

needed

. . .VIOS / NPIV

ProtecTIER

Our Niche – Tiny LPARs

Our Niche – Tired of Handling Tapes?


®

17

™

Overall Speed and Single Stream Speed

IBM i

TS7650 ProtecTIER Full box Save capacity is 1500 MB/sec

with 2 nodes

ProtecTIER

Backup Scheduling

Virtual Tape on IBM i – Questions to Ask Your Vendor

Virtual Tape Devices shine when they can run a large number of medium-speed backup streams. IBM i customers often need a small number of very

fast streams. Be sure to understand the single stream performance provided to make sure your Virtual Tape Device will meet your needs

40-90 MB/sec per stream




Current Technology Physical Drives run at 60-280 MB/sec per stream (umix / largefile)

LPAR 11 pm

11:30 pm

Mid-nite

12:30 am

1 am

IBM i 01

IBM i 02

IBM i 03

IBM i 04

Total MB/Sec

20 160 200 200 200

Draw a Backup Gantt Chart to check the MB/sec and # streams at your peak

Single Stream performance depends on the VTL disk type/amount

Non-Infinite Resources

Although virtual tape if flexible, remember the resources aren’t infinite


®

18

™

ProtecTIER on IBM i – Support and Testing

Supported with:• IBM i V5R4 onwards• Any IBM i fibre card supported on your server• BRMS is strongly recommended

• Tested with the same COMPREHENSIVE Test Buckets used for regular tape drives

IBM ProtecTIER is the ONLY External Virtual Tape product that is tested and

supported by IBM Rochester


®

19

™

ProtecTIER Attachment to IBM i - Details

Fibre cards that use an IOP (fc 2765, 5704, 5761) IBM i V5R4M0 onwards TS7650 ProtecTIER Code Levels

Min for Local Backups: V2.2.3.0 Min for IP Replication: V2.3.0

Fibre cards that don’t use an IOP (fc 5749, 5774/5276, 5735/5273, 5708 FCoE + Blades fibre cards) IBM i V6R1M1 onwards with the following PTFs

IBM i 6.1.1: MF49234 + pre-reqs IBM i 7.1.0: MF49235 + pre-reqs

POWER6 or POWER7 system TS7650 ProtecTIER Code Level

V2.4.1.0 Server Code V2.4.3.0 PT Manager Code (GUI)

BRMS is recommended since TS7650 presents as a tape library


®

20

™IBM i IOPless Support for ProtecTIER, TS7650/G - Notes• Support of TS7650G/TS7650 system attachment to IBM i IOP-less Fibre Channel was added on June 30th, 2010.

– ProtecTIER has been supported on IBM i since June 2009, but only using the IOP-based Fibre Channel adapters.

• Prerequisites for IBM i IOP-less configurations with TS7650G/TS7650:1. POWER6 or POWER7 system2. IBM i 6.1 with 6.1.1 LIC or later3. IBM i PTFs (Program Temporary Fix):

1. IBM i 6.1.1: MF49234 + pre-reqs2. IBM i 7.1.0: MF49235 + pre-reqs

4. IBM i Fibre Channel card options: (all available today)1. fc #5749 - 4 Gb PCI-X 2. fc #5774 - 4 Gb PCIe, fc #5276 (low profile version of this card) 3. fc #5735 - 8 Gb PCIe (NPIV capable), fc 5273 (low profile version of this card)4. fc #5708 – FCoE• Blades fibre cards – #8242, #8271, #8240, #8275

5. ProtecTIER Server / Manager Code Versions: 1. June 30, 2010 - A special release of ProtecTIER Server 2.4 available by request from ProtecTIER support

(v2.4.0.2) with PT Manager (GUI) code 2.4.2.0*or*2. July 15, 2010 - The GA version of the code is v2.4.1.0 with PT Manager (GUI) code 2.4.3.0

• Considerations/restrictions for IOP-less usage:1. If a ProtecTIER drive is going to be used for an alternate IPL device (D-mode), there can only be one drive visible on

the adapter as the alternate restart device. ProtecTIER LUN masking may be used to satisfy this requirement. 2. If any VIOS partition is connected to the ProtecTIER on the SAN, the ProtecTIER must be removed from the zone prior

to initiating a reboot of the ProtecTIER. Failure to follow this restriction will cause errors to occur on other devices attached to the same NPIV port that may be disruptive.


®

21

™IBM i IOPless Support for ProtecTIER -Restrictions

Restriction #1: IBM i alt-IPL (reload)

Node 1TS7650

Virt Drive 0 Virt Drive 2 Virt Drive 3

Node 0

Restriction #2: TS7650 IPL with VIOS

TS7650

VIOS

SAN Switch

Other Tape in VIOS Zone

IBM iIBM i

Virtual Library

If TS7650 is attached to VIOS, remove TS7650 port(s) from the VIOS SAN Zone before IPLing

the TS7650, otherwise it may disrupt other devices

To D-IPL your IBM i, use TS7650 LUN maskingso the adapter card can only see a single virtual

drive (the one with the SAVSYS in it)

SAVSYS Tape

(this only applies to IOPless fibre cards, not the older IOP’d cards)


®

22

™

BRMS DUPMEDBRM Compaction PTF

Part of June 2010 BRMS PTF

V5R4: SI38733 IBM i 6.1: SI38739 IBM i 7.1: SI38740

TS7650

Virtual Tape Savesare not compacted so take 3x as much

virtual media (gained back with dedup)

TS3500

Before PTF

Before the PTF, dups used the

same compaction parameter as the source volume, so

more physical media was needed

With PTF

With the PTF, DUPMEDBRM can request compaction so uses less media

Exposes the COMPACT parameter soyou can compact the physical volumes when you dup from ProtecTIER

Behavior: V5R4: control via Data Area Q1ADUPCOMP in QTEMP can be

set to *FROMFILE, *YES, *NO IBM i 6.1 / 7.1 COMPACT(*YES) is available help text via web For new IBM i 6.1 auto-dup

feature, need to change command default on DUPMEDBRM to *DEV

Future releases: COMPACT(*YES) will be available

with regular help text

IBM i


®

23

™

Sizing ProtecTIERFor IBM i


®

24

™

ProtecTIER on IBM i – Designing / Sizing

LPAR GB in Save

Iterations Kept

GB in repository

IBM i 01 200 GB 3 600

IBM i 02 350 GB 7 2450

IBM i 03 100 GB 3 300

IBM i 04 575 GB 12 6900

Total 10250

Get the ProtecTIER on IBM i Introduction and QuestionnaireIBMers: http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101536Partners: http://partners.boulder.ibm.com/src/atsmastr.nsf/WebIndex/WP101536

Build a Repository Sizing Spreadsheet Build a Backup Schedule Gantt Chart(to figure out the peak MB/sec)

LPAR 11 pm

11:30 pm

midnite

12:30 am

1 am

IBM i 01

IBM i 02

IBM i 03

IBM i 04

Total MB/Sec

20 160 200 200 200

60 60 60 60

80 80 80 80

20 20

80 60 60

Then ask the ProtecTIER FTSS to tell you how many disk arms you need

Simple Environment:1-2 hours of work

Complex Environment:Several days of work


®

25

™

Next Steps


®

26

™

If you would like to consider ProtecTIER for your shop …

Text

Detailed ProtecTIER Presentation

Attend the ProtecTIER Hands-on Workshop

Backup Environment Review

Invite your local IBM ProtecTIER Sales Team

to give you a more-detailed presentation

Ask your ProtecTIER team to engage

an IBM i / ProtecTIER specialist to review your backup environment with

you

• Two-Day Hands-on Workshop in Gaithersburg, Maryland.

• Runs 1-2 times per month

• No charge to attend


®

27

™

Questions?


®

28

™

Deduplication Market at a Glance

DEDUP TECHNOLOGY

RESOURCE UTILIZATION

Single node performance 500 MB/s ! 300 MB/s

Dual node Cluster performance 1000MB/s

No disk staging area required

Ø Staging area > twice the size of largest full backup

Only 4GB RAM needed for a 1PB repository

DXi7500DD880

ProtecTIER with HyperFactor

PERFORMANCE

RockSoft Hash-based

SIRHash-based

! Post processInlineInline

Deduplication ! Post process ! Post process

DeltaStor

Block Level Deduplication

Block Level Block Level Block Level Ø File Level

Byte-level diff comparison

! Potential Hash collision

RockSoft Hash-based

No disk staging area required

! Staging area > than the size of

largest full backup

! Staging area > than the size of

largest full backup

!Clustering not available

! 130 MB/s ! 188 MB/s ! 160 MB/s

S2100-ES2VTL 700

Byte-level diff comparison

!Clustering not available

!Clustering with Global Dedupe not

available



See Note (2)

See Note (1)

See Note (3)

See Note (4)

See Notes (5-6)

See Notes (7-8)!Clustering with Global Dedupe not

available

See Notes (9-10)

!Over 300GBs of RAM!



24GB of RAM Not hash based

See Note (11)


®

29

™

Deduplication Market at a Glance

Single system can scale to 1PB capacity

Up to 16 virtual tape libraries

DXi7500DD880ProtecTIER with

HyperFactor

CAPACITY-SCALABILTY

RockSoft Hash-based

SIRHash-based

! Post processIn production

since 2006ProtecTIER in

production since 2006 ! GA October 2008

DeltaStor

Over 25PBs of in production

Many small systems in production

IBM in business for nearly 100 years

RockSoft Hash-based

!Limits not published

S2100-ES2VTL 700

! Over $400 million in debt

! Small struggling company

See Note (12-13)

PRODUCT STABILITY

Acquired by EMC

Ø Acquisition or failure imminent

! GA May 2008

! Very few small customers

! Very few small customers

Ø Almost no deduplication in

production

See Note (14-15)

! 58TB Maximum useable capacity

!Limited by rapid hash table growth

!Limited by rapid hash table growth

!Limited by huge storage requirements




Up to 512 virtual tape drives


Up to160 virtual tape drives

Up to 1024 virtual drives

Up to 192 virtual tape drives

Up to 512,000 virtual tape cartridges


Up to130,000 virtual cartridges

Up to 64,000 virtual cartridges

Up to 5.3 million virtual cartridges

YES ! NO ! NO

MEETS ENTERPRISE REQUIREMENTS?

! NO! NO


®

30

™

Notes – Binary and Decimal TB

• Binary TB are most common in the industry and are shown on the ProtecTIER Manager GUI screens. The ProtecTIER overhead has been removed from these figures

• Decimal TB are used in the marketing literature. The ProtecTIER overhead has not yet been removed from these figures

protectier on ibm iiseries.homestead.com/files/2011_may_protectier.pdf · – protectier has been...

Documents