NKP supports a variety of approaches for moving application data between workloads and across clusters. Because Persistent Volumes are provisioned as Nutanix Volume Groups within a specific AHV cluster and storage container, data movement should be planned using Kubernetes-aware or application-level mechanisms.
Moving Data Within the Same NKP Cluster
Within a single cluster, data can be moved using:
-
CSI snapshot workflows
-
Filesystem-level copy between PVCs
-
Application-level replication
Using CSI Snapshots
CSI snapshots can be used to create a new Persistent Volume from an existing PVC:
-
Create a VolumeSnapshot of the source PVC.
-
Create a new PVC from that snapshot.
-
Attach the new PVC to the target workload.
This creates a new Volume Group and preserves CSI metadata. Snapshot restore does not overwrite the original volume.
Moving Data Between NKP Clusters
When moving data between clusters (including clusters on different AHV clusters or FlashArrays):
-
Provision a new CSI-managed Persistent Volume in the destination cluster.
-
Restore or copy data into that volume using:
-
Application-level backup/restore
-
Third-party Kubernetes-aware tools that integrate with CSI
-
File-level copy methods (e.g. rsync)
-
In the context of NKP and the Nutanix CSI driver, Nutanix Volume Groups are cluster-level objects and are not designed to be directly moved between AHV clusters.
After migration, snapshot and backup workflows can be resumed using CSI-managed operations in the destination cluster.