This page is for discussing the contents of UnBackup.
Perhaps this page should be renamed Restoring Database, UnBackup seems out of place. —AdamDewitz
Shutdown your wiki if it's running Not sure what needs to be should down. The server will should kill the process (for fcgi at least) if a file has been modified. You can also you killall via command line to kill the process/ E.g # killall -9 index.fcgi On PrintWiki we also have a PrintWiki is Offline gateway page that we tell the server to serve if we are doing anything major. We use a Rewrite rule to handle and direct requests. —AdamDewitz
Update With MySQL, restores can be partially done via phpMyAdmin. We have found that the Views in the database are not included in a database dump. So when we restore a database, the views need to be updated manually. We are working on a set of admin backup scripts that will automate the entire process (We dump the database every night and move a copy offsite). We plan on sharing these scripts once we have deemed them to be stable. —AdamDewitz
Let's move this discussion to Backup under "Future". There's two levels of backing up: DB-level and content-level. We ought to develop a content-level backup / import that dumps to an XML format and imports from such a format.. More on the Export
