Yes, you are correct. The '--hard-links' argument tells rsync to transfer hardlinks from the client.
On the server side, hardlinks are not used to store the hardlink information that rsync sends from the client. On restore, the opposite happens - the server side reconstructs the hardlink information based on the stored metadata, and rsync then reconstructs the correct hardlinks on the client (provided its '--hard-links' argument is specified. Craig On Fri, Oct 2, 2020 at 1:04 PM PGNet Dev <pgnet....@gmail.com> wrote: > BackupPC 4.0 release notes, @ > https://backuppc.github.io/backuppc/BackupPC.html, state new-version > changes include > > "No use of hardlinks (except temporarily to do atomic renames). Reference > counting is handled at the application level in a batch manner (hardlinks > will still remain for any legacy V3 backups)." > > In the default config.pl's rsync section, I still see > > $Conf{RsyncArgs} = [ > ... > '--hard-links', > ... > ]; > > & > > $Conf{RsyncRestoreArgs} = [ > ... > '--hard-links', > ... > ]; > > IIUC, rsync's hard-links usage refers to the source(s), whereas BackupPC's > (ex)hard-links usage refers to links in the destination pool. > > And the two have no relevance to / effect upon one another. > > Is that correct? > > I'd like make sure that the config doesn't need to be changed to avoid any > surprises down the road ... > > > _______________________________________________ > BackupPC-users mailing list > BackupPC-users@lists.sourceforge.net > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: https://github.com/backuppc/backuppc/wiki > Project: https://backuppc.github.io/backuppc/ >
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
