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

Replication Preparation, Migrating your Existing Backup Data

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

• Install deduplication licenses and wait for the "Completed deduplication installation" and "Initialization for node0 complete" notifications. • If deduplication failed to initialize due to lack of free space for the deduplication metadata database (1 TB for VLS6000-series, 2 TB for VLS9000-series and VLS12000), you must free up that disk space by deleting cartridges. In firmware 3.4.0 and higher, you can delete any cartridges (deduplicated or non-deduplicated) via the GUI or CLI. After deduplication is successfully enabled, ensure virtual cartridges are created correctly for optimum deduplication performance and for correct backup capacity: • If you are creating new cartridges for deduplication, then sizing should be 50-100 GB up to 300 GB maximum (see "Media Management " (page 95)). If you are sizing cartridges for a VLS that has existing backup data created when the VLS was running 2.x firmware, the Storage Pool created by the 2.x firmware has lower cartridge limits. You should size the virtual cartridges to at least 100 GB or larger. • If you already have existing non-deduplicated cartridges that exceed these cartridge sizing requirements, you must resize these existing cartridges to match the deduplication requirements. This will not affect any existing backup data until the next backup is performed to the resized cartridge. • Because deduplication automatically enables cartridge oversubscription, you can create more virtual cartridge capacity than the available physical disk capacity (the deduplication will reduce the amount of physical disk used on the virtual cartridge backup data by eliminating duplicate data). Only create the amount of virtual cartridge capacity that you need for your backup retention policy (see "Tape Oversubscription" (page 16)). This means you need to ensure you create enough virtual library slots to contain the oversubscribed set of virtual cartridges. For existing virtual libraries that do not have enough slots, you must modify the existing virtual library to increase the number of slots (either delete/recreate the virtual library with more slots or contact your HP support representative for assistance in expanding the existing virtual library). • Remember to update the backup application library configuration to detect any new library slots and new virtual cartridges. • Use shared media pools (share the media across backup policies/names and across media servers). See Media Management . A complete backup is necessary to initialize Accelerated deduplication, but data in subsequent sessions can then be deduplicated. See the HP Virtual Library System user guide for your system for complete setup procedures. See Migrating your Existing Backup Data for details on how to handle existing non-deduplicated backup data. After deduplication has been running for multiple full backup cycles, you can check the deduplication reports to see how effectively it is running; see "Configuration and Reporting" (page 93). Deduplication configuration options are available through Command View VLS to allow optimization of file server deduplication (see "Optimizing File Server Deduplication" (page 95)) or handling backup application-specific data type configurations. Replication Preparation Prior to configuring replication, ensure that deduplication is licensed and enabled on both the source and target devices and enter the replication licenses on the target device. Create the required virtual libraries on the source and target devices. You also need to create the required virtual libraries and virtual tape drives on source and target VLS devices. With VLS, the virtual libraries/drives on both source and target device are created as normal (the replication configuration is overlaid onto these standard virtual libraries by creating replication targets, LAN/WAN destination libraries, echo copy pools, etc.). If your source device's backup application has media agents in the target site then when mapping the replication library to the front-end Fibre Channel ports in the VLS, remember to hide the target virtual library from the Device Configuration Preparation 133

  • 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
•
Install deduplication licenses and wait for the “Completed deduplication installation” and
“Initialization for node0 complete” notifications.
•
If deduplication failed to initialize due to lack of free space for the deduplication metadata
database (1 TB for VLS6000–series, 2 TB for VLS9000–series and VLS12000), you must free
up that disk space by deleting cartridges. In firmware 3.4.0 and higher, you can delete any
cartridges (deduplicated or non-deduplicated) via the GUI or CLI.
After deduplication is successfully enabled, ensure virtual cartridges are created correctly for
optimum deduplication performance and for correct backup capacity:
•
If you are creating new cartridges for deduplication, then sizing should be 50-100 GB up to
300 GB maximum (see
“Media Management ” (page 95)
). If you are sizing cartridges for a
VLS that has existing backup data created when the VLS was running 2.x firmware, the Storage
Pool created by the 2.x firmware has lower cartridge limits. You should size the virtual
cartridges to at least 100 GB or larger.
•
If you already have existing non-deduplicated cartridges that exceed these cartridge sizing
requirements, you must resize these existing cartridges to match the deduplication requirements.
This will not affect any existing backup data until the next backup is performed to the resized
cartridge.
•
Because deduplication automatically enables cartridge oversubscription, you can create more
virtual cartridge capacity than the available physical disk capacity (the deduplication will
reduce the amount of physical disk used on the virtual cartridge backup data by eliminating
duplicate data). Only create the amount of virtual cartridge capacity that you need for your
backup retention policy (see
“Tape Oversubscription” (page 16)
). This means you need to
ensure you create enough virtual library slots to contain the oversubscribed set of virtual
cartridges. For existing virtual libraries that do not have enough slots, you must modify the
existing virtual library to increase the number of slots (either delete/recreate the virtual library
with more slots or contact your HP support representative for assistance in expanding the
existing virtual library).
•
Remember to update the backup application library configuration to detect any new library
slots and new virtual cartridges.
•
Use shared media pools (share the media across backup policies/names and across media
servers). See
Media Management
.
A complete backup is necessary to initialize Accelerated deduplication, but data in subsequent
sessions can then be deduplicated. See the HP Virtual Library System user guide for your system
for complete setup procedures. See
Migrating your Existing Backup Data
for details on how to
handle existing non-deduplicated backup data. After deduplication has been running for multiple
full backup cycles, you can check the deduplication reports to see how effectively it is running; see
“Configuration and Reporting” (page 93)
. Deduplication configuration options are available
through Command View VLS to allow optimization of file server deduplication (see
“Optimizing
File Server Deduplication” (page 95)
) or handling backup application-specific data type
configurations.
Replication Preparation
Prior to configuring replication, ensure that deduplication is licensed and enabled on both the
source and target devices and enter the replication licenses on the target device. Create the required
virtual libraries on the source and target devices.
You also need to create the required virtual libraries and virtual tape drives on source and target
VLS devices. With VLS, the virtual libraries/drives on both source and target device are created
as normal (the replication configuration is overlaid onto these standard virtual libraries by creating
replication targets, LAN/WAN destination libraries, echo copy pools, etc.). If your source device’s
backup application has media agents in the target site then when mapping the replication library
to the front-end Fibre Channel ports in the VLS, remember to hide the target virtual library from the
Device Configuration Preparation
133