Home » HP Manuals » Storage Devices » HP 12000 » Manual Viewer

HP 12000 HP VLS Solutions Guide Design Guidelines for Virtual Library Systems - Page 115

Link Sizing, Table 22 Network Latency

View all HP 12000 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 115 highlights

Table 22 Network Latency Job Concurrency Required to Saturate Link 2 4 4 7 7 Network Latency 0ms 50ms 100ms 200ms 500ms Aggregate Mbytes/sec 80 MB/sec 80 MB/sec 80 MB/sec 80 MB/sec 52 MB/sec • A new option in firmware versions 3.4.1 and higher is the ability to throttle the number of replication job that can run on the master node0 of a multi-node configuration. ◦ In multi-node configurations of three nodes or more, this option can be used to prevent replication jobs running on node0 and thus optimize overall system performance. ◦ In multi-node configurations where you have a separate management LAN from the replication data LAN, you can prevent replication jobs running on node0: - Set the number of replication jobs to zero on both the source device and the target device. - The separate management LAN must still allow replication management traffic to pass from node0 on the source device to node0 on the target device in the DR site. - The secondary nodes can then be connected to the replication data LAN that provides data communications between the source and target VLS. - All secondary nodes must be configured to the data LAN so that replication job processing is distributed across all secondary nodes. The number of replication jobs on the VLS is set via the "Max number of jobs to run on master node" option in the Global LAN/WAN Replication Target Configuration. This is a global setting that applies to the local VLS device (not the remote target device). When you set the global per job Mbytes/sec limit on the target device, you can calculate the Mbytes/sec limit on each replication target by multiplying the per job limit by the maximum number of concurrent jobs set for that replication target. This is only the Mbytes/sec limit but it will only apply if the replication link bandwidth is higher than this limit. Link Sizing This section focuses on understanding how to size the replication link bandwidth required. The size of the replication link will depend on your usage model for replication. NOTE: For the volumes of data to replicate with HP VLS systems, HP recommends a dedicated replication link wherever possible. • Backup and replication can take place in a fixed window (up to 12 hours) preferably when the WAN link is not heavily used by applications (that is outside business hours). The replication process has almost the full bandwidth of the WAN link available to it. Within the HP VLS System configuration for replication you can set a "replication start time and window" during which time replication is allowed to operate. • The business runs 24x7 and there are no fixed windows in which to do replication. In this example the replication can be "limited" and the HP VLS devices can be configured to only use a percentage of the available bandwidth so as not to adversely affect application performance if applications are sharing the same WAN link. Design Considerations 115

Section	Page
HP VLS Solutions Guide	1
Contents	3
1 Introduction	8
2 Concepts	9
Disk-based Backup and Virtual Tape Libraries	9
Problems Addressed by Virtual Tape Libraries	9
Integration of Disk in Data Protection Processes	9
Where Virtual Tape Fits in the Big Picture	9
HP VLS and D2D Portfolio	10
Typical VLS Environments	11
Typical D2D Environments	11
What are the Alternatives?	12
Physical Tape	12
NAS	12
Application-based Disk Backup	12
Business Copy	13
Deduplication	14
Introduction	14
HP Deduplication Solutions	14
Deduplication Ratios	15
Target-based Deduplication	16
Tape Oversubscription	16
Replication	17
Introduction to Replication	17
HP Replication Solutions	17
Replication Deployment Options	20
Backup Application Interaction with Replication	22
Replication Limitations	23
3 Backup Solution Design Considerations	24
Analyze the Existing Environment	24
Consider How you Want to Back Up your Data to the VLS	24
Consider How you Want to Copy the Backup Data to an Off-site Location	26
Consider Speed and Ease of the Restore as well as the Backup	26
Single Library vs. Multiple Libraries	26
Single Library	26
Benefits of Single Library Systems	27
Considerations for Single Library Systems	27
Multiple Library	28
Benefits of Multiple Library Systems	28
Multiplexing, Multistreaming, and Multipathing	29
Multiplexing	29
Multistreaming	29
Multipathing	29
Blocksize and Transfer Size	30
LAN-free Backups	30
Retention Planning	30
Future Data Growth	31
Considerations for Copies	31
Copy to Physical Tape through the Backup Application	31
Media Server Considerations	32
Benefits of Copying to Physical Tape through the Backup Application	33
Considerations for Copying to Physical Tape through the Backup Application	33
Copy to Tape using VLS Automigration	33
Benefits of Echo Copy	34
Considerations of Echo Copy	34
Copy to Remote Disk Backup Device using Replication	35
Benefits of Replication	35
Considerations of Replication	35
Creating Archive Tapes from the Replication Target	35
Considerations for Restores	36
Restoring from Disk Backup Device	36
Restoring from Backup Application-created Tape Copy	36
Restoring from the Replication Target	36
Performance Bottleneck Identification	37
Backup SAN Design Guidelines	37
General SAN Design Considerations	37
SAN Zoning	37
Operating System Tape Configuration	38
LUN Masking and Mapping	40
4 VLS Devices	42
VLS Defined	42
Prime Environments	43
VLS Benefits	43
VLS9000–series and VLS9200 Configurations	44
VLS Technical Specifications	45
How it Works	52
VLS Scalability	52
VLS Automatic Performance Load Balancing	54
VLS Warm Failover	55
Implementation	55
Capacity Licensing	55
Virtual Libraries/drives/cartridge Configuration	56
EVA Preparation	57
Storage Pooling	59
VLS9000 Storage Pooling	60
VLS Gateway Storage Pooling	61
VLS Sizing	61
Outlining the Steps	61
Considerations	62
EVA Performance Sizing (VLS12X00 Gateway)	62
Sizing/implementation Examples	63
Example 1 VLS Sizing for Performance and Capacity	63
Example 2 Testing Backup to Tape vs. Backup to VLS	63
Example 3: VLS12000 EVA Sizing Without Deduplication	64
Example 4: VLS12000 EVA Sizing With Deduplication	64
VLS Blueprints	64
Reduce Backup Window (No Deduplication)	65
Large Scale Backup Consolidation (No Deduplication)	66
Managing Data Retention and Reducing Backup Storage Costs	67
Full Enterprise Backup and Disaster Recovery Capability	68
Multi-data Center Replication to a Common Disaster Recovery Site	69
VMWare Backup Environment with ESXi.	71
VMWare Backup Environment with ESX4 and VCB-based Backups	72
Larger VMWare Environment with ESX4 and HP Data Protector ZDB IR Integration with VMWare Consolidated Backup	74
Large Enterprise Cross-site Backup with Deduplication and Inbuilt Disaster Recovery	76
Combining D2D and VLS in an End-to-end Solution for ROBO/Regional DCs and Main Data Center using HP Data Protector	77
5 Automigration	79
Echo Copy Concepts	79
Implementation	79
Echo Copy Pools	79
Automigration Policy	80
Automigration Setup	81
Design Considerations	83
Automigration Use Models	83
Backup to Non-shared Virtual Libraries	83
Backup to a Shared Virtual Library	84
Sizing the Tape Library	85
Restoring from Automigration Media	85
6 Accelerated Deduplication	87
How it Works	87
Accelerated Deduplication Implementation	91
Supported Backup Applications and Data Types	92
Licensing	92
Migrating your Existing Backup Data	92
Configuration and Reporting	93
Handling the Device Out of Capacity Condition	93
Design Considerations	94
Performance	94
Capacity Sizing	95
Optimum Record Sizing	95
Optimizing File Server Deduplication	95
Media Management	95
Client and Backup Job Naming	96
Disabling Deduplication on Specific Backup Policies	97
Separate Database Full Backups from Incremental Backups	97
7 Replication	98
How it Works	98
Replication of Incremental Backups	99
Multi-node Replication Scaling	100
VLS Replication Implementation	100
Licensing	100
Replication Setup	101
Implementing the Initialization Process	105
Physical Tape Initialization	106
WAN Initialization	107
Co-location Initialization	108
Continuing Role for Physical Tape	109
Reporting	109
Status of LAN/WAN Replication Connection	110
Source Device Replication Status	110
Target Device Replication Status	112
Replication Job Status	112
Replication Job History	112
Design Considerations	113
Advanced Replication Job Control	113
Link Sizing	115
Basic Calculations	116
Device Sizing	120
VLS Replication Data Recovery Options	120
Restore Directly from the VLS Target Device	120
Restore the VLS over the LAN/WAN	122
Rebuilding Source Device and Re-establishing Replication	123
Rebuilding Target Device and Re-establishing Replication	123
Creating Archive Tapes from the Target	124
ISV Import Email Format	125
Email Processing Example Script	125
8 Non-deduplicated Replication	127
Replicating a Subset of Virtual Cartridges - a Use Case	128
9 VLS Configuration and Backup Application Guidelines	129
SAN Configuration Guidelines	129
Device Configuration Preparation	129
Basic VLS Device Configuration	130
Basic Backup Application Configuration	131
Deduplication Preparation	132
Replication Preparation	133
HP Data Protector	135
HP Data Protector Application Overview	135
Data Protector General Guidelines	136
Data Protector Deduplication Guidelines	137
Data Protector Import Example Script	138
Symantec NetBackup	139
Symantec NetBackup Application Overview	139
NetBackup General Guidelines	140
NetBackup Deduplication Guidelines	140
NetBackup Import Example Script	141
IBM TSM	141
IBM TSM Application Overview	141
TSM General Guidelines	143
TSM Deduplication Guidelines	144
All Firmware Versions	144
Firmware Version 3.4	146
Firmware Version 6.0	147
TSM Useful Queries	147
EMC NetWorker	148
EMC NetWorker Application Overview	148
Networker General Guidelines	149
Networker Deduplication Guidelines	150
Oracle RMAN Scripting	151
Generic RMAN Configuration Optimization	151
Fully-optimized RMAN Configuration for Data Protector	152
Fully-optimized RMAN Configuration for NetBackup and Networker	152
Fully-optimized RMAN Configuration for TSM	153
10 Support and Other Resources	154
Related Information	154
Documents	154
Websites	154
Contacting HP	154
Before you contact HP	154
HP contact information	155
Subscription Service	155
Document Conventions and Symbols	155
Glossary	157

Match case Limit results 1 per page

Table 22 Network Latency

Aggregate Mbytes/sec

Network Latency

Job Concurrency Required to

Saturate Link

80 MB/sec

0ms

80 MB/sec

50ms

80 MB/sec

100ms

80 MB/sec

200ms

52 MB/sec

500ms

•

A new option in firmware versions 3.4.1 and higher is the ability to throttle the number of

replication job that can run on the master node0 of a multi-node configuration.

◦

In multi-node configurations of three nodes or more, this option can be used to prevent

replication jobs running on node0 and thus optimize overall system performance.

◦

In multi-node configurations where you have a separate management LAN from the

replication data LAN, you can prevent replication jobs running on node0:

–

Set the number of replication jobs to zero on both the source device and the target

device.

–

The separate management LAN must still allow replication management traffic to

pass from node0 on the source device to node0 on the target device in the DR site.

–

The secondary nodes can then be connected to the replication data LAN that provides

data communications between the source and target VLS.

–

All secondary nodes must be configured to the data LAN so that replication job

processing is distributed across all secondary nodes.

The number of replication jobs on the VLS is set via the “Max number of jobs to run on master

node” option in the Global LAN/WAN Replication Target Configuration. This is a global

setting that applies to the local VLS device (not the remote target device).

When you set the global per job Mbytes/sec limit on the target device, you can calculate the

Mbytes/sec limit on each replication target by multiplying the per job limit by the maximum number

of concurrent jobs set for that replication target. This is only the Mbytes/sec limit but it will only

apply if the replication link bandwidth is higher than this limit.

Link Sizing

This section focuses on understanding how to size the replication link bandwidth required.

The size of the replication link will depend on your usage model for replication.

NOTE:

For the volumes of data to replicate with HP VLS systems, HP recommends a dedicated

replication link wherever possible.

•

Backup and replication can take place in a fixed window (up to 12 hours) preferably when

the WAN link is not heavily used by applications (that is outside business hours). The replication

process has almost the full bandwidth of the WAN link available to it. Within the HP VLS

System configuration for replication you can set a “replication start time and window” during

which time replication is allowed to operate.

•

The business runs 24x7 and there are no fixed windows in which to do replication. In this

example the replication can be “limited” and the HP VLS devices can be configured to only

use a percentage of the available bandwidth so as not to adversely affect application

performance if applications are sharing the same WAN link.

Design Considerations

115