From: Tristan S. <ag...@ya...> - 2004-05-10 17:14:50
|
Just out of curiosity, can you check $Conf{RsyncClientCmd} = and make sure you've got -x in the command? I had the same problem you're describing, and I had to add a -x in there to get it to work right, on the advice of Daniel Pittman. I was also getting an ALRM signal. -Tristan On Mon, 2004-05-10 at 13:07, Dan D Niles wrote: > I changed the ClientTimeout to 12 hours. Now I got: > > 2004/5/9 11:00:01 full backup started for directory / > 2004/5/9 23:03:12 cleaning up after signal ALRM > > The initial full backup for this directory took 9.9 minutes. It would > seem that there is some sort of bug with rsync full backups. There is > no way that it should take over 12 hours to do a full backup of 723 M. > Any ideas where I should look? > > Thanks, > > Dan > > Carl Wilhelm Soderstrom writes: > > > > # timeout in seconds. > > # in backuppc 2.0.2, this sometimes incorrectly means the duration of the > > # backup. > > # set to 12 hours, and see if backups no longer fail with 'ALRM' > > $Conf{ClientTimeout} = 43200; > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Sleepycat Software > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver > higher performing products faster, at low TCO. > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/backuppc-users > http://backuppc.sourceforge.net/ |