Things are starting to behave strangely with the /usr/local/mysql/data folder refusing to back up, 2 cron processes being kicked off at start-up and no SSH service!!! Data corruption in the mydata.gz file? USB key physical failure?
Time to get back to the drawing board… Easier, simpler and more backed-up than ever! Hopefully…
My leads so far:
Web Server Strategy
– OS: TinyCore Linux – run off frugal install on USB
– Required software: Dropbear, Apache with PHP support, MYSQL
+http://www.parkytowers.me.uk/thin/Linux/TinycoreWS.shtml
+http://blog.matchgenius.com/tinycore-nginx-server-with-php-cgi-and-vsftpd/
– WordPress install
+http://blog.matchgenius.com/tinycore-install-wordpress-with-remote-mysql/
– WordPress Backup to Dropbox plugin AND simple-restore tool
+http://wordpress.org/plugins/wordpress-backup-to-dropbox/
+http://wpb2d.com/simple-restore
+Modify .htaccess to allow access to wp-cron.php, see http://wordpress.org/support/topic/why-won%E2%80%99t-my-backup-start
Run filetool.sh -b ONCE (once set-up is complete with empty wordpress install complete with the 2 plugins and restore tool) and leave it as a manual process.
For smoother integration (and a chance to automatically restore after shutdown, so far the restore options are manual only), check http://wordpress.org/plugins/backupwordpress/faq/, this would require to mount //popcorn at boot, restore backup from //popcorn at boot and back up to //popcorn on a schedule…
TEST IT! In theory, this should eliminate any requirement to run filetool.sh -b on a schedule (no cron, no massive backup file, no data corruption). Just backup the wordpress install to dropbox using wordpress built-in plugins and restore at boot time.
To extend WordPress
http://www.wpbeginner.com/plugins/how-to-create-a-to-do-list-in-wordpress/
For overall reference
http://www.noupe.com/wordpress/how-to-backup-your-wordpress-website.html
Once I get the chance to actually do those, I’ll post a follow-up.
Computer Ramblings 