I like this one :-)
On 1/13/21 8:15 AM, Johan Ehnberg wrote:
On 13.1.2021 0.58, Adam Goryachev via BackupPC-users wrote:
On 13/1/21 09:21, Les Mikesell wrote:
On Tue, Jan 12, 2021 at 4:15 PM Greg Harris
wrote:
Yeah, that “if you can interpret it” part gets really hard when it
looks like:
The ls rendition is super useful, and keeps extra packages off the machine.
Thanks for that one.
Thanks,
Greg Harris
On Jan 12, 2021, at 5:58 PM, Adam Goryachev via BackupPC-users
mailto:backuppc-users@lists.sourceforge.net>>
wrote:
On 13/1/21 09:21, Les Mikesell wrote:
On Tue, Jan 12,
On 13.1.2021 0.58, Adam Goryachev via BackupPC-users wrote:
On 13/1/21 09:21, Les Mikesell wrote:
On Tue, Jan 12, 2021 at 4:15 PM Greg Harris
wrote:
Yeah, that “if you can interpret it” part gets really hard when it
looks like:
select(7, [6], [], [6], {tv_sec=60, tv_usec=0}) = 1 (in [6],
On 13/1/21 09:21, Les Mikesell wrote:
On Tue, Jan 12, 2021 at 4:15 PM Greg Harris wrote:
Yeah, that “if you can interpret it” part gets really hard when it looks like:
select(7, [6], [], [6], {tv_sec=60, tv_usec=0}) = 1 (in [6], left {tv_sec=59,
tv_usec=99})
read(6,
Additionally, 'top' only tells you what is happening now (or in the
last few second sampling period).
What I really want to know is when was the last time data was
successfully transferred across the rsync/ssh pipe which generally
would signal that the backup is progressing vs. being stalled on a
On Tue, Jan 12, 2021 at 4:15 PM Greg Harris wrote:
>
> Yeah, that “if you can interpret it” part gets really hard when it looks like:
>
> select(7, [6], [], [6], {tv_sec=60, tv_usec=0}) = 1 (in [6], left {tv_sec=59,
> tv_usec=99})
> read(6,
>
Yeah, that “if you can interpret it” part gets really hard when it looks like:
select(7, [6], [], [6], {tv_sec=60, tv_usec=0}) = 1 (in [6], left {tv_sec=59,
tv_usec=99})
read(6,
"\0\200\0\0\4\200\0\7\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
32768) = 27748
Scrolling at 32756
On Tue, Jan 12, 2021 at 2:24 PM Greg Harris wrote:
>
I’ve yet to find a solid way to peer into the arena of BackupPC and
find answers to these types of questions.
Strace'ing the rsync process - possibly at both ends - gives you a
pretty detailed view of what is happening if you can interpret
While all of that is true, the answers so far still seem to be kind of like
looking at the parking lot outside the ice hockey arena. (Well, at least,
pre-Covid days anyways.) Is there a game going on or is it a pre-game show
listing players? Is the zamboni on the ice? Which game is in which
>>> I tend to look in the top, if rsync is in progres, it its some CPU. It
iotop would be another method
You could also try following the rsync process with strace
Doug
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:
I tend to look in the top, if rsync is in progres, it its some CPU. It
does not, if it hangs.
Jan
On 1/12/21 6:04 PM, backu...@kosowsky.org wrote:
Short of waiting for 'rsync' to timeout, is there any way to see the
current status of an rsync backuppc backup, such as:
- Current average
Short of waiting for 'rsync' to timeout, is there any way to see the
current status of an rsync backuppc backup, such as:
- Current average 'transfer rate'
- Time last byte was transferred
Sometimes, especially when backing up laptops, it's hard to know if
the ssh connection has been disrupted
12 matches
Mail list logo
