On 9/3/17 15:46, chrischan AT knebb DOT de wrote:
> Hi guys,
>
>
> from time to time I have a strange behaviour. Usually my BackupPC 3.x
> (latest) does full backups on weekends and incr during weekdays. And
> usually they are done within 10 or 20 minutes (except huge file changes
> of course).
>
> But from time to time it takes days as it seems to transfer every file.
> No matter if it has changed or not. During an incr. rsyncbackupc.
>
> This is what I see in logfile from the previous backup:
>
> 2017-02-27 20:03:16 removing incr backup 584
> 2017-02-28 18:54:19 full backup started for directory / (baseline backup #591)
> 2017-02-28 19:49:48 full backup started for directory /srv/ (baseline backup
> #591)
> 2017-02-28 21:27:36 full backup 592 complete, 475953 files, 536626090243
> bytes, 1 xferErrs (0 bad files, 0 bad shares, 1 other)
> 2017-02-28 21:27:36 removing full backup 527
>
> 2017-03-01 18:03:32 incr backup started back to 2017-02-28 18:50:08 (backup
> #592) for directory /
> 2017-03-01 18:34:34 incr backup started back to 2017-02-28 18:50:08 (backup
> #592) for directory /srv
> 2017-03-06 09:14:13 Aborting backup up after signal INT
> 2017-03-06 09:14:14 Got fatal error during xfer (aborted by user (signal=INT))
> # Here I aborted the backup as it caused slow traffic...
>
> 2017-03-06 17:05:24 incr backup started back to 2017-02-28 18:50:08 (backup
> #592) for directory /
> 2017-03-06 17:22:21 incr backup started back to 2017-02-28 18:50:08 (backup
> #592) for directory /boot
> 2017-03-06 17:23:49 incr backup started back to 2017-02-28 18:50:08 (backup
> #592) for directory /home
> 2017-03-06 17:35:24 incr backup started back to 2017-02-28 18:50:08 (backup
> #592) for directory /srv
>
> Since then it is running. Using a "lsof| grep rsync" on the target server
> shows open files beeing backed up which have not changed for ages!
>
> Any idea why this is happening?
I vaguely recall this type of scenario with BPC 3.x a few years ago.
Without seeing your detailed backup logs, I can't tell if it is the same
or not, and my memory is a little vague. I think the circumstance was:
1) the backup was interrupted or there was some error during the backup
2) BPC marked the backup as complete, and so deleted the rest of the
files after the backup point
3) The next backup now needed to re-download all files
The above would not happen with BPC v4 because even if a file didn't
exist in the previous backup of this client, as long as it is in the
pool (and unmodified) then it won't be downloaded. I don't recall what
the fix was, or which version (if any) this was released in. I used to
go back and delete the "partial" backup (and any newer backup) so that
the newest backup actually contained all the files. Then I would start a
backup and make sure it completed properly. This would happen once every
few months for one or two servers (but never for other servers for some
reason).
Sorry I can't be much help, but please provide some more details, and/or
search the archives for the error message (if you find it in the details
xferlog)...
Regards,
Adam
------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
