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

Design Considerations, Automigration Use Models, Backup to Non-shared Virtual Libraries

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 83 highlights

retention period passes, the virtual cartridges are deleted, at which point a physical tape is needed for restore operations. See "Restoring from Automigration Media" (page 85). 5. Thirty days have passed. The truck returns with the physical tapes previously transported off-site that are now to be recycled. 6. The media life cycle starts again. The recycled tapes are loaded into the destination library using Load Media for Overwrite. After scanning the tape headers, automigration automatically creates virtual cartridges with matching headers. At this point, both the virtual and the physical cartridges are ready to back up data again. Design Considerations Automigration Use Models The following sections give examples of backup and restore use cases for automigration. Backup to Non-shared Virtual Libraries In this use case, the customer has multiple virtual libraries on the VLS device, and each virtual library is mapped to a different backup server. In other words, there is no SAN-sharing of virtual library resources. Instead, there is a dedicated, non-shared virtual library for each backup server. This is a possible scenario for SMBs who use backup applications that cannot be SAN-shared across multiple backup servers (for example, single-server backup applications). This situation could also occur with a large enterprise that has multiple different types of backup applications in the same SAN (for example, due to company acquisitions). In both cases, copying to tape via the backup application is very difficult because without SAN sharing of the virtual libraries, the customer needs a separate tape drive/library for every backup server. With automigration, the customer can use a single tape library and effectively share it across the multiple virtual libraries. See Figure 38 (page 83). Figure 38 Multiple Virtual Libraries In this use case, the physical tape library slots are split into separate slot ranges, with each slot range being assigned to a different virtual library. This allows separate backup servers to backup Design Considerations 83

  • 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
retention period passes, the virtual cartridges are deleted, at which point a physical tape is
needed for restore operations. See
“Restoring from Automigration Media” (page 85)
.
5.
Thirty days have passed. The truck returns with the physical tapes previously transported off-site
that are now to be recycled.
6.
The media life cycle starts again. The recycled tapes are loaded into the destination library
using
Load Media for Overwrite
. After scanning the tape headers, automigration automatically
creates virtual cartridges with matching headers. At this point, both the virtual and the physical
cartridges are ready to back up data again.
Design Considerations
Automigration Use Models
The following sections give examples of backup and restore use cases for automigration.
Backup to Non-shared Virtual Libraries
In this use case, the customer has multiple virtual libraries on the VLS device, and each virtual
library is mapped to a different backup server. In other words, there is no SAN-sharing of virtual
library resources. Instead, there is a dedicated, non-shared virtual library for each backup server.
This is a possible scenario for SMBs who use backup applications that cannot be SAN-shared
across multiple backup servers (for example, single-server backup applications). This situation could
also occur with a large enterprise that has multiple different types of backup applications in the
same SAN (for example, due to company acquisitions). In both cases, copying to tape via the
backup application is very difficult because without SAN sharing of the virtual libraries, the customer
needs a separate tape drive/library for every backup server. With automigration, the customer
can use a single tape library and effectively share it across the multiple virtual libraries. See
Figure 38 (page 83)
.
Figure 38 Multiple Virtual Libraries
In this use case, the physical tape library slots are split into separate slot ranges, with each slot
range being assigned to a different virtual library. This allows separate backup servers to backup
Design Considerations
83