HP StoreOnce 4430 HP StoreOnce Backup System Concepts and Configuration Guidel - Page 85

Replication models and seeding, model can easily use co-location to quickly seed the target device

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

Page 85 highlights

During the seeding process it is recommended that no other operations are taking place on the source StoreOnce Backup system, such as further backups or tape copies. It is also important to ensure that the StoreOnce Backup system has no failed disks and that RAID parity initialization is complete because these will impact performance. When seeding over fast networks (co-located StoreOnce devices) it should be expected that performance to replicate a cartridge or file is similar to the performance of the original backup. Replication models and seeding The diagrams in Replication usage models (VTL and NAS) (page 78) indicate the different replication models supported by HP StoreOnce Backup systems; the complexity of the replication models has a direct influence on which seeding process is best. For example an Active - Passive replication model can easily use co-location to quickly seed the target device, where as co-location may not be the best seeding method to use with a 50:1, many to 1 replication model. NOTE: HP StoreOnce Catalyst copy seeding follows the same processes outlined below with the added condition that for multi-hop and one to many replication scenarios the seeding process may have to occur multiple times. Table 8 Summary of seeding methods and likely usage models Technique Best for Concerns Comments Seed over the WAN link Active -- Passive and Many to 1 replication models with: nl Initial Small Volumes of Backup data nl OR nl Gradual migration of larger backup volumes/jobs to StoreOnce over time This type of seeding should be scheduled to occur over weekends where at all possible. Seeding time over WAN is calculated automatically when using the Sizing tool for StoreOnce. nl It is perfectly acceptable for customers to ask their link providers for a higher link speed just for the period where seeding is to take place. Co-location (seed over LAN) Active -- Passive, Active -Active and Many to 1 replication models with significant volumes of data (> 1TB) to seed quickly and where it would simply take too long to seed using a WAN link ( > 5 days) nl This process can only really be used as a "one off" when replication is first implemented. This process involves the transportation of complete StoreOnce units. nl This method may not be practical for large fan-in implementations e.g. 50:1 because of the time delays involved in transportation. Seeding time over LAN is calculated automatically when using the Sizing tool for StoreOnce Floating StoreOnce Many to 1 replication models with high fan in ratios where the target must be seeded with several remote sites at once. nl Using the floating StoreOnce approach means the device is ready to be used again and again for future expansion where more remote sites might be added to the configuration. Careful control over the device creation and co-location replication at the target site is required. See example below. This is really co-location using a spare StoreOnce. nl The last remote site StoreOnce can be used as the floating unit. Seeding and why it is required 85

  • 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
During the seeding process it is recommended that no other operations are taking place on the
source StoreOnce Backup system, such as further backups or tape copies. It is also important to
ensure that the StoreOnce Backup system has no failed disks and that RAID parity initialization is
complete because these will impact performance.
When seeding over fast networks (co-located StoreOnce devices) it should be expected that
performance to replicate a cartridge or file is similar to the performance of the original backup.
Replication models and seeding
The diagrams in
Replication usage models (VTL and NAS) (page 78)
indicate the different replication
models supported by HP StoreOnce Backup systems; the complexity of the replication models has
a direct influence on which seeding process is best. For example an Active – Passive replication
model can easily use co-location to quickly seed the target device, where as co-location may not
be the best seeding method to use with a 50:1, many to 1 replication model.
NOTE:
HP StoreOnce Catalyst copy seeding follows the same processes outlined below with the
added condition that for multi-hop and one to many replication scenarios the seeding process may
have to occur multiple times.
Table 8 Summary of seeding methods and likely usage models
Comments
Concerns
Best for
Technique
Seeding time over WAN is
calculated automatically
This type of seeding should
be scheduled to occur over
Active -- Passive and Many
to 1 replication models with:
nl
Seed over the WAN link
when using the Sizing tool
for StoreOnce.
nl
weekends where at all
possible.
Initial Small Volumes of
Backup data
nl
It is perfectly acceptable for
customers to ask their link
OR
nl
Gradual migration of larger
backup volumes/jobs to
StoreOnce over time
providers for a higher link
speed just for the period
where seeding is to take
place.
Seeding time over LAN is
calculated automatically
This process involves the
transportation of complete
StoreOnce units.
nl
Active -- Passive, Active --
Active and Many to 1
replication models with
significant volumes of data
Co-location (seed over LAN)
when using the Sizing tool
for StoreOnce
This method may not be
practical for large fan-in
(> 1TB) to seed quickly and
where it would simply take
implementations e.g. 50:1
too long to seed using a
WAN link ( > 5 days)
nl
because of the time delays
involved in transportation.
This process can only really
be used as a “one off” when
replication is first
implemented.
This is really co-location
using a spare StoreOnce.
nl
Careful control over the
device creation and
co-location replication at the
Many to 1 replication
models with high fan in
ratios where the target must
Floating StoreOnce
The last remote site
StoreOnce can be used as
the floating unit.
target site is required. See
example below.
be seeded with several
remote sites at once.
nl
Using the floating StoreOnce
approach means the device
is ready to be used again
and again for future
expansion where more
remote sites might be added
to the configuration.
Seeding and why it is required
85