SMWCon Fall 2016/SMW high availability for disaster recovery and production-data-based development

Here are some things that could prove to be useful for your daily work with SMW.


 * 1) During a meeting that ends at 4PM you evolve SMW content on your company wiki and want that content to be backed up immediately and not only at the time of some scheduled backup job at 2AM.
 * 2) Waiting for a flight you evolve SMW content on your notebook-based wiki and want that content to be backed up immediately and remotely.
 * 3) When developing SMW functionality, you want to work on the most recent production data/environment instead of some development wiki instance.
 * 4) If your company wiki crashes you want to have your latest backup up and running within minutes.
 * 5) You might want to store fully functional snapshots of your company wiki on a weekly basis.
 * 6) Working in the field you might want to draw a read-only&lowast; snapshot of your company wiki within minutes.
 * 7) You can use specialized tools for different functional aspects involved with backing up your SMWs, i.e. size management, encryption, synchronization, scheduling, restoring, etc.

My proposed solution regarding these aspects is roughly visualized on my page about building, backing up and restoring SMWs (see second illustration on that page).


 * Backup Instruction "Encrypted, scheduled/ad hoc, full/incremental, local/offsite Duplicity backup"
 * Restore Instruction "Restore a SMW from a GnuPG-encrypted Duplicity backup set"

&lowast; This restriction might drop once multilateral, asynchronous, bi-directional synchronization is implemented. (Keyword: GitifyMediaWiki)