> *From:* Craig Barratt
> *Sent:* 04 October 2020 23:09
> *To:* McDonald, Peter George
> *Cc:* General list for user discussion, questions and support <
> backuppc-users@lists.sourceforge.net>
> *Subject:* Re: [BackupPC-users] backuppc v4 hanging when starting ba
October 2020 19:44
To: General list for user discussion, questions and support
mailto:backuppc-users@lists.sourceforge.net>>
Cc: McDonald, Peter George
Subject: Re: [BackupPC-users] backuppc v4 hanging when starting backup
[External Sender]
Not sure why this should happen. It's just copying a tr
ith v4.
>
> -Peter
>
> --
> *From:* Craig Barratt
> *Sent:* Sunday, October 4, 2020 10:57 pm
> *To:* General list for user discussion, questions and support
> *Cc:* McDonald, Peter George
> *Subject:* Re: [BackupPC-users] backuppc v4 hanging when starti
and support
Cc: McDonald, Peter George
Subject: Re: [BackupPC-users] backuppc v4 hanging when starting backup
Does the localhost/backups file contain entries (rows) for backups #94-#98? Do
those backups appear in the CGI summary for that host?
Is #93 a full/filled backup done using V4?
Craig
> **Corporate
> Responsibility Report <https://bit.ly/tt_cr>*
> <https://bit.ly/tt_cr>
>
> --
> *From:* Craig Barratt
> *Sent:* 04 October 2020 22:32
> *To:* McDonald, Peter George
> *Cc:* General list for user discussion, questions and support &
__
From: Craig Barratt
Sent: 04 October 2020 22:32
To: McDonald, Peter George
Cc: General list for user discussion, questions and support
Subject: Re: [BackupPC-users] backuppc v4 hanging when starting backup
That's an excellent clue. The rsyncTmp.* files could be very large
9:44
> *To:* General list for user discussion, questions and support <
> backuppc-users@lists.sourceforge.net>
> *Cc:* McDonald, Peter George
> *Subject:* Re: [BackupPC-users] backuppc v4 hanging when starting backup
>
> [External Sender]
>
> Not sure why this should
, questions and support
Cc: McDonald, Peter George
Subject: Re: [BackupPC-users] backuppc v4 hanging when starting backup
[External Sender]
Not sure why this should happen. It's just copying a tree of directories that
contain one empty file, so that shouldn't be a problem.
I'd recommend manually
Not sure why this should happen. It's just copying a tree of directories
that contain one empty file, so that shouldn't be a problem.
I'd recommend manually running BackupPC_backupDuplicate as the BackupPC
user with $Conf{XferLogLevel} set to 5. First make sure a backup isn't
running on
Hi,
Apologies if this is not the correct place for this.
We recently upgraded from v3 to v4 in order to try and get better performance,
v3 worked fine. Since upgrading to v4 whenever a new scheduled backup starts
it sits at the 'copy' stage. For example :
Host
10 matches
Mail list logo