RackWare Inc.

Before executing a sync operation on SWIFT, ensure all prerequisites are met to prevent failures or inconsistencies. This KB outlines the necessary configurations, network requirements, and permissions needed before initiating the sync process

Prerequisites to add cluster: 

• Ensure that the source and destination environments are running and accessible.
• All cloud credentials should be working to add the clusters in SWIFT.
• 443 and 22 port should be open in cloud.
• Provide all the required credentials in SWIFT while adding clusters.

Prerequisites to add image registry: 

• We must add the image registry as SWIFT support almost all cloud registries.
• Why we need this as during sync SWIFT pushes the transient pod on source and target clusters, so we can select the registry there.
• Once it has selected, it will be pushed to the transient pod to image registry and same will be used during sync.

Prerequisites to sync: 

• We should whitelist the port 32000-32767 from firewall.
• Users will need to access SWIFT from clusters and vice versa.

For Passthrough sync:

• In this sync mode you can select the source and target cluster.
• It will not store any data on the SWIFT so, it will not create storage pool on SWIFT.
• It’s purely lift and shift migration.

For Stage-1 sync:

• In this stage-1 sync, we will have to add the storage pool, in that it will create backup the application on SWIFT in the storage pool.
• We must attach the disk on SWIFT server, and size would be as per the application.
• Then we can add the storage pool in SWIFT.
• Storage pool will have compression property and backup will remain secure.
• Advantage of this sync that it’s not mandatory have a target cluster always  up and running.

For Stage-2 sync: