Who is this article for?

Admin users considering disaster recovery.

Server, file and database access will be required to complete the steps.

When considering disaster recovery, our Cloud Ops and Implementation Team have comprehensive plans in place to address server failures, coupled with vigilant monitoring to ensure prompt detection. Here are some valuable tips for managing disaster recovery if you are hosted elsewhere.

1. Monitoring
2. Backup and restoration

1. Monitoring

Aspects you may consider monitoring include:

1. The login page: Ensure it loads properly as failure to load may indicate the site being down.
2. Free drive space on the boot drive server: Running out of space could cause the operating system to fail.
3. Free drive space on the drive holding the website files (if different from the boot drive): Combined JavaScript and stylesheets are generated on the fly for users; insufficient space could break functionality.
4. Free drive space on the drive holding the temporary folder (if different from the above): Insufficient space may cause document processing to fail.
5. Free drive space on the drive holding the document files (if different from the above): Insufficient space could prevent new documents from being added to the system.
6. Free drive space on the drive holding the archive files (if applicable): Insufficient space may prevent reviews from being stored and removed correctly.
7. TaraService process: Ensure it is still responsive, although you can set it to auto restart.

2. Backup and restoration

When backing up the Please Review system, it's important to back up both the database and the document files at the same time. This typically requires stopping Please Review to ensure accuracy. When restoring, it's crucial to ensure that both the database and document files are restored to the same state they were in at a specific point in time. Failing to do so can result in discrepancies where files may exist without the database's knowledge or vice versa. Similarly, if reviews or documents were completely deleted, the database might still reference files that no longer exist, or files may exist in the file store without any record in the database. Failure to follow this method can lead to further complications within the application.