Database state
CMS records and site data are protected as part of a recovery point.
Backups and recovery
Included at launch · Currently being completed and tested
A website is more than one database. DashHarbor recovery is designed to protect the pieces needed to return a managed EmDash site to a known working state.
CMS records and site data are protected as part of a recovery point.
Images and other customer media are protected separately rather than assuming database recovery is enough.
The information needed to reconstruct the managed site belongs to the recovery state too.
Recovery knows which deployed site state belongs with the protected content.
The software version forms part of the site state rather than being treated as unrelated to recovery.
The supported design version is recorded so content is restored against the expected website release.
Verified recovery points
DashHarbor does not treat a database row saying “backup complete” as sufficient protection. Recovery points move through a real lifecycle and only become ready when their required components have been protected and verified.
Before a restore
Before an older recovery point is restored, DashHarbor creates a protection point for the current state. That gives the website another route back if the earlier restore is not the result you expected.
Independent of the editor
The recovery engine sits outside the EmDash administration interface. If the editor itself is unavailable, DashHarbor can still work with the protected site state underneath it.
Read the EmDash backups and recovery guidePlanned scheduled protection
After the core recovery system is proven, DashHarbor plans scheduled protection so recent recovery points are created automatically as part of the managed service.
Managed EmDash
You manage your website in EmDash. DashHarbor manages the hosting, deployment and operational layer underneath it.