April 2022
  • 26 Apr 2022
  • 1 Minute to read
  • PDF

April 2022

  • PDF

Article summary

Scenario we used for this mock drill:

Scenario 2 and 3 in the Disaster recovery process

Results of the drill

What is the amount of data loss expected in such a scenario?

Result: Data collected on the day of the event. Normally backups occur at 12:00 AM everyday so any data collected after 12:00 AM till the time the disaster struct will be lost.

Were all the databases backed up correctly in AWS cloud?

Result: Yes, at any point in time the last 3 days database backups were available for restore.

Were all the files / evidence backed up correctly on the AWS cloud?

Result: Yes, at any point in time files from the last 6 hours were available for restore.

Were we able to restore databases and files to another already available server?

Result: Yes, we were able to restore all the databases and evidence from the AWS cloud to the second server to get the sites up and running.

What is the downtime that can be expected in such a scenario?

Result: 2-6 hours. However in our mock we were able to recover all the sites within 4 hours but it is always good to have buffer time in such extreme cases.

Were the file mappings with their respective questions restored?

Result: Yes, all the files were accessible and clickable without any issues.

Was all the responses history recovered?

Result: Yes, we were able to restore all the history till one day before the disaster struck.

Were all Probench functionality working?

Result: Yes, all the functionalities were working as before the disaster as this server was already used by other clients.

Once all the recovery is done and all the sites are restored the next step we would take is to order a new server to replace the old one which was lost which would take anywhere between 24-72 hours.


Was this article helpful?

What's Next
ESC

Eddy AI, facilitating knowledge discovery through conversational intelligence