anchor.diff:  
   ==== "Hot" backups
   
  -The example shell script `snowowl_hot_backup_mysql.sh` exercises all functionality mentioned above, and produces a .zip 
  -archive containing database dumps and copies of index folders in the directory it is started from. Please update the variable 
  -`SNOW_OWL_SERVER_HOME` so that it points to the installation folder of Snow Owl Server before running the script. 
  -
  -The return value is 0 for successful backups, and 1 if an error occurs while backing up content from the server. The script 
  +The example shell script `snowowl_hot_backup_mysql.sh` exercises all functionality mentioned above, and produces a .zip
  +archive containing database dumps and copies of index folders in the directory it is started from. Please update the variable
  +`SNOW_OWL_SERVER_HOME` so that it points to the installation folder of Snow Owl Server before running the script.
  +
  +The return value is 0 for successful backups, and 1 if an error occurs while backing up content from the server. The script
   produces timestamped diagnostic output on its standard output; error messages are directed to the standard error output.
   
   To create backups regularly, add a dedicated non-login user for backups as root:
  
positive.code: 0 4 * * * cd /storage/backups && ( ./snowowl_full_backup_mysql.sh >> /var/log/snowowl-backup/log-`date +\%Y\%m\%d` 2>&1 )
  --------------------------
  
  (If the standard error output is not redirected with the "2>&1" part of the command, errors will be captured by cron 
  and mailed to the snowowl-backup user's mailbox. The destination can be changed by uncommenting the MAILTO parameter 
  and setting it to a different address.)
  
  ==== "Cold" backups
  
  When the server is shut down, the above mentioned REST service for enumerating store content and getting exclusive 
  write locks for the repositories is not available, so a separate script, `snowowl_cold_backup_mysql.sh` is being provided for this case.
  
  ==== Backing up and restoring data in the issue tracker
  
  A detailed list of steps are available at the Move Installation page of Mozilla Wiki (which describes moving the installation from 
  one machine to another, but can also be applied for backup and restore on the same server). The important parts to take note of 
  are the commands used for dumping the SQL database:
  
  --------------------------
  
negative.code: mode of `/storage/backups/snowowl_full_backup_mysql.sh' changed to 0744 (rwxr--r--)
  --------------------------
  
  Add the script to the backup user's crontab (the example runs the script at 4 AM, and outputs log entries to logfiles
  with a year-month-date suffix in /var/log/snowowl-backup):
  
  --------------------------
  