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

Media Server Considerations, Writing to Tape in a LAN/SAN Hybrid 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 32 highlights

After installing the VLS and configuring/redirecting the backups to the device, you will create tape copy/clone jobs in the backup applications to perform the migration to physical tape. Most backup applications include several copy/clone options, ranging from creating the tape copy at the same time as the backup (mirroring), scheduling a copy of all backup media to run when all the backups are expected to finish (scheduled copy), or creating the tape copy immediately after each backup completes (triggered copy). Scheduled copy is the recommended option so the copy jobs run after the backup window; otherwise, having copies and backups running at the same time results in significant performance loss. When copying virtual cartridges to physical cartridges through the backup application, the data is read from the virtual library into one of the available media servers which then writes the data back out again to the physical library. The physical tape library is independent of the virtual tape library and is entirely under the control of the backup application. This means that the virtual library type and virtual drive type and virtual cartridge size do not need to match the physical library in any way; the backup applications all perform "object copy" where they effectively backup the backup and therefore append and span copy jobs onto the physical tapes just like they would with backup jobs. Figure 13 Writing to Tape in a LAN/SAN Hybrid Environment Media Server Considerations To support the background copy of backup data from the VLS to a tape library, use one or more of your existing backup media servers (running the backup application media agents) to copy the data directly from the device media onto the tape media with data passing over the SAN from the VLS to the device server and then back again to the tape library. If you are running the copies 32 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
After installing the VLS and configuring/redirecting the backups to the device, you will create tape
copy/clone jobs in the backup applications to perform the migration to physical tape. Most backup
applications include several copy/clone options, ranging from creating the tape copy at the same
time as the backup (mirroring), scheduling a copy of all backup media to run when all the backups
are expected to finish (scheduled copy), or creating the tape copy immediately after each backup
completes (triggered copy). Scheduled copy is the recommended option so the copy jobs run after
the backup window; otherwise, having copies and backups running at the same time results in
significant performance loss.
When copying virtual cartridges to physical cartridges through the backup application, the data
is read from the virtual library into one of the available media servers which then writes the data
back out again to the physical library. The physical tape library is independent of the virtual tape
library and is entirely under the control of the backup application. This means that the virtual library
type and virtual drive type and virtual cartridge size do not need to match the physical library in
any way; the backup applications all perform “object copy” where they effectively backup the
backup and therefore append and span copy jobs onto the physical tapes just like they would
with backup jobs.
Figure 13 Writing to Tape in a LAN/SAN Hybrid Environment
Media Server Considerations
To support the background copy of backup data from the VLS to a tape library, use one or more
of your existing backup media servers (running the backup application media agents) to copy the
data directly from the device media onto the tape media with data passing over the SAN from the
VLS to the device server and then back again to the tape library. If you are running the copies
32
Backup Solution Design Considerations