HP D2D D2D Best Practices for VTL, NAS and Replication implementations (EH985- - Page 52

What to replicate

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

Page 52 highlights

Replication overview What to replicate D2D VTL replication allows for a subset of the cartridges within a library to be mapped for replication rather than the entire library (NAS replication does not allow this). Some retention policies may not require that all backups are replicated, for example daily incremental backups may not need to go offsite but weekly and monthly full backups do, in which case it is possible to configure replication to only replicate those cartridges that are used for the full backups. Reducing the number of cartridges that make up the replication mapping may also be useful when replicating several source libraries from different D2D devices into a single target library at a data center, for example. Limited slots in the target library can be better utilized to take only replication of full backup cartridges rather than incremental backup cartridges as well. Configuring this reduced mapping does require that the backup administrator has control over which cartridges in the source library are used for which type of backup. Generally this is done by creating media pools with the backup application then manually assigning source library cartridges into the relevant pools. For example the backup administrator may configure 3 pools: Daily Incremental, 5 cartridge slots (overwritten each week) Weekly Full, 4 cartridge slots (overwritten every 4 weeks) Monthly Full, 12 cartridge slots (overwritten yearly) Replicating only the slots that will contain full backup cartridges saves five slots on the replication target device which could be better utilized to accept replication from another source library. 52

  • 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
52
Replication overview
What to replicate
D2D VTL replication allows for a subset of the cartridges within a library to be mapped for replication rather than
the entire library (NAS replication does not allow this).
Some retention policies may not require that all backups are replicated, for example daily incremental backups
may not need to go offsite but weekly and monthly full backups do, in which case it is possible to configure
replication to only replicate those cartridges that are used for the full backups.
Reducing the number of cartridges that make up the replication mapping may also be useful when replicating
several source libraries from different D2D devices into a single target library at a data center, for example.
Limited slots in the target library can be better utilized to take only replication of full backup cartridges rather
than incremental backup cartridges as well.
Configuring this reduced mapping does require that the backup administrator has control over which cartridges
in the source library are used for which type of backup. Generally this is done by creating media pools with the
backup application then manually assigning source library cartridges into the relevant pools. For example the
backup administrator may configure 3 pools:
Daily Incremental, 5 cartridge slots (overwritten each week)
Weekly Full, 4 cartridge slots (overwritten every 4 weeks)
Monthly Full, 12 cartridge slots (overwritten yearly)
Replicating only the slots that will contain full backup cartridges saves five slots on the replication target device
which could be better utilized to accept replication from another source library.