I think i may have solved the problem by looking at the log file. I will
know when next night passes by, but i'm pretty sure.
Sadly enough, I was wrong about a few things:
1st: the problem was going on longer than assumed.
2nd: It must have started when i changed my backup to USB disk shedule.
3th: i assumed something about the nightly process which is wrong (as
clearly stated in the config file)
The last BackupPC_nighlty which ran ok, started at 1 am. (Because the dd
to USB disk failed at 10 pm and process didn't run untill 3 am)
I checked the config file and found BackupPC was indeed configured to
start with BackupPC_nightly at 1 am (standard).
I assumed it would start the process later on, when i restarted the
backuppc process after dd.
So, anyone who is making external backups:
BackupPC must be running at the first number of the wakeup schedule else
the nightly cleanup will not start and no mail alerts will be sent.
It may be a good idea to have a mail sent (at another time than
BackupPC_nightly starting :) when the process hasn't run for x weeks.
On the other hand, i should have noticed much earlier at the start web
page (but i don't check that one daily).
Greetings,
Koen Linders
Standard Start 1 a.m.
# The default value is every hour except midnight.
#
# The first entry of $Conf{WakeupSchedule} is when BackupPC_nightly
# is run. No other backups can run while BackupPC_nightly is
# running. You might want to re-arrange the entries in
# $Conf{WakeupSchedule} (they don't have to be ascending) so that
# the first entry is when you want BackupPC_nightly to run
# (eg: when you don't expect a lot of regular backups to run).
#
$Conf{WakeupSchedule} = [
'4',
'5',
'6',
'7',
'8',
'9',
'10',
'11',
'12',
'13',
'14',
'15',
'16',
'17',
'18',
'19',
'20',
'21',
'22',
'23',
'1',
'2',
'3'
];
On Thu, 20 Mar 2008 07:41:49 +0100, Craig Barratt
<[EMAIL PROTECTED]> wrote:
> Koen writes:
>
>> Ok. Another shorter post about this problem (more info 7/03 -
>> BackupPC_nightly not running)
>>
>> BackupPC_nightly doens't run anymore. Backuppc also doens't start the
>> mail
>> alert system since it seems to start after a succesfull nightly cleanup.
>>
>> The only thing I think which might disrupt this is a cron.daily that
>> start
>> at 9.30 pm
>> stops backuppc, unmount the partition and does a dd to a seperate usb
>> disk. Around 2.30 am, it's ok. Partition is mounted and backuppc
>> started.
>>
>> Backuppc nightly has run in this configuration without problems for a
>> few
>> months (dd stopping at the same hour). And running manually:
>> su backupppc
>> ./BackupPC_serverMesg BackupPC_nightly run
>> works perfectly (and sends a mail when finished)
>>
>> I know I could make a cron.weekly or something to manually start it. But
>> I'd like to find the problem that causes this...
>>
>> Any ideas? Things I could check?
>
> You shouldn't have to run it manually. Can you send me one
> of the daily log files?
>
> Craig
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
