{"id":1058,"date":"2021-04-05T12:19:16","date_gmt":"2021-04-05T10:19:16","guid":{"rendered":"https:\/\/devpath.pro\/?p=1058"},"modified":"2021-04-05T12:19:16","modified_gmt":"2021-04-05T10:19:16","slug":"save-yourself-from-a-disaster-3-redundancy-of-database","status":"publish","type":"post","link":"https:\/\/fabiocicerchia.it\/web\/save-yourself-from-a-disaster-3-redundancy-of-database","title":{"rendered":"Save yourself from a disaster #3: Redundancy of Database"},"content":{"rendered":"

This is the third part of the series Save yourself from a disaster: Redundancy on a budget<\/a>.<\/p>\n

How can we make sure our most important asset (which is the DB) is safely secured in case of a disaster?<\/p>\n

We could do mainly 2 things (and you better do both of them):<\/p>\n