Re: [BackupPC-users] BackupPC fails with aborted by signal=PIPE, Can't write to socket

[Bowie B. <Bowie_Bailey@BUC.com>]

On 1/19/2017 3:25 PM, John Spitzer wrote:
> On 01/19/2017 9:41 AM, Les Mikesell wrote:
>
>> But isn't it much more interesting that I've seem to have found some
>> kind of limit to Backup PC?
>> I think you have found some limit in your network or setup.
>>
> If so, what is that limit and how can I workaround or fix it? If that's
> not possible, then BackupPC isn't the backup solution for me.
>
> Never had this type problem when using Acronis on a Windows host.
>
> This is all off topic. I'm going to continue to back up the VMs this way.

The problem is that your connection is going idle for long periods of 
time while BackupPC processes these huge files to determine if they have 
changed.  Something in your network (router, firewall, etc) is timing 
out on the connection.

If all you are backing up is these VM files, then BackupPC is probably 
not the right solution.  It sounds like these VMs do not change very 
much.  If that is the case, the simplest solution may be using rsync to 
copy the files to a backup drive on an occasional basis.  Write a script 
file with the proper rsync command(s) and then either schedule it with 
cron, or run it manually once a month or whenever.  Rotate backup drives 
so that you still have a good copy if something goes wrong during the 
transfer.

-- 
Bowie