Re: [BackupPC-users] BackupPC 4.1.1 and NFS shares
On Fri, Apr 21, 2017 at 5:09 PM, Bedynek, Matthew J. wrote:
> All,
>
> With version 3 I am using Rsync instead of tar to backup a NFS share which
> the backupPC host has direct access to. This has worked great with the
> exception that linking takes forever if there are a large number of files.
> I simply didn’t have much luck getting version 3 to work with tar and got
> rsync to work rather easily so stopped there.
>
> In the version 4 change log I noted that there were some improvements to
> linking so decided to give that a try. However, with version 4, there have
> been changes to rsync such that am forced to use tar for a local copy.
>
>
> My V3 rsync config looked like:
>
> $Conf{ClientNameAlias} = 'localhost';
> $Conf{BackupFilesExclude} = {
> '*' => [
> ‘/x/y/SEQ/IPTS-*'
> ]
> };
> $Conf{RsyncClientCmd} = 'sudo -u username $rsyncPath $argList+';
> $Conf{RsyncClientRestoreCmd} = 'sudo -u username $rsyncPath $argList+’;
>
>
> I believe the RsyncClientCmd and RsyncClientRestoreCmd are gone in V4. I did
> get Rsync to work with V4 but it seems to ssh to localhost which consumes
> additional host resources.
>
> Rsync isn’t a big deal since I have tar working now but am I correct in
> reading that Rsync might be better for incremental backups in terms of
> handling deletions?
>
If you think about what rysnc is supposed to do, it doesn't make much
sense to run both ends locally accessing data over NFS.For any
file that is not skipped by the timestamp/length check in
incrementals, you are going to read the entire file over NFS so rsync
can compute the differences (where the usual point is to only send the
differences over the network). Is there any way you can run rsync
remotely against the NFS host instead?
--
Les Mikesell
lesmikes...@gmail.com
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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] BackupPC 4.1.1 and NFS shares
All,
With version 3 I am using Rsync instead of tar to backup a NFS share which the
backupPC host has direct access to. This has worked great with the exception
that linking takes forever if there are a large number of files. I simply
didn’t have much luck getting version 3 to work with tar and got rsync to work
rather easily so stopped there.
In the version 4 change log I noted that there were some improvements to
linking so decided to give that a try. However, with version 4, there have
been changes to rsync such that am forced to use tar for a local copy.
My V3 rsync config looked like:
$Conf{ClientNameAlias} = 'localhost';
$Conf{BackupFilesExclude} = {
'*' => [
‘/x/y/SEQ/IPTS-*'
]
};
$Conf{RsyncClientCmd} = 'sudo -u username $rsyncPath $argList+';
$Conf{RsyncClientRestoreCmd} = 'sudo -u username $rsyncPath $argList+’;
I believe the RsyncClientCmd and RsyncClientRestoreCmd are gone in V4. I did
get Rsync to work with V4 but it seems to ssh to localhost which consumes
additional host resources.
Rsync isn’t a big deal since I have tar working now but am I correct in reading
that Rsync might be better for incremental backups in terms of handling
deletions?
-matt
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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/
Re: [BackupPC-users] Multiple issues on newly installed 4.1.0.
Matt, Thanks. Yes, please re-run with XferLogLevel set to 6 and send me the interesting parts (or all) of the log file. Craig On Fri, Apr 21, 2017 at 6:56 AM, Bedynek, Matthew J. wrote: > Craig, > > It was very short so I’ll probably redo it today with more debugging. The > high point being that I saw similar behavior. > > tarExtract: copyInodes: finished getAll() > tarExtract: copyInodes: finished getAll() > tarExtract: copyInodes: finished getAll() > tarExtract: copyInodes: finished getAll() > tarExtract: copyInodes: finished getAll() > tarExtract: copyInodes: finished getAll() > tarExtract: copyInodes: finished getAll() > tarExtract: copyInodes: finished getAll() > tarExtract: copyInodes: finished getAll() > tarExtract: copyInodes: finished getAll() > tarExtract: copyInodes: finished getAll() > tarExtract: copyInodes: finished getAll() > tarExtract: copyInodes: finished getAll() > tarExtract: *** stack smashing detected ***: /usr/bin/perl terminated > tarExtract: === Backtrace: = > tarExtract: /lib64/libc.so.6(__fortify_fail+0x37)[0x7fcb4317b047] > tarExtract: /lib64/libc.so.6(__fortify_fail+0x0)[0x7fcb4317b010] > tarExtract: /usr/lib64/perl5/vendor_perl/auto/BackupPC/XS/XS.so(+ > 0x7a80)[0x7fcb3b602a80] > tarExtract: /usr/lib64/perl5/CORE/libperl.so(Perl_pp_entersub+0x58f)[ > 0x7fcb4447842f] > tarExtract: /usr/lib64/perl5/CORE/libperl.so(Perl_runops_standard+0x16)[ > 0x7fcb44470ba6] > tarExtract: /usr/lib64/perl5/CORE/libperl.so(perl_run+0x355)[ > 0x7fcb4440d9a5] > tarExtract: /usr/bin/perl[0x400d99] > tarExtract: /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fcb4308db35] > tarExtract: /usr/bin/perl[0x400dd1] > tarExtract: === Memory map: > > [..] > BackupPC_tarExtract exited with fail status 6 > Xfer PIDs are now > Got fatal error during xfer (BackupPC_tarExtract exited with fail status 6) > Backup aborted (BackupPC_tarExtract exited with fail status 6) > BackupFailCleanup: nFilesTotal = 1469, type = full, BackupCase = 4, > inPlace = 0, lastBkupNum = 2 > Keeping non-empty backup #2 (/backups/...) > Running BackupPC_refCountUpdate -h m8u-test -f on m8u-test > Xfer PIDs are now 7965 > BackupPC_refCountUpdate: host m8u-test got 0 errors (took 17 secs) > > > > I somehow missed that. Can you re-send to me please? > > > Matt > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > 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/ > > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ 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/
Re: [BackupPC-users] Multiple issues on newly installed 4.1.0.
Craig, It was very short so I’ll probably redo it today with more debugging. The high point being that I saw similar behavior. tarExtract: copyInodes: finished getAll() tarExtract: copyInodes: finished getAll() tarExtract: copyInodes: finished getAll() tarExtract: copyInodes: finished getAll() tarExtract: copyInodes: finished getAll() tarExtract: copyInodes: finished getAll() tarExtract: copyInodes: finished getAll() tarExtract: copyInodes: finished getAll() tarExtract: copyInodes: finished getAll() tarExtract: copyInodes: finished getAll() tarExtract: copyInodes: finished getAll() tarExtract: copyInodes: finished getAll() tarExtract: copyInodes: finished getAll() tarExtract: *** stack smashing detected ***: /usr/bin/perl terminated tarExtract: === Backtrace: = tarExtract: /lib64/libc.so.6(__fortify_fail+0x37)[0x7fcb4317b047] tarExtract: /lib64/libc.so.6(__fortify_fail+0x0)[0x7fcb4317b010] tarExtract: /usr/lib64/perl5/vendor_perl/auto/BackupPC/XS/XS.so(+0x7a80)[0x7fcb3b602a80] tarExtract: /usr/lib64/perl5/CORE/libperl.so(Perl_pp_entersub+0x58f)[0x7fcb4447842f] tarExtract: /usr/lib64/perl5/CORE/libperl.so(Perl_runops_standard+0x16)[0x7fcb44470ba6] tarExtract: /usr/lib64/perl5/CORE/libperl.so(perl_run+0x355)[0x7fcb4440d9a5] tarExtract: /usr/bin/perl[0x400d99] tarExtract: /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fcb4308db35] tarExtract: /usr/bin/perl[0x400dd1] tarExtract: === Memory map: [..] BackupPC_tarExtract exited with fail status 6 Xfer PIDs are now Got fatal error during xfer (BackupPC_tarExtract exited with fail status 6) Backup aborted (BackupPC_tarExtract exited with fail status 6) BackupFailCleanup: nFilesTotal = 1469, type = full, BackupCase = 4, inPlace = 0, lastBkupNum = 2 Keeping non-empty backup #2 (/backups/...) Running BackupPC_refCountUpdate -h m8u-test -f on m8u-test Xfer PIDs are now 7965 BackupPC_refCountUpdate: host m8u-test got 0 errors (took 17 secs) I somehow missed that. Can you re-send to me please? Matt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ 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/
