Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs,how-to: restoring LINSTOR database backups #726

Merged
merged 1 commit into from
Nov 4, 2024

Conversation

WanzenBug
Copy link
Member

We automatically create backups, we should also inform people on how to use them.


## Temporarily stop the LINSTOR Controller Deployment

To perform the upgrade, ensure that the LINSTOR Controller is shut down by scaling the Piraeus Operator and
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

upgrade?

```
$ mkdir restore
$ cd restore
# Replace this with your selected backup name
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not that clear what "this" refers to in the long command.

@@ -0,0 +1,87 @@
# How to Restore a LINSTOR Database Backup

This guide shows you how to restore a LINSTOR® Controller from a database backup.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mention that this only applies to the default custom resources database type?

@@ -0,0 +1,87 @@
# How to Restore a LINSTOR Database Backup

This guide shows you how to restore a LINSTOR® Controller from a database backup.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It ought to be obvious, but warn that changes made since the backup was taken are lost? I guess most things will be re-created by the CSI driver. How reliably are we able to pick up the existing volumes with their data? Should normally work, I suppose.

We automatically create backups, we should also inform people on how to use
them.

Signed-off-by: Moritz Wanzenböck <[email protected]>
@WanzenBug WanzenBug force-pushed the docs-linstor-db-restore branch from 2509927 to ed82589 Compare November 4, 2024 12:14
@JoelColledge JoelColledge merged commit 8a339a9 into v2 Nov 4, 2024
5 checks passed
@JoelColledge JoelColledge deleted the docs-linstor-db-restore branch November 4, 2024 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants