[Deploying Sakai] Restoring from a backup

Paul Gibbs pgibbsjr at hotmail.com
Thu Apr 1 06:38:05 PDT 2010

Are there any special considerations for backing up externally-stored blobs?
To do a backup/restore, can you simply zip up the directory structure,
export the DB, backup the other config files (e.g., Apache stuff,
Tomcat/Sakai config, etc.) and then restore Sakai + tools + config files +
DB + blobs directory to the same locations on the new machine?  Assuming
that the DB and config files are all restored correctly, is unzipping the
blob directory to the new location/setting permissions all that's necessary
to restore those files to working order? 


I realize I'm probably being overly simplistic in my question, but
Leonardo's question has been something I've been wondering about as well.
Right now, we're backing up via disk images. However, the type of backup
I've described above would be valuable in other situations (e.g., moving the
installation to a new OS install).




Paul Gibbs

Lansdale, Pennsylvania


From: production-bounces at collab.sakaiproject.org
[mailto:production-bounces at collab.sakaiproject.org] On Behalf Of leonardo jr
Sent: Thursday, April 01, 2010 4:42 AM
To: production at collab.sakaiproject.org
Subject: Re: [Deploying Sakai] Restoring from a backup


Thanks Stephen for looking in and the suggestion.

I investigated it further and found out that Sakai has 2 options storing
uploaded files: in the db(default), in the file system(setting the
bodyPath at org.sakaiproject.content.api.ContentHostingService property).

The Sakai instance where I backed up the db from uses Option 2, while I
restored the db for my local Sakai instance (using the default
sakai.properties) that uses Option 1. So there goes the cause, next will be
finding/doing the solution. I am still soliciting any advice from anyone who
have done or knowledgeable on this.


--- On Thu, 4/1/10, Stephen Marquard <stephen.marquard at uct.ac.za> wrote:

From: Stephen Marquard <stephen.marquard at uct.ac.za>
Subject: Re: [Deploying Sakai] Restoring from a backup
To: production at collab.sakaiproject.org, "leonardo jr escorido"
<escorido at yahoo.com>
Date: Thursday, April 1, 2010, 12:51 AM

We recently changed our backup script config to include --hex-blob e.g.

/usr/bin/mysqldump --verbose --hex-blob --max-allowed-packet=64M
--debug-info --quick --single-transaction 

May be relevant.


>>> leonardo jr escorido <escorido at yahoo.com> 4/1/2010 5:45 AM >>> 

I am beginning to think that this is more of a db issue than a Sakai, but
still posting it here hoping someone had successfully restored Sakai data
from a backup and will share how they managed to do this.

I backup a db (using Sakai 2.5 schema), restored it in a new db. There were
no errors when restoring, then ran the migration scripts to Sakai 2.6
schema. I am able to use the data from the backup, except for those data
stored as blob type, like resources/files uploaded to Sakai. 
When clicking on the images already uploaded, it is not rendered. 
After downloading document files from the application, the files cannot be

I believe this has been done successfully. I will appreciate it very much
any advice.

Thanks a lot,




This e-mail is subject to the UCT ICT policies and e-mail disclaimer
published on our website at
http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27
21 650 4500. This e-mail is intended only for the person(s) to whom it is
addressed. If the e-mail has reached you in error, please notify the author.
If you are not the intended recipient of the e-mail you may not use,
disclose, copy, redirect or print the content. If this e-mail is not related
to the business of UCT it is sent by the sender in the sender's individual



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20100401/22b31e7a/attachment-0001.html 

More information about the production mailing list