Independent copies
A source incident should not automatically erase or rewrite its recovery history.
Independent backup and recovery
Your operational data is not a backup.
TrunkBackup creates independent recovery copies, verifies the evidence, and rehearses restores away from live work before any approved recovery.
Why a separate recovery boundary matters
A copy beside the thing that failed may fail with it.
Live systems are designed to serve today’s work. Recovery needs a separate path: independent copies, evidence that can be checked, and a controlled way back when the source is unavailable or unsafe.
Recovery that can be examined
Know what is protected before you need it.
Evidence, not a green guess
Integrity checks and durable records show which recovery point was created and verified.
Restore with approval
Rehearse in isolation first, review the result, then approve any action that could affect live data.
How it works
Three deliberate steps from connection to recovery.
Connect
Authorize a specific service and define the source that should be protected.
Protect and verify
Create the independent copy, check its integrity, and retain the evidence with its recovery point.
Rehearse and restore
Restore into an isolated target, examine the result, and require approval before any live recovery.
Where teams begin
Protect the services that hold irreplaceable work.
Mailbox protection
Keep messages and attachments independently recoverable, with an isolated non-sending rehearsal.
Service data
Preserve a verifiable recovery point for application content and configuration that matter together.
Team recovery
Give authorized people a shared view of readiness, approvals, evidence, and recovery history.
Built around trust boundaries
Protection should not require giving every system the keys.
Encrypted
Recovery copies are protected while moving and while retained.
Least privilege
Connections receive only the access needed for the agreed protection and recovery scope.
Auditable
Important backup, verification, approval, and restore actions leave a reviewable record.
Frequently asked questions
Practical answers about the recovery path.
Does a backup guarantee recovery?
No. Verification and restore rehearsals reduce uncertainty and reveal the current posture, but no service can remove every recovery risk.
Can a restore overwrite live data immediately?
The intended path is isolated rehearsal and explicit approval before any action that could alter a live source.
Who can see recovery evidence?
Only authorized account members with the appropriate role and scope.
What can I protect first?
The first evaluation focuses on mailbox recovery. Contact us to discuss the source and recovery outcome your team needs.
Begin with the recovery question
What must your team be able to recover?
Tell us the workload, the acceptable recovery window, and who should approve the result.