What is it?

  • Create system snapshots according to a schedule and/or at any time at the click of a button.
  • Data is encrypted using a self-created key.
  • Clone/restore a system at the click of a button.

What is the motivation behind it?

  • 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.
  • Waiting for a flight you evolve SMW content on your notebook-based wiki and want that content to be backed up immediately and remotely.
  • When developing SMW functionality, you want to work on the most recent production data/environment instead of some development wiki instance.
  • If your company wiki crashes you want to have your latest backup up and running within minutes.
  • You might want to store fully functional snapshots of your company wiki on a weekly basis.
  • Working in the field you might want to draw a read-only snapshot of your company wiki within minutes. (Read-only restriction might drop once multilateral, asynchronous, bi-directional synchronization is implemented.)
  • You can use specialized tools for different functional aspects involved with backing up your SMWs, i.e. size management, encryption, synchronization, scheduling, restoring, etc.

How is it set up?

  1. Set up EasySystemCloning (DSESC) Backup on system servers.
  2. Set up EasySystemCloning (DSESC) Restore on computers that shall be able to clone/restore the system.

    For details see https://smw-cindykate.com/main/easy-system-cloning.