Checking the Status of Replication Jobs
  • 11 Nov 2022
  • PDF

Checking the Status of Replication Jobs

  • PDF


WCSM provides several ways to monitor your replication job status and address any failures.

Dashboard Recent Transfers

  1. Click the Dashboard tab.
  2. At the bottom of the Dashboard, review the Recent Transfers section. It displays the last 20 replication job cycles that were executed. For example:

Replication Status

WCSM never performs any changes to the source bucket. However, Sync Delete (described below) provides the option to synchronize deletions happening in the source bucket to the replica dataset in the destination bucket.
  1. Click the Replication tab.
  2. At the bottom of the Replication page, review the Scheduled Replication Jobs section and note the information described below.

CreatedWCSM indicates the date and time the replication job was created.
Last ExecutedWCSM indicates the date and time the replication job was last executed.
Sync DeleteWCSM gives this option to synchronize deletions happening in the source bucket to the replica dataset in the destination bucket. If you set this option, any deletions that happen in the source bucket (via your S3 application or by you through the Wasabi Console) will propagate to the destination bucket. If you do not select this option, WCSM does not perform any deletions.
StatusReplication job cycles will have one of these states:

Completed—The latest replication job cycle was completed.

Processing—WCSM is processing the bucket log files from the source bucket.

Transferring—WCSM is now transferring data to the replica bucket.

NoChange—WCSM completed processing the bucket log files and there are no changes. Buckets are in sync.

Faulted—The replication job is blocked due to an error. For more information, move your cursor near the blue information bubble.

ActiveYou can toggle a job to be inactive or active using this setting.
DeleteYou can delete a replication job by clicking on this option.

Replication History

  1. Click the Replication tab.
  2. At the bottom of the Replication page, click the Replication History button.

This will display the Transfer History page which lists all available stats on historical replication job cycles.

Retry Failed Files / Download Failed Files Report

As you can see from the screenshot above, you can re-attempt to replicate any failed files that occurred during a replication job cycle by simply clicking Retry Failed Files. But first, you may want to review the Failed files report by clicking Download Failed Files. This report downloads a spreadsheet, which lists the Object keys, Size, and Error encountered when attempting to replicate. This can be helpful to determine why some objects may not have been replicated.



Was this article helpful?