Another aspect of a solution to this problem is to use EDB's replication systems to create a continuous backup, perhaps on the cloud.

If the replication process is simple (i.e. regularly update full copy of DB on server to a version of the DB held on the cloud) this is pretty easy, and adds greatly to customer perception of the safety of their data.

I offer my customers cloud-back-up for their systems using this EDB feature, it is easy to implement and means if a corruption occurs an on-line version exists which can form a good starting point for a backup.

Adam Brett wrote:

> Another aspect of a solution to this problem is to use EDB's replication systems to create a continuous backup, perhaps on the cloud.

Good point. I think cloud is perhaps going a bit far, but in my latest project, I use the EDB backup facility to save the database to the store. Plus, I export all the data to a custom file (zip of text documents) which contain all the JSON data in the database. The custom format can be read in easily, or the database restored. Plenty of options available as belt and braces.


--

Matthew Jones

Hello,

I have a customer that has 2 offices in 2 different towns, they not only have UPS on both places, but also the EDB servers do local backups every 6 hours and send the backup files to the other location - both places have a set of all the backups.

--
Fernando Dias
[Team Elevate]

....

Also, there is job that automatically runs at the end of every month that checks the integrity of the database.
Only once it detected corruption in a period of 6 years, and it was very easy to repair, we didn't have to restore from backup.

--
Fernando Dias
[Team Elevate]