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

Replication of Incremental Backups, The Replication Sequence

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

backup tape on the source device (not the tape currently replicating) runs in parallel with the replication. 5. Once the backup has successfully replicated, the backup is reassembled using the transferred deltas and the older existing duplicate components on the target device. 6. Space reclamation of the previous backups (not the tape just replicated) on the target device begins. The target runs its own space reclamation to eliminate the duplicate data on the older backups on the target. Figure 45 The Replication Sequence 1. A backup is performed (and its metadata is stored in the database). 2. The new backup is compared to the previous versions and the unique data in the new backup is identified. 3. The source device performs space reclamation on the previous backups to eliminate the duplicate data, and concurrently the replication data (containing just the unique data and metadata) is transferred to the target device. 4. The replication data is reassembled into an intact backup combining the new unique data with the duplicate data already replicated from previous backups. 5. The target device performs space reclamation on the previous backups to eliminate the duplicate data. HP VLS backup systems with HP Accelerated deduplication allow only unique pieces of data to replicate across the WAN link. This efficiency in understanding precisely which data needs to replicate may result in bandwidth savings in excess of 90% compared to transmitting the full contents of a cartridge at the source site. In addition to the unique data transmitted, there is some overhead of data instructions that also needs to pass across the replication link. This is known as control data, and is estimated to be about 1% of the full backup size. The control data is optionally compressed before it is transmitted. There are also some variances in the amount of data replicated from database backups and file system backups because of the different deduplication algorithms used and differences with incremental backups. Replication of Incremental Backups Most database incremental backups consist of block level changes in the database, while most file level incremental backups consist of changes at a file level. Depending on your recovery point objective (RPO) requirements at the disaster recovery site, you may choose whether or not to replicate incrementals. With the current capacity-optimized comparison algorithms in the HP VLS, the amount of data replicated for file system incrementals is almost the entire size of the incremental How it Works 99

  • 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
backup tape on the source device (not the tape currently replicating) runs in parallel with the
replication.
5.
Once the backup has successfully replicated, the backup is reassembled using the transferred
deltas and the older existing duplicate components on the target device.
6.
Space reclamation of the previous backups (not the tape just replicated) on the target device
begins. The target runs its own space reclamation to eliminate the duplicate data on the older
backups on the target.
Figure 45 The Replication Sequence
1.
A backup is performed (and its metadata is stored in the database).
2.
The new backup is compared to the previous versions and the unique data in the new backup
is identified.
3.
The source device performs space reclamation on the previous backups to eliminate the
duplicate data, and concurrently the replication data (containing just the unique data and
metadata) is transferred to the target device.
4.
The replication data is reassembled into an intact backup combining the new unique data
with the duplicate data already replicated from previous backups.
5.
The target device performs space reclamation on the previous backups to eliminate the duplicate
data.
HP VLS backup systems with HP Accelerated deduplication allow only unique pieces of data to
replicate across the WAN link. This efficiency in understanding precisely which data needs to
replicate may result in bandwidth savings in excess of 90% compared to transmitting the full
contents of a cartridge at the source site. In addition to the unique data transmitted, there is some
overhead of data instructions that also needs to pass across the replication link. This is known as
control data, and is estimated to be about 1% of the full backup size. The control data is optionally
compressed before it is transmitted. There are also some variances in the amount of data replicated
from database backups and file system backups because of the different deduplication algorithms
used and differences with incremental backups.
Replication of Incremental Backups
Most database incremental backups consist of block level changes in the database, while most
file level incremental backups consist of changes at a file level. Depending on your recovery point
objective (RPO) requirements at the disaster recovery site, you may choose whether or not to
replicate incrementals. With the current capacity-optimized comparison algorithms in the HP VLS,
the amount of data replicated for file system incrementals is almost the entire size of the incremental
How it Works
99