This message was deleted.

What was your process to migrate Rancher?

backup from origin rancher to s3 in new cluster:

helm install rancher-backup-crd rancher-charts/rancher-backup-crd -n cattle-resources-system --create-namespace --version 2.1.5
helm install rancher-backup rancher-charts/rancher-backup -n cattle-resources-system --version 2.1.5

creating s3 secret and then restore yaml : (During a migration,

prune

must be set to

false

.) - https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster

apiVersion: <http://resources.cattle.io/v1|resources.cattle.io/v1>
kind: Restore
metadata:
  name: restore-migration
spec:
  backupFilename: <file_name>
  prune: false 
  storageLocation:
    s3:
      credentialSecretName: s3-creds
      credentialSecretNamespace: default
      bucketName: <backetname>
      folder: rancher
      region: us-east-1
      endpoint: <http://s3.us-east-1.amazonaws.com|s3.us-east-1.amazonaws.com>

even if i remove the finalizers in the old cluster its still the same error.

what version is rancher-backup on the original cluster (that did backup to S3)?

the old cluster is EKS - already depracated, with 1.19 nodes and 1.21. rancher is 2.6.6, New cluster is 1.26 and rancher 2.7.4.

So, if I am understanding correctly... For example: Your old rancher : www.oldrancher.org New (restored) rancher: www.newrancher.org ? If so, I am not sure how downstream cluster would be able to reconnect (since they are registered to old URL)?

i thought they connect by certificate from rancher host and rancher agent. if it by an url so i have to use same url? if so - how can i check if the migration really worked (with active clusters) without the downtime of the old cluster? (or atleast minimum downtime )

sorry, I do not know answer to that. I just followed what it said in step #4 : https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster#4-b[…]helm

--set hostname=<same hostname as the server URL from the first Rancher server>