Dell PowerVault DL4000 Dell PowerVault DL4000 Backup To Disk Appliance - Power - Page 61

Roadmap For Performing Replication, Configuring Replication

Get Dell PowerVault DL4000 PDF manuals and user guides View all Dell PowerVault DL4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 61 highlights

NOTE: Bandwidth specified by the ISP is the total available bandwidth. The outgoing bandwidth is shared by all devices on the network. Make sure that there is enough free bandwidth for replication to accommodate the change rate. Number of Agents It is important to consider the number of agents protected per source core and how many you plan to replicate to the target. AppAssure 5 lets you perform replication on a per protected server basis, so you can choose to replicate certain servers. If all protected servers must be replicated, this drastically affects the change rate, particularly if the bandwidth between the source and target cores is insufficient for the amount and size of the recovery points being replicated. Depending on your network configuration, replication can be a time-consuming process. The following table shows examples of the necessary bandwidth per Gigabyte for a reasonable change rate NOTE: For optimum results, adhere to the recommendations listed in the following table. Table 1. Maximum Change Rate for WAN Connection Types Broadband DSL Cable T1 Bandwidth 768 Kbps and up 1 Mbps and up 1.5 Mbps and up Max Change Rate 330 MB per hour 429 MB per hour 644 MB per hour Fiber 20 Mbps and up 838 GB per hour If a link fails during data transfer, replication resumes from the previous failure point of the transfer after link functionality is restored. Roadmap For Performing Replication To replicate data using AppAssure 5, you must configure the source and target cores for replication. After you configure replication, you can then replicate agent data, monitor and manage replication, and perform recovery. Performing replication in AppAssure 5 involves performing the following operations: • Configure replication on the source and target machines. • Replicate a new agent attached to the source core. • Replicate an existing agent. • Set replication priority for an agent. • Monitor replication as needed. For more information on monitoring replication, see Monitoring Replication. • Manage replication settings as needed. • Recover replicated data in the event of disaster or data loss. Configuring Replication AppAssure 5 provides two options for configuring replication, which are described in the following procedures: • Configuring Replication for a Self-Managed Core • Configuring Replication for a Core Managed by a Third Party 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
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
NOTE:
Bandwidth specified by the ISP is the total available bandwidth. The outgoing
bandwidth is shared by all devices on the network. Make sure that there is enough free
bandwidth for replication to accommodate the change rate.
Number of
Agents
It is important to consider the number of agents protected per source core and how many you
plan to replicate to the target. AppAssure 5 lets you perform replication on a per protected
server basis, so you can choose to replicate certain servers. If all protected servers must be
replicated, this drastically affects the change rate, particularly if the bandwidth between the
source and target cores is insufficient for the amount and size of the recovery points being
replicated.
Depending on your network configuration, replication can be a time-consuming process.
The following table shows examples of the necessary bandwidth per Gigabyte for a reasonable change rate
NOTE:
For optimum results, adhere to the recommendations listed in the following table.
Table 1. Maximum Change Rate for WAN Connection Types
Broadband
Bandwidth
Max Change Rate
DSL
768 Kbps and up
330 MB per hour
Cable
1 Mbps and up
429 MB per hour
T1
1.5 Mbps and up
644 MB per hour
Fiber
20 Mbps and up
838 GB per hour
If a link fails during data transfer, replication resumes from the previous failure point of the transfer after link
functionality is restored.
Roadmap For Performing Replication
To replicate data using AppAssure 5, you must configure the source and target cores for replication. After you configure
replication, you can then replicate agent data, monitor and manage replication, and perform recovery.
Performing replication in AppAssure 5 involves performing the following operations:
•
Configure replication on the source and target machines.
•
Replicate a new agent attached to the source core.
•
Replicate an existing agent.
•
Set replication priority for an agent.
•
Monitor replication as needed. For more information on monitoring replication, see
Monitoring Replication
.
•
Manage replication settings as needed.
•
Recover replicated data in the event of disaster or data loss.
Configuring Replication
AppAssure 5 provides two options for configuring replication, which are described in the following procedures:
•
Configuring Replication for a Self-Managed Core
•
Configuring Replication for a Core Managed by a Third Party
61