Erik P. Olsen wrote:
I've had a strange experience last night. Prior to the nightly back-up runs at
approx. 11 o'clock I made a minor change to bacula-dir.conf and then did a
reload. Basically the change introduced a different schedule time for my
back-up
jobs. They started as expected and finished succesfully. But this morning I
saw
that the jobs had been launched again at 1 o'clock and luckily they did not
run
because there was no tape mounted.
The strange thing is that there is not schedule at 1 o'clock and there has
never
been a schedule at that time. Can it be a problem with the reload command?
This problem had nothing to do with Bacula! The culpret turned out to be VMware
running a Windoze 2000 guest operating system. It screwed up the clock and made
bacula schedule back-up jobs at the wrong time.
--
Erik.
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
