How to Back Up Exchange Mailbox Data to PST - and When OST Is Only a Recovery Source
An OST file is not something you need to back up — Microsoft treats it as a synchronized copy of data that's already on the server.
Converting an OST to PST is a useful point-in-time export when you need a portable copy of a healthy mailbox, and a recovery technique when the server-side mailbox is gone and only the workstation OST survives. Neither is a substitute for a real Exchange backup with a retention and restore policy.
Microsoft Exchange Server is the backbone of business email for organizations worldwide, managing mailboxes, calendars, and contacts at scale. Outlook connects to Exchange and keeps a local, synchronized copy of your mailbox in an OST (Offline Storage Table) file, giving you offline access to emails, contacts, and calendars even without an active server connection. Because the OST is just a copy of what's already on the server, Microsoft's own guidance is that it doesn't need to be backed up in its own right — protecting the mailbox means protecting the authoritative server-side data, not the local cache.
That said, there are two genuinely useful things people mean when they say "back up my Exchange mailbox using OST": exporting a healthy mailbox to a portable PST for a point-in-time copy, and recovering data from a workstation OST when the server-side mailbox is no longer reachable. This guide covers both, and where a real Exchange backup product is actually the right tool instead.
EdbMails OST to PST Converter is built for the export and recovery cases below — a portable copy of a live mailbox, or pulling data out of an orphaned or damaged OST. For continuous, policy-driven protection of the Exchange mailbox itself, see EdbMails Exchange Server Backup instead.
OST vs. PST vs. Exchange Backup
| Source/Method | Purpose | Main limitation |
|---|---|---|
| OST | Local synchronized cache | Not an independent or complete backup |
| PST export | Portable point-in-time copy | Manual and static; may only reflect the current cache |
| Exchange backup | Recoverable server-side protection | Requires an actual backup policy, storage, and a restore process |
A PST export is a snapshot you made once, not a scheduled recovery point — it has no RPO/RTO of its own the way a real backup policy does. If you need predictable recovery points and restore times for the mailbox, that's what Exchange-aware backup is for, not a periodic manual export.
Three Different Tasks, Three Different Tools
| Task | Correct approach |
|---|---|
| Protect live Exchange mailboxes continuously | Exchange-aware backup |
| Create a portable user mailbox copy | Export the live mailbox to PST |
| Server/mailbox unavailable but the workstation OST survives | Recover the cached data from the OST |
When Each Approach Actually Applies
- If Exchange goes offline temporarily, that interrupts synchronization — it does not by itself orphan the local OST. Once the server is reachable again, Outlook resumes syncing normally.
- If the server-side mailbox or database is genuinely lost — an Exchange server crash or an EDB file corruption that can't be recovered server-side — the workstation OST may be the only remaining copy of that user's recent data, which makes it a recovery source rather than a backup.
- Local OST files can still become corrupted from system shutdowns or hardware issues. If malware or ransomware is suspected, remediate the security incident on the endpoint first — converting a local OST to a local PST is not ransomware protection.
- A cached OST reflects the mailbox as of its last successful sync within the current cache window — it may be current or stale depending on your connection and Cached Exchange Mode settings, not something that's always out of date.
- Deleted items aren't necessarily gone: Exchange's Recoverable Items structure, retention policies, or holds may still preserve them natively before you'd ever need to fall back on an OST.
Method 1: Continuous Protection with Exchange-Aware Backup
If what you actually need is scheduled, policy-driven protection of the mailbox — the kind that supports point-in-time recovery, retention, and restore testing — that's a job for a real backup product, not a periodic manual export. EdbMails Exchange Server Backup supports incremental, granular, and encrypted backups of Exchange mailboxes for this purpose.
Method 2: Export a Healthy Mailbox to PST
When the mailbox is healthy and reachable and you just need a portable, point-in-time copy, Outlook can export the account directly, or EdbMails can do the same with more filtering and bulk options. One thing worth knowing either way: if Cached Exchange Mode is on, the export only covers what's in the current cache. Move the "Mail to keep offline" slider to All first if you need all available primary-mailbox history, and handle any separate Online Archive mailbox through its own supported export or backup workflow.
Steps to export an Exchange mailbox to PST with EdbMails
- Step 1: Download and Install the EdbMails converter for OST on your computer.
- Step 2: Before exporting, select the OST file and preview the mailbox/folder data.
- Step 3: Select the PST file location where the exported data should be saved.
- Step 4: Optionally narrow the export with advanced filter settings
- Step 5: Export the selected mailbox data from the OST to PST.
If you need to preserve recoverable data from an offline OST file, you can convert OST to PST and save the required mailbox data in PST format.
Method 3: Recover Data from an Orphaned or Unreachable OST
If the authoritative mailbox itself is gone — the account was deleted, the server is decommissioned, or the database can't be recovered — and a local OST survives, the task shifts from backup to recovery. EdbMails can scan and preview that OST without needing Outlook or the original Exchange profile, and either export the recoverable data to PST or migrate it directly to a live Exchange or Microsoft 365 mailbox. Outlook with a configured profile is only required if you choose the PST export path; direct migration doesn't need it.
Conclusion
An OST doesn't need its own backup — it's already a copy of data that lives on the Exchange server. What actually matters is picking the right tool for the task in front of you: Exchange-aware backup for continuous, policy-driven protection of the mailbox; a PST export when you need a portable, point-in-time copy of a healthy mailbox; and OST recovery specifically for the case where the server-side mailbox is gone and a workstation OST is the only copy left. Treating a periodic manual OST-to-PST conversion as your organization's backup strategy leaves real gaps that a proper backup policy is built to cover.
Frequently Asked Questions
Is an OST file a backup of Exchange?
No. An OST is a local synchronized cache of data that already lives on the Exchange server. Microsoft doesn't treat it as something you need to back up in its own right — protecting the mailbox means protecting the server-side data.
Does Microsoft recommend backing up OST files?
When should I export an Exchange mailbox to PST?
What if the Exchange server is gone but the OST survives?
Does PST export include the entire mailbox?
What is better for scheduled Exchange backup?
