docs(en): Remove TODO from backups article

pull/43/head
Inex Code 2023-09-27 11:56:34 +03:00
parent 490e3221f8
commit b8b1e5be25
1 changed files with 3 additions and 5 deletions

View File

@ -30,7 +30,7 @@ In the interface, you can see a snapshot as having an id, a service it backs up,
## When backups occur?
A snapshot is created in 3 cases:
A snapshot is created in 3 cases:
* By user's manual command to back up a service
* Automatically at certain intervals if Automatic Backups are enabled
@ -57,7 +57,7 @@ There are 2 factors to keep in mind when looking at the list:
## Restoring a snapshot
When you restore a snapshot, the service is stopped, and all of its files are restored to the state when the snapshot was taken.
There are 2 ways to do it.
There are 2 ways to do it.
The safest one, the default one, is to download the snapshot in its entirety, verify that data is not damaged, and replace the service files with the files from the snapshot.
This has a downside that you need to have extra space to store the snapshot.
@ -69,7 +69,7 @@ The app does check that we have enough space before attempting a restore.
## Forgetting a snapshot
Forgetting makes the snapshot inaccessible from the server, but deletion itself is reversible from cloud UI for some time <enter some default value that the app sets>.
Forgetting makes the snapshot inaccessible from the server, but deletion itself is reversible from cloud UI for some time (30 days for Backblaze by default).
## Automatic Backup
@ -93,5 +93,3 @@ If set to zero, autobackups will be disabled.
* If you suspect that the snapshot list is inaccurate, try discarding the cache
* If an inplace restore failed, make sure that your cloud is accessible and your contract is active, then try to either restore a snapshot you tried to restore, or a pre-restore snapshot generated automatically
* If you do not have enough space on the disk for a safe restore, try restoring inplace
TODO: Maybe some UI shots?