• SWIFT product which offers replication, backup and DR of the container platform.
  • Move and Protect your Kubernetes/OpenShift deployments with RackWare SWIFT. 
  • Migrate applications from any environment into the Cloud, including Cloud-to-Cloud 
  • Protect critical workloads with SWIFT’s Converged Disaster Recovery and Backup solution.
  • We don't replicate the actual nodes as we don't have access it, but we actually migrate the application and data.


Easy to setup : 

  1. SWIFT can be provisioned either from Cloud Marketplace as we support OCI, Azure, GCP and IBM.
  2. Also we can provide you SWIFT build on FTP, that we will create a FTP user for you and will share the credentials and steps to download the build from FTP.
  3. Once you install the SWIFT, then you can access the dashboard with SWIFT IP. During initial setup it will ask you to set the password. https://swift_ip/swift/dashboard/  
  4. Only you need to open the 22 and 443 port from cloud or where the SWIFT is located.
  5. Once you set up password for admin user, then you can access the dashboard with that same credentials.


How SWIFT WORKS :

  1. We do support K8S and OpenShift and Rancher.
  2. It is cross platform cloud version replication tool.
  3. SWIFT Product has lot of transformation when you run on OpenShift and try to replicate to other cloud.
  4. The SWIFT tool which will replicate all applications, so it does replicate three things, First is your K8S/OpenShift application metadata like all the objects, etc. then Second is your data persistent volumes in your cluster have all the PV and PVC's and it doe support cross storage replication it will replicate that also. Third is container registry , we do support container registry replication.
  5. So. its any to any tool.
  6. Overall it Hybrid sync mode , we do filesystem , product does have files in the volumes, its a live replication and its actually transfer user spaces like a block solution due to this hybrid capability it will use lot of execution. 
  7. We do support lot of re-configuration or replication for e.g.. You can exclude certain volumes  , you can change service types, like change to nodeport.
  8. You don't need to understand complex YAML. Its very simple interface.
  9. Also we don't reconfigure or modify of your source applications like changing the labels, adding any annotations that kind of things SWIFT won't do. SWIFT just install the pod and transfer the data from source to target site and it is very highly secure and encrypted.
  10. SWIFT is very highly customizable , whenever we configure something in cluster. We provide lot of options to do any customization as we support pre/post script/YAML configuration, Ingress configuration, Volume include/exclude,  pod scaling and so on.


Sync : 

  1. Actually in sync, we will have source and target cluster anything could be of K8S or OpenShift and SWIFT can be installed either side.
  2. When you run a sync, it will run as a  pod and its called traipod. trai is our agent image (RackWare agent image).
  3. It will run on both sides of the clusters. and its for staging environment. Its purely containerized image and stateless image.
  4. Also SWIFT will discover clusters and its very quick, it will take hardly 2-3 seconds to discover the entire cluster.
  5. We do support 3 types of sync. Passthrough and stag1 and stage2 sync.
  6. In Passthrough mode : We can choose this mode for migration only purpose, in this mode it will not store any data on the SWIFT, so it will not backup any data on SWIFT, it will just lift and shift migration from source cluster to target cluster.
  7. In Stage1 : It will create a backup of your application on SWIFT in the storage pool. For that we need to add the storage pool in SWIFT. we can add multiple storage pool, it is not restricted to create only one and it is managed by SWIFT. Storage pool have the compression property and backup will remain secure. Advantage of this approach that its not mandatory have target cluster up and running.
  8. In stage1, there is image group  and this is set of volumes and captured together and has been kept in pool.
  9. In Stage2 : If any Disaster happen then you can directly perform stage-2 , it will keep you backup at target side., also note if you want both cluster UP and Running then you can perform stage2 sync. In that you can set up a DR policy to delta sync with given periodicity. We have multiple  periodicity to run the stage1 and stgae2 syncs.
  10. SWIFT will create a snapshot of the volume associated with selected apps. It will also analyze the app and namespaces, then you have to select the app, once you select the app for sync then it will find out what volumes are used and it will do unleashes which volume changed and which are missing and it will create a snapshot for those and migrate.
  11. In case of snapshot , Kubernetes does not support snapshot for most of the volumes
  12. We support all CSI drivers where snapshot are supported. Non CSI drivers also we support . Most of the clouds have non csi drivers supported, so we also support that also still we do a snapshot for the same with our SWIFT.
  13. There will no any downtime required at source.
  14. In the namespace , it will launch TRAIPOD on both side, once triapod is ready, SWIFT will create a tunnel between them and data will transfer between this tunnel in secure way.