search

garethgeorge / backrest

Backrest is a web UI and orchestrator for restic backup.
GNU General Public License v3.0
1.63k stars 43 forks source link

Add option to restore to original path. #118

Open jindalpratik opened 8 months ago

jindalpratik commented 8 months ago

Is your feature request related to a problem? Please describe. It would be nice to be able to restore directly to the original path.

Describe the solution you'd like An option to during restore which asks if you would like to restore to original path would be nice

Additional context This could aditionally include options like overwriting existing files and such.

wechsler42 commented 8 months ago

Thanks, a very good suggestion that I fully second.

garethgeorge commented 7 months ago

Hmm, iiuc from https://forum.restic.net/t/does-restoring-over-the-top-of-a-previous-restore-work/946 restic will always overwrite existing files (even if restoring on top of an existing directory).

The safe behavior I've picked in backrest is to always restore into a newly created empty folder and then to allow the user to pick out the files they want / merge those into their directory structure. I think I'll save restoring on top of existing files as a 1.0.0 (stable release) feature as I'm very hesitant to add potentially destructive operations.

Witmann commented 6 months ago

Using Docker container, I notice that if I restore something, the restored files go into a root owned folder with none rights for others, anyway it's most likely a missconfiguration on my side. However, to support the @jindalpratik's suggestion I would say that it should be great to have an option to restore into original path with sub-options like renaming the restored file with a sufix like "my_file_RESTORED" or even the possibility to crush present data in target folder. Such option are available in Veeam, Acronis, Data Protector etc. BTW thanks a lot for this Restic wrapper, very good and acurate job !

Pretense2553 commented 6 months ago

Using Docker container, I notice that if I restore something, the restored files go into a root owned folder with none rights for others, anyway it's most likely a missconfiguration on my side. However, to support the @jindalpratik's suggestion I would say that it should be great to have an option to restore into original path with sub-options like renaming the restored file with a sufix like "my_file_RESTORED" or even the possibility to crush present data in target folder. Such option are available in Veeam, Acronis, Data Protector etc. BTW thanks a lot for this Restic wrapper, very good and acurate job !

This is an issue for me too. I've just setup Backrest and find it working great, though when restoring backups, it creates the new folder structure as owned by root and is locked to the main user. Although this can easily be modified in command line, is there an option to default the restore permissions to a different user?

Witmann commented 4 months ago

I've tried today to restore a file, it's now possible to restore into original path, however when restoring, we still have a new original folder structure owned by root, that seems normal because we don't have any environment variable set in the container's yml configuration that says that we could use a specific Linux user ID when restoring files, so as restic is launched as root into the container, it restores as root I guess.

xadips commented 3 months ago

Is there any way to force restore to original path with overwrite could it be like an advanced option, checkbox as it currently is quite messy to use when running in docker and trying to restore.