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

Basic Backup Application Configuration

Page 116 highlights

• Select a storage pooling strategy for the VLS9000 and VLS12000. Identify which pools are used for which virtual libraries. This could be based on separating cartridges across virtual libraries, or decreasing the impact of array failure. See Storage Pooling. If you are planning to use deduplication, note that this currently supports only one storage pool per VLS. • For each virtual library, decide if dual SAN fabric design is needed. If so, this requires dual port virtual library robots and will affect the virtual drive assignment strategy when the system is in LUN masking mode. See Multiplexing, Multistreaming, and Multipathing. • Select the virtual library/drive types. The HP ESL-E library type is generally preferred due to its higher emulation limits, but the HP VLS library type (with the same emulation limits as ESL-E) is recommended for Netbackup because this is officially certified. • Select whether to use shared drives or LUN masked drives. This is based on the number of media servers that will be using each virtual library and on O/S limitations (such as HPUX versions prior to 11.31 not supporting more than eight library/tape LUNs per target port). See Backup SAN Design Guidelines. • Select how many virtual tape drives are needed per library. See Virtual Libraries/drives/cartridge Configuration. • If you use LUN masking, determine how many virtual drives need to be assigned to each media server based on the approximate number of concurrent backups needed for each media server, and develop a strategy for assigning virtual drives to each media server. • If you use shared drives, determine the number of drives based on the total number of concurrent backup streams required. (HPUX versions prior to 11.31 cannot see more than eight library/tape LUNs per target port.) • Determine the cartridge sizing. See Virtual Libraries/drives/cartridge Configuration. • Generally, HP recommends the default 100 GB cartridge size. • If you plan to enable deduplication on this device, assess the average amount of backup data per virtual tape drive and decide if the default 100 GB cartridge size should be decreased or increased. See Deduplication Preparation. • Determine if each virtual library is used as a replication source library; if so, decide if cartridges need to be created first in this source library or in the target library. See Replication Preparation. • Gather virtual cartridge barcode template requirements per library. • Assess the required number of slots in each virtual library. Methods of calculation: • Use the total logical amount of tape capacity per library needed to store the retention policy divided by compression divided by the virtual cartridge sizes. • Check the current total physical tape usage. If you are not changing the backup retention scheme when moving to VLS, the amount of virtual tape will be approximately the same as the current total amount of physical tape (already compressed) divided by the virtual cartridge sizes. • If this virtual library will be a replication target, it must contain at least as many slots as the total number of source slots that are replicating to this target. See Replication Preparation. • Gather the required basic device management settings: • TCP/IP settings for device management (node0). You only need TCP/IP settings for the other nodes if you will be using replication (every node requires a TCP/IP address for replication). • SNMP or email notification settings. • NTP server settings. Basic Backup Application Configuration The following steps highlight the considerations for designing the changes needed in the backup application to optimize for use with a VLS: 116 Virtual Library Systems

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218

Select a storage pooling strategy for the VLS9000 and VLS12000. Identify which pools are used
for which virtual libraries. This could be based on separating cartridges across virtual libraries,
or decreasing the impact of array failure. See
Storage Pooling
. If you are planning to use dedu-
plication, note that this currently supports only one storage pool per VLS.
For each virtual library, decide if dual SAN fabric design is needed. If so, this requires dual port
virtual library robots and will affect the virtual drive assignment strategy when the system is in LUN
masking mode. See
Multiplexing, Multistreaming, and Multipathing
.
Select the virtual library/drive types. The HP ESL-E library type is generally preferred due to its
higher emulation limits, but the HP VLS library type (with the same emulation limits as ESL-E) is re-
commended for Netbackup because this is officially certified.
Select whether to use shared drives or LUN masked drives. This is based on the number of media
servers that will be using each virtual library and on O/S limitations (such as HPUX versions prior
to 11.31 not supporting more than eight library/tape LUNs per target port). See
Backup SAN
Design Guidelines
.
Select how many virtual tape drives are needed per library. See
Virtual Libraries/drives/cartridge
Configuration
.
If you use LUN masking, determine how many virtual drives need to be assigned to each media
server based on the approximate number of concurrent backups needed for each media server,
and develop a strategy for assigning virtual drives to each media server.
If you use shared drives, determine the number of drives based on the total number of concurrent
backup streams required. (HPUX versions prior to 11.31 cannot see more than eight library/tape
LUNs per target port.)
Determine the cartridge sizing. See
Virtual Libraries/drives/cartridge Configuration
.
Generally, HP recommends the default 100 GB cartridge size.
If you plan to enable deduplication on this device, assess the average amount of backup data
per virtual tape drive and decide if the default 100 GB cartridge size should be decreased or
increased. See
Deduplication Preparation
.
Determine if each virtual library is used as a replication source library; if so, decide if cartridges
need to be created first in this source library or in the target library. See
Replication Preparation
.
Gather virtual cartridge barcode template requirements per library.
Assess the required number of slots in each virtual library. Methods of calculation:
Use the total logical amount of tape capacity per library needed to store the retention policy
divided by compression divided by the virtual cartridge sizes.
Check the current total physical tape usage. If you are not changing the backup retention
scheme when moving to VLS, the amount of virtual tape will be approximately the same as the
current total amount of physical tape (already compressed) divided by the virtual cartridge
sizes.
If this virtual library will be a replication target, it must contain at least as many slots as the
total number of source slots that are replicating to this target. See
Replication Preparation
.
Gather the required basic device management settings:
TCP/IP settings for device management (node0). You only need TCP/IP settings for the other
nodes if you will be using replication (every node requires a TCP/IP address for replication).
SNMP or email notification settings.
NTP server settings.
Basic Backup Application Configuration
The following steps highlight the considerations for designing the changes needed in the backup
application to optimize for use with a VLS:
Virtual Library Systems
116