Re: Restore in-place
Tobias Specht <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.dar.support |
|---|---|
| Message-ID | <[email protected]> |
> You want dar to record in the backups the root of the backup (either > explicitely specified with -R or implicitely when no -R option is > provided). At restoration or comparison time, if the user specifies > --in-place option no -R option should be provided and dar will use > the > path recorded at backup time for the root backup, which would restore > file in their original path. > > Is that correct? Yes, that's what I'm thinking about :) > What should be done when merging two backups having recorded two > different root backup? Does not storing any root backup directory > would be OK? Yes, that's probably all we can do in this case. > In which case --in-place option would lead to an error? Yes. This would be also the case, if this option is used in combination with an older archive version, without the extension. For encrypted archives, it would be great, if the backup root path would be stored inside the encrypted part. So we do not leak any information. On Tue, 2021-04-27 at 21:30 +0200, Denis Corbin wrote: > > > On 26/04/2021 23:48, Denis Corbin wrote: > > > > > > On 26/04/2021 20:10, Tobias Specht wrote: > > > Hi Denis, > > > > > > I think there was a misunderstanding. > > > My idea was to restore the file at its original location (eg. > > > /home/tobias/Documents/foo/file1.txt), > > > but without having to specify -R /home/tobias/Documents. > > > Instead, you would say something like --in-place, or dar would > > > default > -R to the source folder of the backup. > > > This option would also be handy when you browse the archive with a > > > UI. > > > Then you can restore a file/folder without selecting the target > > > location and just click on "restore". > > > > > > Do you see what I mean? > > > > Yep, I see, that makes sense. Though you still have to tell where to > > restore, but don't have to "move down" around the restored > > directory/tree from larger tree... > > I was probably tired yesterday and did not understand properly you > request. So let me summarize with my words and tell me if I better > understand this time: :^) > > You want dar to record in the backups the root of the backup (either > explicitely specified with -R or implicitely when no -R option is > provided). At restoration or comparison time, if the user specifies > --in-place option no -R option should be provided and dar will use the > path recorded at backup time for the root backup, which would restore > file in their original path. > > Is that correct? > > What should be done when merging two backups having recorded two > different root backup? Does not storing any root backup directory would > be OK? In which case --in-place option would lead to an error? > > > > > > > > > Regarding dar_manager, I thought there would be an option to "save" > > > the > > -R option and then extract files without having to specify -R again. > > > But maybe I misunderstood that. > > > > there is not such option with dar_manager, but the feature you > > describe > > could be interesting here too > > in dar_manager you can store in the database some arguments that will > be > passed to dar. Of course you can manually specify a -R option, in that > case at restoration time you don't have to specify the -R path, but > that's different from what I understand from your request : > - different backup may have different -R option in a given database > - the -R provided option may not match the original one > > > > > > > > Best regards, > > > Tobias > > > > > > > > > > > > > Cheers, > > Denis > > > > >