What it covers
See the latest recorded data archive, retained archived-record counts and configuration history in Data Hub Recovery, with infrastructure verification kept separate.
Reporting and data
Continuity controls
Review the workspace evidence behind exports, recovery and read-only degraded operation.
How it works
Know which recovery evidence is available
The Continuity panel in Data Hub Recovery gives workspace administrators a concise view of application-level evidence. It shows the latest audited portable JSON export, retained archived records, recorded configuration versions and the migration ledger visible to the application. Those checks help an owner spot gaps before an unexpected interruption. The panel also explains the read-only boundary for degraded operation. It keeps that evidence separate from infrastructure backup and restore verification, which cannot be established simply by displaying a green status inside the CRM.
In practice
A portable archive includes supported business records and document metadata. Secure file binaries need their controlled file-export path. Offline workspace snapshots remain read-only, and queued asset scans require review after the connection returns.
When to use it
Useful situations
- Check when a portable workspace data archive was last prepared.
- Review retained record and configuration history before planning recovery work.
- Understand what the application can show during a connection interruption.
A working path
How the work moves
Inspect the summary
Open Data Hub Recovery as a workspace administrator and review the latest export timestamp, available archived records and configuration-version counts. Use these as starting evidence rather than assuming every item has already been restored successfully.
Choose the relevant recovery path
Use the portable export, eligible record recovery or supported configuration-history controls for the problem you actually need to address. Recovery actions still follow their own plan, permission, retention, dependency and conflict checks.
Review interruption limits
Check the degraded-operation explanation before relying on an offline snapshot. Read-only access can provide context, but live record changes remain blocked while disconnected. Treat infrastructure restore evidence as a separate operational responsibility.
Illustrative scenario
An owner’s continuity review
A business owner notices that no data archive has been prepared recently. They download the supported workspace JSON and review archived-record availability, then separately confirm the organisation’s infrastructure recovery arrangements through its operational process.
Before you start
What to check
- The panel is an application evidence summary; it does not prove that database backup retention or disaster recovery has passed a live restoration test.
- A JSON archive does not contain document binaries, passwords, session secrets or provider credentials.
Can the panel restore the whole infrastructure?
No. It brings workspace recovery evidence together. Infrastructure backup and restoration follow a separate guarded operational process.
Can an offline browser change records?
No. Workspace snapshots are read-only while disconnected; queued asset scans also need an operator’s later review.
Get started
See your customer work in one place.
Start with the core CRM for free, then add the tools your team needs.