Migration of Data from one PVC to another

destination-template.yaml

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: NAME
  namespace: NS
spec:
  accessModes:
    - ReadWriteOnce
  volumeMode: Filesystem
  resources:
    requests:
      storage: SIZE
  storageClassName: csi-ceph-dc1-standard 

migration-template.yaml

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: migration-NAME
  namespace: NS
spec:
  accessModes:
    - ReadWriteOnce
  volumeMode: Filesystem
  resources:
    requests:
      storage: SIZE
  storageClassName: csi-ceph-dc1-standard 

pod-backup-template.yaml

apiVersion: v1
kind: Pod
metadata:
  name: migration-backup
  namespace: NS
spec:
  containers:
  - name: migration-backup
    image: busybox
    args:
    - sleep
    - "1000000"
    volumeMounts:
      - name: source
        mountPath: /data-source
      - name: destination
        mountPath: /data-destination
  volumes:
    - name: source
      persistentVolumeClaim:
        claimName: SOURCEPVC
        readOnly: false
    - name: destination  
      persistentVolumeClaim:
        claimName: migration-SOURCEPVC
        readOnly: false

pod-restore-template.yaml

apiVersion: v1
kind: Pod
metadata:
  name: migration-restore
  namespace: NS
spec:
  containers:
  - name: migration-restore
    image: busybox
    args:
    - sleep
    - "1000000"
    volumeMounts:
      - name: source
        mountPath: /data-source
      - name: destination
        mountPath: /data-destination
  volumes:
    - name: source
      persistentVolumeClaim:
        claimName: migration-SOURCEPVC
        readOnly: false
    - name: destination  
      persistentVolumeClaim:
        claimName: SOURCEPVC
        readOnly: false

@FedeMarchiniHotovo The target-PVC is essentially the same as the source PVC - same name, same labels, etc. So you cannot create it as long as the source-pvc exists.

I see, thanks !