Cluster Migration with Data Movement #8194
Unanswered
raynay-r
asked this question in
Community support Q&A
Replies: 1 comment 1 reply
-
|
In theory, yes. Restoring to alternate cluster work, especially if file system method is working. Is the problem consistent? I am assuming that you restored the namespace "projects-xwiki-restore" and it didn't exist on the target cluster before? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Yes, this is consistently not working. I tried it a few times with different namespaces. Here are some more details from a forgejo backup I tried to restore. The forgejo namespace did not exist before the restore. backup resource: apiVersion: velero.io/v1
kind: Backup
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"velero.io/v1","kind":"Backup","metadata":{"annotations":{},"name":"forgejo-backup-7","namespace":"coreinfra-services-velero"},"spec":{"csiSnapshotTimeout":"10m0s","defaultVolumesToFsBackup":false,"includedNamespaces":["forgejo"],"itemOperationTimeout":"4h0m0s","snapshotMoveData":true,"storageLocation":"playgrnd","ttl":"720h0m0s","volumeSnapshotLocations":["playgrnd"]}}
velero.io/resource-timeout: 10m0s
velero.io/source-cluster-k8s-gitversion: v1.26.4-3004+52589e6ce268bd-dirty
velero.io/source-cluster-k8s-major-version: "1"
velero.io/source-cluster-k8s-minor-version: 26+
creationTimestamp: "2024-09-14T09:42:16Z"
generation: 9
labels:
velero.io/storage-location: playgrnd
name: forgejo-backup-7
namespace: coreinfra-services-velero
resourceVersion: "311745054"
uid: 0620b8a4-4955-485e-81e6-a5bf231a893b
spec:
csiSnapshotTimeout: 10m0s
defaultVolumesToFsBackup: false
includedNamespaces:
- forgejo
itemOperationTimeout: 4h0m0s
snapshotMoveData: true
storageLocation: playgrnd
ttl: 720h0m0s
volumeSnapshotLocations:
- playgrnd
status:
backupItemOperationsAttempted: 2
backupItemOperationsCompleted: 2
completionTimestamp: "2024-09-14T09:44:48Z"
expiration: "2024-10-14T09:42:16Z"
formatVersion: 1.1.0
hookStatus: {}
phase: Completed
progress:
itemsBackedUp: 102
totalItems: 102
startTimestamp: "2024-09-14T09:42:25Z"
version: 1backup describe output on the second cluster the restore was created with velero restore create forgejo-restore-1 --from-backup forgejo-backup-7 -n coreinfra-data-protection-velerorestore resource apiVersion: velero.io/v1
kind: Restore
metadata:
creationTimestamp: "2024-09-14T09:48:02Z"
finalizers:
- restores.velero.io/external-resources-finalizer
generation: 8
name: forgejo-restore-1
namespace: coreinfra-data-protection-velero
resourceVersion: "43861763"
uid: 42c0cb81-e253-4bbc-9a64-bb43008db98f
spec:
backupName: forgejo-backup-7
excludedResources:
- nodes
- events
- events.events.k8s.io
- backups.velero.io
- restores.velero.io
- resticrepositories.velero.io
- csinodes.storage.k8s.io
- volumeattachments.storage.k8s.io
- backuprepositories.velero.io
hooks: {}
includedNamespaces:
- '*'
itemOperationTimeout: 4h0m0s
uploaderConfig: {}
status:
completionTimestamp: "2024-09-14T09:48:06Z"
errors: 2
hookStatus: {}
phase: PartiallyFailed
progress:
itemsRestored: 66
totalItems: 66
startTimestamp: "2024-09-14T09:48:02Z"
warnings: 9restore describe output logs Thanks for your help! |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
I have two OKD cluster and want to migrate an application between them. Both clusters run rook-ceph with the same storage classes. I am using an additional Minio instance as backup storage. Both OKD cluster have access to the Minio instance.
I was able to successfully migrate the application using the file system backup, but I am not able to get it working with data movement. The backup itself works without issue but when I try to restore in the second cluster I get the following error
Should Data Movement between clusters work?
Beta Was this translation helpful? Give feedback.
All reactions