Home » HP Manuals » Storage Devices » HP StorageWorks 6000 » Manual Viewer

HP StorageWorks 6000 HP StorageWorks VLS and D2D Solutions Guide (AG306-96028, - Page 205

Disable Plug and Play Test Unit Ready TUR for any tape drivers in use.

View all HP StorageWorks 6000 manuals

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

Page 205 highlights

• Windows device configuration: The following guidelines apply to Networker on Windows: • Disable Plug and Play Test Unit Ready (TUR) for any tape drivers in use. A SCSI TUR command may rewind a mounted NetWorker tape unexpectedly, causing data loss. • Enable "verify header on eject" in the NetWorker autochanger. This marks any tapes corrupted by a SCSI TUR reset/rewind as suspect. • For versions of NetWorker newer than 7.4.1, use Windows Tape Drive Persistence to ensure that tape device names do not change when Windows is rebooted. This will enable device paths other than the standard \\.\Tape0 to be used, such as \\.\Tape2147483646 or \ \.\tape4801101. For Windows Tape Drive Persistence, see http://support.microsoft.com/ kb/873337. • Confirm that the Fibre Channel device supports a maximum block size larger than that being used in NetWorker. This can most easily be done in Windows via the NetWorker mt command. If the maximum supported block size found via the mt command is too small (typically 64 or 96 KB), contact the Fibre Channel HBA Vendor for assistance in modifying the SCSI Scatter/Gather registry setting in the Windows Registry for the Fibre Channel HBA. The following is an example mt command: C:\>mt -f \\.\Tape4801110 status \\.\Tape4801110: Media Capacity = 292.97GByte Media Remaining = 289.95GByte Media Blocksize = 0 Media Partition Count = 1 Media is not write protected default blocksize = 65536 maximum blocksize = 524288 • Linux device configuration: The following guidelines apply to Networker on Linux: • Configure stinit.def to enable variable block size. This requires the st-mt package to be installed and /etc/stinit.def to be configured. See the Linux man page for configuration details and examples. HP recommend setting stinit to load via an init file (for example, /etc/rc.local on Redhat) to ensure it is loaded properly. • NetWorker supports Linux udef device naming. See the EMC whitepaper Persistent Binding and udef Changes for EMC NetWorker for details (document h5795, available at https:// powerlink.emc.com). • UNIX device configuration: The following guidelines apply to Networker on UNIX: • AIX - Ensure that variable block mode is enabled. AIX does not have a persistent naming option, although the ODM database generally tracks device links properly across reboots. • Solaris - Ensure that the tape drive is supported in the kernel. This is most easily done by running strings /kernel/drv/sparcv9/st |grep -i LTO (for LTO) and comparing this to the tape drive string found in /var/adm/ messages. If tape drive is unsupported by the kernel, configure st.conf to allow variable block mode. For Solaris Persistent Naming, see Section 8, Persistent Binding for Tape Devices available at http://docs.sun.com/source/819-0139/. • HPUX - An issue exists when EMC NetWorker uses tape library SCSI commands via activation of a Common Device Interface (CDI) with the HPUX 11.31. Operating CDI is activated by default in EMC NetWorker. When CDI is activated, HPUX estape driver has a problem distinguishing between EOT and BOT, thus causing job failures. The EMC messages log may contain the following as symptom: Oct 22 13:30:29 nairobi: NetWorker media: (warning) rd=suzanne.ebs.net:/dev/rmt/c8t2d0BESTnb writing: continuation, No space left on device, at file 2 record 0Oct 22 13:30:29 nairobi: NetWorker media: (emergency) HP StorageWorks VLS and D2D Solutions Guide 205

Section	Page
HP StorageWorks VLS and D2D Solutions Guide	1
Table of Contents	3
1 Introduction	13
2 Concepts	15
Disk-based Backup and Virtual Tape Libraries	15
Problems Addressed by Virtual Tape Libraries	15
Integration of Disk in Data Protection Processes	15
Where Virtual Tape Fits in the Big Picture	16
HP VLS and D2D Portfolio	16
Typical VLS Environments	17
Typical D2D Environments	17
What are the Alternatives?	18
Physical Tape	18
NAS	18
Application-based Disk Backup	18
Business Copy	19
Deduplication	20
Introduction	20
HP StorageWorks Deduplication Solutions	20
Deduplication Ratios	21
Target-based Deduplication	22
Tape Oversubscription	23
Replication	23
Introduction to Replication	23
HP StorageWorks Replication Solutions	24
Replication Deployment Options	26
Backup Application Interaction with Replication	28
Replication Limitations	29
3 Backup Solution Design Considerations	31
Analyze the Existing Environment	31
Consider How you Want to Back Up your Data to the VLS or D2D	31
Consider How you Want to Copy the Backup Data to an Off-site Location	33
Consider Speed and Ease of the Restore as well as the Backup	33
Single Library vs. Multiple Libraries	33
Single Library	33
Benefits of Single Library Systems	34
Considerations for Single Library Systems	34
Multiple Library	35
Benefits of Multiple Library Systems	35
Multiplexing, Multistreaming, and Multipathing	36
Multiplexing	36
Multistreaming	36
Multipathing	36
Blocksize and Transfer Size	37
LAN-free Backups	37
Retention Planning	37
Future Data Growth	38
Considerations for Copies	38
Copy to Physical Tape through the Backup Application	39
Media Server Considerations	40
Benefits of Copying to Physical Tape through the Backup Application	40
Considerations for Copying to Physical Tape through the Backup Application	41
Copy to Tape using VLS Automigration	41
Benefits of Echo Copy	42
Considerations of Echo Copy	42
Copy to Tape using D2D Tape Offload	43
Copy to Remote Disk Backup Device using Replication	43
Benefits of Replication	44
Considerations of Replication	44
Creating Archive Tapes from the Replication Target	44
Considerations for Restores	44
Restoring from Disk Backup Device	45
Restoring from Backup Application-created Tape Copy	45
Restoring from the Replication Target	45
Performance Bottleneck Identification	45
Backup SAN Design Guidelines	46
General SAN Design Considerations	46
SAN Zoning	46
Operating System Tape Configuration	47
LUN Masking and Mapping	49
Backup Application Basic Guidelines	50
HP Data Protector Application Overview	51
Symantec NetBackup Application Overview	51
IBM TSM Application Overview	52
EMC NetWorker Application Overview	53
4 D2D Systems	55
D2D Devices	55
D2D Defined	55
D2D Technical Specifications	56
D2D Design Considerations	56
D2D Port Optimization	56
D2D Ethernet Ports	56
Backup Server Networking	57
Fibre Channel SAN	57
Multiple Backup Streams	57
Disable Backup Application Verify Pass	58
Tape Copy or Offload Performance	58
Tape Library Emulation	59
Emulation Types	59
Cartridge Sizing	59
Number of Libraries per Appliance	59
Optimizing Rotation Scheme to Reduce Housekeeping	59
D2D Blueprints	60
Single Site Cost Effective Backup Device Consolidation	60
Large SME Site Consolidation Requiring Fibre Channel Shared Devices	61
Multi-site Small Business Disaster Recovery Solution	63
Introduction to VMWare Terminology	65
Using D2D in Simple VMWare Environments with ESXi	66
Using D2D in VMWare Environments with ESX4 and VMWare Consolidated Backup	66
Using D2D in larger VMWare environments with HP Data Protector Zero Downtime Backup with Instant Recovery (ZDB + IR)	67
D2D Dynamic Deduplication	69
How it Works	69
Dynamic Deduplication Implementation	70
Restoring Data	71
Housekeeping	72
D2D Replication	73
How it Works	73
D2D Replication Implementation	73
Licensing	74
Implementing the Initialization Process	74
Initialization — Co-location and WAN Replication	75
Physical Tape Initialization — Export and Import	75
Replication Setup	76
Configuring Replication	78
Reporting	82
Target Device Reporting	82
Source Device Reporting	83
Design Considerations	84
Link Sizing	84
Telco Provisioning — Overview of Inter-Site Links	90
Some Idea of Telco Costs	92
Telco Terminology and Branding for WAN Services	93
D2D Replication Data Recovery Options	95
Restore Directly from the D2D Target Device	95
Reverse Replication on the D2D	95
Reverse Tape Initialization on the D2D	98
Creating Archive Tapes from the Target	99
5 Virtual Library Systems	101
VLS Devices	101
VLS Defined	101
Prime Environments	102
VLS Benefits	102
VLS9000–series Configurations	103
VLS Technical Specifications	104
How it Works	111
VLS Scalability	111
VLS Automatic Performance Load Balancing	113
VLS Warm Failover	114
Implementation	115
Device Configuration Preparation	115
Basic VLS device configuration	115
Basic Backup Application Configuration	116
Capacity Licensing	117
Virtual Libraries/drives/cartridge Configuration	118
EVA Preparation	119
Storage Pooling	121
VLS9000 Storage Pooling	122
VLS Gateway Storage Pooling	123
VLS Design Considerations	123
VLS Sizing	123
Outlining the Steps	123
Considerations	124
EVA Performance Sizing (VLS12000 Gateway)	124
Sizing/implementation Examples	125
Example 1 VLS Sizing for Performance and Capacity	125
Example 2 Testing Backup to Tape vs. Backup to VLS	125
Example 3: VLS12000 EVA Sizing Without Deduplication	126
Example 4: VLS12000 EVA Sizing With Deduplication	126
VLS Blueprints	127
Reduce Backup Window (No Deduplication)	127
Large Scale Backup Consolidation (No Deduplication)	128
Managing Data Retention and Reducing Backup Storage Costs	129
Full Enterprise Backup and Disaster Recovery Capability	130
Multi-data Center Replication to a Common Disaster Recovery Site	132
VMWare Backup Environment with ESXi.	133
VMWare Backup Environment with ESX4 and VCB-based Backups	134
Larger VMWare Environment with ESX4 and HP Data Protector ZDB IR Integration with VMWare Consolidated Backup	136
Large Enterprise Cross-site Backup with Deduplication and Inbuilt Disaster Recovery	138
Combining D2D and VLS in an End-to-end Solution for ROBO/Regional DCs and Main Data Center using HP Data Protector	139
VLS Automigration	140
Echo Copy Concepts	141
Implementation	141
Echo Copy Pools	141
Automigration Policy	142
Automigration Setup	143
Design Considerations	145
Automigration Use Models	145
Backup to Non-shared Virtual Libraries	145
Backup to a Shared Virtual Library	146
Sizing the Tape Library	147
Restoring from Automigration Media	148
VLS Accelerated Deduplication	148
How it Works	149
Accelerated Deduplication Implementation	152
Supported Backup Applications and Data Types	153
Deduplication Preparation	153
Licensing	154
Migrating your Existing Backup Data	155
Configuration and Reporting	155
Handling the Device Out of Capacity Condition	156
Design Considerations	157
Performance	157
Capacity Sizing	158
Node Oversubscription	158
Optimum Record Sizing	159
Optimizing File Server Deduplication	159
Media Management	160
Client and Backup Job Naming	160
Disabling Deduplication on Specific Backup Policies	161
VLS Replication	161
How it Works	161
Replication of Incremental Backups	163
Multi-node Replication Scaling	164
VLS Replication Implementation	164
Licensing	164
Replication Preparation	165
Replication Setup	166
Implementing the Initialization Process	172
Physical Tape Initialization	172
WAN Initialization	174
Co-location Initialization	175
Continuing Role for Physical Tape	176
Reporting	176
Status of LAN/WAN Replication Connection	177
Source Device Replication Status	177
Target Device Replication Status	179
Replication Job Status	179
Replication Job History	179
Design Considerations	180
Advanced Replication Job Control	180
Link Sizing	182
Basic Calculations	182
Device Sizing	187
VLS Replication Data Recovery Options	187
Restore Directly from the VLS Target Device	187
Restore the VLS over the LAN/WAN	189
Rebuilding Source Device and Re-establishing Replication	190
Creating Archive Tapes from the Target	190
ISV Import Email Format	191
Email Processing Example Script	192
VLS Non-deduplicated Replication	192
Replicating a Subset of Virtual Cartridges - a Use Case	193
Detailed Backup Application Guidelines for VLS	194
HP Data Protector	194
Data Protector General Guidelines	194
Data Protector Deduplication Guidelines	195
Data Protector Import Example Script	196
Symantec NetBackup	197
NetBackup General Guidelines	197
NetBackup Deduplication Guidelines	198
NetBackup Import Example Script	198
IBM TSM	199
TSM General Guidelines	199
TSM Deduplication Guidelines	200
TSM Useful Queries	203
EMC NetWorker	204
Networker General Guidelines	204
Networker Deduplication Guidelines	206
6 Support and Other Resources	209
Related Information	209
Documents	209
Websites	209
Contacting HP	209
Before you contact HP	209
HP contact information	210
Subscription Service	210
Document Conventions and Symbols	210
Glossary	213

Match case Limit results 1 per page

•

Windows device configuration: The following guidelines apply to Networker on Windows:

•

Disable Plug and Play Test Unit Ready (TUR) for any tape drivers in use. A

SCSI TUR

command

may rewind a mounted NetWorker tape unexpectedly, causing data loss.

•

Enable

“

verify header on eject

”

in the NetWorker autochanger. This marks any tapes corrupted

by a

SCSI TUR

reset/rewind as suspect.

•

For versions of NetWorker newer than 7.4.1, use Windows Tape Drive Persistence to ensure

that tape device names do not change when Windows is rebooted. This will enable device

paths other than the standard

\\.\Tape0

to be used, such as

\\.\Tape2147483646

\.\tape4801101

. For Windows Tape Drive Persistence, see

tp://su

ppo

.mi

.co

kb/8

•

Confirm that the Fibre Channel device supports a maximum block size larger than that being

used in NetWorker. This can most easily be done in Windows via the NetWorker

command.

If the maximum supported block size found via the

command is too small (typically 64 or

96 KB), contact the Fibre Channel HBA Vendor for assistance in modifying the SCSI Scat-

ter/Gather registry setting in the Windows Registry for the Fibre Channel HBA. The following

is an example

command:

C:\>mt -f \\.\Tape4801110 status

\\.\Tape4801110:

Media Capacity = 292.97GByte

Media Remaining = 289.95GByte

Media Blocksize = 0

Media Partition Count = 1

Media is not write protected

default blocksize = 65536

maximum blocksize = 524288

•

Linux device configuration: The following guidelines apply to Networker on Linux:

•

Configure

stinit.def

to enable variable block size. This requires the

st-mt

package to

be installed and

/etc/stinit.def

to be configured. See the Linux man page for configur-

ation details and examples. HP recommend setting

stinit

to load via an init file (for example,

/etc/rc.local

on Redhat) to ensure it is loaded properly.

•

NetWorker supports Linux udef device naming. See the EMC whitepaper

Persistent Binding

and udef Changes for EMC NetWorker

for details (document h5795, available at

s://

link

.co

•

UNIX device configuration: The following guidelines apply to Networker on UNIX:

•

AIX

–

Ensure that variable block mode is enabled. AIX does not have a persistent naming option,

although the ODM database generally tracks device links properly across reboots.

•

Solaris

–

Ensure that the tape drive is supported in the kernel. This is most easily done by running

strings /kernel/drv/sparcv9/st |grep

–

i LTO

(for LTO) and comparing this to

the tape drive string found in

/var/adm/

messages. If tape drive is unsupported by the kernel,

configure

st.conf

to allow variable block mode. For Solaris Persistent Naming, see Section

Persistent Binding for Tape Devices

available at

tp://doc

.sun

.co

m/s

ce/819-013

•

HPUX

–

An issue exists when EMC NetWorker uses tape library SCSI commands via activation

of a Common Device Interface (CDI) with the HPUX 11.31. Operating CDI is activated by

default in EMC NetWorker. When CDI is activated, HPUX

estape

driver has a problem dis-

tinguishing between EOT and BOT, thus causing job failures. The EMC messages log may

contain the following as symptom:

--------------------------------------------------------------------------------

Oct 22 13:30:29 nairobi: NetWorker media: (warning)

rd=suzanne.ebs.net:/dev/rmt/c8t2d0BESTnb writing: continuation, No space left on

device, at file 2 record 0Oct 22 13:30:29 nairobi: NetWorker media: (emergency)

HP StorageWorks VLS and D2D Solutions Guide

205