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

Large Scale Backup Consolidation (No Deduplication), Data Protector, Netbackup, Networker, TSM

Page 66 highlights

Large Scale Backup Consolidation (No Deduplication) Company requirements: Up to 500 TB backup storage required in a single unit, high throughput required to meet backup windows. Solution: Multi-node VLS9000 using Object copy to physical tape. Caveats: Very large systems (greater than 300 TB) might be better split into two smaller systems for increased availability. With a single large VLS, typically one storage pool is configured which means if any full shelf in the VLS is lost (highly unlikely) then all virtual media is lost. But configuring multiple storage pools to overcome this means increased manageability overhead. ISVs: Data Protector, Netbackup, Networker, TSM, Commvault. See a full list at http:// www.hp.com/go/ebs. Device configuration highlights: Create as many virtual devices as you need and dedicate devices to certain SAN hosts by using the LUN mapping functionality. Backup application configuration highlights: For best throughput, schedule as many backups in parallel as you can. Use object copy functionality to schedule copy to physical tape. Figure 26 Using VLS for Large Scale Consolidation Recovery options: Typically direct from VLS, single file restores will be particularly fast; set retention periods accordingly. Older copies of data can be recovered directly from physical tape if required. Solution advantages: • Massive scalability in terms of capacity and performance, "hot add" capability for adding capacity and nodes • High availability features in nodes and back-end disk arrays • Flexible emulations in terms of number of libraries, drives, slots, and media sizes • Easy disaster recovery solution if physical tape copy is regularly off-sited Solution trade-offs: To guarantee scalable performance, each array module of 30 TB or 40 TB is a single component and cannot be split. Sizing capacity and throughput correctly is important to the solution being priced competitively. 66 VLS Devices

  • 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

Large Scale Backup Consolidation (No Deduplication)
Company requirements:
Up to 500 TB backup storage required in a single unit, high throughput
required to meet backup windows.
Solution
: Multi-node VLS9000 using Object copy to physical tape.
Caveats
: Very large systems (greater than 300 TB) might be better split into two smaller systems
for increased availability. With a single large VLS, typically one storage pool is configured which
means if any full shelf in the VLS is lost (highly unlikely) then all virtual media is lost. But configuring
multiple storage pools to overcome this means increased manageability overhead.
ISVs
: Data Protector, Netbackup, Networker, TSM, Commvault. See a full list at
h
t
tp://
w
w
w
.hp
.co
m/go/eb
s
.
Device configuration highlights
: Create as many virtual devices as you need and dedicate devices
to certain SAN hosts by using the LUN mapping functionality.
Backup application configuration highlights
: For best throughput, schedule as many backups in
parallel as you can. Use object copy functionality to schedule copy to physical tape.
Figure 26 Using VLS for Large Scale Consolidation
Recovery options
: Typically direct from VLS, single file restores will be particularly fast; set retention
periods accordingly. Older copies of data can be recovered directly from physical tape if required.
Solution advantages
:
Massive scalability in terms of capacity and performance, “hot add” capability for adding
capacity and nodes
High availability features in nodes and back-end disk arrays
Flexible emulations in terms of number of libraries, drives, slots, and media sizes
Easy disaster recovery solution if physical tape copy is regularly off-sited
Solution trade-offs
: To guarantee scalable performance, each array module of 30 TB or 40 TB is
a single component and cannot be split. Sizing capacity and throughput correctly is important to
the solution being priced competitively.
66
VLS Devices