Sorry, I don't have any useful advice, and don't have time to track down
my own problem right now. I expect that you could adjust your backup to
do one of the following:
1) Reduce the number of files backed up per share (by splitting the
include/exclude setting to include a smaller set in each share)
2) Reduce the number of files saved into a single directory (harder to
do probably)
I'm not sure exactly which of the above two is causing the problem, or
if in fact it is one of those two, but it would be interesting to test it.
Probably in December I might have more time to look into this issue.
Please continue to share if you find any more details.
PS, I never use tar, so I can't comment on that. I would suggest
starting with a small host first to get it working with almost all
default settings. Then try to apply the same config to your bigger host.
Regards,
Adam
On 03/11/15 20:07, František Starý wrote:
> Hello.
>
> Dne 2.11.2015 v 1:11 Adam Goryachev napsal(a):
>> Hi,
>>
>> On 02/11/15 05:56, František Starý wrote:
>>> Hello backuppc gurus.
>>>
>>> I've upgraded backuppc from 3.3.0-1ubuntu1 to 4.0.0alpha3. Now I have
>>> the following issues with some of my backuped hosts since the update.
>>> All my hosts are the same machine on the same network - just different
>>> folders with different backup settings.
>>> Host "mail" that backups about 190GB of small files (maildirs) has never
>>> successfully backed up since the upgrade (14 days). The error is:
>> Some generic comments that I found when doing the same upgrade:
>> 1) Make sure you are not overriding the new default rsync arguments.
>> Changing/adding/removing them can definitely cause problems. Start with
>> the default, and then adjust after you know it is working. Also, use the
>> new RsyncArgsExtra (or similar) variable instead of overwriting the default.
> I've removed my custom Rsync argument modifications, restarted backuppc
> daemon and rerun the backup. The result is unchanged - failure.
>> 2) I found backups do not always work properly when backing up files
>> that existed in an old v3.x backup. My solution was to delete the backup
>> folders, and allow new backups to start with v4.x.
> I've tried to rename folder /var/lib/backuppc/pc/mail to
> /var/lib/backuppc/pc/mail.old and rerun the backup. The result is
> unchanged - failure.
>> Those two changes have solved most of my problems with v4.x
>>
>> My one remaining problem is that backups of very large number of files
>> (in one directory, or just per host, not sure) means that the backup
>> never succeeds. I often get these errors:
>> [4851230.076630] rsync_bpc[16712]: segfault at 7f573b73eb28 ip
>> 00000000004473af sp 00007ffce3b9c080 error 4 in rsync_bpc[400000+75000]
>> [4854892.163951] rsync_bpc[16935]: segfault at 7f375b0dbb28 ip
>> 00000000004473af sp 00007ffc0ffa4f50 error 4 in rsync_bpc[400000+75000]
>> [4856658.987895] rsync_bpc[17043]: segfault at 7f5130151b28 ip
>> 00000000004473af sp 00007ffedc7983b0 error 4 in rsync_bpc[400000+75000]
>> [4858478.492391] rsync_bpc[17268]: segfault at 7fb1c53beb28 ip
>> 00000000004473af sp 00007fff55d1cff0 error 4 in rsync_bpc[400000+75000]
>> [4860262.896093] rsync_bpc[17486]: segfault at 7f0f3bad0b28 ip
>> 00000000004473af sp 00007fffb82e86f0 error 4 in rsync_bpc[400000+75000]
>> [4862071.079868] rsync_bpc[17718]: segfault at 7fa6a7cdbb28 ip
>> 00000000004473af sp 00007ffcca0f7050 error 4 in rsync_bpc[400000+75000]
>> [4864030.543342] rsync_bpc[17969]: segfault at 7efcf242db28 ip
>> 00000000004473af sp 00007ffd5d4dd830 error 4 in rsync_bpc[400000+75000]
>> [4880848.314076] rsync_bpc[18779]: segfault at 7efe490b4e28 ip
>> 00000000004473af sp 00007ffc3fda1050 error 4 in rsync_bpc[400000+75000]
>>
>> Which seem to happen each time the backup fails.
>>
>> So, check dmesg output and see if you have this issue too.
> Bingo. I have the same error in "dmesg -T" output:
> [Mon Nov 2 18:53:41 2015] rsync_bpc[910]: segfault at b49fabec ip
> 080918ca sp bfdc4a60 error 4 in rsync_bpc[8048000+75000]
> But I get this error even if i use default backup options with no
> previous V3 or V4 backups. :-(
>
> If i do an fresh backup (default options, deleted the old backup folder)
> using the tar method (so the rsync_bps is NOT used), I'm unable to
> finish the backup too:
> backuppc@backup:~$ /usr/share/backuppc/bin/BackupPC_zcat
> /var/lib/backuppc/pc/mail/XferLOG.0.z |tail
> Got fatal error during xfer (BackupPC_tarExtract exited with fail status 11)
> Backup aborted (BackupPC_tarExtract exited with fail status 11)
> BackupFailCleanup: nFilesTotal = 0, type = full, BackupCase = 6, inPlace
> = 1, lastBkupNum =
> BackupFailCleanup: inPlace with no new files... no cleanup
> Running BackupPC_refCountUpdate -h mail -f on mail
> xferPids 3270
> BackupPC_refCountUpdate: host mail got 0 errors
> BackupPC_refCountPrint: total errors: 0
> xferPids
> Finished BackupPC_refCountUpdate (running time: 24 sec)
>
> Any ideas? I'm considering rollback to V3 backuppc :-(.
>
> With regards,
> Frantisek.
>
>> Regards,
>> Adam
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users AT lists.sourceforge DOT net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
--
Adam Goryachev
Website Managers
www.websitemanagers.com.au
------------------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
