Best practice forum (Archived)

[ERROR] Scheduled backup status

 
??
[ERROR] Scheduled backup status
?? 发表于 2012年03月1日 Thursday 16:08
 

Hi,

I keep getting admin emails from the automated backup process where the 'front page' or main site fails to finish backing up:

==================================================

Courses: 23

OK: 21

Skipped: 1

Error: 0

Unfinished: 1

Some of your courses weren't saved!!

==================================================

I had a look at the backup log for the the 'Front Page' course:

 Monday, 27 February 2012, 12:00 AM
12:00 AM:49 Start backup course VP Learning Hub
12:00 AM:49     Phase 1: Checking and counting:
12:00 AM:49         checking parameters
12:00 AM:49         calculating backup name
12:00 AM:49         calculating modules data
12:00 AM:49             book
12:00 AM:49             certificate
12:00 AM:49             choice
12:00 AM:49             data
12:00 AM:49             exercise
12:00 AM:49             feedback
12:00 AM:49             glossary
12:00 AM:49             hotpot
12:00 AM:49             journal
12:00 AM:49             label
12:00 AM:49             lesson
12:00 AM:49             mplayer
12:00 AM:49             quiz
12:00 AM:49             resource
12:00 AM:49             survey
12:00 AM:49             workshop
12:00 AM:49             oublog
12:00 AM:49             chat
12:00 AM:49             scorm
12:00 AM:49             assignment
12:00 AM:49             facetoface
12:00 AM:49             forum
12:00 AM:49             wiki
12:00 AM:49         calculating users

It doesn't seem to get passed the point of counting users, is this becuase of the LDAP authentication sync (approx 20,000 users)?

Is this a problem?

I can make a manual backup fo the Front Page, so i'm not sure with the automated one doens't finish...

thanks,

-Ira

该论坛帖子已被删除
2012年03月11日 Sunday 16:01
该论坛帖子的内容已被删除,无法再访问。
??
Re: [ERROR] Scheduled backup status
?? 发表于 2012年03月13日 Tuesday 17:47
 

Hi Alastair,

This issue seems to have resolved itself when the cron.php script issue were fixed on our server.

I've also increased the extra PHP memory limit from 128mb to 256mb in the admin settings to hopefully avoid any future issues.

Thanks,

-Ira