Seeding progress

Once replication starts, the initial seeding process will begin immediately. Generally, the number of completed, error-free jobs on both the primary and secondary CFA should be the same when the primary CFA has been replicated successfully to the secondary CFA. It is possible that the counts may be off due to the erred jobs, or when new jobs have been created on the primary CFA and are actively being replicated to the secondary CFA.

With that in mind, use the Jobs group of the replication status panel to judge the overall state of replication between two CFAs.

The job count on the primary CFA indicates how many jobs can be replicated.

The job count on the secondary CFA indicates how many jobs have been replicated.

Therefore, there are two main conditions to look for:

  • Job counts are equal (or nearly equal) – indicates that the primary CFA has been fully (or nearly so if counts are close) replicated to the secondary CFA

  • Job count is greater on the primary CFA – indicates that there are jobs that have not yet been replicated to the secondary CFA

To judge when seeding is complete, monitor the job counts on both CFAs. When they are (nearly) equal and the connection statuses on both CFAs are idle, click Actions > Reconcile Secondary on the primary CFA. If no additional replicable jobs result from reconciling the secondary, seeding can be considered complete.

At this point, if the byte-level replication has been licensed, enable the byte-level delta compression as described in the previous section during the primary CFA configuration, and relocate the secondary CFA to its final destination.

Replication status

There are some additional panels that provide more detailed information on the replication process. On both the primary and the secondary CFA, there is a general status panel available in Replication > Status.

This panel provides an overview of the connection status between two CFAs, and information on the data being processed and transferred as a result of the replication procedure.

Errors during setup and configuration

If an error occurs during setup and configuration of the primary or the secondary CFA, it will be displayed in either a pop-up message or within the Configuration Status area at the bottom of the options panel.

Although unlikely, some errors that you might encounter are as follows:

Error message Description
Could not contact CFA Check that the address and port are correct and that network connectivity is available. Click Test Connection to test any changes and click Apply once corrections have been made
Connection refused Check that the CFA you are connecting to has been set up correctly and the replication service has been started on the CFA
Password mismatch Check that the authentication key specified in the Key field matches exactly between two CFAs, correct the key and click Apply once the keys have been adjusted to match
Version mismatch Check that both CFAs are running the same software version, the first two values must be the same. Minor versions will be able to replicate if they are not matched, e.g. 6.7.4.10 will replicate with 6.7.5.15

If you need to restart setup and configuration of the primary and/or secondary CFA, click Clear at the bottom of the options panel. Once completed, return to the beginning of the primary/secondary configuration section and repeat the steps for configuration. If you continue to experience problems, please contact the Infrascale Support.