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

Avoiding bad practices - vmware

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

Avoiding bad practices The worked example describes the best practices. Typical bad practices are:- Bad Practice Results Not using the Sizing tool Incorrect models chosen because of wrong throughput calculations. Replication Link sizing incorrect Insufficient backup streams configured to run in parallel Poor backup performance, poor replication performance Using single dedupe store (device) instead of separate stores (devices) for different data types. May get higher deduplication ratio but store will become full quicker, and performance will start to degrade with more complex/mature stores. Run all backups without consideration for housekeeping. Try to schedule specific backup/replication and housekeeping windows. Housekeeping will start to interfere with backup performance and replication performance. Use of Appends Impacts replication performance because clones have to be made on the target. Where possible use ―overwrites‖ on cartridges. Using backup methods that use heavy write-in-place functionality - such as, Drag & drop, Granular Recovery Technology, VMWare changed block tracking->create virtual full. Recovery times will be increased because the deduplication engine must perform many write-in-place functions, which slows down restore times. NAS devices only. Daily direct tape offload from D2D with high volumes of data Unable to get all the data onto physical tape in a reasonable time. Use direct write to physical tape where possible. 107

  • 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
107
Avoiding bad practices
The worked example describes the best practices. Typical bad practices are:-
Bad Practice
Results
Not using the Sizing tool
Incorrect models chosen because of wrong throughput
calculations.
Replication Link sizing incorrect
Insufficient backup streams configured to run in parallel
Poor backup performance, poor replication
performance
Using single dedupe store (device) instead of separate
stores (devices) for different data types.
May get higher deduplication ratio but store will
become full quicker, and performance will start to
degrade with more complex/mature stores.
Run all backups without consideration for
housekeeping. Try to schedule specific
backup/replication and housekeeping windows.
Housekeeping will start to interfere with backup
performance and replication performance.
Use of Appends
Impacts replication performance because clones have
to be made on the target. Where possible use
―overwrites‖ on cartridges.
Using backup methods that use heavy write-in-place
functionality
–
such as, Drag & drop, Granular
Recovery Technology, VMWare changed block
tracking->create virtual full.
Recovery times will be increased because the
deduplication engine must perform many write-in-place
functions, which slows down restore times. NAS
devices only.
Daily direct tape offload from D2D with high volumes
of data
Unable to get all the data onto physical tape in a
reasonable time. Use direct write to physical tape
where possible.