HP StoreOnce Backup System –

Technical Product Overview

Rev 1.0
June 2015

1 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Version
Rev Date Description

1.0 June 13th, 2015 Initial release

2 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 How to use this slide deck
• This slide deck includes a large amount of slides. Advice here, don‘t use all slides in front of a customer. Hide the
slides you don‘t want to present.
• Use slide show mode, as animated slides are includes in this deck
• Use the conent menu to jump to different sections
• Use the  Symbol to get back to the content menu
• In case you find erros, inaccuaries or would like to give feedback (e.g. Enhancements), please contact
[email protected]

3 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Marketing Introduction
• For the latest HP StoreOnce Marketing/introduction slides please go to the WW Storage Sales Portal for HP
StoreOnce Backup: http://intranet.hp.com/eg/sales/storage/ww/Pages/HPStoreOnceBackup.aspx

Explore this web site as you will find

additional helpful information.

4 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce Overview content
• HP StoreOnce Backup System – Models
– HP StoreOnce Models – Hardware
– HP StoreOnce Models – Specs
– HP StoreOnce Backup System – Scalability
– StoreOnce Backup System - Storage configuration
– StoreOnce 4x00 & 6500 Storage hardware
– HP StoreOnce Backup System – RAID controller card
– HP StoreOnce Backup System – Connectors
– HP StoreOnce Backup System – internal cabling
– HP StoreOnce Backup System – SKU’s
• HP StoreOnce VSA
• HP StoreOnce Deduplication
– Chunking
– Hashing
– Slicing
– Understanding SO Container
– Matching
– Meta data & reading data back
– More Performance tuning
– Housekeeing

5 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce Overview content
• HP StoreOnce Backup System – Backup Target Emulation Types
– HP StoreOnce – VTL Emulation
– HP StoreOnce – NAS Emulation
– HP StoreOnce Catalyst
• HP StoreOnce - Federated Catalyst
• HP StoreOnce - Federated Catalyst Routing
• HP StoreOnce - Federated Catalyst in action
• HP StoreOnce - Federated Catalyst Networking
• HP StoreOnce - Federated Catalyst Copy
• HP StoreOnce - Federated Catalyst max. streams Support
• HP StoreOnce - Catalyst over Fibre Channel
– HP StoreOnce – VTL/NAS Replication
– HP StoreOnce – Catalyst Copy
• HP StoreOnce - DR scenario based on VTL/NAS
• HP StoreOnce - Replication/Catalyst Copy – Initial seeding

• HP StoreOnce – Licences
• HP StoreOnce – Security Features
– HP StoreOnce - Enhanced Data Integrity

6 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce Overview content
• HP StoreOnce – Microsoft Active Directory Support
• HP StoreOnce – Networking
• HP StoreOnce – Remote Support
• HP StoreOnce – Software upgrade path
• HP StoreOnce – Key Parameter
• HP StoreOnce – General Best Practise

7 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Backup System - Models


 Single Backup Platform: HP StoreOnce Portfolio 6500
Series
Polymorphic simplicity
ONE Architecture
4900
StoreOnce in
4700 Series
HP Data Protector Series

StoreOnce Recovery
Manager Central 4500
Series
Scalable up to
2900 Scalable up to 1.7PB usable
Series 432TB usable
2700
VSA Series Scalable up to Scalable up to
Series Scalable up to 124TB usable
160TB usable
31.5TB usable
5.5TB usable

1TB, 4TB, 10TB, 50TB

usable StoreOnce
Backup App & Source Dedupe
Catalyst
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce VSA at a glance
More agility, more efficiency, lower risk. Software Defined at its best!

Use Cases Features Benefits

• SMBs looking for • Scalable Capacity Options • Federated Deduplication - One
comprehensive data solution from ROBO to data center
protection solution • Flexible Licensing for increased and simplified
management
• Enterprises wanting to • Broad Hypervisor support • 86% lower cost - Compared to
centrally manage their ROBO EMC Data Domain equivalent
backup • Free 1TB VSA
hardware product
• Managed Backup, Backup as • Try it then buy it – with 1TB Free
a Service VSA download

• Converged data protection - Fully

compatible with StoreOnce
Try VSA at
Recovery Manager Central
www.hp.com/go/StoreOnceVSA

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Backup single node at a glance
• PAY AS YOU GROW
– Scale-out capacity available across the range (exception is 2700)
• 2700: 5.5 TB usable
• 2900: 15.5 to 31.5 TB useable
• 4500: from 16 to 124 TB usable
• 4700: from 20 to 160 TB usable
• 4900: from 36 to 432 TB usable
– Scale-out performance from 3.7TB/hour (2700) to 22 TB/hour (4900) with HP StoreOnce Catalyst
• SEAMLESS DATA MOVEMENT
– Enterprise wide movement of data controlled by your backup application
– No need to rehydrate deduped data
• RAPID RESTORE
– At up to 119% ingest speed
• CONSOLIDATE DATA FROM MULTIPLE LOCATIONS
– Supports fan-in from 8 up to 50 remote offices
• SECURE DATA AT RISK
– Security pack provides data at rest encryption functionality

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce 6500 multi node at a glance
• PREDICTIVE PERFORMANCE AND SCALING
– performance up to 139TB/hour with StoreOnce Catalyst
– Industry-leading Scalable capacity from 72 TB up to 1728TB (1.7PB) usable
• AUTONOMIC RESTART
– HA solution, Node failover
• RAPID RESTORE
– Industry-leading restore performance up to 119% of ingest rate
• CONSOLIDATE DATA FROM MULTIPLE LOCATIONS
– Supports fan-in up to 384 remote locations
• SEAMLESS DATA MOVEMENT
– Enterprise wide movement of data controlled by your backup application
– No need to rehydrate deduped data
• SECURE DATA AT RISK
– Security pack provides data at rest encryption functionality


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Models - Hardware


HP StoreOnce 2700

• Hardware model based on Proliant G8 servers with Intel Sandy Bridge CPUs (1 x 6 core 2700)
• Smart memory – increased capacity less power (24 GB)
• Advanced memory error detection
• ‘Active’ health logs in support ticket
• New p1224 12Gb/s (note: 6Gb/s in StoreOnce use ) SAS RAID controller
• New locking bezel with yellow StoreOnce flash.
• 4 x 1GbE flexible LoM (LAN on motherboard)
• iLO4
• 1U rack height

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce 2900
S toreOnc e
2 900

• Hardware model based on Proliant G8 servers with Intel Sandy Bridge CPUs (2 x 6 core 2900)
• Smart memory – increased capacity less power (48GB)
• Advanced memory error detection
• ‘Active’ health logs in support ticket
• p1224 12Gb/s (note: 6Gb/s in StoreOnce use ) SAS RAID controller
• Locking bezel with yellow StoreOnce flash.
• 4 x 1GbE flexible LoM (LAN on motherboard)
• 2 x 10GbE
• iLO4
• 2U rack height

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 HP StoreOnce 4500

• Hardware model based on Proliant G8 servers with Intel Sandy Bridge CPUs (2 x 8 core 4500/4700)
• Smart memory – increased capacity less power (72GB)
• Advanced memory error detection
• ‘Active’ health logs in support ticket
• p1224 12Gb/s (note: 6Gb/s in StoreOnce use ) SAS RAID controller
• Locking bezel with yellow StoreOnce flash.
• Yellow disk drive release catches for hot-swap disks
• 4 x 1GbE flexible LoM (LAN on motherboard)
• 2 x 10GbE
• 2 x 8Gb FC in StoreOnce
• iLO4
• 2U – 8U rack height

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 HP StoreOnce 4700
• New hardware model based on Proliant G8 servers
with Intel Sandy Bridge CPUs (2 x 10 core 4500/4700)
• Smart memory – increased capacity less power
(128GB)
• Advanced memory error detection
• ‘Active’ health logs in support ticket
• p1224 12Gb/s (note: 6Gb/s in StoreOnce use ) SAS
RAID controller
• New locking bezel with yellow StoreOnce flash.
• Yellow disk drive release catches for hot-swap disks
• 4 x 1GbE flexible LoM (LAN on motherboard) plus 2
x 10GbE in 4700
• 4 x 8Gb FC in StoreOnce 4700 models
• iLO4
• 4U – 18U rack height

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 HP StoreOnce 4900
• A single node product based on one Proliant DL380p
with dual 10-core, 64 bit Intel Xeon 2.8GHz CPUs and
one or two D6000 storage modules. No rack supplied –
field installable 7U or 11U
• 256GB Smart Memory
• 2 x p1228 RAID controllers
• Up to 2 D6000 storage modules each can contain 70 x
4TB MDL SAS disk drives including 4 hot spares.
• 2 x 1TB internal disk drives for the operating system
(connected to SmartArray on the motherboard)
• 4 x 1GbE Ethernet ports (on motherboard –LoM)
• 4 x 10GbE ports (Copper or fibre – fibre SFPs provided)
• 4 x 8Gb Fibre channel ports per node

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce 6500
• Hardware model based on Proliant G8 servers with dual 10-
core, 64 bit Intel Xeon 2.8GHz CPUs
• 256GB Smart memory (16 x 16GB) – increased capacity less
power
• Advanced memory error detection
• ‘Active’ health logs in support ticket
• 2 x p1228 12Gb/s (note: 6Gb/s in StoreOnce use ) dual
channel SAS RAID controllers with 1GB flash write cache
backup and supercap cache protection
• Locking bezels for nodes with yellow StoreOnce flash.
• High density D6000 storage units with ‘hot spare’ disks.
• 4 x 1GbE flexible LoM (LAN on motherboard) + 2 x 10GbE
network ports
• 4 x 8Gb Fibre channel ports per node
• iLO4
• New rack with yellow flash
• 10GbE optical SFPs supplied 
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Models - Specs


HP StoreOnce Backup – capacity scalability StoreOnce 4900
StoreOnce 4500 StoreOnce 4700

StoreOnce 2700 StoreOnce 2900 24 TB (2 TB)

24 TB (2 TB) 60 TB (4 TB)
S tore Onc e
2 900

8 TB (2 TB) 24 TB (2 TB)
and/or

Up to 7 x 24 TB (2 TB)
24 TB (4 TB) per shelf
48 TB (4 TB) 44 TB (4 TB) per expansion X 6 per unit
Base SKU
8 TB 24 TB 24 TB (2 TB disks) 24 TB 60 TB
Raw
Capacity
- 24 TB 24 TB or 48 TB 24 TB 44 TB
Upgrade Raw
Total
8 TB 48 TB 168 TB 192 TB 560 TB
Capacity Raw
Base SKU
Capacity 5.5 TB 15.5 TB 16 TB 20 TB 36 TB
Usable

Capacity
Upgrade - 1 x 16 TB 3 x (20 TB or 36 TB) 7 x 20 TB 11 x 36 TB
Usable

Total 5.5 TB 31.5 TB 124 TB 160 TB 432 TB

Capacity
Usable
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce 6500 – capacity scalability
1st couplet 2nd couplet 3rd couplet 4th couplet

Base SKU
120 TB

Capacity Upgrades
88TB per expansion x 5
per unit

Base SKU Raw 120 TB 240 TB 360 TB 480 TB

Capacity Upgrade
Raw 88 TB 88 TB 88 TB 88 TB
Total Capacity
Raw 560 TB 1120 TB 1680 TB 2240 TB
Base SKU
Capacity Usable 72 TB 144 TB 216 TB 288 TB
Capacity Upgrade
Usable 72 TB 72 TB 72 TB 72 TB
Total Capacity
Usable 432 TB 864 TB 1296 TB 1728 TB

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Backup System – Performance figures

Model SO 2700 SO 2900 SO 4500 SO 4700 SO 4900 SO 6500

max Write
performance [TB/h] 1.3 4.6 5.4 7.6 8.5 63.2

max Catalyst
performance [TB/h] 3.7 5.8 14 22 22 139

SO 6500 1 couplet 2 couplet 3 couplet 4 couplet

max VTL Write
performance [TB/h] 15.8 31.6 47.4 63.2

max Catalyst performance

[TB/h] 34.8 69.6 104.4 139

NOTE:
Actual performance is dependent upon configuration, data set type, compression levels, number of data streams, number
of devices emulated and number of concurrent tasks, such as housekeeping or replication. 
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Backup System -
Scalability


StoreOnce 2900

S toreOnc e
2900

• SO2900 base offer 24TB raw / 15.5 TB useable capacity.

• SO 2900 Capacity Upgrade Kit offer 24TB raw / 16TB useable capacity.
• Write performance (max) 4.6 TB/h
• Catalyst performance (max) 5.8 TB/h

Actual performance is dependent upon configuration, data set type, compression levels, number of data streams, number of devices emulated
and number of concurrent tasks, such as housekeeping or replication.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 4500

• SO4500 base offer 24TB raw /

16 TB useable capacity.

4.0TB

4.0TB

4.0TB

4.0TB
• SO4500 Capacity Upgrade Kit offer
24 or 48 TB raw / 20 or 36 TB

4.0TB

4.0TB

4.0TB

4.0TB
useable capacity.

4.0TB

4.0TB

4.0TB

4.0TB
4.0TB

4.0TB

4.0TB

4.0TB
• Write performance (max) 5.4 TB/h
• Catalyst performance (max) 14 TB/h

4.0TB

4.0TB

4.0TB

4.0TB
4.0TB

4.0TB

4.0TB

4.0TB
4.0TB

4.0TB

4.0TB

4.0TB
4.0TB

4.0TB

4.0TB

4.0TB
4.0TB

4.0TB

4.0TB

4.0TB
Actual performance is dependent upon configuration, data set type, compression levels, number of data streams, number of devices emulated
and number of concurrent tasks, such as housekeeping or replication.
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 4700

• SO4700 Capacity Upgrade Kit offer 24 TB raw /

20 TB useable capacity.

• SO4700 base offer 24TB raw /

20 TB useable capacity.

• Write performance (max) 7.6 TB/h

• Catalyst performance (max) 22 TB/h

Actual performance is dependent upon configuration, data set type, compression levels, number
of data streams, number of devices emulated and number of concurrent tasks, such as
housekeeping or replication.
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce 4900: 4TB based Single Node storage layout
Head (node)
out
1 8 15 22 29 1 8 15 22 29
2 9 16 23 30 2 9 16 23 30

Drawer 1
Drawer 1
Front

Front
3 10 17 24 31 3 10 17 24 31
4 11 18 25 32 4 11 18 25 32

Expansion D6000
5 12 19 26 33 5 12 19 26 33

Initial D6000
6 13 20 27 34 6 13 20 27 34
7 14 21 28 35 7 14 21 28 35

1 8 15 22 29 1 8 15 22 29
2 9 16 23 30 2 9 16 23 30

Drawer 2
Drawer 2
Front

Front
3 10 17 24 31 3 10 17 24 31
4 11 18 25 32 4 11 18 25 32
5 12 19 26 33 5 12 19 26 33
6 13 20 27 34 6 13 20 27 34
7 14 21 28 35 7 14 21 28 35

Key Key
Spares for volumes in same Drawer1 only (in drawer by default) Spares for volumes in same Drawer1 only (in drawer by default)
All part All part
Spares for volumes in same Drawer2 only (in drawer by default) Spares for volumes in same Drawer2 only (in drawer by default)
of base 6th Exp
Base Storage Each as RAID 6 (9+2) 36TB usable 6th Expansion Each as RAID 6 (9+2) 36TB usable
1st Expansion Each as RAID 6 (9+2) 36TB usable 7th Expansion Each as RAID 6 (9+2) 36TB usable
2nd Expansion Each as RAID 6 (9+2) 36TB usable 8th Expansion Each as RAID 6 (9+2) 36TB usable
3rd Expansion Each as RAID 6 (9+2) 36TB usable 9th Expansion Each as RAID 6 (9+2) 36TB usable
4th Expansion Each as RAID 6 (9+2) 36TB usable 10th Expansion Each as RAID 6 (9+2) 36TB usable
5th Expansion Each as RAID 6 (9+2) 36TB usable 11th Expansion Each as RAID 6 (9+2) 36TB usable

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce 6500 storage layout
Couplet
Node N Node N+1
out
1 8 15 22 29 1 8 15 22 29
2 9 16 23 30 2 9 16 23 30
Drawer 1

Drawer 1
Front

Front
3 10 17 24 31 3 10 17 24 31
4 11 18 25 32 4 11 18 25 32
5 12 19 26 33 5 12 19 26 33
6 13 20 27 34 6 13 20 27 34
7 14 21 28 35 7 14 21 28 35

1 8 15 22 29 1 8 15 22 29
2 9 16 23 30 2 9 16 23 30
Drawer 2

Drawer 2
Front

Front
3 10 17 24 31 3 10 17 24 31
4 11 18 25 32 4 11 18 25 32
5 12 19 26 33 5 12 19 26 33
6 13 20 27 34 6 13 20 27 34
7 14 21 28 35 7 14 21 28 35

Key
Spares for volumes in same Drawer1 only (in drawer by default) Cluster Storage Capacity (TB)
All part
Spares for volumes in same Drawer2 only (in drawer by default) No of Couplets 1 2 3 4
of base
Base Storage Each as RAID 6 (9+2) 72TB usable Min Capacity - Usable 72 144 216 288
1st Expansion Each as RAID 6 (9+2) 72TB usable Max Capacity - Usable 432 864 1296 1728
2nd Expansion Each as RAID 6 (9+2) 72TB usable
3rd Expansion
4th Expansion
Each as RAID 6 (9+2) 72TB usable
Each as RAID 6 (9+2) 72TB usable

5th Expansion Each as RAID 6 (9+2) 72TB usable
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Backup System - Storage
configuration


Storage configuration - StoreOnce 2700

RAID5

2TB 2TB 2TB 2TB

500GB LUN for operating system

5.2TB LUN for user data

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Storage configuration - StoreOnce 2900

Logical Useable capacity

4GB 4GB 4GB 4GB 4GB 4GB Volume (dec. bytes)
500GB StoreOnce not available to user
Logical Volume 1 – 500GB (OS)
OS
Logical Volume 2 – 14.1TB (useable)
14.1TB StoreOnce 14.1TB
Base configuration RAID 6 (4+2) data

4GB 4GB 4GB 4GB 4GB 4GB

StoreOnce 14.44TB
LUN1 – 14.55 (useable) 14.55TB data
Optional Expansion RAID 6 (4+2)

Note: StoreOnce 2900 RAID configuration is different from the StoreOnce 4500

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
* Note: 10% overhead will be consumed by the file system
Storage configuration – StoreOnce 4500

Base unit

RAID1 RAID6 (8+2)

2TB 2TB 2TB 2TB 2TB 2TB 2TB ~15TB LUN User Data
2TB 2TB 2TB 2TB 2TB
1 LUN Operating System

Optional Expansion shelf

RAID6 (10+2)

2TB 2TB 2TB 2TB 2TB 2TB

1 LUN user data ~19TB useable

2TB 2TB 2TB 2TB 2TB 2TB

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Storage configuration – StoreOnce 4700
RAID1
1 LUN Operating System
1TB 1TB ~ 4.6GB

Base unit RAID6 (10+2)

2TB 2TB 2TB 2TB 2TB 2TB

2TB 2TB 2TB 2TB 2TB 2TB

1 LUN ~18.9TB user data

RAID6 (10+2)

2TB 2TB 2TB 2TB 2TB 2TB

Expansion 2TB 2TB 2TB 2TB 2TB 2TB

(up to 7 shelves)
1 LUN ~18.9TB user data per shelf

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Storage configuration – StoreOnce 4900

RAID1
1 LUN Operating System
2TB 2TB

RAID6 (9+2) 11 x4TB 11 x4TB

4TB 4TB 4TB 4TB 4TB 4TB 11 x4TB 11 x4TB

4TB 4TB 4TB 4TB 4TB

11 x4TB 2 x4TB 11 x4TB 2 x4TB

1 LUN ~36TB user data

11 x4TB 11 x4TB

Two hot spare disks per 11 x4TB 11 x4TB

4TB 4TB
D6000 drawer per default
11 x4TB 2 x4TB 11 x4TB 2 x4TB

The first D6000 must be filled first!

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Storage configuration – StoreOnce 6500 couplet

RAID1
1 LUN Operating System per node
2TB 2TB

RAID6 (9+2) 11 x4TB 11 x4TB

4TB 4TB 4TB 4TB 4TB 4TB 11 x4TB 11 x4TB

4TB 4TB 4TB 4TB 4TB

11 x4TB 2 x4TB 11 x4TB 2 x4TB

1 LUN ~36TB user data

11 x4TB 11 x4TB

Two hot spare disks per 11 x4TB 11 x4TB

4TB 4TB
D6000 drawer per default
11 x4TB 2 x4TB 11 x4TB 2 x4TB


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 4x00 & 6500
Storage hardware


StoreOnce 4500 & 4700 Storage Module

1
3

1) Disk drives
2 2) UID push button and LED
3) Enclosure LEDs
4) Power Supplies
5) Fan 1
6) I/O Module A
4 6 9 10 11 7) I/O Module B
8) Fan 2
9) Rear UID push button
10) Enclosure LEDs
11) Power on/standby button

5 7 8

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 4900 & 6500 Storage Module
Front view Rear View

Drawer 1 Drawer 2 Drawer 2 Drawer 1

• Each unit has 2 drawers for dual storage domain support

2 drawers per module – 35 x 4TB MDL SAS in each. There are 2 ‘hot spares’ per drawer

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 1) Power supply 1
2) Power On/UID 2 status panel
Anatomy of a D6000 3)
A2 4)
Fan module 1 (Drawer 2)
I/O module A (Drawer 2)
Front View 5) SAS 1 connector (Drawer 2)
6) SAS 2 connector (Drawer 2)
7) Power supply 3
8) UID 1 status pane
9) Fan module 1 (Drawer 1)
D6000 A1 10) I/O module A (Drawer 1)
11) SAS 1 connector (Drawer 1)
70 drives in a 5U form factor 12) SAS 2 connector (Drawer 1)

The D6000 has 2 drawers

D6000 supports 6Gbps SAS
(MDS600 is 3Gbps) Drawer 1 Drawer 2
Each drawer:
• Holds 35 LFF drives
• Drive bays are numbered 1-35 Rear View
• Each drawer is effectively it’s own
JBOD
A2 2 A1 2
• Each drawer has 2 I/O Modules for 1 1
13) SAS 1 connector (Drawer 1)
14) SAS 2 connector (Drawer 1)
dual domain support B1 15) I/O module B (Drawer 1)
16) Fan module 2 (Drawer 1)
– Domain A 17) Power supply 4
B2 2 B1 2 18) SAS 1 connector (Drawer 2)
– Domain B
1 19) SAS 2 connector (Drawer 2)
1
B2 20)
21)
I/O module B (Drawer 2)
Fan module 2 (Drawer 2) 
22) Power supply 2

Drawer 2
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Drawer 1
HP StoreOnce Backup System – RAID
controller card


p1224 RAID controller

1x p1224 in StoreOnce 2700

1x p1224 in StoreOnce 2900
1x p1224 in StoreOnce 4500
2x p1224 in StoreOnce 4700

1GB FBWC (Flash Backup Write Cache)

12Gbps SAS (HP StoreOnce currently only uses 6Gbps)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Storage RAID controller – p1224
• 12Gb SAS capable* x 8 PCIe half-height, half length RAID controllers developed for use in G8 ProLiant servers
using an LSI ROC.(RAID on Chip)
• Raptor firmware is used in these controllers
• StoreOnce ‘Single-node’ products are using Defender 4i/4e version :
• 1 x 4 Phy Internal SAS port
• 1 x 4 Phy External SAS port (for JBODs)
• Cache - the ISS “Gold” DIMM. The Gold DIMM includes flash memory and a SuperCap to power the backup
process.

* All of our peripherals connected are 6Gb

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
p1228 RAID controller (2 per node)

SuperCap 2x p1228 in SO 4900 node

connects here
2x p1228 per SO 6500 node

4 phys

6Gbps SAS to 1 GB write cache module

storage
modules

4 phys


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Backup System –
Connectors


 StoreOnce 2700 – connectivity
HP StoreOnce 2700 has 4 x 1GbE ports. They can be configured for individual subnets
or bonded in any combination. Note for initial configuration the unit is configured with one
subnet set to DHCP.
RRAA
IIDD
ccrr
ttll
11

et
h
eetthh

po
33

tt 22
rrtt

iLo 44
rt
ppoo

ppoorr

ppoorr

iLo
hh
eett

tt 11
eetthh

iLO4 connection, user connection

External 1GbE, user connections

RAID controller 6 Gb/s (internal)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 2900 - connectivity

RRAA
IIDD
ccrr
ttll
11

. .
TOP

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 4500 – connectivity

RRAA
IIDD
ccrr
ttll
11

. .
FC port 1 . . FC port 3

eth port 5 . . eth port 4

et
h
eetthh

po
33

tt 22
rrtt

rt

iLo 44
ppoo

ppoorr

ppoorr

iLo
hh
eett

tt 11
eetthh

iLO4 connection, user connection

All required
External 10 GbE, user connections

External 1GbE, user connections RAID controller 6 Gb/s (internal)

SFPs supplied
External 8 Gb fibre channel, user connections

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 4700 – connectivity

RRAA
RRAA

IIDD
IIDD

ccrr
ccrr

ttll
ttll

22
11
. .
FC port 1 . . FC port 3
. .
FC port 2 . . FC port 4 eth port 5 . . eth port 4

et
h
eetthh

po
33

tt 22
rrtt

rt

iLo 44
ppoo

ppoorr

ppoorr

iLo
hh
eett

tt 11
eetthh

iLO4 connection, user connection

All required
External 10 GbE, user connections

External 1GbE, user connections RAID controller 6 Gb/s (internal)

SFPs supplied
External 8 Gb fibre channel, user connections

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 4900 node – connectivity

RRAA

RRAA
11

11
rrtt

rrtt
IIDD

IIDD
ppoo

ppoo
ccrr

ccrr
11

22
ttll

ttll
ttll

ttll
ccrr

ccrr
11

22
ppoo

ppoo
IIDD

IIDD
rrtt

rrtt
RRAA

RRAA
22

22
. .
FC port 1 . . FC port 3 eth port 7 . . eth port 6

. .
FC port 2 . . FC port 4 eth port 5 . . eth port 4

et
h
eetthh

po
33

tt 22
rrtt

rt

iLo 44
ppoo

ppoorr

ppoorr

iLo
hh

All required
eett

tt 11
eetthh

External 10 GbE, user connections iLO4 connection, user connection SFPs supplied
External 1GbE, user connections RAID controller 6 Gb/s (internal)

External 8 Gb fibre channel, user connections

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 6500 node – connectivity

RRAA

RRAA
11

11
rrtt

rrtt
IIDD

IIDD
ppoo

ppoo
ccrr

ccrr
11

22
ttll

ttll
ttll

ttll
ccrr

ccrr
11

22
ppoo

ppoo
IIDD

IIDD
rrtt

rrtt
RRAA

RRAA
22

22
. .
FC port 1 . . FC port 3 eth port 7 . . eth port 6

. .
FC port 2 . . FC port 4 eth port 5 . . eth port 4

et
h
eetthh

po
33

tt 22
rrtt

rt

iLo 44
ppoo

ppoorr

ppoorr

iLo
hh

All required
eett

tt 11
eetthh

External 10 GbE, user connections iLO4 connection (internal) SFPs supplied

External 1GbE, user connections 10 GbE connections (internal)

External 8 Gb fibre channel, user connections RAID controller 6 Gb/s (internal)


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Backup System –
internal cabling


Capacity upgrade kit - BB881A
adding to StoreOnce 4500

• StoreOnce 4500 accepts ONE BB881A upgrade kit

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Capacity upgrade kit - BB881A
adding to StoreOnce 4700

• StoreOnce 4700 accepts up to SEVEN additional BB881A upgrade kits

Shelf Connection Order

3rd upgrade kit
  Storage Controller
In this example 3 additional shelves
Shelf Slot1 Slot4
1st upgrade kit Have been added.
1 X  
2   X
3 X  
4   X
5 X   Main Storage
6   X
7 X   2nd upgrade kit
8   X

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 4900 SAS wiring – one D6000

1) HD SAS cable - RAID card 1, port 2 to Disk

enclosure 1, Drawer 2, I/O Module B, Port 2
2) HD SAS cable - RAID card 1, port 1 to Disk
enclosure 1, Drawer 1, I/O Module A, Port 1
3) 0.5m mini SAS cable - Drawer 1, I/O module
A, port 2 to Drawer 2, I/O module A, port 1
4) 0.5m mini SAS cable - Drawer 2, I/O module
B, port 1 to Drawer 1, I/O module B, port 2

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 4900 SAS wiring – 2 D6000 Storage units
5
The FIRST storage unit must be filled with
disks before adding the SECOND unit!
6

5) HD SAS cable - RAID card 2, port 2 to Disk enclosure

1. HD SAS cable 2, Drawer 2, I/O Module B, Port 2
6) HD SAS cable - RAID card 2, port 1 to Disk enclosure
2, Drawer 1, I/O Module A, Port 1
7 7) 0.5m mini SAS cable - Drawer 1, I/O module A, port 2
to Drawer 2, I/O module A, port 1
8) 0.5m mini SAS cable Drawer 2, I/O module B, port 1
8 to Drawer 1, I/O module B, port 2

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce 6500 Standard Config
6500 Couplet
Dual p1228

Def 8E

Def 8E
P1228

P1228
Mock

Mock
Def 8EUp

Def 8EUp
StoreOnce

P1228
P1228
Mock

Mock
Up

Up
1 4
PS1

NC 552SFP
PCIe x8 8Gb FC

8 4 2

8 4 2
AJ764 A

PORT 1

PORT 2

NC552SFP
AJ 764A
2 5

DL380p (node 2)
Two D6000s
TX RX TX RX

Convention
PS2

NC 552SFP
PCIe x8 8Gb FC

8 4 2

8 4 2
AJ764 A

PORT 1

PORT 2

NC552SFP
3 6

AJ 764A
PLC B
TOP
TX RX TX RX

1200W

Node #2
94%
4 1

iLO UID

StoreOnce

Def 8E

Def 8E
P1228

P1228
Mock

Mock
Def 8EUp

Def 8EUp
P1228
P1228
Mock

Mock
Up

Up
1 4
PS1

NC 552SFP
PCIe x8 8Gb FC

8 4 2

8 4 2
AJ 764A

PORT 1

PORT 2
Convention

NC552SFP
AJ 764A
DL380p (node 1)
2 TX RX TX RX 5
PS2

Cabling Approach

NC 552SFP
PCIe x8 8Gb FC

8 4 2

8 4 2
AJ764 A

PORT 1

PORT 2

NC552SFP
3 6

AJ 764A
PLC B
TOP
Node #1
TX RX TX RX

1200W
94%
4 1

iLO UID

Controller Pairs
• p1228 RAID controller #1’s form a controller pair and
are cabled to D6000 #1.
• p1228 RAID controller #2’s form a controller pair and StoreOnce
are cabled to D6000 #2. Convention
D6000 #2
D6000 support (Slot #4
Defenders)
• Each controller pair can support a single D6000
Defender Port Cabling
• Port 1 of RAID controller connects to I/O Module A
(both drawers)
• Port 2 of RAID controller connects to I/O Module B StoreOnce
Convention
(both drawers)
D6000 #1
• Port 1 and Port 2 of the same Defender should connect (Slot #1
to different drawers in the D6000 Defenders)

(reverse loops from each other)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 
HP StoreOnce Backup System – SKU’s


HP StoreOnce 2700/2900 models – product SKUs
Model Base Maximum Expansion details Product No. Includes:
Capacity capacity
(useable) (useable)
StoreOnce 2700 5.2TB 5.2TB N/A BB877A HP StoreOnce 2700 Backup System, 4 x hot swap 2TB disks,
power cables, documentation CD, iLO4 license. 1x p1224
RAID controller. Rack mount rail kit.
(Note: only 1 PSU as standard – for additional PSU order
656362-B21). ‘Start here’ Installation poster.

StoreOnce 2900 15.5 TB 31.5 TB BB910A HP StoreOnce 2900 24TB Backup System, 6 x hot swap
4TB disks, 2 x power cables, ethernet cable (Cat 5e),
Installation poster and HP StoreOnce Information card. Rack
mount rail kit.

HP StoreOnce 16 TB 6 x 4TB HDD BB911A HP StoreOnce 2900 24TB Capacity upgrade kit, 6 x 4tB
2900 24TB disks and entitlement certificate
Expansion

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce 4500/4700 models – product SKUs
Model Base Maximum Expansion details Product No. Includes:
Capacity capacity
(useable) (useable)
StoreOnce 4500 16TB 124TB 1 x D2600 disk enclosure BB878A HP StoreOnce 4500 Backup System, 12 x hot swap 2 TB
(12 x 2TB disks) disks, 2 x power cables, 2 x Ethernet cables, iLO4 license, 1
x p1224 RAID controller, 2nd HA PSU included, rack-mount
rail kit . ‘Start here’ installation poster, documentation CD.

Storeonce 4700 18.9TB 160TB Up to 7 additional D2600 disk BB879A HP StoreOnce 4700 Backup System base unit with 2 x 1TB
Includes 1 D2600 enclosures (12 x 2TB midline OS disks, 1 x D2600 Storage shelf with 12 x hot swap 2TB
shelf with 12 x SAS disks) disks, 2m SAS cable, 2 x Ethernet cables, 4 x power cables,
2TB midline SAS iLo4 license. 2 x p1224 RAID controllers, 2nd HA PSU
disks included, rack mount kit, ‘start here’ installation poster

D2600 Expansion 1 x D2600 disk 18.9TB N/A BB881A D2600 Storage Enclosure with 12 x 2TB disks, redundant
shelf for 4500 enclosure power supplies and fans, 0.5m and 2m SAS cable,
and 4700 (12 x 2TB midline entitlement certificate (licence). Rack mount rail kit and
SAS disks) power cords. 2 AC power cords and PDU interconnect
cables. 2nd HA PSU included.

D2600 Expansion 1 x D2600 disk 33TB N/A BB909A D2600 Storage Enclosure with 12 x 4TB disks, redundant
for 4500 only enclosure (12 x 4 power supplies and fans, 0.5m and 2m SAS cable,
TB midline SAS entitlement certificate (licence). Rack mount rail kit and
disks) power cords. 2 AC power cords and PDU interconnect
cables. 2nd HA PSU included.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce 4900 models – product SKUs
Model Base Maximum Expansion details Product No. Includes:
Capacity capacity
(useable) (useable)
HP StoreOnce 36 TB 432 TB Up to 5 capacity upgrade kits BB903A HP StoreOnce 4900 Backup System, 15 x hot swap 4TB
4900 Backup and up to one HP StoreOnce disks, ethernet cable (Cat 5e), 2 x power cords, Installation
System 4900 60TB drawer upgrade kit poster. Rack mount rail kit.

HP StoreOnce 36 TB 216 TB Up to 5 capacity upgrade kits BB904A HP StoreOnce 4900 60TB Drawer/Capacity Upgrade Kit, 1
4900 60TB storage enclosure with 15 x hot swap 4TB disks, redundant
Drawer/Capacity power supplies, fan modules, 0.5m mini - SAS cable + 2m
Upgrade mini - SAS cable . Rack mount rail kit.
Kit

HP StoreOnce 36 TB N/A N/A BB908A HP StoreOnce 4900 44TB Capacity Upgrade Kit, 11 x 4TB
4900 44TB disk and entitlement certificate
Capacity
Upgrade Kit

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce 6500 models – product SKUs
Model Base Capacity Maximum Product No. Includes:
(useable) capacity
(useable)
HP StoreOnce 6500 72 TB 432 TB BB896A • HP 6500 Processing Nodes (2)
120TB • HP 6500 Switch kit
for Initial Rack • HP 6500 Storage Drawers (2)(each with 15* 4 TB HDDs)
• 4 x 0.5m Mini SAS cables
• 16 x 2m SAS - HD to Mini SAS cables
• 16 x Power cords
• Provided in a 42U rack

HP StoreOnce 6500 88TB 72 TB BB899A • 22 * 4 TB HDDs

Capacity Upgrade Kit • HP 6500 88TB Capacity Upgrade License Entitlement Certificate

HP StoreOnce 6500 72TB BB897A • HP 6500 Processing Nodes (2)

120TB • HP 6500 Storage Drawers (2)(each with 15* 4 TB HDDs)
for Existing Rack • 4 x 0.5m Mini SAS cables
• 12 x Power cords

HP StoreOnce 6500 72TB BB900A • HP 6500 Processing Nodes (2 )

120TB • HP 6500 Switch kit
for Second Rack • HP 6500 Storage Drawers (2)(each with
• 15* 4 TB HDDs)
• 4 x 0.5m Mini SAS cables
• 16 x 2m SAS - HD to Mini SAS cables
• 16 x Power cords
• Provided in a 42U rack

HP StoreOnce B6200 to BB902A • 8 x 15m optical cables

6500 Interlink Kit • 4 x 10GbE SFP+ transceivers

HP StoreOnce 6500 Mixed BB912A • 4 x 10GbE SFP+ transceivers

Couplet
© CopyrightSFP Ki
2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. • 8 x 2m SAS HD to Mini SAS cables
HP StoreOnce multi node models – Expansion details
Existing Upgrade SKUs Required
Configuration
B6200 6500 Adding BB897A BB897A#0D1 BB900A BB902A BB912A
Couplet(s) Couplet(s) 6500 For existing For existing racks, For extra Mixed couplet Mixed couplet SFP
couplet(s) racks factory integrated racks interlink cable kit kit

1 0 1 1 0 0 0 1

1 0 2 1 0 1 1 0

1 0 3 1 1 1 1 0

2 0 1 0 0 1 1 0

2 0 2 0 1 1 1 0

3 0 1 1 0 0 0 1

1 1 1 0 0 1 1 0

1 1 2 0 1 1 1 0

1 2 1 1 0 0 0 0

2 1 1 1 0 0 0 0

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce VSA


StoreOnce VSA features & benefits
• Delivers 1 – 50TB of raw storage – cost/flexibility/security
• Provides up to 16 iSCSI VTL (iSCSI) targets, NAS shares or Storeonce Catalyst Stores
• Fully compatible with the StoreOnce hardware based appliances. Is able to replicate VT/NAS or use StoreOnce Catalyst copy.
• StoreOnce VSA can act as a replication target for ONE StoreOnce appliance or StoreOnce VSA source. (i.e. fan-in=1)
• Management GUI – same as the hardware based StoreOnce product.
• CLI (some commands restricted)
• Fully integrated with HP StoreOnce Enterprise Manager 1.4 for management and reporting.
• No support for VTL on fibre channel
• Supported on Vmware, Microsoft Hyper-V platforms and KVM (Kernel Virtual Machine)
• 1TB free demo license for 3 years1
• Can be upgraded via rpm update procedure. (Licences must be re-applied if upgrading from the VSA 1.x versions running
StoreOnce 3.7.0 code version)
• Support for IPv6 for Catalyst and replication only. (dual network stack)

Note 1. The 60-day instant on license applies to all licensed capacities. However if capacity exceeds 1TB the 3 year 1TB free license cannot be applied.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce VSA - Specification
VSA 4 TB VSA 10 TB VSA 50 TB
Max useable configurable capacity 4 TB 10 TB 50 TB
Catalyst write performance (max) 1TB/hour 2TB/hour 6TB/hour
NAS, VTL write performance (max) 400GB/hour 800GB/hour 2.4TB/hour
Replication fan-in/fan-out (appliance) 8/2 8/2 8/2
Max backup targets 4 12 16
Backup targets supported Catalyst, VTL, NFS, CIFS over Ethernet
Hypervisor support VMware ESXi, Microsoft Hyper-V, Ubuntu KVM - for
details see www.hp.com/go/ebs
License to use term 3 or 5 years
Technical support Business hours phone technical support included for
license to use term
Care Packs Available to upgrade included technical support

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce VSA configuration information
All Hypervisor
• Capacity upgrade licenses are available. Adding a capacity upgrade license is non-disruptive. Once the new
license is added increased backup data capacity can be configured. The larger usable capacity will require
adding more memory and processor resources to meet performance. Adding resources requires the StoreOnce
VSA to be restarted so these upgrades should be done outside backup times.
• The StoreOnce VSA requires significant disk I/O for backup and recovery operations. The number, type and
configuration of hard disks that provide capacity for the virtual disks is an important choice. The number of
disks and the type of disk will significantly affect the I/O potential and consequently backup and recovery
performance.
• To be resilient to hard disk failure it is recommended that RAID protection is used. To further reduce risk
from physical hard disk failure, the disks used for StoreOnce VSA backup data storage should not be shared
with hard drives that provide storage for the protected data and virtual machines particularly if backup data
copy/replication is not used.
• It is recommended that the effect of the resource consumption of the StoreOnce VSA on other virtual
applications running on the same pool of resources is assessed. This impact assessment should consider any
backup software components, running in virtual machines, which will require resources to execute backup
and recovery jobs.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce VSA configuration information
VMware
• It is recommended that the virtual disks used to provide capacity for StoreOnce VSA are in a
.vmdk format from a VMFS3 or VMFS5 data store. NFS data stores are supported but careful
consideration of the performance implications should be made before deployment. RAW disks
are not supported. Virtual disks should be thick provisioned
• If the VMware host has AMD CPUs some configuration is needed to run the StoreOnce VSA. It
is necessary to create a single host cluster with the EVC (Enhanced vMotion Compatibility)
mode set to AMD generation 3 or earlier.
• StoreOnce VSA is supported for use with VMware vMotion and VMware Storage vMotion. It is
not supported for use with the following VMware features: VMware High Availability (HA),
VMware Fault Tolerance (FT), VMware Distributed Resource Scheduler (DRS), Vmware
Distributer Power Manager (DPM)and VMware Site Recovery Manager (SRM).

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce VSA configuration information
Hyper-V
• StoreOnce VSA requires NTFS storage. There is no support for NFS data stores or pass-through disks. StoreOnce
VSA can run on all processors supported for Windows Server Hyper-V provided the performance and quantity
meets the minimum requirements for the capacity of StoreOnce VSA configured.
• StoreOnce VSA supports thick provisioned virtual hard disks (.VHDX or .VHD).
• StoreOnce VSA supports use of Hyper-V Live Migration during backup and recovery operations.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce VSA configuration information
Ubuntu KVM
• The base or system disk type should always be presented as a VirtIO device type (disk bus) and ‘qcow2’ storage
format for StoreOnce VSA on KVM.
• For data disks StoreOnce VSA supports both SCSI and VirtIO device type with either raw or qcow2 storage
formats.
• For optimal performance, HP recommends a device type of VirtIO and ‘raw’ storage format.
• It is recommended to use Virtual Network Interface device model as VirtIO for optimal performance with
StoreOnce VSA.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Recommended minimum resources

Conifgured capacity 1 TB to 4 TB 5 TB to 10 TB 10 TB to 50 TB
Memory (min) 16 GB 24 GB 32 GB
Processor (min @ 2.2 GHz) 2 vCPU 4 vCPU 12 vCPU
IOPs (typical) 450 900 2700

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce VSA – Licensing information

• The StoreOnce VSA is fully functional from its first installation with a 60-day instant-on
period. If no license key is added within 60 days of start up all backup targets become read-
only. Once a license key is added full functionality is returned.
• If a license to use (LTU) reaches the end of its term all backup targets become read-only. Once
a valid license key is added full functionality is returned.
• The StoreOnce VSA license enables use as a replication target and does not require an
additional Replication license. If you intend to replicate to VTL and/or NAS targets on a
StoreOnce appliances a Replication license will need to be installed on the target appliance.
• The StoreOnce VSA license enables creation of Catalyst Stores and execution of Catalyst Copy
operations and does not require an additional Catalyst license. If you intend to use Catalyst
Copy between a StoreOnce VSA and a StoreOnce appliance, the StoreOnce appliance will need
a Catalyst license installed.
• The StoreOnce VSA license enables on data at rest encryption, data in flight encryption and
secure erase and does not require an additional Security Pack license
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce VSA – Licensing information

• The StoreOnce VSA license enables users to create Catalyst Stores and act as a replication
target, configuration of the Catalyst Stores and Replication Targets is covered in the optional
configuration services.
• Data Replication Service:
http://dccappshares01.austin.hp.com/SALES_LIBRARY-PRO/CONCENTRA/Autofed%20Content/UCM/UCM-Concentra/
Pub/ucm4AA4-3945ENW/4AA4-3945ENW.pdf

• Catalyst Solution service:

http://dccappshares01.austin.hp.com/SALES_LIBRARY-PRO/CONCENTRA/Autofed%20Content/UCM/UCM-Concentra/
Pub/ucm4AA4-4489ENW/4AA4-4489ENW.pdf

• A capacity upgrade license can be added only if there is a valid license installed on the
StoreOnce VSA.
• For example, a 4TB to 10TB capacity upgrade license can be applied only if a 4TB base license is installed on the
StoreOnce VSA.
• For example, a 10TB to 50TB capacity upgrade license can be applied only if a 10TB base license is installed on the
StoreOnce VSA
• There is no license to upgrade directly from 4TB to 50TB. This is accomplished by upgrading
first to 10TB, then to 50TB.
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce VSA – Licensing information

• Once the capacity upgrade license is added, the licensed term of the StoreOnce VSA will be 3 or
5 years, depending on license purchased, regardless of the remaining term of the previous
smaller capacity license.
• The license to use term starts from the day the license is redeemed from the HP licensing portal.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce VSA SKU information

Description 3 year license to use 5 year license to use

StoreOnce VSA 4 TB D4T77AAE, D4T77A D4U49AAE, D4U49A
StoreOnce VSA 10TB TC458AAE, TC458A D4U62AAE, D4U62A
StoreOnce VSA 4TB to 10TB Capacity D4U56AAE, D4U56A D4U58AAE, D4U58A
Upgrade
StoreOnce VSA 50TB D4U47AAE, D4U47A D4U48AAE, D4U48A
StoreOnce VSA 10 TB to 50TB Capacity D4U57AAE, D4U57A D4U59AAE, D4U59A
Upgrade

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce VSA – Key Parameter
Parameter VSA 1 TB min VSA 4 TB min VSA 10 TB VSA 50 TB min
config config min config config
Requirements

Required vCPU cores at 2.2 2 2 4 12

GHz
Min req memory 16 GB 16 GB 24 GB 32 GB

System limits

Recommended maximum 4 4 12 16
number of libraries, shares,
and StoreOnce Catalyst Stores
Recommended overall 16 16 24 32
maximum concurrent inbound
data streams in this recipe

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce VSA – Key Parameter

Parameter VSA 1 TB min VSA 4 TB min VSA 10 TB VSA 50 TB min

config config min config config
VTL

Max cartridges per library 512 512 512 512

Max cartridge size (GB) 3200 3200 3200 3200

NAS

Max files per share (vers 1) 25.000 25.000 25.000 25.000

Max files per share (vers 2) 1 million 1 million 1 million 1 million

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce VSA – Key Parameter
Parameter VSA 1 TB min VSA 4 TB min VSA 10 TB VSA 50 TB min
config config min config config
StoreOnce Catalyst Stores

Max concurrent outbound 16 16 16 16

copy jobs (per VSA)
Recommended max 16 16 24 32
concurrent data and inbound
copy jobs (per VSA)
Replication

Max replication appliances 8 8 8 8

fan-in (per VSA)
Max replication appliances 2 2 2 2
fan-out (per VSA)


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Deduplication
Technology


Deduplication
• The goal of deduplication is to allow customers to store more data on disk for longer periods by eliminating
redundant data.
• In general deduplication methods fall into 2 categories:
1. Post processing where deduplication is performed after backups complete.
2. In line hash-based chunking where deduplication is performed as data is received from the host system.
• HP StoreOnce deduplication is performed as the data is received from the host system and uses in-line hash
based chunking technology. Deduplication appliances have to provide target devices for the host systems and
these typically are Virtual Tape or NAS or vendor specific targets such as
StoreOnce Catalyst.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 The HP StoreOnce ‘appliance’

HP HP StoreOnce Appliance
FC-SCSI
Virtual
Virtual Tape
Tape
Emulation
Emulation
FC-
FC- Fibre
Fibre Channel
Channel
SAN
SAN HBA
HBA Deduplication
Deduplication
Backup ‘engine’
‘engine’
Data via NAS:
NAS:
SAN/WAN
CIFS
CIFS server
server Filesystem
IP Filesystem
IP
network
Network
Network HBA
HBA NFS
NFS Server
Server
network

iSCSI HP
HP
StoreOnce
StoreOnce
StoreOnce
Catalyst
management
management Catalyst
Catalyst
Backup Servers
CIFS/NFS RAID
Storage

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 The Basic Mechanics of hash – based chunking.
cut cut cut cut

Chunk #1 Chunk #2 Chunk #3 Chunk #4

1st backup Chunk data stored with hash code

2nd backup
= new data Unique chunks have to be saved with
their hash code.
Chunk
Chunk #1
#1 Chunk
Chunk #2
#2 Chunk
Chunk #3
#3 Chunk
Chunk #4
#4
contains
contains new
new data
data unchanged
unchanged contains
contains new
new data
data unchanged
unchanged
Unchanged chunks are not stored,
only their hash code and the location
of the chunk in the first backup is
stored!
The incoming data stream is divided into ‘chunks’ of approximately 4KB
using a proprietary algorithm (TTTD). Each chunk has a SHA-1 hash applied.
Chunks are stored with their hash code but any chunks with the same hash
code are duplicates and HP StoreOnce only need to increment the count in the
index.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 HP StoreOnce deduplication process
Catalyst hashing/chunking/compression performed by media server

Buffers
Buffers
Catalyst

Sparse index in RAM (for speed)

Buffers
VT/NAS

Buffers
chunking hashing slicing matching
emulation Sample hash Container
IP
IP

20 bytes ID

110..011111 xxxx
Following sort: compress & store
new chunks and update metadata, 101..111111 xxxx
IP

Catalyst Selects best

or IP

Catalyst
Client container index, & sparse index Sort & Save
FC or

Client containers for

110..111111 xxxx
FC

compress
matching
hash 011..111111 xxxx

chunk Update Container Compress

Index chunks (LZO)

cache

Dedupe Store ‘Containers’ – 2 files

metadata ‘ compressed chunks
files
index C C C
Media/application
Servers with DP8/ISV Filesystem
Apps.
RAID disk subsystem

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce dedupe write pipeline Hyperthreads

thread thread
Multi-core CPU
Each part of the pipeline process is
VT/NAS/Catalyst designed to be multi-threaded for thread thread x2
optimum performance.
thread thread
Buffer manager

release ring buffer

40MB ring buffer in RAM (one per virtual tape drive/NAS file or
catalyst session*). The data is processed by a series of
‘transforms’ forming a pipeline. Each stage is multi-threaded

Chunking Hashing Slicer Matching Sort &Save I/O Writer

RAID
subsystem
FIFO FIFO FIFO FIFO FIFO


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Chunking


 Detect duplicate data by dividing into ‘chunks’
• Backup Data streams are broken into ‘chunks’ by the deduplication process.

A data stream can be considered to be an ordered list of chunks

First backup
Second backup

•Much of the data is unchanged between backups!

•How do we choose where to divide the chunks?
•How do we find which chunks are changed?

•HP Labs looked at these challenges and their ideas led to HP StoreOnce technology!

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Detect duplicate data by dividing into ‘chunks’
• Backup Data streams are broken into ‘chunks’ for comparison

A data stream can be considered to be an ordered list of chunks

First backup
Second backup

Only these chunks have changed! All the duplicates can be replaced by
a reference to the original ‘chunk’ location plus a count of how many times
StoreOnce has received the ‘chunk’.

•How big should the chunk be?

•Should they be of fixed size, or variable?
•Where do we make the divisions in the data stream?
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Chunking – An example in English
Let’s consider a backup as a sequence of sentences in a stream of data.

“I wok e u p i n t h e m o r n i n g a n d g o t a c u p
Da ta of coffee before checking my backups
stre a m f r o m l a s t n i g h t .”

“I wok e u p . i n t h e m o r . n i n g a n d g . o t a
Fixe d cup o.f coffee b.efore chec.king my
chunking b a . c k u p s f r o m . l a s t n i g h t .”
[e ve ry 10 cha ra cte rs]

“I w.o k e u p i n t h e m . o r n i n g a n d g . o t a
Va ria b le cup .of c.offee bef.ore checking my
chunking b a c k u p s f r . o m l a s t n i g h t .”
[b a se d o n the le tte r ‘o’]

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Example – Fixed Chunking
Fixed chunking does not match after the change in the data stream

“I wok e u p i n t h e m o r n i n g a n d g o t a c u p
N ew d a ta of black coffee before checking my
stre a m b a c k u p s f r o m l a s t n i g h t .”

“I wok e u p . i n t h e m o r . n i n g a n d g . o t a
Previous cup o.f coffee b.efore chec.king my
b a . c k u p s f r o m . l a s t n i g h t .”

“I wok e u p . i n t h e m o r . n i n g a n d g . o t a
N ew cup o.f black co.ffee befor.e checking.
m y b a c k u p . s f r o m l a s . t n i g h t .”

Only 4 out of 10 chunks now match! – 40% saving

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Example – Variable Chunking
• Variable chunking resynchronizes after the change to find more duplicates

“I wok e u p i n t h e m o r n i n g a n d g o t a c u p
N ew d a ta of black coffee before checking my
stre a m b a c k u p s f r o m l a s t n i g h t .”

“I w.o k e u p i n t h e m . o r n i n g a n d g . o t a
Previous cup .of c.offee bef.ore checking my
b a c k u p s f r . o m l a s t n i g h t .”

“I w.o k e u p i n t h e m . o r n i n g a n d g . o t a
N ew cup .of black c.offee bef.ore checking
m y b a c k u p s f r . o m l a s t n i g h t .”

7 out of 8 chunks match - 88% saving!

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Fixed versus Variable Chunking

Fixed chunks
..ddea123ac223bdf99877765dae6e6a7cbb23a33ab332556fd155900f0f0dd2237d7dc ..

fixed chunk (boundary determined by chunk size e.g. 8KB)

Chunk boundary determined by “Rabin
Fingerprint” . A mathematical function using a
48 byte -sliding window producing a 32-bit
marker output constant = Σ. If Σ= a pre-set
marker value a marker is set at the chunk boundary.
Variable chunks
........ddea123ac223bdf99877765dae6e6a7cbb23a33ab332556fd155900f0f0dd2237d7dc ........

variable length chunk ~4KB

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Chunking TTTD Fallback to a second less
stringent marker.
end of last chunk
2nd threshold 1st threshold

Rabin fingerprint

.
sedf112ddea123ac223bd.....765dae6e6a7cbb23a....ab332556fd155900f0f0dd2237d7dc2 .....
approx. 4KB

•The chunk boundary markers are created ‘on the fly’ by the output.
•The HP StoreOnce technology uses a Rabin fingerprint to identify ‘landmarks’ in the data stream and
is set to trigger at one of 2 thresholds (TTTD= two thresholds two divisors). The 2 nd threshold is
mathematically adjusted to be less stringent. The aim is to obtain chunks of data no larger than 10KB
but of an average size but with the majority around 4KB.

•This is patented HP technology

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Chunk distribution – 2 thresholds

No. of chunks

Threshold 1
Threshold 2

4KB chunk size


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Hashing


Hashing Data

76762e76f73223
Hello, everyone Hash Function 6aa9833a8c86b2
– let’s hash this cb4856ac6b9e
message (SHA-1)

Always 20 bytes
Hello, everyone
– let’s hash this d72688ad6acdde
message and Hash Function ca041b3dd6daf8
add some text (SHA-1) 80517efd3a3f

The chance of a hash ‘collision’ is 1 in 2 63


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Slicing


Slicing into portions
• After chunking and hashing the HP StoreOnce appliance further divides that data into ‘portions’. A portion will
consist of ‘chunks’ with their hash code.
• Portions are approximately between 8 and 13MB from 3.5.0 code onwards.
• Portion slicing is always at a chunk boundary and is selected with a special algorithm similar but not identical to
the ‘TTTD chunking algorithm’.
• Portions are necessary because it would be very difficult to process a whole backup as a continuous entity and
would be inefficient.
• Each backup is then held as ‘metadata’ as a set of portions. After the matching process each portion will consist of
a set of hash codes and ‘container’ id references.
• Each store item is listed in an item ‘manifest’ which references the relevant portion ‘manifest’. This is called
‘metadata’.


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Understanding StoreOnce containers


 The StoreOnce ‘Container’
Made up of 2 files:

Container Index Approx. 15,000 chunks but can increase to ~50,000

#value count comp. Compressed chunk offset in file
20 bytes 1 byte length

……….. 12 not used XX YY

………. 45 not used XX YY
………. 126 not used XX YY
……….. …. not used ………. ……….

As part of the matching process the count is

increased if a chunk is ‘matched’. For ‘new’ chunks Container Data
A new entry is made and its container location stored.
chunk chunk chunk chunk chunk
Deletion or overwrite triggers ‘housekeeping’ which
chunk chunk chunk chunk chunk
decrements the count. The compression 1 byte is for future
use. chunk chunk chunk chunk chunk
chunk 
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Matching


 Matching – Locality of data.

Backup datastreams as a list of ‘chunks’ (~4KB) – note that file marks etc. are stripped out before dedupe.

Backup #1

Backup #2

Backup #3

New chunk – ie. Some data changed and therefore a new hash code.
Unchanging chunk from 1st backup.

These chunks are identical AND in the same sequence for each backup iteration.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Matching. Locality of data – identifying ‘landmarks’

Backup datastreams as a list of ‘chunks’ (~4KB)

Backup #1

Backup #2

Backup #3

Chunk data around the ‘landmark’ hash remains mostly unchanged. The ‘hook’ is used in a sparse index to determine best
containers for matching.

New chunks – ie some data changed

160 bit hash value with least significant 5 bits = 0. StoreOnce technology refers
To these hash code as ‘hooks’

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Matching
• Each portion is matched in turn.
• The portion is a list of hash codes and chunks.
• Any hash with the 5 least significant bits=0 is designated a hook and will be checked against the sparse index.
• As the hashes are essentially as set of random numbers there is one hook for every 32 hash codes.
• StoreOnce matching works on the theory that the neighbouring chunks to the hook value are present in each
subsequent backup (some of chunks of course will be new).
• The sparse index is used to rapidly select ‘containers’ which will provide good matches for the portion. It IS NOT
and index to the actual data. The ‘Sparse Index’ is not used in reading back data!

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Sparse index (SI)
CI = container index container id10

chunk chunk
Sparse index (in memory) CI container
container
SHA-1 Hash ( 160bits ) Container ID (32
bits) container id 60

0011011000001 nnn...00000 10
chunk chunk
0001001011010 nnn...00000 60
0001000011001 nnn...00000 60 CI container
container
1100001010111 nnn...00000 10
1101001101101 nnn...00000 32 container id 32
0000100101010 nnn...00000 16 chunk
0010101111000 nnn...00000 16
chunk
0110000101101 nnn...00000 32 CI container
container

the last 5 bits of the hash value = 0 container id 16

are called ‘hooks’ in StoreOnce
chunk chunk
CI container
container
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Matching & writing data to the store
• Once suitable containers are identified the indexes held in the container can be checked against the portion being
matched. It is the container indexes which tell dedupe whether a chunk has been previously stores.
• This causes disk I/O which is bad for performance so StoreOnce applies several patented methods to limit the
number of containers checked.
• The incoming portion is matched and any new chunks are compressed (DCLZO) and stored in the data section of
the container. Matched chunks just increase a counter held in the index part of the container.
• The portion can then be stored as metadata as a list of hash codes versus container ids.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Matching #1- Candidate containers selected
Portion=10MB approx next portion
chunk chunk chunk chunk chunk chunk chunk chunk chunk chunk chunk

hash hash hash hash hash hash hash hash hash hash hash

Dedupe Store
hash Sparse Index (in memory)
Container
Hash value Container id
hook 160 bits 32 bits compressed chunks
(last 5 bits=0) index
010000101000....00000 xxxxxxxxxxxxx C C C

000100100010....00000 xxxxxxxxxxxxx
Container
001000010001...00000 xxxxxxxxxxxxx
compressed chunks
index
100000111101...00000 xxxxxxxxxxxxx C C C

Typically there are around 40 010000101010...00000 xxxxxxxxxxxxx

Container
‘hooks’ per portion 110000101111...00000 xxxxxxxxxxxxx
compressed chunks
index
C C C

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Meta data & reading data back


Meta data and chunk data
Container #345

Item
Item ## Tape/File= an item. When overwritten index compressed chunks

/generation
/generation A generation # is incremented. Locates chunk C C C C
C C C C

Item
Item manifest
manifest Bar
Bar codes/EOD
codes/EOD Container #124
(list
(list of
of portions)
portions) etc.
etc.

index compressed chunks

Portion manifest C C C C
Locates chunk
Hash Code 128 bits Container ID C C C C

0AB33888 ……….. 345

Container #124

AFF03312………… 124
0AACCB3………… 124 compressed chunks
… index
Locates chunk C C C C
BBOA112………….. 392
C C C C
……………………… ……………………………………
…. ……………

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Retrieving data from StoreOnce

SCSI commands
VT emulation rebuild data stream
FC/iSCSI with filemarks etc. ring buffer (40MB)
IP
CIFS/NFS
server
CIFS/NFS/catalyst protocol Chunk

item(tape/file) Chunk

meta-data Chunk

Dedupe store (one per VT/NAS share)

Item
manifest list of hashes
C C C C C C C C C C
portion1
vs container id#
container container
container##
CI container## CI
Portion portion2
manifest
C C C C C C C C C C
portion’n’
container
container## container
container##
CI CI

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
More performance tuning!


StoreOnce Deduplication enhancements – major changes. Improvements
in the write ‘pipeline’
• There are several changes which have been made to the in the write process. The TTTD algorithm which segments
the data stream has now been modified to use multi-threading.
• Changes to the container matching algorithm improves deduplication efficiency with interleaved data sets.
• Some slight tuning enhancements will improve the read pipeline.
• BlobFS
• Compressed entities

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Deduplication enhancements – major changes
Blob FS (3.2.0 onwards)
• Read/writes to the filesystem is a large overhead. In ‘Blob FS’ portions and container index files are
grouped together with an 4K header index into one large file. There are 256 files in a blob. The header
tracks the individual files as ‘in-play’ or committed. Once all fields are committed the new larger file
is written to disk. HP StoreOnce also renames the metadata files once committed and this is expensive
in terms of overhead. Blob FS reduces this load.

4K header 4K header
portion up to 256 portions or container index
portion container indices per container index
portion ‘blob’ container index
1 file 1 file

portion container index

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Deduplication enhancements – compressed entities
• When chunks are written into the Dedupe store they are compressed.
As the chunk average size is 4K this leads to inefficient data compression.

• By writing and compressing 32 chunks in one a better efficiency is achieved.

• EMC Data Domain dedupe does something similar storing (2 x~8K segments)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Compressed entities

LZO compression
Chunk

Chunk

Chunk

Chunk
Compressed
32 ‘new’ chunks to be Entity Entity Container File

added to a container from

sort & save

Chunk

Chunk

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Deduplication enhancements – high pass hook filter
• Introduced in 3.2.0/3.3.0 we now set a ‘target’ value of 3% for the number of hooks referenced for each container.
• In a 10MB portion the sampling is now 32:1 with the new sparse index. This is approximately say 80 ‘hooks’ per
portion.
• 3% = 2 hooks. So if container indices with less than 8 hooks referenced from the sparse index are not used for
matching (even if ‘Kitty’ allowed more!). AND this has been determined without any disk I/O as the sparse index
is in memory!
• This improves performance because of less disk I/O wasted on poor matches.
• Of course this does result in a slight reduction in dedupe.
• The values for target hook matching and Kitty are being ‘tuned’ more carefully for (3.6.0) release.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Deduplication enhancements – Super portions
• A ‘portion’ is the a list of hash codes and container id #s which is stored as metadata in the dedupe store. There
will be many portions in a backup. A virtual tape is an ‘item’ and an ‘item manifest’ lists all the port
• Instead of storing them away individually StoreOnce now groups them into a “superportion” of 10 portions. This
saves on disk I/O.
• In data read the data is reconstituted from the portions referenced in the portion index.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Duplication improvements on multiplexed datasets (3.11)
• The sparse index is at the heart of StoreOnce deduplication. Its job is to select good ‘candidate’ containers for the
matching process.
• Multiplexed datasets are challenging for deduplication as data locality changes for each backup.
• The sparse index is memory based therefore is fast. Once the top candidate containers are selected then the actual
files can be opened and the container index checked. Recent container index data may be in memory because
StoreOnce uses extensive caching methods.
• Multiplexed datasets tend to select fewer candidates for matching. This results in poor deduplication.
• HP StoreOnce R&D have now developed a method by which the container candidates can be reconsidered for
matching.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 HP StoreOnce Sparse index (SI)

Non-multiplexed data sets Multiplexed data sets

Sparse index (in memory) Sparse index output result. Sparse index output result.

SHA-1 Hash ( 160bits ) Container ID (32 Container id# No. of hooks Container id# No. of hooks
bits)
10 30 10 4
Hashes from incoming 0011011000001 nnn...00000 10
data are checked against 60 24 60 3
the Sparse Index. 0001001011010 nnn...00000 60
32 10 32 2
0001000011001 nnn...00000 60
16 4 16 2
1100001010111 nnn...00000 10
25 4 25 1
1101001101101 nnn...00000 32
24 2 24 1
0000100101010 nnn...00000 16
0010101111000 nnn...00000 16 32 2 32 1

0110000101101 nnn...00000 32 Select top values for matching. Do This sparse index output indicates
not proceed to matching stage if 3 or poor matching potential. With the
less hooks per candidate container new 3.11.0 code StoreOnce proceeds
otherwise we open the container and to matching providing that this is a
The last 5 bits of the hash value = 0 proceed to matching otherwise store recent container and is in cache. If
are called ‘hooks’ in StoreOnce chunks. neither condition is true then the
chunks are stored in a new container.

Matching Store Chunks Matching Store Chunks

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Deduplication improvements for multiplexed data sets – typical results
MS SQL server backups

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Deduplication improvements (3.12.1)
• Improved performance with sparse index updates and searches.
• Improved deduplication of interleaved datasets like MaxDB and Microsoft SQL.
• Reduce meta data size on disk to improve deduplication ratios.
• Removal of unnecessary empty directories to speed up ibdircheck times.
• Additional checks to prevent hash collisions.
• Encryption of meta data, including the encryption of existing meta data.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
And here is the proof! (Testing with SQL DB).


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Housekeeping


Housekeeping with StoreOnce

• Housekeeping is used to remove fragmentation and redundant data from the deduplication store. This process will
occur when data is overwritten or deleted providing the housekeeping ‘blackout window’ is not active.
• Housekeeping can be delayed – but not forever. Use the blackout window to restrict to times when workload is
light.
• Container compaction is the highest workload. If the size of the chunks with an index count of zero exceeds 10%
of the container capacity compaction is triggered.
• All deduplication technologies have a degree of housekeeping!
• Secure erase function if selected is part of housekeeping.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Housekeeping processes with container matching
complete VT/NAS/Catalyst portionmanifest
manifest 6 portions are checked and the containers
overwrite portion
item (listofofhash
(list hashvalues
valuestotochunk
chunkidid used identified. Each container index is opened
index andcontainer
containerid#)
id#) in turn but all index counts for the 6 portions
and modified.
partial removal
or VT overwrite P0 P1 P2 P3 P4 P5 Pn

complete removal
Of VTL/Catalyst or NAS share batch process Transaction Log

directory structure for the sparse SI remover if > 10% of index counts=0
library/share removed. index container
for the container then compaction
compactor
is started.

container
container container
container
C C C C C C
Index count C C C Index count C C C

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Fragmented store before/after housekeeping compaction

Container #345

index compressed chunks

C C C C C C C C
C C C C C C C C
count=0 C C C C C C C C
C C C C C C C C

Container #345

index compressed chunks

Space returned
C C C C C C C C
no counts=0 C C C C C C C C To FS


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Backup System –
Backup Target Emulation Types


HP StoreOnce VSA & 2700 – Emulation Types

Catalyst NAS share

Store (CIFS/NFS)
CP/IP
T
Via

Via iS
C SI Virtual Libraries: Virtual Drives:
VTL • MSL2024 • LTO-2
• MSL4048 • LTO-3
• MSL8096 • LTO-4
• EML-e, • LTO-5
• ESL-e, • LTO-6
• D2D generic • Ultrium VT
• IBM TS3500 • IBM LTO-3

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce 4x00 – Emulation Types

NAS share
(CIFS/NFS)
T CP/IP
Via

Catalyst
T CP /I P & F C Store
Via

Virtual Libraries: Virtual Drives:

Via FC VTL
/ i SC S • MSL2024 • LTO-2
I • MSL4048 • LTO-3
• MSL8096 • LTO-4
• EML-e, • LTO-5
• ESL-e, • LTO-6
• D2D generic • Ultrium VT
• IBM TS3500 • IBM LTO-3

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce 6500 – Emulation Types

NAS share
(CIFS/NFS)
T CP/IP
Via

Catalyst
T CP /I P & F C Store
Via

Virtual Libraries: Virtual Drives:

Via FC VTL
/ i SC S • MSL2024 • LTO-2
I • MSL4048 • LTO-3
• MSL8096 • LTO-4
• EML-e, • LTO-5
• ESL-e, • LTO-6
• D2D generic • Ultrium VT
• IBM TS3500 • IBM LTO-3

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce – VTL Emulation


Virtual Tape
• Seamlessly integration into most backup application
• Emulated tape libraries: MSL G3 (2x24, 4x48, 8x96), EML-e, ESL-e, D2DBS Generic,
IBM-TS3500
• Emulated tape drives: HP LTO-2, -3, -4, -5, -6, UltriumVT, IBM LTO-3
• Flexible cartridge size from 10 GB up to 3200 GB in different increments
• Flexible amount of slots per library (8 – 16384)
• Flexible emulation type
• Library changer device can be mapped out via two FC port for redundancy
• Up to 500 tape drive per library (4700/4900/6500)
• Non Deduplication mode for pre-encrypted or -compressed data. (also legal compliance
in some regions)
• Enable encryption for data at rest
• Secure Erase functionality (up to 7 overwrite passes)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
VTL Tape features

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
VTL Tape features – Secure Erase Mode

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce IBM Tape

Feature HP Tape IBM Tape

Seamless Integration into IBM TSM for all versions of
all supported TSM Server operating systems X

Full integration into IBM AIX X

Seamless integration for Symantec NetBackup on AIX X
Seamless StoreOnce Multi-Node Failover / Autonomic
Restart Support for AIX and for TSM using IBM X
SANDISCOVERY supported Operating Systems

• Does not enable IBM Mainframe Support or I-series (requires 3 rd party conversion unit)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Difference between StoreOnce IBM Tape and HP Tape?

• HP Tape
• No Robotics Support on AIX/OS and HP Tape drives utilize generic scsi driver
• Requires non-native ‘pass-thru’ device drivers on TSM
• IBMi/OS cannot see any HP Robots or HP Tape Drives

• IBM Tape
• Utilizes IBM Tape Drivers providing for full Tape and Robotics Support for TSM, AIX and IBMi

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Benefits of StoreOnce IBM Tape Emulation

• Utilizes proprietary IBM Tape Drivers allowing for near-to-full IBM Tape feature functionality
• Seamless integration into proprietary IBM hardware platforms, operating systems, and ISVs
• Allows HP to venture into joint IBM-HP solutions
• Autonomic VTL Restart upon StoreOnce node failover for TSM (using IBM supported SANDISCOVERY
operating systems)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce IBM Tape - GUI


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce – NAS Emulation


NAS share emulation

• Security feature Data at Rest encryption for NAS targets on all StoreOnce products. (requires
Secure Pack license)
• User selectable non-deduping NAS shares for when you have data that doesn't deduplicate well
or want to use source side deduplication in backup software
• CommVault Simpana aware NAS shares to optimize deduplication ratio and performance
• Two version of NAS share available.
 ‘Type 1’ store has the following:
o Maximum file limit is 25000
o The 1st 24 MB is left un-deduplicated (intended for ISV R/W)
 ‘Type 2’ store has the following:
o Maximum file limit is 1 million
o The 1st 1 MB is left un-dedulicated (intended for ISV R/W)
o Optimised to improve performance with CommVault Simpana backup software

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
NAS Server configuration

• CIFS
o Server name: Should match hostname (small change to default hostname made to
ensure this)
o Authentication method:
• None
• User
• AD
– Workgroup / Domain name information
– User List: List of usernames which can be given access to shares

• NFS
o Server name: Same as for CIFS
o Host List: List of hosts which can be allowed access to shares

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
NAS share configuration

Select what NAS share you would like to use on creation

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Choice of NAS share ‚Type‘

Select share type on creation

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
NAS Share feature

Select non-dedup share on creation

Enable encrpytion for data at rest on creation

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
NAS Share feature – Secure Erase Mode

Specify number of overwrite passes

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Write in place
• The StoreOnce deduplication engine was designed for a sequential workload, with NAS
there is the possibility of overwriting data before the end of a file – this is termed Write-
in-place.
• In order to allow this happen two steps were taken:
1. Since most WIP is done at the start of a file (e.g. ISV header catalogues) the first 1 or 24MB of
each file is not deduplicated and therefore “random access”
2. Any WIP that occurs in the deduplicated portion of a file is dealt with by putting the new data
in a separate file and referencing it so that it is retrieved during restore.
• Deduplication of a NAS share can be completely disabled at store creation time. In case
you know that lots of random I/O will happen or pre-compressed or –encrypted data will
be stored.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Writing file to a StoreOnce NAS share
Backup
application
software

24 MB

1 MB

Non-dedup part Dedup sub-system & store

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 WIP Diagram

First Backup Backup File

non-dedup

X GB dedup

Second Backup Backup File

WIP WIP non-dedup

X GB X GB dedup

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Sparse Files and Extent Writes
• Backup applications are allowed to create “Sparse files” i.e. Truncate a file many
MB or GB beyond where the EOF is currently located.
• However a limit is applied to how far ahead of the current location within a file
the backup application may perform a write. This limit is 200MB.

previous EOF extent write new EOF

X GB
non-dedup
part 1 or 24 < 200 MB
MB

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
NAS performance

• Performance of the NAS target devices is similar to that of iSCSI VTL

devices.
• As with all inline deduplication solutions performance is less than an
equivalent non-deduplicating device. As such D2D NAS devices are not
suitable as General Purpose NAS devices which require fast response
times for small amounts of data.


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Catalyst


Why a new interface?
• This is a new device which ISVs can use with none of restrictions of tape emulation and NAS shares. No unnecessary
‘geometry’ limitations. (library slots, cartridge sizes etc.)
• Allows ISV software to be aware of the StoreOnce Backup system and it’s capabilities.
• Allows the backup server to support node failover in multi-node systems without complex restart scripts (some ISV
still have scripts) and restart from checkpoints
• Use bandwidth efficient methods to move (copy) data without re-hydration. This enables backup over WAN or LAN,
with increased performance.
• Enables deduplication in different locations (federated deduplication)
• Tight integration with HP Data Protector
• Fully support Symantec OST
• Enables ISV applications control copies of backups. Copy to multiple locations and to set different expiry dates. ISV
is fully aware of all copies and jobs.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Catalyst – new features

Performing chunking and hashing across

multiple Media Servers can increase the overall
performance of backups to a Catalyst Store.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Catalyst – deployment options 2

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Catalyst enables part of the deduplication process to be
performed at the backup server

Catalyst Client API StoreOnce

StoreOnce Catalyst
Catalyst Appliance
Appliance

Chunker Surrogate Hasher

FIFO FIFO
IP network

Memory
Hasher (SHA-1)

Shared Memory
link (WAN) Matcher
FIFO
buffer
buffer

buffer
buffer

FIFO
Slicer Surrogate Sort-save
FIFO FIFO

Shared
Remote matcher
Surrogate Matcher
backup FIFO match hash FIFO
data from Compressor codes
ISV app. Sort -Save
FIFO
Store
Remote Saver Sparse Index
save – new
chunks only
update sparse index
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst terminology
Term Description
HP StoreOnce Catalyst Correct HP name for the technology available on the B6200 which enables a new interface to be
used for advanced features in backup
HP StoreOnce Catalyst The target device type in which backups are stored.
store
HP StoreOnce Catalyst Backup data is held as ‘items’ in a catalyst store. Item size and number are set by the ISV backup
items application. Items are NOT files!
HP StoreOnce Catalyst ISV applications which connect using the HP StoreOnce Catalyst interface. Currently HP Data
clients Protector 7 and NetBackup 7.1
Data Job Any job which stores or restores data from the HP StoreOnce Catalyst store.

HP StoreOnce Catalyst Backups where part of the deduplication process occurs on the catalyst client system. (Low/High
optimised backups bandwidth backup).
Copy job Copies created by backup applications and not ‘mirror’ images. the ISV application internal
database is fully aware of these copies. Data is moved between catalyst stores.
Optimised copy job The data is moved between catalyst stores in a bandwidth efficient manner. Only changed ‘chunks’
are actually transmitted across WAN or LAN. Referred to in Symantec NetBackup as ‘Opdupe’ or
‘optimised duplication’.
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Catalyst ISV integration
1. Target-side deduplication

Backup server control StoreOnce Appliance

Store
Store
Buffer(memory) Chunk
Chunk Hash
Hash Matching
Matching Compress
Compress
write chunks
chunks ++
Data write all
all data
data chunks
chunks >> <<
SHA-1
SHA-1 ## Unique chunks metadata
metadata
API Segment
dedupe
user data catalyst client IP connection store

2. Source-side deduplication

Backup Server StoreOnce Appliance

control
Buffer(memory) Chunk
Chunk Hash
Hash
Data send hashes Matching
Matching
SHA-1
SHA-1 #
#
Segment
user data match data
Compress
Compress
>> << Store
Store
API Unique chunks dedupe
chunks
chunks ++
new chunks metadata store
metadata
catalyst client
IP connection

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce Catalyst – new features ISV
controlled replication (low-bandwidth) – multi hop

DP 7 Cell manager/ Site A Site B Site C

Symantec master server

Deduplication StoreOnce StoreOnce StoreOnce

system 1 System 2 System 3

media Catalyst Store WAN

WAN Catalyst Store WAN
WAN Catalyst Store
media agent
agent #1
#1
1 2 3

user data Dedupe Data Dedupe Data Dedupe Data

Backup to Catalyst Store Duplicate low-bandwidth backup to ....and to Site C

StoreOnce System 1 on Site A Site B under ISV control (multi-hop)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
The StoreOnce Catalyst API
HP Data Protector 7 Symantec NetBackup Symantec Backup Exec2015
Backup server Backup server Backup server
DP7 media Media server
agent OST
OST API
API OST
OST API
API
optional optional optional
Catalyst API part dedupe catalyst
catalyst plug-in
plug-in part dedupe catalyst
catalyst plug-in
plug-in part dedupe

catalyst catalyst catalyst catalyst catalyst catalyst

commands data commands data commands data

network
HBA
LAN or
WAN
HP StoreOnce HP StoreOnce HP StoreOnce
Catalyst ‘store’ Catalyst ‘store’ Catalyst ‘store’
Data Protector (NetBackup) (Backup Exec)

Deduplication Deduplication Deduplication

Store Store Store

HP StoreOnce Backup System 

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce - Federated Catalyst


StoreOnce Federated Deduplication
• The architecture is an extension of the HP StoreOnce Catalyst implementation and protocol. Designed of HP multi-node appliances
(B6200 and 6500).
• Catalyst ‘client’ software is embedded in HP DataProtector code or in a ‘plug-in’ module for Symantec NetBackup.
• Each StoreOnce ‘service set’ which runs on a ‘node’ hosts one or more federated stores.
• The catalyst ‘client’ running on a backup server presents a single logical federated catalyst store.
• Data from the backup server is automatically distributed fairly evenly across the federated store.
• Can be configured to distribute between 2 and 10 Stores.
• Catalyst client aggregates data form multiple nodes.
Backup Server
• Supported on DP9 and Symantec NetBackup Backup
App.

• RMAN and SQL plug-ins supported. Catalyst

Client

StoreOnce Node StoreOnce Node StoreOnce Node

Node
Catalyst
‘server’
Node
Catalyst
‘server’
2 – 8 nodes Node
Catalyst
‘server’
Federated
Federated Store
Store Federated
Federated Store
Store Federated
Federated Store
Store
Single logical store

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst
Backup Server Backup Server

StoreOnce Catalyst
Client User Data
Data ISV App. User
Data Protector
Protector Data
(Chunk/Hash/match Plug-in
compress)

WAN or LAN

10GbE internal network

StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node
Node
management Node
management Node
management Node
management Node
management Node
management Node
management Node
management

Catalyst Catalyst Catalyst Catalyst Catalyst Catalyst Catalyst Catalyst

Store#1 Store#2 Store#3 Store#4 Store#5 Store#6 Store#7 Store#8

Catalyst
VTL NAS NAS VTL VTL
Store#9

Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID
Couplet 1 Couplet 2 Couplet 3 Couplet 4
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Multinode System
StoreOnce Federated Catalyst
Backup Server Backup Server

StoreOnce Catalyst
Client User Data
Data ISV App. User
Data Protector
Protector Data
(Chunk/Hash/bid Plug-in
compress)

WAN or LAN

10GbE internal network

StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node
Node
management Node
management Node
management Node
management Node
management Node
management Node
management Node
management

Federated Catalyst Store #1

Federated Catalyst Store #2

Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID
Couplet 1 Couplet 2 Couplet 3 Couplet 4
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. StoreOnce Multinode System
StoreOnce Federated Catalyst is flexible
Backup Server#1 Backup Server#2

StoreOnce Catalyst
Client User Data
Data ISV App. User
Data Protector
Protector Data
(Chunk/Hash/bid Backup Servers
Plug-in using FC VTL
compress) FC-SAN

WAN or LAN

10GbE internal network

StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node
Node
management Node
management Node
management Node
management Node
management Node
management Node
management Node
management
Federated Catalyst Store #1 VTL#2
VTL#1

NAS#1 NAS#2
Federated Catalyst Store #2 Federated Catalyst Store #3

Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID
Couplet 1 Couplet 2 Couplet 3 Couplet 4
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. StoreOnce Multinode System
StoreOnce Federated Catalyst Stores can be expanded!
Backup Server#1 Backup Server#2

StoreOnce Catalyst
Client User Data ISV App. User
Data
Data Protector
Protector Data
(Chunk/Hash/bid Plug-in
compress)

WAN or LAN

10GbE internal network

StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node
Node
management Node
management Node
management Node
management Node
management Node
management Node
management Node
management
Federated Catalyst Store #1

Federated Catalyst Store #2

Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID
Couplet 1 Couplet 2 Couplet 3 Couplet 4
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. StoreOnce Multinode System
…………..and contracted! 
Backup Server#1 Backup Server#2

StoreOnce Catalyst
Client User Data
Data ISV App. User
Data Protector
Protector Data
(Chunk/Hash/bid Plug-in
compress)

WAN or LAN

10GbE internal network

StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node
Node
management Node
management Node
management Node
management Node
management Node
management Node
management Node
management
Federated Catalyst Store #1

Federated Catalyst Store #2

Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID
Couplet 1 Couplet 2 Couplet 3 Couplet 4
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. StoreOnce Multinode System
HP StoreOnce - Federated Catalyst
Routing


Federated Catalyst Routing
• Performed by an HP Labs developed algorithm.
• Now part of the StoreOnce Catalyst ‘client’ software which is embedded in HP Data Protector 9 or supplied as OST
‘plug-in’ for Symantec NetBackup and other integrated catalyst Backup solutions.
• Routes data to multiple federated catalyst stores on different nodes (Federated Catalyst is only supported on the
multi-node StoreOnce models.
• Routing is based on a combination of best chunk matching and space available on node.
• Uses the HP StoreOnce memory based ‘spare index’ in a ‘bid’ system.
• Every 20MB of logical data requests a ‘bid’ from each node derived from the sparse index output.
• The algorithm ensures that each member store are evenly filled!

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Sparse Index revision!
• Each member store of a federation will be located on a StoreOnce ‘node’ and will have it’s own sparse index.
• Sparse index links sample hash codes (known as ‘hooks’) to container IDs in the catalyst dedupe store.
• The sparse index output is a list of container IDs where best matches may be obtained (ie. # of hooks).
• The spares index is memory resident. (FAST!)
chunk
• Each store has a sparse index. chunk
chunk chunk
Container ID=10
• Not used in the read process. Container ID=10
Container ID=32
Container ID=32

chunk
chunk

Container ID=60
Container ID=60
Hash codes

chunk
chunk

Container ID=16
Container ID=16

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Matching. Locality of data – identifying ‘landmarks’

Backup datastreams as a list of ‘chunks’ (~4KB) – a hash code is produced from the chunk data to identify each chunk.

Backup #1

Backup #2

Backup #3

Chunk data around the ‘landmark’ hash remains mostly unchanged. The ‘hook’ is used in a sparse index to determine best
containers for matching.

New chunks – ie some data changed

160 bit hash value with least significant 5 bits = 0. StoreOnce technology refers
To these hash code as ‘hooks’

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Catalyst
Multi-Node Federated Deduplication
Write Data Path
• Each Federation Member is sent sample hashes, and bids based on ability to deduplicate the data segment
• Bid is very efficient; just an in-memory lookup (uses sparse index).
• The data segment is routed to a Federation Member based on bid and other factors

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Deduplication
Multi-Node Federated Deduplication
Read Data Path
• On read the Catalyst Client
will request manifest region
information from each
Federation member store.
• The manifest region
information enables the
Catalyst Client to then request
the data from the appropriate
Federation Member for each
region.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Catalyst Routing – bid process -1

Catalyst
1. Using the data VIF IP the client contacts the federated
User data
Client store. Each store knows about the other federation ‘members’.
Embedded in 2. A list of hash coded representing 20MB of actual data are sent to each
DP or plug-
in
store member.
ISV application sends 3. Each store member checks it sparse index and a ‘bid’ is returned which indicates
A write request. chunk matching potential and it’s free disk space.
4. If this is a new store then one member is chosen at random there will be no bid
‘winner’.

Bid return

StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node

Node
Federated
Federated Store
Store
Node
Federated
Federated Store
Store
Node
Federated
Federated Store
Store
Node
Federated
Federated Store
Store

Sparse Sparse Sparse Sparse

Index Index Index Index

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Catalyst Routing – bid process #2

Catalyst
1. A re-bid is sent to the selected store member and it is matched the
Client actual container indexes are checked for matches.
Embedded in 2. The store member sends a list of hashes it requires to the client. As
DP or plug-
in
this is was an empty store it is nearly all hashes as there is no matches.
ISV application sends 3. The client takes the data from the ISV software and sends chunks across
A write request. the network after compression.
4. These chunks are stored in the StoreOnce system.
5. A new bid is sent on the next 20MB of user data.

StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node

Node
Federated
Federated Store
Store
Node
Federated
Federated Store
Store
Node
Federated
Federated Store
Store
Node
Federated
Federated Store
Store

Sparse Sparse Sparse Sparse

Index Index Index Index

Bid winner

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Catalyst Routing – bid process #3

Catalyst
1. As this is a new store it is likely that the same node ‘wins’ the bid. So the
Client process continues for every 20MB of user data.
Embedded in 2. After a set amount of user data (50GB), in order to prevent filling up a store on
DP or plug-
in
a particular node, the next ‘bid’ is won by the store with the most free space.
ISV application sends 3. The process continues and the other member’s stores fill. There is always a bid
A write request. every 20MB of logical data.

StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node

Node
Federated
Federated Store
Store
Node
Federated
Federated Store
Store
Node
Federated
Federated Store
Store
Node
Federated
Federated Store
Store

Sparse Sparse Sparse Sparse

Index Index Index Index

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Catalyst Routing – bid process #4

Catalyst
1. Once the store is ‘mature’ the bid ‘winner’ is likely to change before
Client the 50GB threshold is reached and data is evenly distributed across the
Embedded in federated store.
DP or plug-
in
2. Whenever there is no clear bid ‘winner’ the store with the most free space is
ISV application sends used. (Bid returns contain store freespace information in addition to sparse
A write request. index hit rate!)

StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node

Node
Federated
Federated Store
Store
Node
Federated
Federated Store
Store
Node
Federated
Federated Store
Store
Node
Federated
Federated Store
Store

Sparse Sparse Sparse Sparse

Index Index Index Index

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Catalyst Routing with NAS/VTL

Full Full
Free space Free space

Node 1 Node 2 Node 3 Node 4 Node 1 Node 2 Node 3 Node 4

Disk space used by existing VTL/NAS data

Subsequent backups to the federated store. 
New data to the federated store (seeding) – ie matching is poor.
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce - Federated Catalyst in
action!


Federated Catalyst in action - GUI

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Creating a federated catalyst store

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Expanding/Contracting a Federated Catalyst store

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Catalyst Stores – HP Data Protector 9

Set IP address of ANY node in the federation

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Deduplication Store in NetBackup 7.6

• Requires OST 3.0 plug-in

• Configure as normal catalyst store (OpenStorage)
• Use one node’s IP address (VIF) to create a Storage Server
• Then configure as a Storage Unit (SU)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Deduplication Stores in GUI


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce - Federated Catalyst
Networking


 
Federated Catalyst Networking – 2 subnet example (No VLANs)
Backup Server

Use any ONE DATA Management VIF

StoreOnce Catalyst VIF in the subnet when
configuring DP Data VIFs subnet 1 Management (GUI/CLI)
Client Gateway or NetBackup WA
Storage Server
Data VIFs subnet 2 N
(Chunk/Hash/bid
compress)
Subnet 1 (default)

Subnet 2

10GbE internal network

StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node
Node
management Node
management Node
management Node
management Node
management Node
management
Node
management
Node
management

192.168.6.210 192.168.6.220 192.168.6.230 192.168.6.240 192.168.6.250 192.168.6.260 192.168.6.270 192.168.6.280

192.168.7.310 192.168.7.320 192.168.7.330 192.168.7.340 192.168.7.350 192.168.7.360 192.168.7.370 192.168.7.380

Federated Catalyst Store #1

Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID
Couplet 1 Couplet 2 Couplet 3 Couplet 4
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. StoreOnce Multinode System
HP StoreOnce - Federated Catalyst
Copy


Federated Catalyst Copy
• Using ISV software (DP9 or Symantec NetBackup) backups can be copied via low-bandwidth links to other catalyst
stores on any network connected StoreOnce appliance.
• Copies can be made to or from non-federated stores – there is no restriction providing there is enough space.
• Use the Data Protector ‘Object Copy’ function or NetBackup ‘Lifecycle Management Policy’.
• RMAN federated catalyst can back up to multiple destinations.
• Care has to be taken with networking because federated stores us the IP address (VIF) which was used to create a
source/server side gateway (DP) or storage server (NBU).
• Data is redistributed to the federated stores at the target system. (uses StoreOnce appliance internal 10GbE network)
• For multiple stores it is worth using different IP addresses for multiple federated stores. In NetBackup create a
storage server for each store using a different node IP address (VIF).

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Subnet #1 on both systems

Federated Catalyst Copy management + data (and is default)
Subnet #1 data
Backup Server

Management VIF Data is copies from node1 (in this example) Catalyst copy data is re-distributed from node2 to the other federation
Configure a gateway / storage server (NBU) members over the internal 10GbE network.
Data VIFs subnet 1 for each StoreOnce system. Backups can be router
via subnet 2 but copies via subnet1.
Data VIFs subnet 2

Subnet 1 (default) Subnet 1 (default)

Subnet 2

10GbE internal network

StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node
Node
management Node
management Node
management Node
management Node
management Node
management
Node
management
Node
management

192.168.6.21 192.168.6.22 192.168.6.23 192.168.6.24 192.168.6.25 192.168.6.26 192.168.6.27 192.168.6.28

192.168.7.31 192.168.7.32 192.168.7.33 192.168.7.34

Federated Catalyst Store #1 Federated Catalyst Store #2

Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID
Couplet 1 Couplet 2 Couplet 1 Couplet 2
StoreOnce Multinode System #1
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. StoreOnce Multinode System #2
HP StoreOnce - Federated Catalyst
max. streams Support


Federated Catalyst Maximum Streams supported.
• StoreOnce 6500 systems support a maximum of 512 streams across the cluster (appliance).
• StoreOnce B6200 systems support a maximum of 192 streams across the cluster (appliance).
• A mixed cluster will support a maximum of 192 streams. (Limited by B6200 couplets).
• Federated and non-federated catalyst will be limited by the same stream count.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Catalyst - FAQ
Q. Will Federated Stores be faster?
A. No. Federated Catalyst deliver much simpler capacity management and more flexibility.

Q. Is Symantec NetBackup Accelerator supported with Federated Catalyst Stores?

A. Yes

Q. When a federation member is full does StoreOnce ‘spillover’ into another store.
A. No. It is likely an alert will be sent before this condition. Forcing spillover has undesirable affects
in dedupe efficiency due to poor matching.

Q. Can Federated Catalyst Stores be encrypted?

A. Yes

Q. Can federated catalyst be configured to perform high-bandwidth backups.

A. No.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Catalyst - FAQ
Q. What is the maximum number of federated stores allowed per appliance?
A. The number of federated stores is limited by the node limit of 48 for any one node.
Provided you don’t exceed the node limit more than 48 could be configured. In theory the
maximum would be 192.

Q. How many nodes can I use for federation members?

A. Between 2 and 8 nodes. Nodes do not have to be consecutive.

Q. What happens if a node fails?

A. Autonomic failover is activated. Federated Store will be available when the service set is
running on it’s partner node.

Q. Can I use Catalyst over Fibre channel?

A. Yes.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce - Catalyst over Fibre
Channel


Why use Catalyst over Fibre Channel?
• CoFC is useful where customers have an existing FC-SAN infrastructure, (Switches, fibre cable etc.).and do not have
10GbE infrastructure.
• Easy to use with minimal changes to configurations.
• Support in 3.12.0 for Federated Catalyst.
• Can be used with NetBackup, Data Protector, RMAN Oracle plug-in
• Fully compatible with catalyst backups using IP network.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over Fibre Channel - Overview
• Common functionality for Catalyst over Ethernet and Fibre Channel
• Low Bandwidth / High Bandwidth Backup
• Client Permissions
• Store Encryption
• Failover
• Federated Catalyst
• Equivalent performance

• Supported on single node and multi-nodes supporting Fibre Channel

• A Catalyst store can be shared for Ethernet and Fibre Channel backups
• A Catalyst backup over Fibre Channel can be restored over Ethernet and a Catalyst Ethernet backup can be
restored over Fibre Channel
• Concurrent Catalyst over Fibre Channel & VTL backup / restore from a single host is possible
• Catalyst copy functionality remains to be over LAN / WAN
• Supported on Windows, Linux and HP-UX 11.31

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Catalyst over FC – Architecture
Catalyst Stack Showing Addition Of
Catalyst Over FCP
• Initiator library is compiled within the current Catalyst
Catalyst Client (e.g. Netbackup) client plugin so there’s only a single version of the
Catalyst Server (HP) Catalyst Client API (HP)
backup application software.
Catalyst Over
FCP Library
• Decision of Catalyst over FC or Ethernet is based on the
address. Addresses starting “COFC-” will use Fibre
Channel, and IP addresses or FQDNs will result in
Linux Sockets Sockets
Ethernet being used. Catalyst over FC identifiers are case
TCP
OS SCSI Host
(Initiator) Stack
TCP
sensitive.
IP IP

Ethernet HP FCP TMD Ethernet

• Architecture supports both Catalyst over FC and VTL
simultaneously from a single host.
Ethernet NIC Qlogic HBA
FCP HBA (Qlogic/
Emulex)
Ethernet NIC • Seamless StoreOnce FC Port Failover (no loss of
connection).
• On platforms other than Linux, concurrent access
FCP SAN
achieved by presenting multiple LUNs (configurable with
maximum of 64 per host HBA port).
• “StoreOnce Catalyst Service” for each service set is
accessible through all accessible target ports of a
StoreOnce node.
Ethernet
LAN / WAN

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over Fibre Channel - GUI
• A new Fibre Channel Settings configuration page is displayed in the GUI

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over Fibre Channel – Step 1
• Zone the Catalyst over Fibre Channel client and StoreOnce target HBA ports

• Each StoreOnce FC port presents a single Catalyst over Fibre Channel WWPN / WWNN.
•

• Use the WWPN / WWNN values to zone each Catalyst over Fibre Channel service with the client HBA port. On the switch, the
Catalyst over FC device will be presented as follows:

• Once zoning is complete the “Number of Logins” will increase in the GUI

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over Fibre Channel – Step 2
• Determine the number of concurrent backup / restore streams required

• On Linux it is possible that a single client HBA port talking to a single StoreOnce HBA port can open multiple concurrent connections;
i.e. backup / restore streams. On Windows this is not possible; Windows has a queue depth of 1.
• Catalyst over FC implements a multi-LUN solution to allow multiple simultaneous connections from a Windows client. By presenting
multiple LUNs a host port can open multiple simultaneous connections to a target StoreOnce port. The number of LUNs is controlled
via the “Devices per Initiator Port” setting in the StoreOnce GUI.

• If a StoreOnce target port is used ONLY for Linux backups the “Devices per Initiator Port” can be left at 1.
• If a StoreOnce target port is used for Windows backups the “Devices per Initiator Port” must be calculated, as described in the next
slides.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over Fibre Channel – Step 2 cont.

• How to Calculate the required number of “Devices per Initiator Port”

• By default each client HBA port to server HBA port will present 1 LUN. If a client HBA port can see multiple server ports, it has
multiple FC routes into the StoreOnce node.
• To increase the number of devices or LUNs presented in each client - server HBA port relationship, increase the “Devices per
Initiator Port” as described below:

• Example 1:
• 1 FC client port zoned with 4 target FC ports of a StoreOnce node.
• With a devices per initiator port setting of 1 for each StoreOnce target port,
• the total possible concurrent streams is 4:

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over Fibre Channel – Step 2 cont.

• Example 2:
• 2 FC client ports zoned with 4 target FC ports of a StoreOnce node.
• With a devices per initiator port setting of 1 for each StoreOnce target port,
• the total possible concurrent streams is 8:

• Example 3:
• 2 FC client ports zoned with 4 target FC ports of a StoreOnce node.
• With a devices per initiator port setting of 2 for each StoreOnce target port,
• the total possible concurrent streams is 16:

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over Fibre Channel – Step 3

• Confirm that the client and target HBA ports are zoned together

• On Linux, use one of the following to list the available “StoreOnce CoFC” devices:

Run “lsscsi --generic”: Run “cat /proc/scsi/scsi”:

•
[root@greenday ~]# lsscsi --generic [root@greenday ~]# cat /proc/scsi/scsi
[4:0:6:0] process HP StoreOnce CoFC CAT1 - /dev/sg6 Attached devices:
[4:0:6:1] process HP StoreOnce CoFC CAT1 - /dev/sg7 Host: scsi4 Channel: 00 Id: 06 Lun: 00
Vendor: HP Model: StoreOnce CoFC Rev: CAT1
Type: Processor ANSI SCSI revision: 03
Host: scsi4 Channel: 00 Id: 06 Lun: 01
Vendor: HP Model: StoreOnce CoFC Rev: CAT1
Type: Processor ANSI SCSI revision: 03

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over Fibre Channel – Step 3 cont.

• On Windows:
Devices will be displayed in the “device manager” in the “other devices”
section

• NOTE: If you increase the number of “Devices per Initiator Port” in

the StoreOnce GUI you must “scan for hardware changes” in the
Windows “device manager” before the new devices will be seen by
Windows.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over Fibre Channel – Step 4
• Backup using the Catalyst over FC Identifier or Alias

• In Ethernet, Catalyst backups are performed using the VIF / FQDN address of the StoreOnce service set. Catalyst
over FC has equivalent addresses called the “Identifier” and “Alias”. The “COFC-” addresses should be used
where an IP address would have previously been entered.

• Identifiers may not be modified, but users can alter the alias. All addresses must begin “COFC-” as this is the
way that Catalyst determines the backup / restore is Fibre Channel based.

• Identifiers and aliases are case sensitive and must be entered into the backup application correctly.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over FC – StoreOnce configuration

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over FC – NetBackup configuration

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over FC configuration - Data Protector 9

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst over FC – Catalyst Store.

Note that the actual store configuration is identical to Catalyst over IP store.
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Subnet #1 on both systems

StoreOnce Catalyst over FC Copy management + data (and is default)

Subnet #2 data
Backup Server
Catalyst copy via IP network
Configure 2 Data Protector FC Management VIF
gateways or 2 Storage Backup/recovery to catalyst store#1 Backup via CoFC – FC SAN
Servers (NetBackup) Data VIFs subnet 1
router Data VIFs subnet 2
NIC
FC
SAN

Subnet 1 (default) Subnet 1 (default)

Subnet 2

10GbE internal network 10GbE internal network

StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node StoreOnce Node

Node
management Node
management Node
management Node
management Node
management Node
management
Node
management
Node
management

192.168.6.21 192.168.6.22 192.168.6.23 192.168.6.24 192.168.8.25 192.168.8.26 192.168.8.27 192.168.8.28

192.168.7.31 192.168.7.32 192.168.7.33 192.168.7.34

Catalyst Store 1 Catalyst Store 2

Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID
Couplet 1 Couplet 2 Couplet 1 Couplet 2
StoreOnce Multinode System #1
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. StoreOnce Multinode System #2
Catalyst over Fibre Channel FAQ
Q: Is Catalyst over fibre channel supported with Federated Catalyst?
A: Yes (requires DP 9.02)
Q: I received -1404 error (server offline) when starting my backup / restore.
A: Check that the client / target FC ports are zoned together correctly
If you are using a Windows client please ensure the “Devices per Initiator Port” is set appropriately
If you have increased the “Devices per Initiator Port” you may need to “scan for hardware changes”
via Windows “Device Manager”
Q: Can I use Catalyst Over Fibre Channel with single-node StoreOnce models?
A: Yes

Q: Which Backup applications support Catalyst over Fibre Channel?

A: HP Data Protector 9, NetBackup using OST 3.0/3.1 plug-in, RMAN to catalyst 2.0

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Catalyst over Fibre Channel FAQ
Q: Can I perform Catalyst Copy operations with catalyst over FC?
A: No. Copy functions must use TCP/IP connection.

Q: Can the connection to StoreOnce just be fibre channel?

A: Yes. For backup/restore (but not copy).


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce – VTL/NAS Replication


HP StoreOnce VTL and NAS replication
• Federated data deduplication to reduce amount of data that needs to be
replicated
• Network efficient offsite data replication
• Enabling the use of lower bandwidth, lower cost links
• Target device requires VTL/NAS Replication License
• VTL/NAS replication controlled and managed by the StoreOnce device

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Replication deployment options (VTL/NAS)
Controlled & managed by the StoreOnce device Replication
license

Active to Passive configuration Active to active configuration

StoreOnce StoreOnce StoreOnce StoreOnce
VTL Copy VTL VTL Copy VTL
NAS share Copy NAS share Copy NAS share NAS share

Many to one configuration N-way configuration

StoreOnce VSA StoreOnce StoreOnce
VTL 1 VTL 1 Copy VTL 1
StoreOnce
StoreOnce Copy VTL 2 NAS share
Copy VTL 1 + 2
VTL 2
Copy NAS share VTL 2
StoreOnce
NAS share
Copy NAS share 
StoreOnce
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce – Catalyst Copy


HP StoreOnce Catalyst Copy
• Federated data deduplication to reduce amount of data that needs to be
replicated
• Network efficient offsite data replication
• Enabling the use of lower bandwidth, lower cost links
• Controlled and managed via supported backup application
• Backup application aware of copied data
• Catalyst license required at source and target StoreOnce device

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst Copy deployment options
Controlled & managed by supported Backup application Catalyst
license

Active to Passive configuration Active to active configuration

StoreOnce StoreOnce StoreOnce StoreOnce
Catalyst Store Copy Catalyst Store Catalyst Store Catalyst Store

Many to one configuration

StoreOnce
Catalyst Store 1
StoreOnce
StoreOnce Copy Catalyst Store
1+2+3
Catalyst Store 2

StoreOnce VSA
Catalyst Store 3

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Catalyst Copy deployment options
Controlled & managed by supported Backup application Catalyst
license

N-way configuration One to many configuration

StoreOnce StoreOnce StoreOnce
Copy 1 Catalyst Copy 1 Catalyst
Catalyst Store
Store Store
StoreOnce StoreOnce
Copy 2 Catalyst
Copy Catalyst Store
Copy n Catalyst Store
Store
StoreOnce StoreOnce
Copy 3 Catalyst
Store


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce - DR scenario based on
VTL/NAS


HP StoreOnce VTL/NAS Disaster Recovery – Scenario 1
ISV IDB
QWERT
XYZ
UIOF
Res Disco
ABC tor ver
Daily Backup e Da tar
nadta get
sca V
n d TL/N
SAN/LA ev i
Optional: ce AS
Regular copy to N
physical tape

StoreOnce StoreOnce
Tape
failure
VTL / NAS VTL / NAS
Library share HP StoreOnce low- share
bandwidth replication

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 HP StoreOnce VTL/NAS Disaster – Scenario 2
Replication of ISV
IDB to DR site
ISV IDB ISV IDB
QWERT
XYZ
UIOF
ABC

Daily Backup Optional:

e
at
SAN/LA SAN/LA Regular copy to

D
physical tape

re
N N

sto
Re
StoreOnce StoreOnce
Tape
VTL / NAS VTL / NAS
share HP StoreOnce low- share Library
bandwidth replication

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 HP StoreOnce VTL/NAS Disaster – Scenario 3

ISV IDB ISV IDB

QWERT QWERT
XYZ XYZ
UIOF UIOF
ABC ABC

Daily Backup Optional:

ile
ttaFT
oahEreS
SAN/LA SAN/LA Regular copy to

apRc
gD
Cm
physical tape

I icrsaeienI
N N

AP ecsOcetedons
oAerM
SRt
StoreOnce StoreOnce
Tape
VTL / NAS VTL / NAS
share HP StoreOnce low- share Library
bandwidth replication


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce - Replication/Catalyst
Copy – Initial seeding


 ATTENTION
Seeding over WAN link
Initial seeding may take
longer as more data will be
Initial
StoreOnce transfered or temporary use
backup Initi
VTL / NAS al seed a higher bandwidth for the
ing
share / Catalyst seeding process.

Initial Initiall seeding

StoreOnce StoreOnce
backup
VTL / NAS WAN VTL / NAS
share / Catalyst share / Catalyst

Initial
StoreOnce e ding
backup ia l se
VTL / NAS Init
share / Catalyst

WAN Bandwidth

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Co-location (seed over LAN)
Initial backup to local
Initial seeding of
StoreOnce System
StoreOnce target System
StoreOnce StoreOnce
VTL / NAS LAN VTL / NAS
share / Catalyst share / Catalyst

Re-establish
Replication/ WAN
Catalyst Copy

StoreOnce
VTL / NAS
share / Catalyst

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Floating StoreOnce

StoreOnce Floating SO StoreOnce Floating SO StoreOnce Floating SO

VTL / NAS share VTL / NAS share VTL / NAS share VTL / NAS share VTL / NAS share VTL / NAS share
/ Catalyst / Catalyst / Catalyst / Catalyst / Catalyst / Catalyst

Est
abl

Est alyst
sh i

Ca t

/
ion
rep

abl Cop
Initial seeding lica Initial seeding Initial seeding

op licat
ish
tio
site #1 n/
Ca
site #2 site #n

rep

ys rep
y
t aly

lica
st C

tal sh
tC
y
o py WAN

Ca tabli
tion

Es
/
StoreOnce Floating SO
VTL / NAS share VTL / NAS share
/ Catalyst / Catalyst

Copy data from remote sites

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
to central SO target device
 Backup application Tape offload

Initial Initial Initial

backup backup backup
Copy initial Copy initial Copy initial
backup to tape StoreOnce backup to tape StoreOnce backup to tape StoreOnce
VTL / NAS share VTL / NAS share VTL / NAS share
/ Catalyst / Catalyst / Catalyst

catalys replication /
Es
ta bl i
sh co py
rep st
lic ca taly

t copy
ati /
on WAN at ion
/ ca lic

sh
taly rep

Establi
st is h
Co st abl
py E

StoreOnce
Copy data from tape to central
VTL / NAS share
/ Catalyst target StoreOnce

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 backup application copy to USB disk

Initial Initial Initial

backup backup backup
Copy initial Copy initial Copy initial
backup to disk StoreOnce backup to disk StoreOnce backup to disk StoreOnce
NAS share / NAS share / NAS share /
Catalyst Catalyst Catalyst

catalys replication /
Es
ta bl i
sh co py
rep st
lic ca taly

t copy
ati /
on WAN at ion
/ ca lic

sh
taly rep

Establi
st is h
Co st abl
py E

StoreOnce
Copy data from disk to central
VTL / NAS share
/ Catalyst target StoreOnce

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce - Licences


Licensing requirements for StoreOnce HW products
• There are two types of license:
• Full license (not time limited)
• Instant on or Demo (time limited to 90 days): This allows you to try out licensable functionality before paying for a full license for any of the
features described below.

• The HP StoreOnce Backup system licensing requirements are:

• All capacity expansion must be licensed. Each storage expansion kit contains a license that must be loaded.
• No licensing is required for VTL or NAS emulations.
• VTL and NAS replication requires a license (per couplet) on the target system.
• StoreOnce Catalyst devices require a license for backup and for Catalyst copy (Catalyst replication), so licenses must be installed on both origin
and destination systems. A StoreOnce Catalyst license, if required, must be installed on every couplet in the cluster. Without a StoreOnce
Catalyst license for each couplet, the StoreOnce Catalyst feature is reported as unlicensed for the entire HP StoreOnce Backup system.
• Security features (Data at Rest Encryption, Data in Flight Encryption, and Secure Erase) require a Security license. A Security license, if
required, must be installed on every couplet in the cluster. If you do not add a Security license for each couplet, the Security feature is reported
as unlicensed for the entire HP StoreOnce Backup system.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Licensing requirements for StoreOnce HW products
StoreOnce Catalyst License

NOTE: HP StoreOnce VSA license already includes StoreOnce Catalyst. No additional license required.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Licensing requirements for StoreOnce HW products
VTL/NAS Replication

Replication licenses enable an appliance to host replication target libraries.

(No license is required for appliances which only act as replication sources)
For the 6500 a separate license is required per couplet (EJ026A or EJ026AAE)
NOTE: HP StoreOnce VSA license already includes replication. No additional license required.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Licensing requirements for StoreOnce HW products
HP StoreOnce Security Package

An HP StoreOnce Security Pack license (2600, 2700, 2900, 4200, 4400, 4500, 4700, 4900, B6200, 6500) is required for each
appliance .The StoreOnce Security Pack license for the 6000 is required per couplet.
A 90 day trial license is available. Each license includes HP StoreOnce Data at Rest, Data in Flight Encryption and Secure Erase.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Instant On license / Demo license
To apply an Instant On license / Demo license
• The Instant On license is available for all StoreOnce Backup systems
• Is a single license that enables two features:
– StoreOnce Catalyst and StoreOnce Replication, for a period of 90 days.
• This allows customer to try some of the advanced features in StoreOnce units without having to purchase a full license in advance.
• This license does not include capacity expansion nor the Security Pack.
• To continue using these features, separate licenses must be purchased for StoreOnce Catalyst and Replication and applied within the Instant-
On period. If they are not, data is not lost but:
– Replication: Replication Target libraries will continue receiving replicated data, however, you will receive notification every 24 hours that your license has expired.
– StoreOnce Catalyst: Catalyst stores will still be available as target devices for backup, however, you will receive notification every 24 hours that your license has
expired.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Instant On license / Demo license
To apply an Instant On license
• Use StoreOnce CLI commands as follows:
– >license show
– to show the current license status
– >license add demo
– to apply the 90–day license for all licensable features.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Full License
Obtain/redeem a license
• Features that require a license include a license entitlement certificate with the hardware product.
• This is either an electronic document provided at purchase, such as Replication, StoreOnce Catalyst, Security (Data at Rest Encryption, Data in
Flight Encryption, or Secure Erase), or a paper document provided with a capacity upgrade kit.
Note: Keep the paper document at a safe place – DON’T LOOSE IT!
• The document contains all information required to obtain a unique License to Use (LTU) key.

• Obtain the key from the HP Licensing web site (http://www.myhplicensing.hp.com)

• product's serial number required when requesting an LTU key.
– the System ID that can be found on the Device Configuration page of the GUI. This is a 14–digit alphanumeric string in lower case that has "hp" as the first two
characters.
– Do not use the warranty serial number that can be found on the server or tag attached to it.
– The key is specific to the HP StoreOnce Backup system. It cannot be transferred.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Full License
Install a License
• Save LTU as a file in StoreOnce repository
– sftp Admin@<Management_VIF>
– cd repository
– put <LTU>.dat
– exit sftp
• Note: Ensure the File Protocol is set to SFTP, not SCP when using a Windows sftp client

• Verify the LTU is stored within the repository using StoreOnce CLI command:
– system show repository
• Apply the license using one of the following StoreOnce CLI commands:
– license load <LTU>.dat
• to load a license that has been saved as a file image. The file image must exist in the Backup system's repository directory.
– license add <license key string>
• to key in the license directly.


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce – Security Features


Encryption of data at rest

• new VTL/NAS/Catalyst data store can be encrypted.

• Encryption is enabled at store creation time (cannot be retrospectively applied) and is
implemented with FIPS approved algorithm (AES-256).
• Requires security pack licence.
• Keys are generated internally – one key for each data store. Keys are ‘wrapped’ and
can be saved with configuration backup. Restore however would only be required if
key store file is corrupted. The key is stored in 2 locations anyway!
• The store cannot be re-keyed. IE all data re-encrypted with a new key.
• Data is decrypted before replication or catalyst copy.
• Data in flight encryption will be enabled in later software releases.
• Performance overhead is low (<10% degradation on write <5 % read)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Enabling encryption VTL

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Enabling encryption – StoreOnce Catalyst

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Security Enhancements in 3.12.0
User data
Create
Create device
device –
–
enable/disable
enable/disable
encryption key
key store
store config
config
encryption
(passphrase)
(passphrase)

Data at rest encryption module

VTL Catalyst NAS ICAPI
ICAPI (access
(access layer)
layer)

StoreOnce Chunk + hash Store Manager Manager Software Local Key Management
Dedupe
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Store
Store ID
ID Key
Key ID
ID CRC
CRC
match + compress Generate Key Store Generate Key Store Key Store
Store
Store ID
ID Key
Key ID
ID CRC
CRC Backup Backup
Encryption Key (KEK)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Store
Store ID
ID Key
Key ID
ID CRC
CRC
Sort
Sort &
& save
save
New key Key store API

Request key
Ñ
Ñ

Encrypt Encrypt data

metadata Key chunks Key
Delete Key

REST API calls

KSEK
KSEK
Metadata Deduplication store Stores Key ID and
(location)
(location) Encrypted key store
CRC of key used
System Filesystem
StoreOnce Filesystem

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Security Enhancements in 3.12.0
User data
Create
Create device
device –
–
enable/disable
enable/disable
encryption key
key store
store config
config
encryption
(passphrase)
(passphrase)

Data at rest encryption module

VTL Catalyst NAS ICAPI
ICAPI (access
(access layer)
layer)

StoreOnce Store Manager Manager Software Local Key Management

Request Dedupe
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
data Store
Store ID
ID Key
Key ID
ID CRC
CRC Generate Key Store Generate Key Store Key Store
Store
Store ID
ID Key
Key ID
ID CRC
CRC Backup Backup
Encryption Key (KEK)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Store
Store ID
ID Key
Key ID
ID CRC
CRC
Re-assemble data
Request key
Key store API

Key
Ñ
Ñ

Decrypt Decrypt data

metadata Key chunks Key

REST API calls

KSEK
KSEK
Metadata Deduplication store Stores Key ID and
(location)
(location) Encrypted key store
CRC of key used
System Filesystem
StoreOnce Filesystem

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Storeonce encryption – VT CLI commands

• CLI command for creating an encrypted VTL:

• There is no CLI equivalent for StoreOnce Catalyst in 3.9.0

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Storeonce Encryption – saving the keystore

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Secure erase- data shredding
• If enabled will securely delete on overwrite/erase or complete store removal. Available VTL/NAS/Catalyst. Only
unreferenced chunks will be erased as part of the housekeeping process triggered by overwrite/erase. Complete
store removal will erase everything! This parameter can be selected/unselected at any time.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Secure Erase- (data shredding)

• Erase is to comply with NIST SP 800-88 standard

• An event log entry will be made when secure erase is completed.
• Start process with the backup application. Recycle/export media. From
the tape menu delete tapes.
• Not recommended to delete catalyst items. The backup application will
clean up its own store. Use as last resort.
• Secure erase in incorporated into the housekeeping jobs. There will be a performance
overhead so schedule wisely.
• If a VTL/Catalyst store is deleted secure erase will overwrite the contents before
removing the files.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Storeonce encryption of data in-flight
• ip packets have no inbuilt security measures. Access to the network enables packet content to be viewed. There is no
verification so there is no indication as to whether a packet has been viewed or the content modified.
• ipsec is an OSI layer 3 protocol which provides encryption and mutual verification.
• HP StoreOnce now supports ipsec on all models
• Enabled in the network configuration via the CLI.
• Cannot be set on a management only subnet in a multi-node system. (Access to management GUI is encrypted
anyway.)
• A security pack license is required
• Performance is impacted and is dependent on model – worst case 40% reduction in throughput
• Configure of hosts is via Windows local security policy

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Storeonce encryption of data in-flight CLI example

# net show config ipsec_test ----------------------

Network: subnet_2
---------------------- ----------------------
Network Name: ipsec_test IP Addresses: 192.168.7.141
Network Description: Created by wizard on: Wed Mar 12 14:34:26 2014 Net Mask: 255.255.255.0
Write Protected: no Domain Name:
DNS Servers: 192.168.0.2 192.168.0.3 Gateway:
Port Sets: portset_1 portset_2 Default Network:
Management VIF: 192.168.6.20 Net Usage:
---------------------- VLAN tag: 17
Number of Networks: 2 Port Set: portset_2 with these interfaces: eth2 eth3
Number of VLANs configured: 1 out of possible 128 Encryption Links: IP Address: 192.168.4.31 Key ID: K34323536-3832-5A43-3331-313141563557-
---------------------- 03AACDF0-2F9-535E2EB8
Network: subnet_1 Bonding Mode: 6 (Active Load Balance Bonding)
----------------------
IP Addresses:
192.168.6.11,192.168.6.12,192.168.6.13,192.168.6.14,192.168.6.15,192.168.6.16,192.168.6.17,192.168.6.1
8
Net Mask: 255.255.255.0
Domain Name: nearline.local
Gateway: 192.168.6.1
Default Network: yes
Net Usage: both
VLAN tag:
Port Set: portset_1 with these interfaces: eth0 eth1
Encryption Links:
Bonding Mode: 6 (Active Load Balance Bonding)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Signed Firmware

• Signed firmware guarantees the authenticity of code supplied by HP.

• Code is signed with an electronic signature. When code is signed it answers the
following question for customers:
1. Does this code originate from HP?
2. Has the code been modified since leaving HP?

• Both Quick Restore images and RPM updates are digitally signed by HP at build
time. (This is before code images reach a download site).
• If signature is incorrect code will not load/update!
• The code is signed by computing a hash function and encrypting the result. This is
digital certificate.
• When loaded the code uses the same public key cipher to test its authenticity.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Security – disable root access

• Root access is now disabled from the console in the 3.9.0 code. Access is only via ssh.
(root access is restricted to HP R&D and support staff).
• There is a new login to reset the Admin password.
• To reset the default Admin password login from either the console(monitor/keyboard
connected to appliance) or iLO (single-node systems only). You cannot login from an
ssh connection.
Login as hpresetpassword and the password ‘hpresetpassword’.
This account has only 2 functions:
1. Reset the Admin password to default which is ‘admin’. Use the CLI command
>reset (this will reset the Admin account password to admin)
2. Change it’s own password. It is recommended this is performed immediately after
code upgrade. But don’t lost it! Use the CLI command: >manage (you will be
prompted for old and new passwords).

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 
Security – SSL certificate
• Eliminate ‘man in the middle’ attacks
• Certificate can now be modified with user details – modify function.
• Can generate a certificate signing request for 3rd party SSL certificate supplier and then re-import.
• Optionally export a self-signed certificate and import into browser.
• 3rd party intermediate certificates are pre-installed in browsers.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce - Enhanced Data
Integrity


Additional data integrity checking

• Since 3.9.0 software includes additional data integrity checks.

• Every piece of user data now has a checksum applied as it is written.
This is checked on read and if incorrect the store will report a data
integrity error and pass a check condition to the host.
• The container index file also have data check.
• StoreOnce 3.9.0 uses a SHA-1 hash for data (chunks). This is the most efficient and
only costs incurs 3% performance penalty.
• Container Index files have MD-5 hash applied
• Metadata also has MD-5 hash applied and checked on read.
• Applied at the ‘entity’ level following data compression. This is how StoreOnce
writes chunks into containers.
• VT still has an additional CRC checksum added to every data block. 
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce – Microsoft Active
Directory Support


User accounts and AD
• User Management
• Two “local” user accounts, Admin and Operator, and passwords are created at installation time. Users may use the User
Management tool page to modify the passwords. They may also create, edit, and delete additional users.
• User accounts and AD
– Before granting access to external users or groups using the User Management tool, you must:
1. Set the Authentication mode to AD on the NAS CIFS server tab.
2. Add the StoreOnce device to an AD domain.
3. Add any required users or groups to your active directory to grant access to the AD domain.
4. Grant your external users or groups access permissions to the HP StoreOnce backup system using the User Management tool
page.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Joining a domain:
• To use AD for user login authentication OR CIFS share access control the StoreOnce appliance must be first be
joined to a domain.
• For StoreOnce multinode systems join each service set to the same domain.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
AD integration – joined successfully to domain

• Note that now there is a local administrator PLUS a domain admins group as default.
In this section users or groups can now be added for CIFS share access management.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
AD integration – managing share access 1
• Use the MMC to add the snap-in for shared folders. (run > mmc. The file >add/remove snap-in)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
AD integration – managing share access 2
• Enter the hostname* of the StoreOnce system
(* note in this case we have manually added a pointer A record to DNS.
Default StoreOnce hostnames are of the form HP<<serial no.>>. With current software it is not possible to set a hostname for the appliance.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
AD integration – managing share access 3

• The snap-in console now displays the shares on the StoreOnce appliance.
Right-click on the share to manage the permissions.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
AD integration – managing share access 4

Click on tab ‘share

permissions – select
desired access.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
AD integration – adding domain users for management of the appliance

• Now the appliance is joined to the domain we can now add users or groups to
the user management section. The role can be Admin or operator. Note the default
local users Admin and operator

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
AD integration – domain user logging in


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce - Networking


Accessing the StoreOnce Management Console
There are two ways of accessing the StoreOnce Management Console:
• Using the StoreOnce Command Line Interface, CLI
• Using the StoreOnce Web Management Interface, GUI

LAN Port 1 to a DHCP-enabled 1 Gbit ethernet network

• connect to and manage the StoreOnce Backup system from any client attached to the same network using the appliance's Fully
Qualified Domain Name (FQDN)
• Once connected, run the StoreOnce CLI network commands to optimize your network configuration
• HP StoreOnce 2700, 2900, 4500, 4700 Backup systems support DHCP

If network is not DHCP enabled or you have attached to a different network port
• connect a monitor with keyboard directly to the appliance to configure initial network settings using the StoreOnce CLI
commands.
• As a minimum, you must configure network access to the StoreOnce CLI and GUI across the internet.
• Once configured for internet access, use the StoreOnce CLI or GUI, as appropriate, to manage the appliance and refine network
settings, as appropriate.

266 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Systems – networking configuration
StoreOnce Single Nodes
• Similar configuration syntax across the range.
• Configuration ‘wizard’ (net set wizard)
• Network settings can have individual subnets or bonded connections.
• Bonding can not mix 1GbE and 10GbE interfaces in the same ‘bond’.
• Bonding modes 1,4 and 6 are available.
• A gateway can be configured for each subnet. (1 gateway must be default).
• Only IP addresses are displayed by the management GUI.
• If bonding is set and 2 switches are in use they must be layer 2 linked somewhere in the network.
• Mode 6 bonding will failover if one network connection is lost.
• No special switch support is required for mode 6 bonding.

267 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
Portsets
What are portsets?
• A port set defines the physical 1 Gbit and 10 Gbit Ethernet ports that you intend to connect to your network.
• A port set also defines the network bonding mode (1, 4 or 6) for the ports and whether they are VLAN enabled.
(VLAN tagging enables more subnets to be accessed without extra NIC host bus adapters.)
• At least one Port Set must be configured to support connection to the StoreOnce Management CLI and GUI.
Further Port Sets may be defined, according to the number and type of physical ports still available and how
they are bonded.
• Each Port Set will have at least one Subnet.
• If the Port Set is not VLAN enabled, it may be configured with one Data Subnet that uses the IPv4 protocol and
one Data Subnet that uses the IPv6 protocol. (This configuration is sometimes referred to as a dual stack
configuration.)
• If the Port Set is VLAN enabled, multiple virtual subnets (IPv4 and IPv6), up to a maximum of 128 for the
whole system, may be attached to a single Port Set. If VLAN enabled, a Port Set cannot use bonding mode 6.

268 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
Subnets
What are subnets?
• Subnets define the network paths used by clients to access the StoreOnce Backup system for Backup and
Management, and the network paths that are used for StoreOnce Catalyst Copy and Replication.
• Subnets are attached to each Port Set that is configured. Both IPv4 and IPv6 address protocols are supported.
Single-node systems also support DHCP.
• IPv6 is supported for backup to all StoreOnce Catalyst stores, replication and Catalyst Copy, and for appliance
management. It cannot be used with VTL or NAS shares (CIFS or NFS).
• If multiple Subnets are defined, one (and only one) Subnet for each protocol, IPv4 and IPv6, must always be
designated as the default Subnet for routing traffic to IP addresses that are not within the configured Subnets.
• StoreOnce software provides support for Data In Flight Encryption using the IPSec protocol. This can only be
configured using the StoreOnce CLI (requires HP StoreOnce Security Package).

269 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
Network configuration hierarchy

DNS Servers (up to 3, IPv4 and IPv6)

Portset 1 Portset n
• Ports • Ports
• Bonding Mode – 1,4,6 • Bonding Mode – 1,4,6
• VLAN enabled - yes/no • VLAN enabled - yes/no

Subnet A Subnet n
• DHCP/Static – yes/no • DHCP/Static – yes/no
• IP Address • IP Address
• Gateway • Gateway
• Netmask/Prefix • Netmask/Prefix
• Domain Name • Domain Name
• VLAN Tag ID • VLAN Tag ID
• Default Subnet – Y,N • Default Subnet – Y,N

270 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
IPv6 Support

IPv6 is enabled in >=3.12.1 code release.

What is supported:
• Access to the management interface via CLI and GUI.
• Active Directory user authentication.
• Catalyst and NAS/VTL Replication data path.

What is NOT supported*:

• CIFS data path.
• NFS data path.
• VTL iSCSI data path.
• IPSec encrypted connections.

NOTE: There is no change to IPv4 support for interfaces that are not configured to use IPv6.

271 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
Network bonding modes
Mode 1 (Active/Backup)
– This is the most simple bonding mode; it allows network traffic via one active port only and requires no specific extra switch
configuration. It is recommended for simple network connections, if the active network link fails then traffic moves to the
backup port.
Mode 4 (IEEE 802.3ad Dynamic Link Aggregation)
– This bonding mode is also known as LACP and requires a special external switch configuration. It provides a link aggregation
solution, increasing the bond physical bandwidth, but only works if all the ports in the bond are connected to one switch or
switches joined by an interswitch link. It is recommended when:
• The customer wants to increase throughput to the StoreOnce appliance.Trunks between switches on the customer network already use LACP
mode. The LACP protocol only works when it is configured on both the network switch and StoreOnce end of the connection. Please refer to
your switch documentation for information on LACP configuration.
Mode 6 (Active Load Balancing)
– This mode provides a load balance solution. It does not require specific external switch configuration but does require the
switch to allow ARP negotiation. It can be used in a 2–switch configuration.
– This configuration is generally recommended for backup data performance and also for resiliency of both data and
management network connectivity. However, in some environments ARP packet negotiation may be disabled within the
network infrastructure, so this mode may not be appropriate

272 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
VLAN guidelines

• The user can configure up to a total of 128 different VLAN Subnets on each StoreOnce Backup system; the VLAN Subnets may be
consecutive or non-consecutive.
• The user can configure all VLAN Subnets on one Port Set or divide the VLAN Subnets over multiple Port Sets.
• It is not permitted to configure VLAN Subnets on a Port Set that uses Mode 6 network bonding.
• Each VLAN tag interface is configured using the VLAN ID index, which is the same as the switch VLAN ID number and must be an
integer from 2 to 4094.
• Each VLAN tag interface can configured for use with one IPv4 and one IPv6 subnet.
• For example, if a VLAN tag ID was configured for use with ports eth 0 and eth1 on IPv4, it can also be configured for use on IPv6 with that
Port Set but it cannot be used with any other Port Set.
• The user can add/delete/modify the VLAN network configuration without interrupting non-affected network configuration on the appliance.
• VLAN tagging does not increase bandwidth because the bandwidth is bound by the physical speed of the Port Set. The number of open
streams is bound by the specification for the StoreOnce appliance.
• StoreOnce monitoring is on the physical Port Set, not on each VLAN Subnet.
• VLAN tagging is not a multi-tenancy solution. Once configured, all StoreOnce services can bind / listen to all VLAN Subnets. For example
the NAS shares are available on all configured Subnets, and permissions are required to regulate access to shares.

273 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce 2700 model – physical network connections

RAID CTRL 1
1

USB ports
eth2 eth0
eth3 eth1 Monitor/Console

1GbE ports

• HP StoreOnce 2700 has 4 x 1GbE ports. They can be configured for individual subnets
or bonded in any combination. Note for initial configuration the unit is configured with one
subnet set to DHCP.

274 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce 2700 Systems – networking example configuration – 4
subnets

Network – subnet#4

Network – subnet#3

Network – subnet#2

Network – subnet#1

default gateway eth0 eth1 eth2 eth3 gateway

subnet #1 subnet #3
4 network ports on motherboard (LoM)
gateway gateway
subnet #2 StoreOnce 2700 subnet #4

DNS server address Backup System

entries (max 3)
Domain name

275 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce 2700 System – networking example configuration 3 subnets
with bonding (no VLANs)

Subnet#3

Subnet#2

Subnet#1 (default)

Bond

default gateway eth0 eth1 eth2 eth3 gateway

subnet #1 4 network ports on motherboard (LoM) subnet #3
gateway
subnet #2 StoreOnce 2700
Backup System
DNS address (max. 2)
Domain name

276 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce 2700 System – networking example configuration (with
VLAN tagging)
subnet 1 subnet 2 192.168.4.21
192.168.1.21 192.168.2.21 VLAN 30 (subnet 4)
Network
Network Switch
Switch
192.168.1.1
U U U U T T U U U U U U

VLAN 23(subnet 3)
Subnet#2

Subnet#1 (default)

Bond

eth0 eth1 eth2 eth3

4 network ports on motherboard (LoM)

StoreOnce 2700 Backup System

Subnet # IP address Portset VLAN gateway management/data default network
Default
1 192.168.1.20 eth0 No 192.168.1.1 Both yes
Gateway
2 192.168.2.20 eth1 No both no

3 192.168.3.20 eth2, eth3 23 both no

277 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
4 192.168.4.20 eth2, eth3 30 both no
StoreOnce 2900 model – physical network connections

278 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce 2900 – Networking
Example Configuration: 6 subnets, no VLAN tags
Subnet#6

Subnet#5

Subnet#4

Subnet#3

Subnet#2

Subnet#1(default)

default gateway
eth0 eth1 eth2 eth3 eth4 eth5
subnet #1
gateway 4 network ports on motherboard (LoM) 2 x 10GbE NIC
subnet #2
StoreOnce 2900
DNS server address
entries (max 3)
Backup System
Domain name

279 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
 StoreOnce 2900 – Networking
Example configuration: 4 Subnets, Bonded Interface, VLAN tags

Server 3 IP=10.7.8.1 Server 4 IP=10.5.5.2

server 1 ip=192.168.6.1 server 2 ip=10.7.7.3

subnet 1 VLAN 126 Subnet

Subnet 3
3 Subnet
Subnet 44 subnet 2 VLAN 124
VLAN 22
VLAN 22 VLAN
VLAN 23
23

U U U U U U U U U U U U T=tagged port
T T U U U U U T U=tagged port

VLAN tag=22 VLAN tag=124 VLAN tag=126

VLAN tag=23
default gateway bond

subnet #1 only
eth0 eth1 eth2 eth3 eth4 eth5

DNS server address 4 x 1GbE network ports on motherboard (LoM) 2 x 10GbE NIC
entries (max 3) subnet 1 vlan tag 124 subnet 192.168.6.2 eth4 StoreOnce
StoreOnce 2900
2900
subnet 2 vlan tag 126 subnet 10.7.7.4 eth4 Backup System
Backup System
Domain name
subnet 3 vlan tag 22 subnet 10.7.8.4 eth1 eth2
subnet 4 vlan tag 23 subnet 10.5.5.1 eth1 eth2

280 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce 4500 model – physical network connections

2 x 10GbE ports (fibre/copper)

eth5 eth4

RAID CTRL 1

8Gb FC 10GbE
4 1

iLO4 USB ports

eth2 eth0
eth3 eth1
Console

4 x 1GbE ports
LoM (LAN on motherboard)

• Note: 10GbE SFP+ are supplied with system

281 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
 StoreOnce 4500 System – networking example configuration 6 subnets
no VLANS
Subnet#6

Subnet#5

Subnet#4

Subnet#3

Subnet#2

Subnet#1

default gateway gateway

eth0 eth1 eth2 eth3 eth4 eth5 subnet #3
subnet #1
gateway 4 network ports on motherboard (LoM) 2 x 10GbE NIC gateway
subnet #2 subnet #4
gateway
StoreOnce 4500/4700
subnet #5
DNS server address Backup System gateway
entries (max 3) subnet #6

Domain name
282 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce 4900 Network Connections

RAID
RAID Ctrl
Ctrl RAID
RAID Ctrl
Ctrl

8Gb
8Gb FC
FC eth7 bonding
10GbE
10GbE mode eth6
1
8Gb
8Gb FC
FC eth5 10GbE
10GbE eth4

4 1

eth3 eth2 eth1 eth0

• 4 x 1GbE (LoM)
• 4 x 10GbE (copper or
fibre)

283 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
 StoreOnce 4500/4700 System – networking example configuration 4
subnets with bonding

Subnet#4 (bonded)

Subnet#3 (bonded)

Subnet#2

Subnet#1
Bond Bond
default gateway gateway
eth0 eth1 eth2 eth3 eth4 eth5 subnet #4
subnet #1
gateway 4 network ports on motherboard (LoM) 2 x 10GbE NIC gateway
subnet #2 subnet #3
StoreOnce 4500/4700
DNS server address
entries (max 3)
Backup System
Domain name

284 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
Useful Network CLI command

285 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce Network Configuration CLI

286 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce Network Configuration CLI

• You cannot modify the current config!

287 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce Networking: Creating a new network configuration config
with the CLI (without ‘wizard’)

Before you start the user will require to know:

• Sufficient IP address range (IPv4 only at present).
• Number of subnets required. (Dedicated management subnet is available on multi-node systems only.)
• DNS server addresses (up to 3)
• Default gateway IP address (optional)
• Type of Ethernet ports required (1GbE/10GbE depending on model)
• If bonding required – bonding mode. (multi-node systems always have bonded interfaces)
• Domain name
• VLAN number if being used.

288 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce Networking: Creating a new network configuration config
with the CLI (without ‘wizard’)

$net create config myconfig1 dns 192.168.6.2

$net add subnet mysubnet1 subnet subnet1 ipaddr 1.2.3.4 gateway 1.2.3.6 netmask
255.255.0.0 domain demo.com default yes portset portset1 netusage both
$net create portset myconfig1 myportset1 ports eth0,eth1 bondmode 6 vlansupport no
$net add subnet myconfig1 subnet subnet1 ipaddr 192.168.7.50 netmask 255.255.0.0
domain mearline.local default yes portset myportset1
$net validate config myconfig1
$net activate config myconfig1

289 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
 StoreOnce 4900 System – networking example configuration 8 subnets
(no bonding)

Subnet#8

Subnet#7
Gateway (non-default*)

Subnet#6

Subnet#5

Subnet#4

Subnet#3

Subnet#2 (default subnet)

Subnet#1
default gateway
subnet #2
eth0 eth1 eth2 eth3 eth4 eth5 eth6 eth7
DNS server address
entries (max. 3). 4 network ports on motherboard (LoM) 2 x 10GbE NIC 2 x 10GbE NIC
Domain Name
* Only 2 gateways are StoreOnce
StoreOnce 4900
4900
supported On 3.10.0 software
Backup
Backup System
System
290 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
All subnets can be used for data and management
 StoreOnce 4900 System – networking example configuration 6 subnets
(2 x 10Gbe bonded)
Subnet#6 (bonded)

Subnet#5 (bonded)

Subnet#4

Subnet#3

Subnet#2

Subnet#1 (default)
Bond Bond
default gateway
subnet #1 eth0 eth1 eth2 eth3 eth4 eth5 eth6 eth7
gateway 4 network ports on motherboard (LoM) 2 x 10GbE NIC 2 x 10GbE NIC
subnet #2
StoreOnce
StoreOnce 4900
4900
DNS server address Backup System
Backup System

entries (max 3) gateway

gateway gateway gateway
Domain name subnet #3 subnet #4 subnet #5
291 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
subnet #6
 StoreOnce 4900 System – networking example configuration with 5
subnets
Subnet#5 (bonded)

Subnet#4 (bonded)

Subnet#3 (bonded)

Subnet#2

Subnet#1 (default)
Bond Bond Bond
default gateway
subnet #1 eth0 eth1 eth2 eth3 eth4 eth5 eth6 eth7
gateway 4 network ports on motherboard (LoM) 2 x 10GbE NIC 2 x 10GbE NIC
subnet #2
StoreOnce
StoreOnce 4900
4900
DNS server address
Backup System
Backup System
entries (max 3)
Domain name

gateway gateway gateway
subnet #3 subnet #4 subnet #5
292 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce 6500 - Networking



© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
StoreOnce 6500 Networking – user connections to nodes

P1228 SAS RAID controllers (to storage modules)

eth5 eth7 External 10 GbE user

connections
RAID Ctrl RAID Ctrl
External 1GbE user
8Gb Fibre channel (4 ports) 8Gb FC 10GbE connections
8Gb FC 10GbE
iLO4 connection
4 1 (internal)
Internal 10 GbE
connections
Internal 2 X10GbE (fibre)
eth3 eth0 iLO4
External 2 X10GbE (fibre/copper)
eth2 eth1

1GbE user ports

Users ONLY connect to the external network ports as shown.

All connections are bonded.

294 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
 CLI examples – 2 subnets no VLANs, 6500 System

# net show config current

---------------------- ----------------------
Network Name: current Network: subnet2
Network Description: Management on (2) 1Gb ports (bonded), Data/Replication on (2) 10Gb ports ----------------------
(bonded) IP Addresses: 192.168.6.11,192.168.6.12,192.168.6.13,192.168.6.14
Write Protected: no Net Mask: 255.255.255.0
DNS Servers: 192.168.0.2 192.168.0.3 Domain Name: nearline.local
Port Sets: portSet1 portSet2 Gateway: 192.168.6.1
Management VIF: 192.168.6.20 Default Network: yes
---------------------- Net Usage: mgmt
Number of Networks: 2 VLAN tag:
Number of VLANs configured: 0 out of possible 128
----------------------
Port Set: portSet2 with these interfaces: eth0 eth2
Encryption Links:
1GbE ports
Network: subnet1 Bonding Mode: 1 (Active Passive Bonding)
----------------------  
IP Addresses: Command Successful
192.168.7.21,192.168.7.22,192.168.7.23,192.168.7.24,192.168.7.25,192.168.7.26,192.168.7.27,192.168.7.2  
8
Net Mask: 255.255.255.0
Domain Name: nearline.local
Gateway: 192.168.7.1
Default Network: no
Net Usage: data
VLAN tag:
Port Set: portSet1 with these interfaces: eth5 eth7
Encryption Links:
10GBe ports
Bonding Mode: 1(Active Passive Bonding)

295 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
VLAN tagging on B6200/6500 multi-node systems – basic rules:

• Ports must always be bonded – (maximum 4 x 1GbE)

• Management subnet cannot be a VLAN
• A subnet can be configured for management only or management and data.
• 3 subnets maximum without VLANS – management + 2 data subnets
• Replication or catalyst copy jobs must use a data subnet
• There can only be ONE default gateway. This will be the gateway configured on the default subnet. (can be a VLAN).
• Additional (non-default) gateways can be configured but these are only useful for incoming traffic (server which is
off-subnet initiates the traffic.)
• 128 VLANs maximum
• It is recommended to allocate ip addresses for a full cluster (8-nodes)

296 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
VLAN tagging on B6200/6500 multi-node systems – basic rules:

• It is necessary to specify a range of ip addresses but they no longer need to be contiguous.

• Network configuration is via CLI only but from 3.11.0 the virtual ip addresses for management and data are shown in
the GUI.
• It is recommended to use the wizard to configure a basic configuration as a first step. (#net set wizard)
• Build a new configuration file for the full configuration. Then if there is a validation error because of a mistake it can
be re-edited.
• DNS and domain name setting are cluster wide

297 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
 StoreOnce 6500 system – VLAN tagging example 1
4 subnets 10.168.5.22
Remote
Remote
StoreOnce
StoreOnce
System
System
router
10.168.6.22
10.168.7.23 WAN
AD VLAN 27 VLAN 22 VLAN 17 10.168.5.1
DNS U U U U
network switch(s) U U U U U U U U
NTP
Management Subnet #4 Data (VLAN 27)
GUI
Subnet #3 Data (VLAN 22)
Subnet #2 Data (VLAN 17) - default
VLAN tags=17,22,27 VLAN tags=17,22,27 VLAN tags=17,22,27 VLAN tags=17,22,27

T T T T T T T T

network switch U U Management VIF

Management subnet (no VLANs permitted)
1P ip 1P+1V ip 1P ip 1P+1V ip 1P ip 1P+1V ip 1P ip 1P+1V ip
U U U U U U U U
Bond Bond Bond Bond Bond Bond Bond Bond

eth0
eth0 eth1
eth1 eth2
eth2 eth3
eth3 eth5
eth5 eth7
eth7 eth0
eth0 eth1
eth1 eth2
eth2 eth3
eth3 eth5
eth5 eth7
eth7 eth0
eth0 eth1
eth1 eth2
eth2 eth3
eth3 eth5
eth5 eth7
eth7 eth0
eth0 eth1
eth1 eth2
eth2 eth3
eth3 eth5
eth5 eth7
eth7

10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE
1GbE NIC
NIC NIC
NIC 1GbE NIC
NIC NIC
NIC 1GbE NIC
NIC NIC
NIC 1GbE NIC
NIC NIC
NIC

6500
6500 node
node 11 eth4
eth4 eth6
eth6 6500
6500 node
node 22 eth4
eth4 eth6
eth6 6500
6500 node
node 33 eth4
eth4 eth6
eth6 6500
6500 node
node 44 eth4
eth4 eth6
eth6

Bond
Bond Bond
Bond Bond
Bond Bond
Bond

Internal dual 10GbE management network (no user access)

Subnet # IP Address range Physical/Virtual Ports(portset) VLAN tag gateway default Mgmt/data

1 192.168.6.2-6 4P + 1V eth0, eth1 no Management U untagged switch port

2 10.168.5.10-17 4P + 4V eth5, eth7 17 10.168.5.1 Yes data T tagged switch port

3 10.168.6.10-17 eth5, eth7 22 data

298 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
4 10.168.7.10-17 eth5, eth7 27 data
 StoreOnce 6500 system – VLAN tagging example 2
5 subnets
VLAN 27 VLAN 22 VLAN 17

network switch(s) U U U U U U U U U U U U
Subnet #4 Data (VLAN 27)
Subnet #3 Data (VLAN 22)

VLAN 16 Subnet #2 Data (VLAN 17) - default

VLAN tags=17,22,27 VLAN tags=17,22,27 VLAN tags=17,22,27 VLAN tags=17,22,27
T T T T T T T T
U U U
Subnet
Subnet #5
#5 Data
Data (VLAN
(VLAN 16)
16)
network switch
T T
network switch
Management VIF
Management subnet (no VLANs permitted)
1P ip 1P+1V ip 1P ip 1P+1V ip 1P ip 1P+1V ip 1P ip 1P+1V ip
U U U U U U U U
Bond Bond Bond Bond Bond Bond Bond Bond Bond

eth0
eth0 eth1
eth1 eth2
eth2 eth3
eth3 eth5
eth5 eth7
eth7 eth0
eth0 eth1
eth1 eth2
eth2 eth3
eth3 eth5
eth5 eth7
eth7 eth0
eth0 eth1
eth1 eth2
eth2 eth3
eth3 eth5
eth5 eth7
eth7 eth0
eth0 eth1
eth1 eth2
eth2 eth3
eth3 eth5
eth5 eth7
eth7

10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE
1GbE NIC
NIC NIC
NIC 1GbE NIC
NIC NIC
NIC 1GbE NIC
NIC NIC
NIC 1GbE NIC
NIC NIC
NIC

6500
6500 node
node 11 eth4
eth4 eth6
eth6 6500
6500 node
node 22 eth4
eth4 eth6
eth6 6500
6500 node
node 33 eth4
eth4 eth6
eth6 6500
6500 node
node 44 eth4
eth4 eth6
eth6

Bond
Bond Bond
Bond Bond
Bond Bond
Bond

Internal dual 10GbE management network (no user access)

Subnet # IP Address range Physical/Virtual Ports(portset) VLAN tag gateway default Mgmt/data

1 192.168.4.2-6 4P + 1V eth0, eth1 no Management

U untagged switch port
2 10.168.5.10-17 4P + 4V eth5, eth7 17 10.168.5.1 Yes data
T tagged switch port
3 10.168.6.10-17 eth5, eth7 22 data

299 © Copyright4 2015 Hewlett-Packard

10.168.7.10-17
Development Company, L.P. eth5, eth7
The information 27
contained dataHP Confidential.
herein is subject to change without notice.
5 10.168.8.10-17 4P +4V eth 2, eth3 16 data
 StoreOnce 6500 system networking - one subnet example 2 (no
VLANS)
AD 10.168.5.1
DNS
NTP 10.168.6.21 10.168.6.22 10.168.6.24 10.168.6.1
Management Remote
Remote
GUI/CLI WAN StoreOnce
StoreOnce
System
System
router

U U Management VIF (1V ip) U U U U

network switch

Management and data subnet (no VLANs permitted)

1P +1V ip address 1P +1V ip address 1P +1V ip address 1P +1V ip address

U U U U U U U U U U U U U U U U
Bond Bond Bond Bond

eth0
eth0 eth1
eth1 eth2
eth2 eth3
eth3 eth5
eth5 eth7
eth7 eth0
eth0 eth1
eth1 eth2
eth2 eth3
eth3 eth5
eth5 eth7
eth7 eth0
eth0 eth1
eth1 eth2
eth2 eth3
eth3 eth5
eth5 eth7
eth7 eth0
eth0 eth1
eth1 eth2
eth2 eth3
eth3 eth5
eth5 eth7
eth7

10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE 10GbE
10GbE
1GbE NIC
NIC NIC
NIC 1GbE NIC
NIC NIC
NIC 1GbE NIC
NIC NIC
NIC 1GbE NIC
NIC NIC
NIC

6500
6500 node
node 11 eth4
eth4 eth6
eth6 6500
6500 node
node 22 eth4
eth4 eth6
eth6 6500
6500 node
node 33 eth4
eth4 eth6
eth6 6500
6500 node
node 44 eth4
eth4 eth6
eth6

Bond
Bond Bond
Bond Bond
Bond Bond
Bond

Internal dual 10GbE management network (no user access)

Subnet # IP Address range Physical/Virtual Ports(portset) VLAN gateway default Mgmt/data U untagged switch port
tag
T tagged switch port
1 192.168.6.2-6 4P + 5V eth0, eth1, eth2, eth3 no 192.168.6.1 yes Management

300 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
 CLI examples – 3 subnets VLANs, 6500 System

Network Name: net_wizard ----------------------

Network Description: Created by wizard on: Wed Mar 12 11:19:29 2014 Network: subnet_2
  ----------------------
Write Protected: no IP Addresses: 192.168.7.21,192.168.7.22,192.168.7.23,192.168.7.24
DNS Servers: 192.168.0.2 192.168.0.3 Net Mask: 255.255.255.0
Port Sets: portset_1 portset_2 Domain Name: nearline.local
Management VIF: 192.168.6.20 Gateway: 192.168.7.1
---------------------- Net Usage: data
Number of Networks: 3 VLAN tag: 17
Number of VLANs configured: 2 out of possible 128 Port Set: portset_2 with these interfaces: eth5 eth7
---------------------- Encryption Links:
Network: subnet_1 (default) Bonding Mode: 6 (Active Load Balance Bonding)
---------------------- ----------------------
IP Addresses: 192.168.6.11,192.168.6.12,192.168.6.13,192.168.6.14 Network: subnet_3
Net Mask: 255.255.255.0 ----------------------
Domain Name: nearline.local IP Addresses: 192.168.4.221,192.168.4.222,192.168.4.223,192.168.4.224
Gateway: 192.168.6.1 Net Mask: 255.255.255.0
Net Usage: mgmt Domain Name: nearline.local
VLAN tag: Gateway: 192.168.4.1
Port Set: portset_1 with these interfaces: eth0 eth1 Net Usage: data
Encryption Links: VLAN tag: 14
Bonding Mode: 6 (Active Load Balance Bonding) Port Set: portset_2 with these interfaces: eth5 eth7
Encryption Links:
Bonding Mode: 6 (Active Load Balance Bonding)

 
Validation succeeded
301 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
 Networking Example #1 StoreOnce multi-node 
Site ‘A’’ Site ‘B’’

HP Data subnet #3 HP Data subnet #3

WAN
WAN

HP Data Subnet #2 (default) HP Data Subnet #2 (default)

Mgmt Mgmt

HP Management Subnet #1 HP Management Subnet #2

G G

Bond
Bond Bond
Bond Bond
Bond Bond
Bond Bond
Bond Bond
Bond Bond
Bond Bond
Bond Bond
Bond Bond
Bond Bond
Bond Bond
Bond bonded

4 x 1GbE 2 x 10GbE 4 x 1GbE 2 x 10GbE 4 x 1GbE 2 x 10GbE 4 x 1GbE 2 x 10GbE

Catalyst
Catalyst Catalyst VT Catalyst
Catalyst
Catalyst VT (Target)
(Target)
NAS
NAS VT
VT VT
VT NAS
NAS (target)
(target)

StoreOnce 6500 node 1 StoreOnce 6500 node 2 StoreOnce 6500 node 1 StoreOnce 6500 node 2
Couplet 1 Couplet 2

G =default gateway
302 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential.
HP StoreOnce – Remote Support


Problem Statement
Problems with current support methods

• Majority of the StoreOnce devices are not attached to HP support center

• Existing solutions are designed for generic server monitoring (e.g. Proliant)
• Any improvement in monitoring and correlation requires software upgrade for customer
• Existing solutions unaware of StoreOnce entitlement scheme
• Solutions like IRS require additional hosting hardware at customer site
• We want to track number of events and type
• Cannot track customer install base (SW version)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support Overview
And what does it do?

• NOT IRS
• Uses 3PARs ‘STaTS’ (Service Tools and Technical Support) established reporting system
• Communicates directly to HP (no additional hardware required)
• Rules can be updated from HP side (does not require SW update for customer)
• Possibility for future expansion and additional support models
• Fixes all of the ‘problems’ from previous slide
• Allows for serial numbers to be stored on box (historically on toe-tags at rear of unit)
• Hardware events only (so far)
• Metric and configuration data
• Built-in integration with the HP Data Center
• Real time hardware monitoring for component failures and alerts, for all warrantied components
• Analyzes alert, warning and informational events generated by the device and generates serviceable and
actionable events
•
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Opens and updates support cases in HP Support Center (RSDC)
Remote Support Architecture
Overview

• The following diagram shows the various systems responsible for transferring remote support data (note that this is
not a complete picture, but captures overall data flow between major systems)

Customer Device(s) “Enterprise Server” “Support Automation” Support Cases etc.

FIREWALL

StoreOnce HTTPS Axeda STaTS Bridge SA / BLI GCSS

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support Architecture
Overview

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support Architecture
Registration process – Backend

iDocs process imports sales data from HP database into STaTS database

HP Sales/
iDocs Process STaTS
Warranty DB

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support Architecture
Registration process – Device registration

Customer initiated registration system

Customer enters
SN

Set the SN ‘Site’

to ‘Dummy Site’
Remote Support
sends ‘custdata’
to STaTS No

Does SN exist Associate SN to a Support

STaTS Yes Bridge Automation
in STaTS DB? ‘Site’ (ID)
(Backend) / BLI

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support Architecture
Support case creation

Customer Device(s) Axeda STaTS Bridge SA / BLI GCSS Support Agent

Convert to
‘HDD Failed’ Transfer Rules engine: Investigate
Log event SA/BLI Create case
event event files case or not? case
compatibity

Send email
to customer
with case #

Axeda STaTS Bridge SA / BLI GCSS

Convert to Rules engine:

‘HDD OK’ Transfer
Log event SA/BLI case open or Close case
event event files
compatibity not?

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Remote Support GUI Configuration
Customer configuration – Settings

Active – Remote SSH (N/A)

Passive – Outbound traffic only
No Support – No traffic

https://remote3par-itg.atlanta.hp.com

Contact agreement
Customer network proxy
details

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support Configuration
What values to use and where to find them

• SKU = EJ021A+EJ022A+(3*EJ025A)+BB897A+BB900A+BB902A

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support GUI Configuration
Customer configuration – Customer Details

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support GUI Configuration
Customer configuration – Server & Switch

OEM Serial Warranty Serial

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support GUI Configuration
Customer configuration – Storage

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support GUI Configuration
Customer Configuration – Status

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support Packets
List of all remote support packets

• custdata
• Customer registration packet. Sent once per entered serial number. Includes SW version, serial number, and
customer contact information.
• event
• Will only generate after a custdata packet has been sent. Ad-hoc message sent as soon as an event happens.
Includes all information that is given to eventing system.
• metric
• Will only generate after a custdata packet has been sent. Sent on upgrade (from X to Y) and/or after Remote
Support has been configured. Includes ‘historical’ data at an hourly resolution for all store (and file system)
‘size on disk’ and ‘user data stored’ (dedupe ratio).
• config
• Will only generate after a custdata packet has been sent. Sent once every 8hrs, starting 8hrs after the ‘metric’
packet is sent. Includes the current ‘snapshot’ of device configuration (all services (VTL/NAS/CAT/REP),
hardware, licenses, configuration).

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support Case Analysis
STaTS

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support Case Analysis
STaTS

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support Future Roadmap
What to look forward to

• Software defined events

– E.g. service set, file system, services
• Inclusion of ‘basic support ticket’ with events
– To provide a substantial amount of information with a case automatically (very helpful for SW events)
• Existing configuration and parametric data to produce statistics and graphs
• Provides historical data on devices performance and configuration
• Enhanced parametric data
– Reporting and general use of customer device
• More BIOS populated serial numbers
– Removes customer need to enter serials (reduce incorrect serials)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support Troubleshooting
Help and support

• Cannot entitle a device

– Click ‘Rescan Devices’
– Clear all config (rm -f /usr/local/ibrix/sa/* ; /etc/init.d/ibrix_fusionmanager restart )

• Test event cannot make it back to HP

– Check customer proxy settings + customer firewall
– Check ‘enterprise server’ URL has not been altered (https://remote3par.houston.hp.com)

• Serial number has made it into Dummy site

– Validate serial number, if not valid then change it, if is valid contact MSDU/STaTS (missing from STaTS)

• Log files location

– /usr/local/ibrix/sa/* – Config files
– /usr/local/ibrix/log/fusionserver.log – Main FusionManager logs (Remote Support records in here)
– /Axeda/Gateway/*.log – Axeda (xGate) logs

• URL addresses?
– ‘Enterprise Server’ = https://remote3par.houston.hp.com
– ‘STaTS’ = https://stwebint.atlanta.hp.com/st/st_main.php

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Remote Support FAQ
Frequently asked questions

• Q: What happens if customer does not want to use Remote Support?

• A: Set to ‘No Support’, but still set warranty serial numbers as these are useful for support calls and tickets to speed
up help and assistance for the customer

• Q: How much bandwidth does Remote Support use?

• A: ~10Kb per packet, packets only sent on events, configuration, and once every 8hrs

• Q: Who will use/see the data transferred?

• A: Primarily support use, secondary metrics analysis to improve product and contact customer (if agreement
selected) for expansion opportunities (e.g. file system >90% full, offer customer expansion of help to reduce usage)

• Q: Security risks?
• A: Data sent over port 443 (HTTPS), databases are access controlled 
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce – Software upgrade path


Update recommendation
• Update recommendation:
– StoreOnce 3.12.1 is a new release that is valid for all HP StoreOnce Backup systems in “Product models” (next slide).
• It is a recommended upgrade for:
• Customers wishing to take advantage of the new features and enhancements introduced in 3.12.1 (see Features and enhancements in the “HP
StoreOnce Backup system software revision 3.12.1 release notes (EJ022-10540)” document at www.hp.com/go/support in the “Drivers &
Download” section.
• Customers who require a fix that is not available with the previous release, 3.11.7

• Firmware management (not applicable to StoreOnce VSA)

• The hardware component firmware can now be managed through the StoreOnce GUI, as well as via StoreOnce CLI commands.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Product Models
The 3.12.1 software release is applicable to the following product models:

Current Models (HW&VSA) Legacy Models

BB877A: HP StoreOnce 2700 Backup HP StoreOnce 2610 iSCSI Backup system
BB910A: HP StoreOnce 2900 Backup BB852A: HP StoreOnce 2620 iSCSI Backup system
BB878A: HP StoreOnce 4500 Backup BB853A: HP StoreOnce 4210 iSCSI Backup system
BB879A: HP StoreOnce 4700 Backup BB854A: HP StoreOnce 4210 FC Backup system
BB903A: HP StoreOnce 4900 Backup BB855A: HP StoreOnce 4220 Backup system
BB896A: HP StoreOnce 6500 Backup BB856A: HP StoreOnce 4420 Backup system
TC458A/AAE: HP StoreOnce VSA 10 TB 3 Year Software BB857A: HP StoreOnce 4430 Backup system
D4T77A/AAE: HP StoreOnce VSA 4 TB 3 Year Software EJ022A: HP StoreOnce B6200 Backup
D4U47A/AAE: HP StoreOnce VSA 50TB 3-year LTU/E-LTU
D4U49A/AAE: HP StoreOnce VSA 4TB 5-year LTU/E-LTU
D4U62A/AAE: HP StoreOnce VSA 10TB 5-year LTU/E-LTU
D4U48A/AAE: HP StoreOnce VSA 50TB 5-year LTU/E- LTU

NOTE: The HP StoreOnce 2610 iSCSI Backup system is only available as a conversion from an existing HP D2D2502 Backup
system, so has no product number.
The 3–year 50TB and all 5–year StoreOnce VSA products are new with StoreOnce software 3.12.1 and later.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Languages
• Languages supported for this release:
• English
• Japanese
• Chinese
• French
• German
• Portuguese
• Russian
• Spanish


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce – Key Parameter


StoreOnce 2700, 2900, 4500, 4700, and 4900 Backup
Capacity

2700 Backup 2900 Backup 4500 Backup 4700 Backup 4900 Backup
Minimum raw 8 24 20 24 60
storage capacity
(TB)
Maximum raw 8 48 164 192 560
storage capacity
(TB)
Minimum usable 5.5 15.5 16 20 65.5
(after RAID)
capacity (TB)
Maximum usable 5.5 31.5 124 160 392.97
(after RAID)
capacity (TB)

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 2700, 2900, 4500, 4700, and 4900 Backup
System Limits

2700 Backup 2900 Backup 4500 Backup 4700 Backup 4900 Backup
Maximum number 8 24 32 50 50
of libraries, shares
and StoreOnce
Catalyst Stores
combined

Maximum 48 96 128 192 500

concurrent
inbound data
streams1

1
This limit is not rigidly enforced, it is dependent on memory availability.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 2700, 2900, 4500, 4700, and 4900 Backup
VTL

2700 Backup 2900 Backup 4500 Backup 4700 Backup 4900 Backup
Maximum drives 32 96 128 500 500
per library
(D2DBS and ESL
Emulation)

Maximum 96 1024 1024 4096 16384

cartridges per
library
Maximum 768 24576 32768 204800 819200
cartridges per
appliance
Maximum 3200 3200 3200 3200 3200
cartridge size
(GB)
Maximum — — 254 254 254
supported
devices (drives
and loaders) per
FC port (NPIV)
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 2700, 2900, 4500, 4700, and 4900 Backup
NAS

2700 Backup 2900 Backup 4500 Backup 4700 Backup 4900 Backup
Maximum files per 1 million 1 million 1 million 1 million 1 million
NAS Share
Maximum 48 96 128 192 500
concurrent NAS
backup streams

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 2700, 2900, 4500, 4700, and 4900 Backup
StoreOnce Catalyst

2700 Backup 2900 Backup 4500 Backup 4700 Backup 4900 Backup
Maximum 12 24 32 96 96
concurrent
outbound copy
jobs

Maximum 48 96 128 192 500

concurrent data
and inbound
copy streams

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 2700, 2900, 4500, 4700, and 4900 Backup
Replication

2700 Backup 2900 Backup 4500 Backup 4700 Backup 4900 Backup
Maximum 8 24 32 50 50
replication
appliances fan-in

Maximum 2 4 4 8 8
replication
appliances
fan-out

Maximum 1 8 8 16 16
replication fan-in
per library

Maximum replication 1 1 1 1 1
fan-out per library

Maximum 12 24 32 48 96
concurrent
replication jobs
as source

Maximum 24 48 96 124 192

concurrent
replication jobs
as target

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 6500 Backup
Capacity

Per Node 1 2 Node Cluster 4 Node Cluster 6 Node Cluster 8 Node Cluster
Minimum raw - 120 240 360 480
storage capacity
(TB)
Maximum raw - 560 1120 1680 2240
storage capacity
(TB)
Minimum usable - 72 144 216 288
(after RAID)
capacity
(TB)

Maximum usable - 432 864 1296 1728

(after RAID)
capacity (TB)
1
For simplicity, the values here are listed as Per Node. During normal operation, each service set resides on its own node and the Per Node values are correct. However, in the event of a failover,
consider the values shown as Per Service Set. For example, the maximum number of concurrent inbound data streams is 192 for one service set on one node. During failover, the service set from
the failed node moves to the other node in the couplet. The live node now supports 192 streams for each service set.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce 6500 Backup
System Limits

Per Node 1 2 Node Cluster 4 Node Cluster 6 Node Cluster 8 Node Cluster
Maximum number 48 96 192 288 384
of libraries, shares
and StoreOnce
Catalyst Stores
combined

Overall maximum 512 1024 2048 3072 4096

concurrent inbound
data streams 2, 3
Maximum VLAN 128 128 128 128 128
tag subnets

1
For simplicity, the values here are listed as Per Node. During normal operation, each service set resides on its own node and the Per Node values are correct. However, in the event of a failover,
consider the values shown as Per Service Set. For example, the maximum number of concurrent inbound data streams is 192 for one service set on one node. During failover, the service set from the
failed node moves to the other node in the couplet. The live node now supports 192 streams for each service set.
2
This is the maximum number of inbound data streams (VTL, NAS, Catalyst, Replication) if not using StoreOnce Catalyst
exclusively.
3
This limit is not rigidly enforced, it is dependent on memory availability

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 6500 Backup
VTL

Per Node 1 2 Node Cluster 4 Node Cluster 6 Node Cluster 8 Node Cluster
Maximum drives 500 1000 2000 3000 4000
(D2DBS and ESL
Emulation)
Maximum 786432 1572864 3145728 4718592 6291456
cartridges
Maximum cartridge 3200 3200 3200 3200 3200
size (GB)
Maximum 127 127 127 127 127
supported devices
(drives and loaders)
per FC port (NPIV)

1
For simplicity, the values here are listed as Per Node. During normal operation, each service set resides on its own node and the Per Node values are correct. However, in the event of a failover,
consider the values shown as Per Service Set. For example, the maximum number of concurrent inbound data streams is 192 for one service set on one node. During failover, the service set from
the failed node moves to the other node in the couplet. The live node now supports 192 streams for each service set.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 6500 Backup
NAS

Per Node 1 2 Node Cluster 4 Node Cluster 6 Node Cluster 8 Node Cluster
Maximum files per 1 million 1 million 1 million 1 million 1 million
NAS Share
Maximum number 500 1000 2000 3000 4000
of concurrent NAS
backup streams per
node

1
For simplicity, the values here are listed as Per Node. During normal operation, each service set resides on its own node and the Per Node values are correct. However, in the event of a failover,
consider the values shown as Per Service Set. For example, the maximum number of concurrent inbound data streams is 192 for one service set on one node. During failover, the service set from
the failed node moves to the other node in the couplet. The live node now supports 192 streams for each service set.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce 6500 Backup
StoreOnce Catalyst

Per Node 1 2 Node Cluster 4 Node Cluster 6 Node Cluster 8 Node Cluster
Maximum 48 96 192 288 384
concurrent
outbound copy
jobs 4

Maximum 512 1024 2048 3072 4096

concurrent data and
inbound copy jobs 5

1
For simplicity, the values here are listed as Per Node. During normal operation, each service set resides on its own node and the Per Node values are correct. However, in the event of a failover,
consider the values shown as Per Service Set. For example, the maximum number of concurrent inbound data streams is 192 for one service set on one node. During failover, the service set from the
failed node moves to the other node in the couplet. The live node now supports 192 streams for each service set.
4
If using Federated StoreOnce Catalyst, then one job will be consumed for each node in the federation.
5
If using Catalyst Stores ONLY with StoreOnce 6500 then the maximum number of inbound jobs is 512 per node (higher than when using VTL, NAS where the limit is 192).

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce 6500 Backup
Replication

Per Node 1 2 Node Cluster 4 Node Cluster 6 Node Cluster 8 Node Cluster
Maximum replication 48 96 192 288 384
appliances fan-in
Maximum replication 8 16 32 48 64
appliances fan-out
Maximum replication 16 16 16 16 16
fan-in per VTL library
Maximum replication 1 1 1 1 1
fan-out per VTL library
Maximum concurrent 48 96 192 288 384
replication jobs
as source
Maximum concurrent 96 192 384 576 768
replication jobs
as target
1
For simplicity, the values here are listed as Per Node. During normal operation, each service set resides on its own node and the Per Node values are correct. However, in the event of a failover,
consider the values shown as Per Service Set. For example, the maximum number of concurrent inbound data streams is 192 for one service set on one node. During failover, the service set from
the failed node moves to the other node in the couplet. The live node now supports 192 streams for each service set.

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Federated Catalyst Maximum Streams supported.
• StoreOnce 6500 systems support a maximum of 512 streams across the cluster (appliance).
• StoreOnce B6200 systems support a maximum of 192 streams across the cluster (appliance).
• A mixed cluster will support a maximum of 192 streams. (Limited by B6200 couplets).
• Federated and non-federated catalyst will be limited by the same stream count.


© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP StoreOnce – General Best Practise


 Deployment Planning / Sizing
Know the customer environment
• What operating systems are running on Media Server / Media Agent?
• Is the environment Fibre Channel or Ethernet?
• What speed is their SAN / LAN / WAN?
• Does the environment have any known bottlenecks?
• What data types does the customer plan to backup to StoreOnce?
• Do they have any encrypted / compressed data?
• Construct a topology of the customer’s environment

What problem is the customer trying to solve?

• What is the customers priority:
• Dedupe Ratio?
• Performance?
• Ease of management?
• Capacity?
• All of the above?

342 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Choosing the most appropriate solution

6500
Muti-node
4900 72 – 1,728TB
Single node Enterprise data
4700 36 – 432TB protection & DR sites
Single node Large offices & data
4500 20 – 160TB centers
Single node Large branch
2900 16 – 124TB offices & data centers
2700 Single node Branch offices & mid
Single node 15.5 – 31.5TB sized data centers
VSA 5.5TB large ROBO’s & large
Virtual appliance small ROBOs & branch offices
up to 50TB small branch offices
virtual environments

343 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Choosing the most appropriate solution
Catalyst, NAS or VTL?

Backup Interface Key Features Best Used In Comments

NAS (CIFS / NFS) • Shares are easily configured • Environments preferring to use • NAS target is for backup – should
and viewed by the operating backup to disk NOT be used for random NAS file
system • Environments where lower access
licensing costs are required
• Ethernet environments not using
Catalyst integrated ISVs
Virtual Tape • Uses virtual tape drives and • Enterprise FC SAN environment • Tried & tested, well understood but
virtual slots to emulate physical • Customers wanting to emulate lacks sophistication
tape libraries current physical tape environments • Uses Robot and Drives device types
• Fibre Channel and iSCSI
connectivity (model dependant)
StoreOnce • Backup application has total • ROBO to DC backups • Requires StoreOnce Catalyst license
Catalyst control over backup & copy / • Network resource constrained • Requires backup application support
data lifecycle environments • Is the StoreOnce interface of choice
• Network efficient backup / • Environments requiring a single
copy management console for all backup
• Improved DR and replication activities
• HP owned IP

344 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Choosing the most appropriate solution
Check the configuration is supported

Consult the EBS matrix

• If it’s not listed it’s not a supported configuration
• Missing this step could lead to an un-usable StoreOnce deployment
• It is better to identify early whether the configuration is supported or not
http://www.hp.com/go/ebs or http://h18000.www1.hp.com/products/storageworks/ebs/matrix_archives.html

345 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Installation Planning
Data Center Considerations
• Does the customer have the required space on the data center floor for the StoreOnce rack(s)
• Is the customer likely to expand their StoreOnce in the future? If so, leave floor space for expanding multi-node configurations.
• Does the data centre meet the StoreOnce power requirements?
• Check that the correct PDUs have been ordered

What StoreOnce network configuration will the customer use?

• Combined management and backup Ethernet traffic
• Separate management and backup Ethernet traffic
• 1Gb or 10Gb Ethernet network
• Will VLAN tagging be used?
• Port bonding options of Mode 2 (active / passive), Mode 4 (LACP) and Mode 6 (active / active) are available.

346 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Installation Planning
IP address allocation
• If possible, for multi-node, allocate IP addresses upfront, during an initial cluster installation. Additionally added
couplets will then automatically make use of the pre-allocated IP addresses with out needing to disrupt the current
configuration

SNMP / Email Alerting

• Setting up alerting is often a missed stage, but it is vital for customers to be able to early identify any issues

Don’t forget to apply the licenses!

• Security
• Storage Capacity
• Catalyst / Replication (simplified single license from 3.9 onwards)
• 90 day, instant on demo license is available (#license add demo)

347 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Configuration Best Practises - General
Choosing the number of backup devices (stores)
• Performance is attained by sharing the work load across multiple backup devices
• The number will depend on the customer deployment but recommendation would be between 2 and 6 backup devices
• Single store configurations will hit performance bottlenecks
• Configure a large blocksize min 256KB in your backup application

Separate backup devices for differing data types – to maximise dedupe ratios
• Common data types dedupe better against each other more than foreign data types
• Performance is attained by improving dedupe ratios

Separating windows of activity - Backup / Replication / Housekeeping / tape offload

• Each operation puts a heavy work load on the StoreOnce
• Separating the activities into different windows will improve performance
• Make use of StoreOnce blackout windows for Housekeeping, Replication and Catalyst copy

348 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Where to find the latest StoreOnce Software code

Go to http://www.hp.com/go/support (best use the US link)  Drivers & Downloads  enter

StoreOnce model e.g. “StoreOnce 4700” and press “Go” button  expand “HP StoreOnce Backup”
section and click on the StoreOnce base model you are looking for  choose “OS independent” at
Operating systems in English  scroll down to “Software” and expand this section  choose the latest
StoreOnce Software version and click at “Obtain software” and following instructions.

349 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Performance
• Run multiple backups in parallel to improve aggregate
throughput to StoreOnce. ~95 % of
max
• Running too many concurrent jobs will impact the performance
performance of each individual job. This will be true

Performance
for all types of job: backups, restores and replication.

Performance
Ensure that the solution has been sized correctly to
accommodate the concurrent load requirements.
StoreOnce Model Max number of Referene streams (min) to
streams achieve 95% max ingest
SO2700 49 6

SO2900 96 24
Number of
SO4500 128 20
concurrent streams
Number of min concurrent
SO4700 192 28 reference streams (model
SO4900 500 32
dependant)

SO6500 (per node) 512 36

SO VSA 4TB 16 4

SO VSA 10TB 24 6

SO VSA 50TB 32 10

350 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Separating windows of activity - Backup / Replication / Housekeeping /
tape offload

BAD,
try to avoid

  Backup
  Replication
  Housekeeping
  Start of Replication Window
  Spare Time for future growth or Physical Tape Offload
  Housekeeping Window

351 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Separating windows of activity - Backup / Replication / Housekeeping /
tape offload

GOOD

  Backup
  Replication
  Housekeeping
  Start of Replication Window
  Spare Time for future growth or Physical Tape Offload
  Housekeeping Window

352 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Choosing the number of backup devices – SO single-node

VTL/NAS/Catalyst
• Where possible send the same data types to the same
Application
device configured on the StoreOnce system, to Servers
maximize deduplication ratios.
• Run multiple backups in parallel to improve aggregate
throughput to a StoreOnce appliance Virtualized Catalyst Store/VTL/NAS
Servers
• To be able to reach a acceptable performance work with
minimum two stores and split the number of reference
streams per appliance equal to each store. Catalyst Store/VTL/NAS
File
Servers
Catalyst Store/VTL/NAS

Database Catalyst Store/VTL/NAS

Servers

353 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Choosing the number of backup devices – SO multi-node

VTL/NAS/Catalyst Application
Servers
• Data segmentation
• For higher throughput create multiple stores
(VTL/NAS/Catalyst) for same data type on Virtualized
VTL/NAS VTL/NA
Servers
different nodes /Catalyst S/Catalyst
VTL/NAS VTL/NA
• Run multiple backups in parallel to improve /Catalyst S/Catalyst
aggregate throughput to a StoreOnce multi-node File
and to each single node Servers

• To be able to reach a acceptable performance VTL/NA

VTL/NA
S/Catalyst
work with minimum two stores per node and split S/Catalyst
Database VTL/NA
the number of reference streams per node equally Servers S/Catalyst
VTL/NA
S/Catalyst
to each store.

354 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Choosing the number of backup devices – SO multi-node

Federated Catalyst Application

Servers
• Consolidate dedupe stores and simplify
management with automatic capacity-balancing
across nodes Virtualized <8 nodes
Servers
• Up to 8 nodes
• Expansion of federated stores
<8 nodes
• Supported with Catalyst over Fibre Channel File
Servers
• Fully Qualified Domain Name support <8 nodes

• To be able to reach a acceptable performance

work with minimum two Federated Catalyst Database <8 nodes
Servers
Stores per system and split the number of
reference streams per node equally to each store.
• A single Federated Catalyst Store can handle a
max of 512 streams.

355 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Working example – SO multi-node using VTL/NAS/Catalyst
Simplified example does not reflect correct StoreOnce key parameter
• Use “Data types” not Media Servers as the preferred mapping
Use of excessive number of streams to a single device can impair performance

Media Filesystem TB Database TB Other data type Filesystem TB Database TB Other data type
Server # retained on Retained on TB Retained on retained on NAS Retained on TB Retained on
VTL VTL VTL NAS NAS

1 20 5 0 0 0 0
2 10 2 0 4 4 0
3 5 0 10 0 0 0
4 40 0 0 4 0 0
5 0 3 0 0 10 4
6 0 0 0 6 2 0
7 0 30 0 0 0 0

356 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Use “Data types” not Media Servers as the preferred mapping
Simplified example does not reflect correct StoreOnce key parameter

Management Potential
Console Management
Console
Media Active Node failover node
server

Media Media Media Media Media Media

server server server server server server

Node1 Node 2 Node1 Node 2 Node1 Node 2 Node1 Node 2

3TB/Hr 3TB/Hr 3TB/Hr 3TB/Hr 3TB/Hr 3TB/Hr 3TB/Hr 3TB/Hr
Master

X TB

Couplet 1
128 –
X TB
X TB

Couplet 2
avoid 128 –
X TB
Couplet 3
X TB
128 –
X TB
X TB

Couplet 4
128 –
X TB

Cluster

357 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Sample Media server configs by data type (required perf)
Simplified example - does not reflect correct StoreOnce key parameter

Media Filesystem backup Database backup Other data type Filesystem backup Database backup Other data type
Server # job on VTL job on backup job on job on NAS job on backup job on
throughput req in VTL throughput VTL throughput throughput req in NAS throughput NAS throughput
TB/Hr req in TB/Hr req in TB/Hr TB/Hr req in TB/Hr req in TB/Hr

1 1.48 0.4 0 0 0 0
2 0.75 0.16 0 0.30 0.32 0
3 0.37 0 0.75 0 0 0
4 2.95 0 0 0.30 0 0
5 0.36 0.24 0 0 0.81 0.30
6 1.1 0 0 0.44 0.16 0
7 0 3.2 0 0 0 0

Max config storage on node with > 16 streams will deliver 2.8 TB/Hr Assumes all backup windows are
12 hrs. These calculations based on backup size not retained data size.

358 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Sample Media server configs by data type (streams available)
Simplified example - does not reflect correct StoreOnce key parameter

Media FS Max # DB Max # Other data Max # FS Max # DB Max # Other data
Server # concurrent concurrent concurrent streams concurrent concurrent Max # concurrent
streams reqd on streams reqd on reqd on VTL streams reqd streams reqd streams reqd on
VTL VTL on NAS on NAS NAS
1 5 2 N/A N/A N/A N/A
2 2 1 N/A 8 8 N/A
3 2 N/A 5 N/A N/A N/A
4 10 N/A N/A 4 N/A N/A
5 2 1 N/A N/A 5 4
6 3 N/A N/A 12 1 N/A
7 N/A 16 N/A N/A N/A N/A

359 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Worked calculation - SO multi-node using VTL/NAS/Catalyst
Simplified example - does not reflect correct StoreOnce key parameter

Service Set 1 Service Set 2 Service Set 3 Service Set 4 Service Set 5 Service Set 6
Node Capacity 48 48 48 48 32 32

PASS 1
VTL Device #1
retained Capacity 40 40 35 10
Drives (streams) 10 20 9 5
Throughput
Name FSVTL1 DBVTL1 FSVTL2 OTHVTL1
Split 1            
VTL Device #2
retained Capacity 20
Drives (streams) 5
FSVTL2
             
NAS Device #1
retained Capacity 4 14 16
Streams 4 24 14
Name OTHNAS1 FSNAS1 DBNAS1
Total retained capacity 40 40 35 34 14 16
Total # streams 10 20 9 14 24 14

360 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Worked calculation - SO multi-node using VTL/NAS/Catalyst
Simplified example - does not reflect correct StoreOnce key parameter
Service Set 1 Service Set 2 Service Set 3 Service Set 4 Service Set 5 Service Set 6
Node Capacity 48 48 48 48 32 32

PASS 2
VTL Device #1 retained
Capacity 40 30 35 10
Drives (streams) 10 16 9 5
Throughput
Name FSVTL1 DBVTL1 FSVTL2 OTHVTL1
Split 1            
VTL Device #2 retained
Capacity 10
Drives (streams) 4
DBVTL2
NAS Device #1 retained
Capacity 4 8 16
Streams 4 12 14
Name OTHNAS1 FSNAS1 DBNAS1
Split1            
NAS Device #2 Capacity 6
Streams 12
Name FSNAS2
Total retained capacity 40 40 35 34 14 16
Total # streams Device set 1 10 16 9 9 12 14
Total # streams Device set 2   4     12  

361 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Data Segmentation – fully worked example
Simplified example does not reflect correct StoreOnce key parameter

Media Media Media

Media server 3 Media Media Media server 7
server server 5 server 6
1 server 2 4TB server 4
20TB 10TB
4TB 5TB
40TB 4TB 3TB 10TB 6TB
2TB
30TB
2TB
5TB 4TB
10TB

Couplet 1 Couplet 2 Couplet 3

48 TB 48 TB 40 TB 40TB 16TB 16 TB
service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set
OTHVTL1 Replication
DBVTL1
(10TB)
(30TB) FSNAS1 (8TB)
FSVTL1 FSVTL2
(40TB) OTHNAS DBNAS1
DBVTL2 (35TB) (16TB)
(4TB) FSNAS2
(10TB) (6TB)
node1 node2 node3 node4 node5 node6

storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage

362 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Do not send multiplexed data to StoreOnce Backup Systems
HP Data Protector

• In DataProtector set concurrency to „1“ to avoid

multiplexing
• This setting needs to be done for each single tape drive in
DataProtector under tape drive properties

363 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Do not send multiplexed data to StoreOnce Backup Systems
Symantec NetBackup

Do NOT check this box! This feature should

be used for physical tape drives (not virtual
tape drive), where several data streams are
supplied from different sources to enable
streaming of the physical tape drive.

364 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Network
• Choose the appropriate interface 1 or 10 GbE for required throughput
• Choose the appropriate network bonding mode (1, 4 or 6) that fulfills requirements
• Up to 128 vlan can be configured per StoreOnce model

365 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Performance consideration: e.g. FS & Print Server using VTL

FS & Receives data

Print from client
Backup target
Server and writes it to
E: D: backup target E: D:
D: E:
2TB 2TB

Backup client Backup server

Backup Performance depends on disk performance, Backup client, infrastructure bandwidth, throughput
performance of the Backup server and Backup target.
The slowest device or medium with the smallest bandwidth dictates backup performance.

366 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Performance consideration: e.g. FS & Print Server using VTL
Improvement

FS & Print Backup target

Server Backup
D: D:
Backup client Server

D: E: E: E:
2TB 2TB

FS & Print Backup target

Server Start multiple disk agent, in this case each disk drive creates
D:
Backup client minimum one backup stream that is able to run concurrently. In the
& server StoreOnce Backup System you are creating VTL‘s with multiple
E:
D: E: virtual tape drives with no extra cost compared to physical tape
2TB 2TB library.
As the StoreOnce Backup System requires multiple concurrent
backup streams for best performance it is advised to go for a setup
that uses concurrent running backup streams.

367 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Performance consideration: e.g. FS & Print Server using VTL
Further improvement

FS & Print Server Backup target

DP DA + MA D:

D: E: E:
500G 500
B GB
F:
F: G:
500G 500
B GB
G:

For future investment you should care about to keep your data simple to handle. In general there is a yearly data
growth of 30% - 60%. Most customer purchase Backup hardware for the next five years. Assuming 30% data
growth per year, your data is multiplied by factor ~3,7.
To avoid getting trouble with the data volume becoming too large to be backed up via a single backup stream,
multiple smaller disk drives should be used at the source. In case more capacity is required, add additional small
disk volumes. As a good advice, use disk volume with a size of 500GB – 1TB.

368 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 SO multi-node to multi-node Data Centre deployments - dedicate nodes
to VTL/NAS replication

• Easier to manage
• Allows predictable performance
• In failover – we expect backup & replication to be in different “windows” so it reduces the impact of fail-over on
both backup & replication.
• Scalable approach
• Consider initial seeding procedure

369 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 SO multi-node to multi-node – active/passive VTL/NAS replication
Simplified illustration
Couplet 1 Couplet 2
Site A
service
service set
set service
service set
set service
service set
set service
service set
set
Replication Replication
VT7 NAS 7
NAS1 NAS2
(target) (target)
Active/Passive Replication ( backup sources on Site B)
VT1 (target) VT5(Target)
Node 1 Node 2 node5 node6 node7 node8
Node 3 Node 4

storage
storage storage
storage storage
storage storage
storage

Site B
Couplet 1 Couplet 2 Couplet 3 Couplet 4

service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set
Replication

Replication Replication Replication Replication

VT3 VT4 VT6
VT2
VT1(Source) VT5 Source NAS 1 Source NAS 2 Source

node1 node2 node3 node4 node5 node6 node7 node8

storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage

8 node cluster Active/Passive Replication – VT1&5, NAS1&2 to be replicated

370 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 SO multi-node to multi-node – active/active VTL/NAS replication
Simplified illustration

8 node cluster Active/Active Replication Site A

Couplet 1 Couplet 2 Couplet 3 Couplet 4

service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set
Replication

VT2 (Source) VT4(Source) VT6 NAS2

VT1 (target) VT3
VT3 (target)
(target) VT5
VT5 (target)
(target) NAS
NAS 11 Source
Source
Source (target)
node1 node2 node3 node4 node5 node6 node7 node8

storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage

Site B
Couplet 1 Couplet 2 Couplet 3 Couplet 4
))
service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set
Replication

VT1(Source)
VT1(Source) VT3(Source) NAS1
VT2 NAS1
VT2 (target)
(target) VT4 (target) VT5
VT5 Source
Source VT6(Target) NAS 2 Source
(target)
(target)
node1 node2 node3 node4 node5 node6 node7 node8

storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage

371 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 SO multi-node to multi-node – active/active VTL/NAS replication &
backup
Simplified illustration

8 node cluster Active/Active Replication and local backup

Couplet 1 Couplet 2 Couplet 3 Couplet 4

service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set
Replication
VT2 (Source) VT4 VT6 NAS2
VT1 (target) VT3 VT6
VT3 (target)
(target) Source
NAS
NAS 11 Source
Source
Source (target)
node1 node2 node3 node4 node5 node6 node7 node8

storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage

Local backup
not replicated
Local backup not
replicated Site B
Couplet 1 Couplet 2 Couplet 3 Couplet 4

service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set
Replication
VT1(Source)
VT1(Source) VT3(Source)
VT3(Source) NAS1
VT2 NAS1
VT2 (target)
(target) VT5 VT6(Target)
VT6(Target) NAS
NAS 22 Source
Source (target)
(target)
node1 node2 node3 node4 node5 node6 node7 node8

storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage

372 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Many to One – SO single node to multi-node Data Centre deployments
Simplified illustration - load balance remote sites across dedicated replication nodes at target

Local backups Local backups Local backups Local backups

Site A
Couplet 1 Couplet 2 Couplet 3 Couplet 4

service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set service
service set
set
Replication

VT2 VTT 1-10 VT4

VT4 VTT 10-20 VTT 20-30 NAST
NAST 1-10
1-10
(targets) (targets) VT6
VT6 (target) NAS
NAS 11 (targets)
(targets)

node1 node2 node3 node4 node5 node6 node7 node8

storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage storage
storage

8 node cluster supporting Many to One Replication

Max configuration couplet (4 storage shelves)

can support replication apparent throughput
of 1166 MB/sec when dedicated to replication.

Remote Sites
Max 48 streams Max 48 streams Max 48 streams Max 48 streams
VTR
VTR 1-10
1-10 VTR
VTR 10-20
10-20 VTR 20-30 NASR
NASR 1-10
1-10
(Sources)
(Sources) (Sources)
(Sources) Sources Sources
Sources

373 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 SO multi-node: VIF takes care of GbE Fail-over but FC fail-over
requires NPIV support and careful implementation using VTL

Host 1 Host 2 Host 3 Host 4 Host 5 Host 6

Fabric1 Fabric 2
FC FC FC FC
Switch 1 Switch 2 Switch 3 Switch 4

• Zoning by WWPN.
• Each zone to include a
Port 1 Port Port 3 Port 4 Port 1 Port 2 Port 3 Port 4 host and the required
2
targets on StoreOnce
VTL1 VTL2 VTL3 VTL4
Node 1 Node 2

374 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 SO single node - Create redundancy of your VTL robotic
VTL medium changers (robots) can be presented to Port1, Port 2, Port 3, Port 4, Port 1 & 2 or Port 3 & 4 on the SO
multi nodes. By placing all configured robots on Port 1 & Port 2 or Port 3 & 4 it is possible to build in external SAN
redundancy (through the use of multiple fabrics).

Fabric 1 Fabric 2

Port 1 Port 2 Port 3 Port 4

SO single node
applicance
or VTL1 VTL2
B6200/6500 node Robotic Robotic

375 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce Catalyst over Fibre Channel - GUI
Fibre Channel Settings configuration page is displayed in the GUI

376 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce Catalyst over Fibre Channel – Step 1
Zone the Catalyst over Fibre Channel client and StoreOnce target HBA ports

• Each StoreOnce FC port presents a single Catalyst over Fibre Channel WWPN / WWNN.

• Use the WWPN / WWNN values to zone each Catalyst over Fibre Channel service with the client HBA port. On the
switch, the Catalyst over FC device will be presented as follows:

• Once zoning is complete the “Number of Logins” will increase in the GUI

377 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce Catalyst over Fibre Channel – Step 2
Determine the number of concurrent backup / restore streams required

• On Linux it is possible that a single client HBA port talking to a single StoreOnce HBA port can open multiple concurrent
connections; i.e. backup / restore streams. On Windows this is not possible; Windows has a queue depth of 1.
• Catalyst over FC implements a multi-LUN solution to allow multiple simultaneous connections from a Windows client. By
presenting multiple LUNs a host port can open multiple simultaneous connections to a target StoreOnce port. The number of LUNs
is controlled via the “Devices per Initiator Port” setting in the StoreOnce GUI.

• If a StoreOnce target port is used ONLY for Linux backups the “Devices per Initiator Port” can be left at 1.
• If a StoreOnce target port is used for Windows backups the “Devices per Initiator Port” must be calculated, as described in
the next slides.

378 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce Catalyst over Fibre Channel – Step 3 cont.
How to Calculate the required number of “Devices per Initiator Port”
• By default each client HBA port to server HBA port will present 1 LUN. If a client HBA port can see multiple server ports, it has
multiple FC routes into the StoreOnce node.
• To increase the number of devices or LUNs presented in each client - server HBA port relationship, increase the “Devices per
Initiator Port” as described below:

Example 1: Host Port

• 1 FC client port zoned with 4 target FC ports of a StoreOnce node.

• With a devices per initiator port setting of 1 for each StoreOnce target port,
• the total possible concurrent streams is 4:
Node 1 Node 1 Node 1 Node 1
FC Port FC Port FC Port FC Port
1 2 3 4

379 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce Catalyst over Fibre Channel – Step 4 cont.
Example 2: Host Port Host Port
1 2
• 2 FC client ports zoned with 4 target FC ports of a StoreOnce node.
• With a devices per initiator port setting of 1 for each StoreOnce target port,
• the total possible concurrent streams is 8:

Node 1 Node 1 Node 1 Node 1

FC Port FC Port FC Port FC Port
1 2 3 4

Example 3: Host Port Host Port

1 2
• 2 FC client ports zoned with 4 target FC ports of a StoreOnce node.
• With a devices per initiator port setting of 2 for each StoreOnce target port,
• the total possible concurrent streams is 16:

Node 1 Node 1 Node 1 Node 1

FC Port FC Port FC Port FC Port
1 2 3 4

380 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce Catalyst over Fibre Channel – Step 5
• Confirm that the client and target HBA ports are zoned together
• On Linux, use one of the following to list the available “StoreOnce CoFC” devices:

Run “lsscsi --generic”: Run “cat /proc/scsi/scsi”:

[root@greenday ~]# lsscsi --generic [root@greenday ~]# cat /proc/scsi/scsi
[4:0:6:0] process HP StoreOnce CoFC CAT1 - /dev/sg6 Attached devices:
[4:0:6:1] process HP StoreOnce CoFC CAT1 - /dev/sg7 Host: scsi4 Channel: 00 Id: 06 Lun: 00
Vendor: HP Model: StoreOnce CoFC Rev: CAT1
Type: Processor ANSI SCSI revision: 03
Host: scsi4 Channel: 00 Id: 06 Lun: 01
Vendor: HP Model: StoreOnce CoFC Rev: CAT1
Type: Processor ANSI SCSI revision: 03

381 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce Catalyst over Fibre Channel – Step 6 cont.
• On Windows:
Devices will be displayed in the “device manager” in the “other
devices” section

NOTE: If you increase the number of “Devices per Initiator Port” in

the StoreOnce GUI you must “scan for hardware changes” in the
Windows “device manager” before the new devices will be seen by
Windows.

382 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 StoreOnce Catalyst over Fibre Channel – Step 7
• Backup using the Catalyst over FC Identifier or Alias

• In Ethernet, Catalyst backups are performed using the VIF / FQDN address of the StoreOnce service set. Catalyst over FC
has equivalent addresses called the “Identifier” and “Alias”. The “COFC-” addresses should be used where an IP address
would have previously been entered.

• Identifiers may not be modified, but users can alter the alias. All addresses must begin “COFC-” as this is the way that
Catalyst determines the backup / restore is Fibre Channel based.

• Identifiers and aliases are case sensitive and must be entered into the backup application correctly.

383 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Federated Catalyst Copy
Backup Server • Backup to System #1 is done via Subnet 2.
• Catalyst Copy of Fed Cat Store from System
Management VIF #1 to System #2 is done via Subnet 1 System #2:
Node 2 (proxy) receives Catalyst Copy data and re-distributes it to the
Data VIFs subnet 1 other federation members over the internal 10GbE network.
router
Data VIFs subnet 2 System #1:
All federation members are sending their data
over the internal 10GbE network to node 1
(proxy) who will Catalyst Copy data to System
Subnet 1 (default) #2. Subnet 1 (default)

Subnet 2

10GbE internal network

SO Node 1 SO Node 2 SO Node 3 SO Node 4 SO Node 1 SO Node 2 SO Node 3 SO Node 4

Node
management Node
management Node
management Node
management Node
management Node
management
Node
management
Node
management

192.168.6.21 192.168.6.22 192.168.6.23 192.168.6.24 192.168.6.25 192.168.6.26 192.168.6.27 192.168.6.28

192.168.7.31 192.168.7.32 192.168.7.33 192.168.7.34
192.168.6.20
Federated Catalyst Store #1 Federated Catalyst Store #2

Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID Shared Filesystem + RAID
Couplet 1 Couplet 2 Couplet 1 Couplet 2
StoreOnce Multinode System #1
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
StoreOnce Multinode System #2
 Federated Catalyst Copy
• To configure a federated catalyst store into one of
the supported backup application a single node out
of the federation is used.
• This node will do the routing and acting as a proxy
for other federation member.
• This node will catalyst copy all data to a StoreOnce
target device.
IP
LAN

External 2 x 10GbE
Internal dual 10GbE

Federated Catalyst Store

proxy
Node 1 Node 2 Node 3 Node 4 Node 5 Node 6 Node 7 Node 8

385 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Federated Catalyst Copy - optimization
• To distribute catalyst copy traffic via multiple
nodes, create smaller federation stores spanned
over different nodes.
• In general not more data will be able to catalyst
copy than the internal bandwidth is able to
provide

IP
LAN
External 2 x 10GbE
External 2 x 10GbE

Internal dual 10GbE

Federated Catalyst Store Federated Catalyst Store

proxy proxy
Node 1 Node 2 Node 3 Node 4 Node 5 Node 6 Node 7 Node 8

386 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Federated Catalyst Copy - optimization
• To distribute catalyst copy traffic via multiple
nodes, create multiple federation stores but
configure different federation member acting as a
proxy
• In general not more data will be able to catalyst
copy than the internal bandwidth is able to provide

IP
LAN
External 2 x 10GbE
External 2 x 10GbE
Internal dual 10GbE

Federated Catalyst Store 1

Proxy 1

Federated Catalyst Store 2

Proxy 2

Node 1 Node 2 Node 3 Node 4 Node 5 Node 6 Node 7 Node 8 

387 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
 Thank you

Contact information


388 © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.