Re: [BackupPC-users] Pending Jobs and Conf{MaxBackups}
Clemens writes:
got another one, I don't understand. I configured 4 hosts, of which 1
has a very poor network connection. I expect the first full backup to
need about two days. Now, this full is running for about 15 hours and
the cgi-interface status page shows me:
* 2 pending backup requests from last scheduled wakeup,
* 1 pending user backup requests,
from the other hosts.
My main config.pl contains:
$Conf{MaxBackups}
http://server.vonmusil.de/backuppc/index.cgi?action=viewtype=docs#item_%24conf%7bmaxbackups%7d
= 4;
$Conf{MaxUserBackups}
http://server.vonmusil.de/backuppc/index.cgi?action=viewtype=docs#item_%24conf%7bmaxuserbackups%7d
= 4;
Since the one running job plus all three waiting jobs don't exceed the
$Conf{MaxBackups}, why doesn't backuppc run all jobs in parallel?
If you are running 2.x then BackupPC_nightly has to run exclusively
with any backups. So when BackupPC_nightly is pending no more backups
are started.
In 3.x this restriction has been removed.
Craig
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
[BackupPC-users] Backupp Errors
All, All of a sudden, none of my backups (rsync) are working. I'm getting Unable able to read 4 bytes for each backup. Any insight? Thanks, Byron J. Trimble Technical Specialist/Systems Administrator 407-409-5207 [EMAIL PROTECTED] Skype ID: btrimble - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
Re: [BackupPC-users] Backupp Errors
Byron Trimble wrote: All, All of a sudden, none of my backups (rsync) are working. I'm getting Unable able to read 4 bytes for each backup. Any insight? I had this happen to me when I had an old File::RsyncP version using protocol 26 trying to connect to rsyncd that was at protocol 29. Check your logs and see what protocol they negotiate to. If this is your issue, update with CPAN on the server. My problem was complicated further by having two different versions of Perl installed (one from yum, another from sources), and CPAN was updating one version, but BackupPC ran the other. If CPAN checks out as having the latest version, you might check for someone installing another Perl on your system. Hope that helps, JH - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
[BackupPC-users] tar error 256
Running into a problem with my larger machines doing backups. 90% of the time, the backup ends with the following message: backup failed (Tar exited with error 256 () status) I believe I read somewhere that it was due to a file changing during backup, probably in combination with the latency introducted in backup across the network. The reason I went with tar in the first place is that I read that rsync consumes more memory the larger the file list is, and this box has 256MB of RAM. My question at this point is the best approach to fixing this problem. I have been running backuppc since the beginning of the year, so I have at least 2 fulls and a weeks worth of incrementals, so, at least in theory, the number of files being rsynced should not be overly large. So should I convert my problem children to rsync, or should I convert everything over to rsync? Or is there a workaround for tar? Thanks, --b - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
Re: [BackupPC-users] tar error 256
Bradley writes: Running into a problem with my larger machines doing backups. 90% of the time, the backup ends with the following message: backup failed (Tar exited with error 256 () status) I believe I read somewhere that it was due to a file changing during backup, probably in combination with the latency introducted in backup across the network. The reason I went with tar in the first place is that I read that rsync consumes more memory the larger the file list is, and this box has 256MB of RAM. My question at this point is the best approach to fixing this problem. I have been running backuppc since the beginning of the year, so I have at least 2 fulls and a weeks worth of incrementals, so, at least in theory, the number of files being rsynced should not be overly large. So should I convert my problem children to rsync, or should I convert everything over to rsync? Or is there a workaround for tar? What version of tar are you using? Torsten reported that the newest version has changed the exit status in the case of certain relatively benign warnings that are therefore considerd fatal by BackupPC. Could you also look through the XferLOG file and confirm that it is this same warning that tar is reporting? I still need to fix this issue for 3.x. Craig -- Forwarded message -- To: backuppc-users@lists.sourceforge.net From: Torsten Sadowski [EMAIL PROTECTED] Date: Fri, 1 Dec 2006 13:55:15 +0100 Subj: [BackupPC-users] /bin/tar: ./totty: file changed as we read it Hi, the new tar seems to be a bit more nervous than the old one. One Problem could be solved with LANG=C but another point are probably changes in the backed up filesystem. Is there a possibility to ignore this error? Cheers, Torsten /bin/tar: ./totty: file changed as we read it [ skipped 1 lines ] Tar exited with error 256 () status [ skipped 46 lines ] tarExtract: Done: 0 errors, 1557378 filesExist, 63760417431 sizeExist, 45188423124 sizeExistComp, 1615232 filesTotal, 63767351947 sizeTotal Got fatal error during xfer (Tar exited with error 256 () status) Backup aborted (Tar exited with error 256 () status) -- Forwarded message -- To: backuppc-users@lists.sourceforge.net From: Torsten Sadowski [EMAIL PROTECTED] Date: Tue, 5 Dec 2006 10:35:51 +0100 Subj: Re: [BackupPC-users] /bin/tar: ./totty: file changed as we read it I found the reason and a (for now) quick solution. The Reason first (from: http://cvs.savannah.gnu.org/viewcvs/tar/NEWS?rev=1.125root=tarview=auto): GNU tar NEWS - User visible changes. Please send GNU tar bug reports to bug-tar@gnu.org version 1.16 - Sergey Poznyakoff, 2006-10-21 * After creating an archive, tar exits with code 1 if some files were changed while being read. Previous versions exited with code 2 (fatal error), and only if some files were truncated while being archived. The quick solution was to download tar-1.15.1, build and use it. Does 3.0.0 work with tar 1.16? Torsten Am Freitag, 1. Dezember 2006 13:55 schrieb Torsten Sadowski: Hi, the new tar seems to be a bit more nervous than the old one. One Problem could be solved with LANG=C but another point are probably changes in the backed up filesystem. Is there a possibility to ignore this error? Cheers, Torsten /bin/tar: ./totty: file changed as we read it [ skipped 1 lines ] Tar exited with error 256 () status [ skipped 46 lines ] tarExtract: Done: 0 errors, 1557378 filesExist, 63760417431 sizeExist, 45188423124 sizeExistComp, 1615232 filesTotal, 63767351947 sizeTotal Got fatal error during xfer (Tar exited with error 256 () status) Backup aborted (Tar exited with error 256 () status) - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
Re: [BackupPC-users] tar error 256
Craig Barratt schrieb: Bradley writes: Running into a problem with my larger machines doing backups. 90% of the time, the backup ends with the following message: backup failed (Tar exited with error 256 () status) I believe I read somewhere that it was due to a file changing during backup, probably in combination with the latency introducted in backup across the network. The reason I went with tar in the first place is that I read that rsync consumes more memory the larger the file list is, and this box has 256MB of RAM. My question at this point is the best approach to fixing this problem. I have been running backuppc since the beginning of the year, so I have at least 2 fulls and a weeks worth of incrementals, so, at least in theory, the number of files being rsynced should not be overly large. So should I convert my problem children to rsync, or should I convert everything over to rsync? Or is there a workaround for tar? What version of tar are you using? Torsten reported that the newest version has changed the exit status in the case of certain relatively benign warnings that are therefore considerd fatal by BackupPC. Could you also look through the XferLOG file and confirm that it is this same warning that tar is reporting? I still need to fix this issue for 3.x. I'm getting the same error from one client since last week. It's an debian etch server that was updates just before the problem started. tar version 1.16, no problems with the old 1.15. Ralf - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
