The changes made to these settings affect the data transfer to all target Cores associated with this source Core.
Option | Description | ||
---|---|---|---|
Cache lifetime (seconds) | Specify the amount of time between each target Core status request performed by the source Core. | ||
Volume image session timeout (minutes) | Specify the amount of time the source Core spends attempting to transfer a volume image to the target Core. | ||
Maximum parallel streams | Specify the number of network connections permitted to be used by a single protected machine to replicate that machine’s data at one time. | ||
Maximum transfer speed (MB/s) | Specify the speed limit for transferring the replicated data. | ||
Maximum transfer data size (GB) | Specify the maximum size in GB for transferring blocks of replicated data. | ||
Restore Defaults |
Select this option to change all replication settings to the system defaults.
|
You can change the host and port settings for individual target Cores from the source Core.
The Replication page appears.
In the Outgoing Replication pane, the summary table includes a row for each target Core that has been configured to replicate recovery points from this source Core.
Option | Description | ||
---|---|---|---|
Host |
Enter the host for the target Core. | ||
Port |
Enter a port for the target Core to use for communication with the source Core.
|
Replication priority determines which replication jobs are sent to the Core first. Prioritization is set ordinally, on a scale of 1 to 10, where a priority of 1 is the first priority, and a priority of 10 is the last priority. When you first establish replication for any machine, its priority is set to 5. You can view and change priority at the protected machine level from the source Core.
In some cases, it is possible that some replication jobs are abandoned. For example, replication jobs can be abandoned if your environment is experiencing unusually high change rates or if your network does not have enough bandwidth. This situation is particularly likely if you set schedules which limit the hours when replication occurs in your environment. For more information about setting schedules replication, see Scheduling replication.
To ensure replication occurs for important machines first, set critical servers to a priority with a lower number (between 1 and 5). Set priority for less important machines to a higher number (between 6 and 10).
Setting replication priority to 4 for any protected machine assures its replication job is started before a machine with the default replication priority of 5. Replication jobs for machines with a priority of 3 are queued before 4, and so on. The lower the priority number, the sooner its replication jobs are sent. It is easy to remember that priority 1 is most important. Machines with a replication priority of 1 are the first machines queued for replication.
Complete the steps below to edit the settings that prioritize when a protected machine replicates.
Complete the steps in this procedure to remove one or more protected machines from replication on the source Core.
The Replication page appears.
In the Outgoing Replication pane, the summary table includes a row for each target Core that has been configured to replicate recovery points from this source Core.
For more information, see the following related topics:
© ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center