On 02/06/2020 21:31, Adrian wrote:
> In message , druck  writes
>> On 02/06/2020 14:31, Adrian wrote:
>>> And what I forgot to mention is that those other Pis are running a 
>>> copy of the rsync script (same target machine, different file 
>>> locations)  without problem, and my source machine does a daily
>>> "pull" rsync from  the target which is much bigger, and that always 
>>> works.
>>
>> Are they all running at the same time, with the same destination 
>> machine/drive?
> 
> I deliberately staggered the run times.  In the normal way of things 
> each "push" takes under 2 minutes, so fitting them all in overnight 
> isn't a problem.
> They all push to the same machine and drive (which has one file system), 
> although to different directories on that drive.

OK, I just had a thought that it might be a resource constraint issue.

I initially set up each of my dozen Pi's to have 6 different SMB mounts 
to a shared drive connected to the router, but found some of the Pi's 
couldn't access the mounts at certain times, for example if previous 
backups were still running. It seems the router had a maximum number of 
SMB shares it would service simultaneously.

I changed things so most of the Pi's only had one permanent mount, and 
mounted the rest on demand to work around the issue, until I upgrade the
router, or get one of the Pi4's to share the disc. The 4GB Pi 4B on 
gigabit Ethernet has twice the large file performance sharing a USB3 
spinning rust drive, and about 8x faster for random access due to more 
memory for caching

---druck

--- SoupGate-Win32 v1.05