10.6 Recovering from a Catastrophic Loss of the iFolder Server

If the iFolder server configuration or data store becomes corrupted, use your iFolder backup files to restore the database to its last good backup. Restoring the iFolder server to the state it was in at the time of the backup also reverts the iFolders on any connected iFolder clients to that same state.

IMPORTANT:All changes made since the time of the backup will be lost on all connected clients.

Consider the following implications of restoring iFolder data:

Before restoring the iFolder server, consider notifying all users to save copies of any files or directories they might have modified in their iFolders since the time of the last backup. After the iFolder server is restored, they can copy these files or directories back into their respective iFolders

  1. Notify users to save copies of iFolders or files that have changed since the time of the backup you plan to use for the restore.

  2. Stop the iFolder server by entering the following command as root user:

    /etc/init.d/apache2 stop
    
  3. Remove the following corrupted data:

    • Simias store directories

      The default location is /var/simias/data/simias.

      If there are multiple store, ensure that the corresponding data is also removed.

  4. Use your normal iFolder system restore procedures to restore the following data to its original locations:

    • Simias store directories

      The default location is /var/simias/data/simias.

      Restore the additional Simias store directories to their respective locations, if multiple store paths has been configured.

      IMPORTANT:Be careful not to modify anything else under the Simias store directory.

  5. Start the iFolder server by entering the following command as root user:

    /etc/init.d/apache2 start
    
  6. Notify users that they can return their saved files to their iFolders for upload to the server. Users should coordinate this with other shared members of the iFolder to avoid competing updates.