You can configure the DR policy for Passthrough (PT) and stage syncs in SWIFT.


Setting up a Disaster Recovery (DR) policy is crucial for ensuring business continuity in the event of a disaster.


This will help you to reduce downtime, ensuring that your systems and applications can be quickly restored after a disaster in SWIFT.


  1. You can configure the DR policy in two ways for the syncs in SWIFT.
    1. With existing application replication
    2. With New application replication.


With Existing application replication.

  • You need to go to the SWIFT dashboard and select ‘All Replication’ and click on ‘New’ button and select 'Application Replication’ then choose the any sync mode you want. Please find snippet below.



  • You now need to choose the replication mode, select the platform type (K8S/OpenShift), choose the cluster name from the drop-down, and specify the namespace on both the source and target sides. Please provide the remaining appropriate inputs for this PT sync. Please refer to the ‘Sync between container platform’ KB article for the more detailed information.



  • If you performed a PT sync here, you could create a DR policy for it and select the ‘Existing Application Replication’ option in the DR policy. Please see below snippets.




  • Now you need to create a DR policy, then select that policy and click ‘Apply’. You will then see the replication listed under ‘Existing Replication’. Choose the replication and click ‘Apply’.



  • After that, you will see a window with the option ‘Existing Replication.’ Select the replication from the dropdown menu, which will list the currently completed sync. Optionally you can select the ‘Fallback configuration’ if you want. Then, click the ‘Apply’ button. Please check below snippet.



  • After applying the DR policy, it will run according to the timeline you specified during the DR policy creation.



With New Application Replication.

  • You need to go ‘DR Policies’ under Business Continuity & DR and select the created DR policy and click on ‘apply’ button to start Replication Application. Please see below snippet.



  • After clicking on ‘Application Replication,’ a new replication window will appear where you must enter the cluster and namespace details by selecting ‘New Replication.’ Additionally, there is an option to configure the start time if you want the replication to run at a specific time. This can be set in the start time section.
  • You can then see the ‘Exclude Application’ option in the snippet below. If you want to exclude any services, deployments, etc., on the source side, you can use this option to have SWIFT exclude the selected objects.
  • Next, select the TRAIPOD option according to your configuration. For more information about this option, please refer to the ‘Sync between Container Platform’ KB article.
  • Then click on ‘Apply’ button to start the new sync with DR policy.






  •   Once you apply the replication, then DR Policy will be in a Active state and start the replication.


  • Sync has been completed with the selected DR policy. Please check below snippet. It will now sync every 25 minutes, as mentioned in the snippet above.



With Existing application replication with DR policy for Stage1 sync.


  • You need to go to the SWIFT dashboard and select ‘All Replication’ and click on ‘New’ button and select 'Application Replication’ then choose the stage1 sync mode and do one replication. Please find snippet below.
  • In that step, you need to provide the source cluster information along with the namespace, select the ‘Storage Pool,’ and enter the ‘Image Group’ name on the target side.
  • In Stage 1 replication, the data will be replicated from the source to the SWIFT server storage pool.
  • For storage pool you need to create a storage pool in ‘Storage pool’ under ‘Business Continuity & DR’ section in SWIFT. Please refer to the ‘Storage pool administration’ KB article for the same.



  • Completed the Stage1 replication.




  • Here source is K8S cluster and Target is Image group. The data has been transferred to SWIFT storage.


Now you can do a replication with created DR Policy for existing replication.


  1. Go to the DR Policies, select the DR policy which was created and apply with ‘Application Replication’.



  1. Choose the ‘Existing Replication’ to start the replication with existing replication as below. It’s the same as PT sync.


  1. Once you click on ‘Apply,’ the DR policy will be triggered and it will in a ‘Active’ state, and Stage 1 replication will begin



  1. In the above snippet you can see policy state, sync schedule and type.



  1. It started the Stage 1 sync with the DR policy as you can see in above snippet, which is set to run every 30 minutes according to the policy's frequency.



With New application replication with DR policy for Stage1 sync.


  1. You need to go ‘DR Policies’ under Business Continuity & DR and select the created DR policy and click on ‘apply’ button to start Replication Application. Please see below snippet. It is the same as PT sync as above.


  1. You need to choose ‘New Replication’ and put the cluster details at source side. And choose the storage pool and put the image group name on the target side.
  2. Order-level will be ‘Level 0’ for the first time by-default.
  3. The rest of the thing remains same as PT sync.






  1. In the below snippet, you can configure the TRAIPOD option as per your requirement.




  1. Once apply, then DR policy will be triggered to ‘Active’ state and new stage-1 replication will be begin. Please see below snippets.






With Existing application replication with DR policy for Stage2 sync.



  1. You need to go to the SWIFT dashboard and select ‘All Replication’ and click on ‘New’ button and select 'Application Replication’ then choose the stage2 sync mode and do stage-2 replication.
  2. In Stage-2 replication, you need to choose Platform type Kubernetes/OpenShift, select the storage pool and choose the Image group from the dropdown which has already been created at stage-1. And select the Cluster and namespace at target side.
  3. It will also display all the ‘Storage Classes’ on the target side in SWIFT. You just need to select one of these storage classes. The target volumes will be created using the selected storage class.
  4. Basically, in Stag-2 replication, the data will be transferred from SWIFT to Target.





  1. This is the same configuration as PT and Stage-1 sync, so you can refer that.
  2. As you can see in the snippet below, Stage 2 sync has been completed. You can review the source, target, and sync type.





Now you can do a replication with created DR Policy for existing replication.


  1. Go to the DR Policies, select the DR policy which was created and apply with ‘Application Replication’
  2. In the DR policy below, you can see the type of sync and the ‘sync schedule’. We have configured the DR policy so that once Stage 1 is completed, Stage 2 will start immediately. You can choose any option when creating a DR policy. For more information, please refer to the DR policy creation KB article.



  1. Once you click on the ‘Application Replication’, the windows will appear that you need to choose the ‘New Replication’ at source and target as well. Also there is one more option for existing Replication. You can select that also if the sync has already done with respect to the same sync type.
  2. Then you must choose the Platform type K8S/OpenShift as per your environment.
  3. Then select the cluster, namespace at both sides. Additionally, you need to select the Storage class and put image group if you want, or you can choose existing also.
  4. Now, if you want to exclude some objects from the source, you can do so using the ‘Exclude Application’ options for both Stage 1 and Stage 2. When you click on Stage 2, you will see an option called ‘Inherit Exclude Objects from Stage 1.’ This option allows you to inherit the list of objects to be excluded from Stage 1 sync for Stage 2 sync.
  5. In the TRAIPOD section, you can configure this as per your environment. Or refer this TRAIPOD KB article for more information.
  6. Also, if you need any customization with ‘Advanced Options,’ you can configure these during Stage 1 and Stage 2 replication. For details, please refer to the ‘Advanced Options’ KB article.
  7. Now click on the Apply button to start the replication.




  1. If you look at the snippet above, you will see that Stage 1 and Stage 2 have been completed with the Stage 1+2 DR Policy.
  2. You can review the end time of Stage 1 and the start time of Stage 2 to confirm that the sync began immediately after Stage 1 finished, as configured in the DR policy.