Skip to content

Commit

Permalink
chore: Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
OminousLama authored Aug 10, 2024
1 parent c51b82f commit 467b377
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,11 +27,11 @@ https://github.com/user-attachments/assets/cf3998e2-6805-4e8e-9282-2a5f5516ee20

> THIS IS NOT A LOST DATA RECOVERY PROGRAM! It can not restore files from restic that restic has forgotten or purged!
Restic Restore Everything is a Command-Line Interface tool designed to restore every file that has ever been checked into a [Restic](https://restic.net/) repository - **and that is remembered**. This is useful for repo that are used as a fire-and-forget repositories; i.e. repositories that periodically receive files which are removed from the source immediately after completed backup and a means to save space.
Restic Restore Everything is a Command-Line Interface tool designed to restore every file that has ever been checked into a [Restic](https://restic.net/) repository - **and that is remembered**. This is useful for repos that are used as a fire-and-forget repositories; i.e. repositories that periodically receive files which are then removed from the source immediately after completed backup as a means to save space on the source side.

More concrete example: Let's say I have a server that has about 1 TB of disk space available. After some time, the avaialble disk space runs out. So I set up an external storage bucket over at AWS or Backblaze in which I init a new restic repository. I'll then setup some script on my server that periodically backs up files that are no longer needed on the server to this bucket repository (like old documents, images, etc). After the backup completes, the files are deleted from the server to free up space, but live on long-term in the bucket repository.
**More concrete example:** Let's say I have a server that has about 1 TB of disk space available. After some time, the avaialble disk space runs out. So I set up an external storage bucket over at AWS or Backblaze in which I init a new restic repository. I'll then setup a script on my server that periodically backs up files to this bucket repo that are no longer needed (like old documents, images, etc). After the backup completes, the files are deleted from the server to free up space, but live on long-term in the bucket repository.

Restic as of August 2024 does not offer an easy to use way of restoring all data that is stored this way. It is a very specific usecase, but from what I could find in the forums, it is not unique to me.
Restic - as of August 2024 - does not offer an easy to use way of restoring all data that is stored this way. Yes, it is a very specific usecase, but from what I could find in the forums, it is not unique to me.


### Limitations
Expand Down

0 comments on commit 467b377

Please sign in to comment.