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

Tape Offload/Copy from StoreOnce Backup system versus Mirrored Backup from Data Source

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

Tape Offload/Copy from StoreOnce Backup system versus Mirrored Backup from Data Source A summary of the supported methods is shown below. Table 9 Tape Offload/Copy For easiest integration nl Backup application copy to tape For optimum performance nl Separate physical tape mirrored backup The backup application controls the copy from the StoreOnce appliance to the network-attached tape drive so that: This is a parallel activity. The host backs up to the StoreOnce appliance and the host backs up to tape. It has the following benefits: • It is easier to find the correct backup tape • The backup application still controls the copy location • The scheduling of copy to tape can be automated within • It has the highest performance because there are no the backup process read operations and reconstruction from the StoreOnce appliance Constraints: Constraints: • • Streaming performance will be slower because data • It requires the scheduling of specific mirrored backup must be reconstructed. policies. • This method is generally only available at the "Source" side of the backup process. Offloading to tape at the target site can only use the backup application copy to tape method. When is Tape Offload required? • Compliance reasons or company strategy dictate Weekly, Monthly, Yearly copies of data be put on tape and archived or sent to a DR site. Or a customer wants the peace of mind that he can physically "hold" his data on a removable piece of media. • In a StoreOnce Replication model it makes perfect sense for the data at the StoreOnce DR site or central site to be periodically copied to physical tape and the physical tape be stored at the StoreOnce site (avoiding offsite costs) yet still providing long term data retention. • The same applies in a StoreOnce Catalyst Copy model. However, the StoreOnce Catalyst Copy feature allows the backup application to incorporate tape offload, as well as Catalyst Store copy between StoreOnce appliances into a single backup job specification. The following examples relate to StoreOnce Replication. Catalyst device types The visibility, flexibility and integration of Catalyst stores into the backup software is one of the key advantages of HP StoreOnce Catalyst - especially because the replicated copies are already known to the backup application. 110 Tape Offload

  • 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
Tape Offload/Copy from StoreOnce Backup system versus Mirrored Backup from
Data Source
A summary of the supported methods is shown below.
Table 9 Tape Offload/Copy
For optimum performance
nl
For easiest integration
nl
Separate physical tape mirrored backup
Backup application copy to tape
This is a parallel activity. The host backs up to the
StoreOnce appliance and the host backs up to tape. It has
the following benefits:
The backup application controls the copy from the
StoreOnce appliance to the network-attached tape drive
so that:
•
The backup application still controls the copy location
•
It is easier to find the correct backup tape
•
•
The scheduling of copy to tape can be automated within
the backup process
It has the highest performance because there are no
read operations and reconstruction from the StoreOnce
appliance
Constraints:
Constraints:
•
• Streaming performance will be slower because data
must be reconstructed.
•
It requires the scheduling of specific mirrored backup
policies.
•
This method is generally only available at the “Source”
side of the backup process. Offloading to tape at the
target site can only use the backup application copy to
tape method.
When is Tape Offload required?
•
Compliance reasons or company strategy dictate Weekly, Monthly, Yearly copies of data be
put on tape and archived or sent to a DR site. Or a customer wants the peace of mind that
he can physically “hold” his data on a removable piece of media.
•
In a StoreOnce Replication model it makes perfect sense for the data at the StoreOnce DR site
or central site to be periodically copied to physical tape and the physical tape be stored at
the StoreOnce site (avoiding offsite costs) yet still providing long term data retention.
•
The same applies in a StoreOnce Catalyst Copy model. However, the StoreOnce Catalyst
Copy feature allows the backup application to incorporate tape offload, as well as Catalyst
Store copy between StoreOnce appliances into a single backup job specification. The following
examples relate to StoreOnce Replication.
Catalyst device types
The visibility, flexibility and integration of Catalyst stores into the backup software is one of the
key advantages of HP StoreOnce Catalyst - especially because the replicated copies are already
known to the backup application.
110
Tape Offload