Recent Changes for "Backup" - Sycamore Wiki

Backup

PhilipNeustrom — 2008-12-24 00:44:09

sqlite

Differences for Backup

Deletions are marked with - .	Additions are marked with +.
Line 27:	Line 27:
	+ == SQLite database backup == + + {{{ cp sycamore_dir/share/data/wiki.db your/new/location/wiki.db }}} + + :) SQLite uses just a single file for the whole database. +

PhilipNeustrom — 2007-12-17 02:05:57

linked export

Differences for Backup

Deletions are marked with - .	Additions are marked with +.
Line 2:	Line 2:
	+ + For a usable neat little wiki export, see the ["export"] page.

AdamDewitz — 2006-09-28 02:55:27

+ Export link

Differences for Backup

Deletions are marked with - .	Additions are marked with +.
Line 28:	Line 28:
	+ + An ["Export"] function is currently being investigated.

AdamDewitz — 2006-09-20 04:12:56

Renamed from "backup"

Differences for Backup

No differences found!

AdamDewitz — 2006-09-20 03:54:41

- _ in ["Sycamore maintenance"]

Differences for Backup

Deletions are marked with - .	Additions are marked with +.
Line 13:	Line 13:
- I noticed that some of the pages would render with errors after I used a database I just restored. Running the ["Sycamore_maintenance"] and choosing ''Rebuild all page caches'' seemed to clear that up.	+ I noticed that some of the pages would render with errors after I used a database I just restored. Running the ["Sycamore maintenance"] and choosing ''Rebuild all page caches'' seemed to clear that up.

2006-09-05 23:43:55

added a bit

Differences for Backup

Deletions are marked with - .	Additions are marked with +.
Line 1:	Line 1:
- This page will hopefully one day have all the info you need to make decent backups of your databases and files.	+ This page will hopefully one day have all the info you need to make decent backups of your databases and files. The two methods described below, for MySQL and PostgreSQL, will dump sensitive user information as well, so be careful who you give your backups to!
Line 3:	Line 3:
- ----- - - '''MySQL database backup'''	+ == MySQL database backup ==
Line 20:	Line 18:
- -----	+ + == PostgreSQL database backup == + + {{{pg_dump my_sycamore_db > my_sycamore_db.sql}}} + + This will dump everything! + + == Future == + + In the future we'd like to have a backup that uses python to dump to a standard format (and import, as well). XML might be fine for this purpose.

MichaelWoods — 2006-09-05 22:20:53

Differences for Backup

Deletions are marked with - .	Additions are marked with +.
Line 9:	Line 9:
- This will dump all the tables but none of the tables that end in "Changes" because they have the table type of VIEW.	+ This will dump all the tables but none of the tables that end in ''Changes'' because they have the table type of VIEW.

MichaelWoods — 2006-09-05 22:20:15

initial page creation

Differences for Backup

Deletions are marked with - .	Additions are marked with +.
Line 1:	Line 1:
	+ This page will hopefully one day have all the info you need to make decent backups of your databases and files. + + ----- + + '''MySQL database backup''' + + {{{mysqldump -u username -pPASSWORD -h mysql.mydomain.com my_sycamore_db > my_sycamore_db.sql}}} + + This will dump all the tables but none of the tables that end in "Changes" because they have the table type of VIEW. + + To restore from this backup I am using phpmyadmin to run the sql file this generates. + + You will also need to run the CREATE VIEW code from your sycamore/buildDB.py file. Search for {{{if config.db_type == 'mysql'}}} around line 559, then copy and run those SQL queries on your database. + + I noticed that some of the pages would render with errors after I used a database I just restored. Running the ["Sycamore_maintenance"] and choosing ''Rebuild all page caches'' seemed to clear that up. + + I'll try and add the command line info later. + --["MichaelWoods"] + + -----