- It's automatic. No setting for it. Does it sound ok?
- Any info related to non-exported modules is skipped.
- Any info related to non-exported users is skipped.
for scheduled backups and only done in SITE backups. Structure is:
<MESSAGES>
<MESSAGE>
Content of the message with one flag to difference read & unread
</MESSAGE>
<CONTACTS>
<CONTACT>
Content of the contact
</CONTACT>
</CONTACTS>
</MESSAGES>
message_get_participants() should include contact users too!!
- Old (>4 hour) directories are deleted at the beginning of the
execution, so the disk full problem should be out!
- There are 2 types of errors:
- Controlled errors: The backup process finish although something
has been wrong.
- Uncontrolled errors: The backup process dies (memory fault, apache
problem, electric problem...:-)).
- Now scheduled backup is able to detect previous uncontrolled errors to
avoid repeating the same course always. It'll be deferred to the next
execution.
- Every time that a backup cycle has finished, admins will receive an email
with the summary of the execution.
- The 'ERROR' text will be present in email subjects if something was wrong.
With this, all should be ok (I hope).
Merged from MOODLE_14_STABLE
configured to 48 hours). Force to execute the clean before doing the
backup itself. This should avoid the disk full of temp backup files
issue. See bug 1520.
http://moodle.org/bugs/bug.php?op=show&bugid=1520
Changes merged from MOODLE_13_STABLE.
Solve an important issue about scheduled backups not working properly
when encoding links...
Added support for event->visible in backup & restore.
TODO: Add wwwroot to backup/restore to use it when decoding.
Change the system to encode forum calls.
- Now course events are supported in backup & restore.
- in manual backups
- in scheduled backups
- Fixed important bug when restoring groups.
- Added support to the "user change password" action
(with some changes done in login/change_password.php)
Please, test it !!!!
old is that status in backup_logs table. If there is no activity
in that period, then the script status is unlocked automatically.
This prevents to become RUNNING for ever !!!
TODO:
- Insert info about process in backup_log
- Be able to see that info from admin/backup.php
- Email to the admin with the execution progress
- Create all languaje strings
Bye :-)
Now backup of one course is ENTIRELY encapsulated inside backup_scheduled.php.
And a backup of EVERY course can be executed invoking try.php.
Backing up to a custom directory is working too !!
They are preliminary versions, of course, but seem to work fine :-)
Now I'm going to make all the necessay structures to support the cron system
and to be able to inform the admin about every scheduled backup process.
Ciao :-)
