Daily snapshots
Every site, every database, every config — snapshotted nightly and retained on a rolling schedule.
A backup that’s never been restored isn’t a backup. YesGov runs three copies on two media types with one off-site, snapshots daily, exercises the restore on a documented cadence, and hands you the runbook your insurer wants to see before they renew.
The Baltimore, MD outage cost $18M and ran for months. Tested 3-2-1 backups make recovery measured in hours.
Every site, every database, every config — snapshotted nightly and retained on a rolling schedule.
Hot block storage on the production cluster + cold object storage on a separate tier. A failure on one doesn’t reach the other.
Off-site replication to a geographically separate region. A regional outage doesn’t take both copies.
Quarterly restore exercise with documented results. The runbook is real because we run it.
Off-site copies in object-lock retention — ransomware credentials can’t delete history they don’t have permission to touch.
Backup configs, retention policy, drill results, recovery time / point objectives — the package your insurer asks for at renewal.
Attacker encrypts the live database and the hot snapshots they could reach. The off-site cold tier they couldn’t.
A staff member drops a table or wipes a directory. You need yesterday’s state of one specific table, not a full restore.
Power, network, or upstream provider goes down for the production region. You need to fail over before residents notice.
Underwriter requests last quarter’s restore-drill report and the RPO/RTO commitments. You either have the binder or you don’t.
Included in every YesGov plan, no separate DR SKU. Migrate this quarter and your next insurance renewal will go smoother.