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

Backup Solution Design Considerations, Analyze the Existing Environment

Get HP 12000 PDF manuals and user guides View all HP 12000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 24 highlights

3 Backup Solution Design Considerations This section uses use models to explores many of the concepts you must consider when designing your system. Use models are organizational schemes that provide a basic organizational framework that you can use to delineate your environment and visualize how to implement the VLS for your best results. You might also think of the use models as decision trees in which each branch junction is a decision point that comes with value judgments and trade-offs. The decisions you make lead to an implementation plan. The choices you make are economic as well as functional. Different implementations can have different direct costs such as investment in licensing or equipment purchase/usage, and indirect costs such as investment in maintenance or configuration. You need to balance time, money, and use policies against one another. As with the major categories (tape, VTL, clone), there is no one size fits all solution. The optimum solution will be a balance of the models. Analyze the Existing Environment Carefully consider your environment in general, and your topology. Think about what you have, how you use it, and most importantly, what you want to optimize or improve. Determine your goals for your environment. Consider How you Want to Back Up your Data to the VLS • Identify the data that you want to backup to the VLS. For example: ◦ Data that needs a better service level than going directly to tape but does not need the highest service level (split mirror, for example). ◦ Slow servers in your current backup topology. Supported topologies include SAN or LAN/SAN hybrid: 24 Backup Solution Design Considerations

  • 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
3 Backup Solution Design Considerations
This section uses use models to explores many of the concepts you must consider when designing
your system. Use models are organizational schemes that provide a basic organizational framework
that you can use to delineate your environment and visualize how to implement the VLS for your
best results. You might also think of the use models as decision trees in which each branch junction
is a decision point that comes with value judgments and trade-offs. The decisions you make lead
to an implementation plan.
The choices you make are economic as well as functional. Different implementations can have
different direct costs such as investment in licensing or equipment purchase/usage, and indirect
costs such as investment in maintenance or configuration. You need to balance time, money, and
use policies against one another. As with the major categories (tape, VTL, clone), there is no one
size fits all solution. The optimum solution will be a balance of the models.
Analyze the Existing Environment
Carefully consider your environment in general, and your topology. Think about what you have,
how you use it, and most importantly, what you want to optimize or improve. Determine your goals
for your environment.
Consider How you Want to Back Up your Data to the VLS
•
Identify the data that you want to backup to the VLS. For example:
Data that needs a better service level than going directly to tape but does not need the
highest service level (split mirror, for example).
◦
◦
Slow servers in your current backup topology. Supported topologies include SAN or
LAN/SAN hybrid:
24
Backup Solution Design Considerations