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

Summary of Catalyst best practices, Catalyst copy models

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

Figure 33 Catalyst copy models Summary of Catalyst best practices HP StoreOnce Catalyst is a unique interface and is fundamentally different from virtual tape or NAS. It provides the backup application with full control of backup and replication (called Catalyst Copy). For this reason, best practices are dependent upon the backup application. See the separate document, HP StoreOnce Backup system Best Practices for VTL, NAS, StoreOnce Catalyst and Replication Implementations with sizing and application configuration examples for more details. Generic best practices for HP StoreOnce Catalyst implementations are: • Ensure that the media servers where Catalyst low bandwidth backup is to be deployed are sized accordingly; otherwise, the implementation will not work well. • As with other device types, the best deduplication ratios are achieved when similar data types are sent to the same device. • Best throughput is achieved with multiple streams, the actual number per device/appliance varies by model . Because Catalyst stores can be acting as a backup target and inbound replication target the maximum value applies to the two target types combined (although inbound copy jobs would not normally run at the same time as backups) • Although Catalyst copy is controlled by the backup software, the copy blackout window overrides the backup software scheduling. Check for conflicts. • The first Catalyst low bandwidth backup will take longer than subsequent low bandwidth backups because a seeding process has to take place. • If you are implementing multi-hop or one-to-many Catalyst copies, remember that these copies happen serially not in parallel. Summary of Catalyst best practices 61

  • 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
Figure 33 Catalyst copy models
Summary of Catalyst best practices
HP StoreOnce Catalyst is a unique interface and is fundamentally different from virtual tape or
NAS. It provides the backup application with full control of backup and replication (called Catalyst
Copy). For this reason, best practices are dependent upon the backup application. See the separate
document,
HP StoreOnce Backup system Best Practices for VTL, NAS, StoreOnce Catalyst and
Replication Implementations with sizing and application configuration examples
for more details.
Generic best practices for HP StoreOnce Catalyst implementations are:
•
Ensure that the media servers where Catalyst low bandwidth backup is to be deployed are
sized accordingly; otherwise, the implementation will not work well.
•
As with other device types, the best deduplication ratios are achieved when similar data types
are sent to the same device.
•
Best throughput is achieved with multiple streams, the actual number per device/appliance
varies by model . Because Catalyst stores can be acting as a backup target and inbound
replication target the maximum value applies to the two target types combined (although
inbound copy jobs would not normally run at the same time as backups)
•
Although Catalyst copy is controlled by the backup software, the copy blackout window
overrides the backup software scheduling. Check for conflicts.
•
The first Catalyst low bandwidth backup will take longer than subsequent low bandwidth
backups because a seeding process has to take place.
•
If you are implementing multi-hop or one-to-many Catalyst copies, remember that these copies
happen serially not in parallel.
Summary of Catalyst best practices
61