Quest Engineering DL4300, User Manual

Page: 286 / 540

DL4300 Appliance
About retention policies for replication
286
This factor is relevant if the bandwidth between the source and target Cores is insufficient for the amount and size of the
recovery points being replicated.
The maximum change rate for WAN connection types is shown in the following table, with examples of the
necessary bandwidth per gigabyte for a reasonable change rate.
Table 127. Examples of bandwidth per gigabyte
Broadband Bandwidth Max Change Rate
DSL 768 Kbps and up 330MB per hour
Cable 1 Mbps and up 429MB per hour
T1 1.5 Mbps and up 644MB per hour
Fiber 20 Mbps and up 8.38GB per hour
NOTE: For optimum results, adhere to the recommendations listed in the table preceding.
If a link fails during data transfer, replication resumes from the previous failure point of the transfer (once link
functionality is restored).
Depending on your network configuration, replication can be a time-consuming process. Ensure that you account
for enough bandwidth to accommodate replication, other Rapid Recovery transfers such as backups, and any
other critical applications you must run.
If you experience issues successfully transferring data over the network, especially for certain protected or
replicated machines, considering adjusting the rate of data transfer for those machines. For more information,
see About modifying transfer settings and Throttling transfer speed .
Parent topic
About replication and encrypted recovery points
While the seed drive does not contain backups of the source Core registry and certificates, the seed drive does
contain encryption keys from the source Core if the recovery points being replicated from source to target are
encrypted. The replicated recovery points remain encrypted after they are transmitted to the target Core. The
owners or administrators of the target Core need the passphrase to recover the encrypted data.
Parent topic
About retention policies for replication
Retention policies on the source and target Cores are not synchronized. Rollup and on-demand deletion perform
independently on each Core on initial action, as well as when running nightly jobs.
For more information on retention policies, see
Managing retention policies .
Parent topic