Stefan, Les,
Thanks you for your excellent suggestions. I have solved the problem by
increasing the config value: timeout=2400 in the rsyncd.conf file.
I appreciate the time you took to help.
John
On 01/20/2017 12:18 PM, Stefan Peter wrote:
> On 20.01.2017 09:13, Stefan Peter wrote:
>> If you
On 20.01.2017 09:13, Stefan Peter wrote:
> If you use the rsync method, make sure your
> RsyncClientCmd does not use the --timeout parameter or at least sets a
> reasonably high paramter value.
As an afterthought, I suppose the BackupPC parameter
$Conf{ClientTimeout} from the clients Backup
This is exactly the kind of information I was hoping to get. I had
overlooked where these timeout values were configured. I will experiment
with these settings and get back with my results.
Thank you Stefan for this very helpful information.
Kind Regards,
John S.
On 01/20/2017 12:13 AM, Stefan
Am 20.01.2017 um 04:57 schrieb John Spitzer:
> On 01/19/2017 1:28 PM, Les Mikesell wrote:
>> On Thu, Jan 19, 2017 at 2:25 PM, John Spitzer
>> wrote:
>>
>> The most likely suspect is that rsync timeout shown in the log snippet
>> you posted. But you didn't provide any
On 01/19/2017 1:28 PM, Les Mikesell wrote:
On Thu, Jan 19, 2017 at 2:25 PM, John Spitzer wrote:
The most likely suspect is that rsync timeout shown in the log snippet
you posted. But you didn't provide any details about why or how your
rsync had timeouts enabled.
That
On Thu, Jan 19, 2017 at 2:25 PM, John Spitzer 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
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
On 01/19/2017 9:41 AM, Les Mikesell wrote:
> On Thu, Jan 19, 2017 at 10:16 AM, John Spitzer wrote:
>> Because:
>> 1. I have a dozen VMs, each of which would need a backup job. Much more
>> complicated backup setup.
>> 2. The VM would need to be running to backup,
> Note
On Thu, Jan 19, 2017 at 10:16 AM, John Spitzer wrote:
> Because:
> 1. I have a dozen VMs, each of which would need a backup job. Much more
> complicated backup setup.
> 2. The VM would need to be running to backup,
Note that a consistent backuppc copy will only happen if
Because:
1. I have a dozen VMs, each of which would need a backup job. Much more
complicated backup setup.
2. The VM would need to be running to backup,
3. I can only run a few at a time due to host system limitations. Make
that work automatically would be much more difficult than just backing
Hi there,
On Wed, 18 Jan 2017, John Spitzer wrote:
> ... The backup I'm creating has quite a few very large files. On the
> order of 20 - 50 GBytes in size. These are VirtualBox VMs disk files.
That's insane. Why not just back up the files on the VMs instead?
--
73,
Ged.
On Wed, Jan 18, 2017 at 7:03 PM, John Spitzer wrote:
> After much debugging, using strace and looking at logs, I think I'm on a
> better track about what may be happening. I sincerely welcome it if anyone
> reading this has more inside info about how BackupPC might be
After much debugging, using strace and looking at logs, I think I'm on a
better track about what may be happening. I sincerely welcome it if
anyone reading this has more inside info about how BackupPC might be
contributing to this.
Based on the strace and logs, I've come to lean in the
On Mon, Jan 16, 2017 at 2:13 PM, John Spitzer wrote:
> I have BackupPC setup with three host configurations to backup three
> separate areas of one system. Two of the hosts configurations are
> working. One repeatedly fails with the messages:
>
> Can't write 33792 bytes to
I have BackupPC setup with three host configurations to backup three
separate areas of one system. Two of the hosts configurations are
working. One repeatedly fails with the messages:
Can't write 33792 bytes to socket
Can't write 35328 bytes to socket
...
Got fatal error during xfer (aborted by
15 matches
Mail list logo