I have the same problem and cron is running (Sinc32.exe)
The automatic backup of the configuration page (site level) is not working and I made some unsuccsessful research and here is my configuration.
- 1 the manual backup (course Level) is working (I can see the zip file in the default path /moodledata/2/backupdata)
- 2 the log of the automatic backup give this
- 3 I am using windows 2000 with easyphp7.1 and Moodle 1.3 development (2004050500)
- 4 Sinc32 live is running
Thanks for your help
I highly recommend you to upgrade to 1.3 beta, because some HUGE changes were done in the backup system (specially in scheduled backups) to support some new features (mainly encoding/decoding links).
Please, do it. Any comment will be welcome...
The scheduled and manual backup are working for me with the 1.3 beta release.
I wanted to do more tests but it seems that you can do only one automatic backup per day. I changed the hour of the backup but this one is scheduled for the next selected day.
The backup was started today so the next->date is wrong in the log page (stop I just see that it is updated by the cron ? anyway it's disturbing).
(am I clear ?)
For the help, I had this problems as a w2k user :
1. Not forget to start the cron thing (it's evident but ...)
2. What's the default dir ? "leave blank to save in its course default dir" it's usually moodledata/courseNo/backupdata/ ?
3. Not all moduls are saved ? (this information is in the manual process)
4. The automated backup erased my manual backup I did not expect this (I did the test 3 times) !!
5. And do not trust backup when it is important, this is my personnal opinion
Now, everytime that the execution time is changed in the setup page, it's updated (without waiting for cron's next execution) and showed properly in logs page. Hope this makes things a bit less disturbing...
Now some answers about your problems:
1.-Sure, it's evident but...
3.-All modules are saved in scheduled backups.
4.-The scheduled execution makes a filename comparison so, if you modify your manual backup name (leading it with a "m_", for example), I think that the scheduled process won't delete it.
5.-Although courses backup/restore is the way to move courses between servers, it's highly recommended to have a "full backup" of every Moodle production system (DB + moodle dir + moodle_data dir) and to save them in a safe place everytime you are going to make any important change in your system (upgrade, delete courses...), sure!!
3. "All modules are saved in scheduled backups".
I believe that a home made module needs to implement the backup/restore code in order to be saved. (for the" little story" I am trying to make a new module, and I am not sure if I will implement the backup/restore stuff maybe it's a bad idea ?)
5. "Although courses backup/restore is the way to move courses between servers"
This was not clear for me and I thought (I am leasy) it could be a more or less a "full backup".