Restore instructions are unnecessarily complicated about docker-volume-backup HOT 6 CLOSED

Anytime. Will submit a PR in sometime

from docker-volume-backup.

About your suggestion: I'm not entirely sure why you would need / want to remove the volume? From what I understand you should be able to keep the existing volume and replace its contents with the untared archive?

from docker-volume-backup.

The example extracts an archive directly into a volume and overwriting data, which can cause problems if for example it's a database volume. Instead of resulting in a database that you know works (eg: last night's backup), you end up with good files mixed with stale and possibly corrupted files (if someone's restoring to recover from corruption)

from docker-volume-backup.

Hmm, I see what you mean. Then again there is probably no one size fits all approach and I have to admit I would be afraid to advise people to remove the volume by default (looking at the config examples posted in the issues here there are lots of different approaches taken, people for example add compose files and such to the backup).

Maybe it'd be a good idea to structure the docs with some possible restoration scenarios and explain the pros and cons of each in detail. What do you think?

from docker-volume-backup.

Agreed. I guess the doc could suggest to trigger a manual backup first, then restoring a snapshot. The word is key. Or have two scenarios of snapshots and overwriting

from docker-volume-backup.

Sounds good. I'll try to add this when time allows (unless you would like to join here, which would also be much appreciated). Thanks for your input!

from docker-volume-backup.