Disaster recovery assumes you have tried the process and verified it works.

I had a false server issue and I put my disaster recovery in to action. My sleeping instance told me I couldn't update the subscription as the AMI was no longer available in the Marketplace. Trying to restore the nightly backups failed with bad signatures. It seems the software I was using to do the auto backups was uploading garbage to S3.

Thankfully the issue with my server was my IP was jailed by the hosting software preventing access. Once I made the IP trusted everything returned to normal.

I spent the rest of the day certifying my disaster recovery worked and not just assuming it would.

Disaster recovery assumes you have tried the process and verified it works.

I had a false server issue and I put my disaster recovery in to action. My sleeping instance told me I couldn't update the subscription as the AMI was no longer available in the Marketplace. Trying to restore the nightly backups failed with bad signatures. It seems the software I was using to do the auto backups was uploading garbage to S3.

Thankfully the issue with my server was my IP was jailed by the hosting software preventing access. Once I made the IP trusted everything returned to normal.

I spent the rest of the day certifying my disaster recovery worked and not just assuming it would.

Agreed.  Testing the restore is a critical part of any backup and recovery solution.

Yeah I should probably go ahead and export my test environment after making changes to it (invoices or whatever just to create some delta between sage and the database), then reload it - which is what I would do from DATTO restore. I'm not super concerned with the database restore - I'm comfortable with SQL restores.