Jeff, Sure, that's possible. But given that it was necessary to use a file to pass along the list of files to restore, it seemed easier to just use that one mechanism.
It would be pretty easy to write a wrapper script that takes command-line arguments and writes the request file and passes it along to BackupPC_restore ((see lib/BackupPC/CGI/Restore.pm) . Craig On Wed, May 20, 2020 at 11:59 AM <backu...@kosowsky.org> wrote: > Couldn't their be an option to read the to-be-restored files from a > file (similar to what tar and rsync allow) but allowing basic restores > to be done form the command line. > Other parameters could either be via command line or added config.pl > settings if more permanent. > Craig Barratt via BackupPC-users wrote at about 11:31:37 -0700 on > Wednesday, May 20, 2020: > > Jeff, > > > > For restores, there could be a long list of specific files or > directories > > to restore, which might not fit on the command line, so that's what > > triggered putting everything in a request file and just passing its > name. > > There are also several other settings specific to the restore (eg, the > path > > to restore to etc), none of which are in config files. > > > > Craig > > > > On Wed, May 20, 2020 at 10:29 AM <backu...@kosowsky.org> wrote: > > > > > Thanks Craig, > > > > > > Why is restore inherently that much more complicated than dump? > > > It seems like config.pl already has a number of parameters built-in > > > for both including rsync args and pre/post restore commands. > > > > > > Conceptually, I would think that what one needs to specify each time > > > is: > > > 1. Host > > > 2. Backup number > > > 3. Share > > > 4. Additional includes/excludes to determine what to restore > > > 5. Option to "delete" files no longer found > > > 6. Path to root of restore. > > > > > > Otherwise, existing includes/excludes would be assumed... > > > > > > I'm sure one could make it more complicated but am I missing something > > > basic??? > > > > > > The reality is that rsync + backuppc is really awesome... and I can do > > > (and automate) so much more with CLI and scripts than with a CGI. > > > > > > Jeff > > > > > > Craig Barratt via BackupPC-users wrote at about 09:32:48 -0700 on > > > Wednesday, May 20, 2020: > > > > Jeff, > > > > > > > > BackupPC_restore takes quite a few parameters, so many years ago I > > > decided > > > > to pass those parameters via a file rather than command-line > arguments. > > > > Probably a bad choice... > > > > > > > > There are two alternatives: > > > > > > > > - write a script that creates the restore request parameter > file (see > > > > lib/BackupPC/CGI/Restore.pm) and then runs BackupPC_restore > > > > - directly run rsync_bpc using an example of the many arguments > from > > > a > > > > successful restore log file > > > > > > > > The drawback of the 2nd approach is that information about the > restore > > > > isn't saved or logged, and you have to make sure it doesn't run > > > > concurrently with a backup. > > > > > > > > Craig > > > > > > > > > > > > On Wed, May 20, 2020 at 6:31 AM <backu...@kosowsky.org> wrote: > > > > > > > > > > > > > > Is it possible to do an rsync restore from the command line using > > > > > BackupPC_restore? > > > > > If so, it's not clear from the (limited) documentation how to use > > > > > it. For example, how do you specify the desired backup number, > share, > > > > > paths, etc. > > > > > > > > > > Alternatively, is there an rsync analog of BackupPC_tarCreate? > > > > > > > > > > Said another way, rather than first creating a tar file via > > > > > BackupPC_tarCreate and then untarring (or piping through tar), is > > > > > there a way to hook directly into rsync to restore from the > command > > > line? > > > > > > > > > > This would have several advantages: > > > > > 1. It would automatically incorporate the ssh and compression > features > > > > > to restore seamlessly, efficiently, and securely across > platforms > > > > > > > > > > 2. It would allow for restoring special file types that tar > doesn't > > > > > support > > > > > > > > > > 3. It would be able to better and more exactly mirror the > parameters > > > > > given to Rsync dump (for example the same format of > 'includes' and > > > > > 'excludes' > > > > > > > > > > > > > > > _______________________________________________ > > > > > BackupPC-users mailing list > > > > > BackupPC-users@lists.sourceforge.net > > > > > List: > https://lists.sourceforge.net/lists/listinfo/backuppc-users > > > > > Wiki: http://backuppc.wiki.sourceforge.net > > > > > Project: http://backuppc.sourceforge.net/ > > > > > > > > > _______________________________________________ > > > > BackupPC-users mailing list > > > > BackupPC-users@lists.sourceforge.net > > > > List: > https://lists.sourceforge.net/lists/listinfo/backuppc-users > > > > Wiki: http://backuppc.wiki.sourceforge.net > > > > Project: http://backuppc.sourceforge.net/ > > > > > > > > > _______________________________________________ > > > BackupPC-users mailing list > > > BackupPC-users@lists.sourceforge.net > > > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > > > Wiki: http://backuppc.wiki.sourceforge.net > > > Project: http://backuppc.sourceforge.net/ > > > > > _______________________________________________ > > BackupPC-users mailing list > > BackupPC-users@lists.sourceforge.net > > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > > Wiki: http://backuppc.wiki.sourceforge.net > > Project: http://backuppc.sourceforge.net/ >
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
