Re: Re: [BackupPC-users] Backing up log files

[Ilya R. <il...@bc...>]

Hello Nguyen,

>Thanks for your response. In fact, there are no real error from BackupPC;
>in xferlog, I only get an error like "/bin/tar: XXXX: file changed as
>we read it" when I aborted manually the BackupPC process for the full
>backup of the server.
IMHO, this is a only tar problem. I had this bug with my old backup program - reoback (tgz -> ftp), thus 
I switched to rsync, and now i found BackupPC as a best rsync `wrapper'.
Actually i backing up a couple (12) linux servers and ... no such problem more. :)

Respect to Craig, you a real man! :)

ps: sorry for my poor english.

Best regards, 
  
======= At 2005-01-05, 19:04:06 you wrote: =======

>Hi Craig,
>
>
>My problem is, more precisely, that I've got a full BackupPC process
>which starts, for example, at 3h in the morning but is still running 10h
>later. I have tried to lauch 2 times manually the full backup, and, ouf,
>the second has terminated normaly (after 345.2 duration/mins).
>
>Because the master BackupPC machine and the client BackupPC machine
>aren't in the same network, I think (maybe badly) that the problem
>occurs with the use of ssh and tar. I have set the tar option
>("ignore-failed-read") but somewhere, with tar, it seems that tar
>cannot end the reading of the log file.
>
>So, I have read somewhere that the use of rsync is preferred than the use
>of  ssh/tar. Do you agree with that ? And do you think that the problem
>could be resolved with rsync ?
>
>Thank you again.
>
>Phong
>
>Le 5/1/2005, "Craig Barratt" <cba...@us...> a ecrit:
>
>>Phong Nguyen writes:
>>
>>> I have an important web site which daily rotating log files, but
>>> everytime my BackupPC tries to make a full backup, it cannot stop
>>> because it reads indefinitely the log  file (or until the log file
>>> rotates, which means at least 24 h). Maybe a solution could be to start
>>> the full backup at exactly midnight (when the log file totates), but
>>> because I have 10 machines to backup, it seems that  BackupPC starts
>>> separately each backups at different time (in the time-intervalle
>>> specified in config file), and so, I don't know how to act.
>>
>>I don't understand the problem.  A linux machine allows multiple
>>processes to read/write the same file concurrently.  Do you mean
>>the file appending causes an error that makes BackupPC keep
>>retrying the entire BackupPC?  If so, please paste the error
>>message from the XferLOG.bad file.
>>
>>Craig
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by: Beat the post-holiday blues
>Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
>It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
>_______________________________________________
>BackupPC-users mailing list
>Bac...@li...
>https://lists.sourceforge.net/lists/listinfo/backuppc-users
>http://backuppc.sourceforge.net/

= = = = = = = = = = = = = = = = = = = =
			
Ilya Rubinchik
il...@bc...
2005-01-05