To migrate applications, there are three types of sync modes you can use:
1. Passthrough sync:-This is a simple lift and shift operation. Your application is directly copied to the target environment without storing any data on the SWIFT server.
2. Stage1 sync: - Use this when you want to create a backup copy of your application on the SWIFT server. This allows you to re-hydrate (restore) and deploy the application to the target environment at any time in the future.
3. Stage2 sync:- Use this when you are ready to fully move your application to the target environment. This sync uses the backup from Stage 1 (if available) or performs a fresh sync to complete the migration.
Pre-requisite:
1. Discover the source cluster.
2. Create the Storage pool --> Pls refer below KB link:
https://rackware.freshdesk.com/a/solutions/articles/5000889816?lang=en
Topics Covered
Stage1 Replication
1.Once you add the storage pool, you can start the Stage 1 replication. For this, you only need to select the source cluster, and the other side will be your storage pool. To do this, go to the ‘All Replications’ section under the Sync Administration tab, click the ‘New’ button, then choose ‘Application Replication’ and select ‘Stage-1 Replication’. Please refer below screenshot.
2. Now yo just select your source cluster and choose storage pool and put the image group name. As you can see below screenshot we have selected the IBM cluster at source and at target side there will be a storage pool that we have created in SWIFT.
5. Now you can click on 'Add' button to start the stage1- sync.
6. Once added, it will indicate that Stage 1 has started. As you can see in the snippet below, the Source will be your primary cluster, and the Target will be your image group name.
# Now stage has been completed as you can see below snippet.
7. Now, you can verify whether your application has been successfully backed up in the Image Group.
Go to Business Continuity and DR, select Image Group, and choose the image group name you provided during the sync process. You will see the images of your application listed there. Please refer to the snippet below.
# expand that image group and see Image section.
Stage2 Replication
Pre-requisite:
1. Stage1 sync should have completed which will create a image group in SWIFT. Please refer below KB.
https://rackware.freshdesk.com/a/solutions/articles/5000897128/edit?lang=en
1. Once the stage1 is completed, then IG will be created, go to the > All replication under Sync Administration > click on New > Application replication > Stage2 Replication.
2. Once clicked on Stage2 replication, it will prompted New replication Replication for stage2 . Please see below screenshot
| Field Name | Field Description |
| Platform type (Source side) | Select the platform where your cluster is running |
| Storage Pool (Source side) | It will be listed which you have added a storage pool How o create SP by using anchor tag (KB: https://rackware.freshdesk.com/a/solutions/articles/5000889816?lang=en) |
| Image group (Source side) | Image-Group in SWIFT represents a logical group of captured Kubernetes or OpenShift volumes. In the above screenshot, the IG was already created during stage1 sync. |
| Application (Source side) | ALL -> Everything in your IG, all objects will be replicated. Selective --> IF you want to do only selected object then you can use this option. Include K8S native objects --> Include native k8s objects' ensures that Kubernetes objects like Services, ConfigMaps, Secrets, and Ingress are migrated along with the application |
| Sync webhook (Source side) | ALL --> IF you select this, then all webhook that are present in the source, it will migrated to target. Native Webhook --> Includes cluster-level native Kubernetes webhooks during migration. Dont delete the taints --> By default taints going to be deleted, if you dont want this, then you can select this option |
| Cluster Name | Select the cluster that is for target. |
| Namespace | You can either create a new namespace or select the existing from dropdown. So, your app will be migrated to specific namespace. |
| StorageClass | SWIFT will give you choice to choose the storageclass as per your k8s cluster |
| Zone | Specifies the availability zone where the target cluster nodes are deployed for migration. |
| TRAIPOD Config | This is an optional input. They can be configured for each sync, and the values input for the sync will override the defaults set for the cluster. For more info you can look TRAIPOD KB article. To more know about Traipod Config section, Please follow below KB Article. https://rackware.freshdesk.com/a/solutions/articles/5000890139?lang=en |
| Add | Once you click on 'Add' button, then migration will be started. |
3. After Stage 2 sync completes, verify by accessing the source application to ensure it is functioning correctly on the target cluster.
4. Once Stage 2 sync is completed, the application should be accessible on the target cluster. (Refer to the screenshot below showing WordPress accessed successfully on the target side.)
#What Next:
You can Set up a DR Policy for this sync. Please refer below KB.
<want to make KB>