History: Backups
Preview of version: 9
Table of contents
Admin Documentation
- backups are encrypted
- set your php.ini to allow for enough time for the process to finish, as well as the size of the download.
Note
Backups are broken in Tiki Eta Carinae and until now Polaris too.
Damian's Ideas and Guidelines
Damian says: Dont forget that as well as a backup of the database, we also need to take into consideration any Image Galleries, File Galleries, Forum upload locations too. so what we can have a 1 click backup and restore procedure.
One problem tho, is those users on shared hosts, will not be able to increase there PHP script runtime, whats going to be the best solution here?
Damians Idea: Have a calling page that automatically calls subpages to handle different sections of the backup example pages:
- tiki-perform_backup.php calls in this order at given time intervals:
- tiki-perform_backup.php?backup=wiki - Backups wiki pages
- tiki-perform_backup.php?backup=articles - Takes care of articles
etc - tiki-perform_backup.php?backup=imggals&offset=0&qty=10 - backup the first 10 images in the image gal folder
- tiki-perform_backup.php?backup=imggals&offset=11&qty=10 - backup the next 10 images in the image gal folder
until completed
same style procedure for file gals, forum uploads etc
I think that method would get past need for uping the script timeout.
Any comments?
Other approaches
- hey ! what application is that screenshot from ?
Approach of Felix:
I installed phpMyBackupPro v.1.8 http://www.phpmybackuppro.net and modded 1 line of tiki-login: including a call of the scheduled backup script of pMBP. Now I get my daily gziped backup of the Database delivered right into my mailbox.
phpMyBackupPro has also a feature for directory backup per FTP; I've not yet tried it for attachment and gallery folders located outside of wwwroot.
I included the backup feature into the Login-script because only logged users can post on my site - thus the script is only called once for every user, and performance is only slightly affected for the first user each new day who triggers the daily backup (has to wait some seconds until backup is finished). If nobody logs in there's no need to update the last backup.