You can do registry replication by applying DR policy as well.


It is applicable for only PT sync. We support almost every cloud registry sync along with docker.


1. First, go to ‘DR Policies’ under the ‘BC & DR’ menu and click the ‘New’ button. A window will appear as shown below, where you can configure the DR policy according to your requirements.



2. You will also see an ‘Advanced Option’ when creating a DR policy. There, you can configure the pre/post script/YAML and set up the maximum parallel sync configuration.




3. After creating a DR policy for registry replication, you can now apply it for the registry sync. Select the created DR policy and click the ‘Apply’ button. You will see two options; choose ‘Registry Replication’ as below




4. Once you click on ‘Registry Replication,’ a window will pop up where you can see various options.
  1. Policy name: Provide the policy name as per your convenience.
  2. Order Level: By default, Order-0 will be selected unless you choose something else.
      c. Start time: There are two options: ‘Start Immediately’ and ‘Start Later.’ If you choose ‘Start Immediately,’ the sync will begin as soon as you click the Apply button. If you choose ‘Start Later,’ you will need to provide the time and date, and the sync will be triggered at the specified time. 

       d. You will then see ‘New Replication’ and ‘Existing Replication’ options.

                        a. New Replication: This will start a fresh registry sync between the source and target cloud registries you want to replicate. 

                        b. Existing Replication: This allows you to select an existing sync job related to registry sync.



New Replication:
  • In this replication, you need to select the source registry and the target image registry. For example, you might choose AWS ECR as the source and GCP GCR as the target. 
  • You just need to select the friendly name of the respective image registry and provide the Repositories and then apply. Please see below snippet for your reference.




  • You can also see that SWIFT supports multiple cloud registries, not just AWS ECR and GCP GCR along with docker.





  • Once you apply the registry sync, the DR policy will change from an ‘Idle’ state to an ‘Active’ state, and the actual sync process will begin. Please refer to the snippets below for more details.




Existing Replication:
  • In this replication, when you select Existing Replication, you will see the existing replication box. Choose the sync job you want to replicate and simply apply it. However, to do this, you need to first create a simple registry replication by going to ‘All Replication’ under the ‘Sync Administration’ tab, clicking the ‘New’ button, and selecting ‘Registry Replication’.
  • We ran simple Registry sync job first as below.




  • Then, select ‘Existing Replication’ by choosing the DR policy and clicking ‘Apply’ with the ‘Registry Replication’ options. 
  • Once you select ‘Existing Replication’, you will see the sync job in the Existing Replication pop-up box. Choose the desired sync job, click the ‘Plus’ sign, and then click ‘Apply’. Please refer to the below snippet.




  • You can choose multiple jobs in the existing replication mode.