Alternate RestoreSession format #2

New Issue

jandre · 2021-02-21T15:12:37Z

jandre commented

2021-02-21 15:12:37 +00:00

Currently, the RestoreSession references a BackupSession and uses the information from the BackupSession and the associated BackupConfiguration to do the restore.

This implies the RestoreSession must have access to the referenced BackupSession which limits the restore possibility. We cannot restore into another or a new cluster.

I have to find a way to make the restore independant from the backup.

Currently, the RestoreSession references a BackupSession and uses the information from the BackupSession and the associated BackupConfiguration to do the restore. This implies the RestoreSession must have access to the referenced BackupSession which limits the restore possibility. We cannot restore into another or a new cluster. I have to find a way to make the restore independant from the backup.

jandre changed title from ~~Alternate~~ to Alternate RestoreSession format

2021-02-21 15:18:12 +00:00

jandre self-assigned this 2021-02-21 15:19:05 +00:00

jandre commented

2021-03-01 02:39:03 +00:00

hmmmm.

Actually, maybe it makes more sense to stay with the reference to the BackupSession.
If we move to a new environment, we re-create everything:

the deployment, statefulset, ...
the Repo, Functions, BackupConfiguration

And then we can also create a BackupSession with a YAML file that references the snapshots for the different steps.

For instance:
kubectl -n nextcloud get bs -o yaml backupsession-backupconf-nextcloud-1614560145 > backupsession.yaml

Remove the unecessary tags and lines and import it in the new environment:
kubectl apply -f backupsession.yaml

hmmmm. Actually, maybe it makes more sense to stay with the reference to the BackupSession. If we move to a new environment, we re-create everything: + the deployment, statefulset, ... + the Repo, Functions, BackupConfiguration And then we can also create a BackupSession with a YAML file that references the snapshots for the different steps. For instance: ```kubectl -n nextcloud get bs -o yaml backupsession-backupconf-nextcloud-1614560145 > backupsession.yaml``` Remove the unecessary tags and lines and import it in the new environment: ```kubectl apply -f backupsession.yaml```

jandre added the

enhancement

label 2021-04-27 20:22:48 +00:00

Sign in to join this conversation.