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

Appendix D, Making use of improved D2D performance in 2.1.01 and, 1.01 software

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

Appendix D Making use of improved D2D performance in 2.1.01 and 1.1.01 software Overview HP StoreOnce D2D software released in February 2011 includes significant performance stabilization updates that reduce the disk access overhead of the deduplication process and therefore improve overall system performance. However this performance improvement only applies to D2D virtual devices (NAS Shares and VTLs) created after updating to the new software. Older devices will continue to work in the same way as they did prior to the update and if performance is acceptable then there is no need to make any changes. If improved performance is required then there are three main options for making use of the new functionality whilst retaining previously backed up data: 1. Retire existing libraries and shares, create new ones and re-direct backups to them. Once backup sessions to the retired libraries/shares are obsolete (i.e. outside of retention policies) they may be deleted. 2. Replicate data to new libraries/shares on a different D2D appliance, create new devices on the original appliance then replicate the data back. This method is termed ―Replication for Virtual Device Migration‖. 3. Replicate data to new libraries/shares on the same D2D (self replicate), delete original devices and re-target backups to the new devices once replication is complete. This method is termed ―Self Replication for Virtual Device Migration‖. This document provides detailed information on implementing options 2 and 3. Option Option 1 Retire original libraries Option 2 Replication Option 3 Self Replication Benefit Limitations No migration time required Needs enough disk space and available virtual devices to store two copies of data Makes use of a standard replication configuration Easy to implement if a ―floating‖ D2D is used and co-located on the same site The same library and share names can be re-used Requires no additional hardware or licenses Some migration time required to perform replication when backups cannot run Requires 2 D2D systems and a replication license Needs enough disk space to store two copies of data Complex if replication is already being used Some migration time required when backups cannot run 116

  • 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
116
Appendix D
Making use of improved D2D performance in 2.1.01 and
1.1.01 software
Overview
HP StoreOnce D2D software released in February 2011 includes significant performance stabilization updates
that reduce the disk access overhead of the deduplication process and therefore improve overall system
performance.
However this performance improvement only applies to D2D virtual devices (NAS Shares and VTLs) created after
updating to the new software. Older devices will continue to work in the same way as they did prior to the
update and if performance is acceptable then there is no need to make any changes.
If improved performance is required then there are three main options for making use of the new functionality
whilst retaining previously backed up data:
1.
Retire existing libraries and shares, create new ones and re-direct backups to them.
Once backup sessions to the retired libraries/shares are obsolete (i.e. outside of retention policies) they may
be deleted.
2.
Replicate data to new libraries/shares on a different D2D appliance, create new devices on the original
appliance then replicate the data back.
This method is termed ―Replication for Virtual Device Migration‖.
3.
Replicate data to new libraries/shares on the same D2D (self replicate), delete original devices and re-target
backups to the new devices once replication is complete.
This method is termed ―Self Replication for Virtual Device Migration‖.
This document provides detailed information on implementing options 2 and 3.
Option
Benefit
Limitations
Option 1
Retire original libraries
No migration time required
Needs enough disk space and
available virtual devices to store
two copies of data
Option 2
Replication
Makes use of a standard
replication configuration
Easy to implement if a ―floating‖
D2D is used and co-located on
the same site
The same library and share
names can be re-used
Some migration time required to
perform replication when
backups cannot run
Requires 2 D2D systems and a
replication license
Option 3
Self Replication
Requires no additional
hardware or licenses
Needs enough disk space to
store two copies of data
Complex if replication is already
being used
Some migration time required
when backups cannot run