Hi Markus, So if I am understanding correctly, you basically manually build your own rsync command (including all the rsync arguments and the rsync source) and then store that as RsyncClientPath.
I can see how this works but it's not pretty. Would you be able to share the code snippet you use for v3? I fear though that it may be even uglier in v4, given the changes to how rsync is called. Ultimately, I think the right way would be to add something like the hash that I mentioned below, but that would be up to Craig to evaluate and consider. Craig - what do you suggest? Iturriaga Woelfel, Markus wrote at about 17:06:42 +0000 on Sunday, May 5, 2019: > Jeff - the way we have done this in the past is by using a script that takes > all the normal options that rsync takes but translates them to the mount > point for your snapshot. You then use this script as the RsyncClientPath. > We also have a DumPreShareCmd that makes the actual snapshot and then a > DumpPostShareCmd that removes the snapshot. Our scripts are pretty crappy > Perl (I can say that because I wrote them) but they work. As far as BackupPC > is concerned, the share name doesn't need to change and restores work just > fine. > > I haven't re-implemented this since we moved to BackupPC 4 and it would > probably need to make sure this works right with rsync_bpc, but I don't see > why this approach wouldn't work. > > Markus > > On May 5, 2019, at 12:23 PM, > backu...@kosowsky.org<mailto:backu...@kosowsky.org> wrote: > > I would like to backup snapshots (e.g., btrfs, lvm, shadow mounts) of > my shares so that I can get a (more) accurate point-in-time backup. > > To do so, I would like to preserve the share name as pointing to the > original but have the actual backup point to the snapshot location. > > I am able to do this when using rsyncd, since the rsyncd.conf has an > independent path assigned to each share that I can set to the snapshot > location. > > I have not been able to figure out how to do this for rsync itself. > > Ideally, there would be something equivalent to ClientNameAlias, that > would allow one to create a path alias for each share. Perhaps a hash > similar to BackupFilesExclude that would allow this alias to be > defined on a share by share basis. > > Then in DumpPreShareCmd, the snapshot could be created before backup > and then deleted in DumpPostShareCmd. > > At a minimum, I would like to be able to even kludge a redirection that I > could for example set in DumpPreShareCmd to redirect the rsync source. > > Jeff > > > _______________________________________________ > BackupPC-users mailing list > BackupPC-users@lists.sourceforge.net<mailto: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/ > > --- > Markus A. Iturriaga Woelfel, IT Administrator > Min H. Kao Department of Electrical Engineering and Computer Science > University of Tennessee > Min H. Kao Building, Suite 424 / 1520 Middle Drive > Knoxville, TN 37996-2250 > mitur...@utk.edu<mailto:mitur...@utk.edu> / (865) 974-3837 > http://twitter.com/UTKEECSIT > > > > > > _______________________________________________ > 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/
