Loading...
 
Skip to main content

Features / Usability

Forum List Topic List

 
Thread actions
Print this page
  • Print all pages

    • Backup

    Posted by David Morris posts: 12 United States
    I recently created a TIKI site and am working on a backup scheme. This particular site supports a non-profit group and a down day won't be too big of a deal. Since the standard backup appears to be out of commision, I set up a job to RSYNC process but I am not sure what directories I need to include. Right now I only have the tiki Web site directory but I know there are others I should back up.
    Reads: 1944
    Posted by Damian Parker posts: 2881 United Kingdom

    Hiya,

    The directory doesnt need to be backuped up. well maybe img/wiki img/wiki_up and any modified templates/theme files

    The biggest thing to backup is the database. My favourite is a mysqldump cronjob with bzip2 option every 6 or 12 hours.

    --
    Damian
    TikiWiki Development/Hosting/Support Services

    Posted by scalar posts: 16

    hello,

    what exatly is a "mysqldump cronjob". Is that something tikiwiki features or do you do that over phpMyAdmin?

    thanks

    Posted by Damian Parker posts: 2881 United Kingdom

    Hi,

    It is neither.

    mysqldump is a console command, (it is also available in windows) that is part of the Mysql package. it basically allows you to dump a database, or all the databases to a text file, which can then be used to restore the database in case of a disaster.

    Mysqldump can be used in a cronjob, which is run at a specific time or interval. In windows the same thing can be setup using "Scheduled Tasks" and a .bat file.


    --
    Damian
    TikiWiki Development/Support/Hosting Services


    Posted by David Morris posts: 12 United States

    Thanks for the tip. After posting my original message, I decided to list all files on the server that had changed in the last month. That gave me a list of volitile directories. From that I found that /var/www/tiki, /var/lib/mysql, /var/spool, and /var/logs seem to be the only important directories with changes (there were also some temp files).

    From that list I created a job that uses rsync to copy everything to my laptop running cygwin. The backup runs each night and takes about 1 minute. I still need to try a restore but a quick look at the database tells me this process seems promising. Does this sound like a reasonable approach? I would be happy to share what I have if anyone is interested in a more throrough critic.

    Posted by Mathias posts: 22 Switzerland

    Hey

    I also do the backup with mysqldump, and I realy advise you to do it this way! because its the proper way to save the content of a database!

    mysqldump --opt -u -p > 'outputfile'

    this is the line I use to do so (cronjob) after that run, I backup the whole server on tape so I even have History. I realy like that solution, because I can even use that file for my testinstallations of new releases.

    greez matz


    Posted by David Morris posts: 12 United States
    Thanks again. I added the mysqldump and pick that up along with the other directories using rsync.

    Posted by biffer posts: 24

    Hi,

    Regarding mysqldump for backup of all databases, I just tried restoring the backup file and got an error "Specified key too large".

    I'm using mysql 4.1 and from the mysql site it appears this bug is currently shifted to "to be done later".

    Has anyone else encountered this? Is there a way around it?
    Does anyone know if I drop down to mysql 4.0 if this bug exists?

    Thanks a bunch