Quick answer
If NinjaTrader opens, save the workspace changes you need, disconnect all providers, and use Control Center > Tools > Export > Backup File. Select the components the repair could affect, save the archive outside the folders being changed, and confirm the named file exists. An exported archive is a preservation checkpoint; successful restoration still needs its own checks.
Choose components by what you need to preserve
A workspace export covers layouts. A backup archive can include more components, but only the items you select. Use the following distinctions to avoid mistaking chart data for trade history or layouts for strategy code.
Component scope described in NinjaTrader’s backup documentation.
| Component | What it preserves | When it matters |
|---|---|---|
| Configuration files | User-specific license, account and option settings. | Settings migration or installation repair; treat the archive as private. |
| Database (Historical trade data) | Local historical executions used for performance reports. | Preserving local trade history before database work. |
| NinjaScript files | Custom indicators, strategies and add-ons, including third-party files. | Repairs or migration involving custom code. |
| Templates and Workspaces | Saved feature settings and overall window layouts. | Rebuilding a working layout and its saved configurations. |
| Log and Trace files | Diagnostic activity for support investigation. | Keeping evidence from before the repair. |
| Historical chart data and Market replay | Stored chart data and Playback data. | Keeping local datasets that may not be available to download again. |
Create the archive and check the preservation checkpoint
The guide’s file-existence check confirms that an archive was written. A plausible filename, size or timestamp alone does not establish that every selected component can be restored. Preserve an older known-good archive too, rather than replacing your only copy with one made after the problem started.
- Save the workspace changes you want to keep. NinjaTrader’s Workspaces menu provides Save for the selected workspace; unsaved changes should not be assumed to be in its saved file.
- Disconnect all connectivity providers, then choose Tools > Export > Backup File in the Control Center.
- Select the components needed for the repair. Record that selection and the NinjaTrader version with the archive.
- Choose Export, specify the location and a recognizable filename, then choose Backup. The documented default folder is Documents\NinjaTrader 8 Backup.
- Allow the export to finish and inspect the chosen destination for that exact filename. Record its size and completion time; keep a separate protected copy outside the repair scope.
Protect configuration data and understand the reminder
Configuration files can contain license and account settings. Keep the archive in controlled storage and share it only through the support channel that requested it. Public forum attachments and public links are unsuitable for the full archive. Keep the component record separate from any account identifiers.
NinjaTrader offers “Please remind me to back up my files every…” during backup. Its documented behavior is a pop-up reminder on the selected day or monthly date. It does not establish a scheduled unattended export or a completed new archive. Check the destination after each actual export.
The documentation notes that some chart and replay data may be downloadable again, but availability depends on the provider and time period. Confirm that before excluding a local dataset you still need.
Restore selected components and verify the result
Use Control Center > Tools > Import > Backup File, choose the archive and select the items to restore before starting Import. Keep the component selections with the import result; the backup and import selections can differ.
The restore guide shows import progress and warns that archives from older releases may have resource-structure compatibility issues. Preserve the exact error and archive for support when an import fails. The observations below are a proposed verification record, not tests we performed.
Evidence after an import, beyond seeing the progress bar finish.
| Restored item | Useful observation |
|---|---|
| Workspaces and templates | Expected named layouts and saved feature settings open. |
| NinjaScript | Expected custom files are present; any compilation or loading error is captured. |
| Historical executions | The intended local performance history is present. |
| Chart or Playback data | The required instrument and time period can be loaded. |
| Configuration | The intended options are present; account/provider and strategy state are checked separately. |
If NinjaTrader will not open
The in-app exporter requires NinjaTrader to open. If it cannot, keep existing archives and preserve the affected files using the support procedure for that failure. Do not describe a copy of an active database’s main .sqlite file as a complete backup: SQLite recovery may depend on accompanying journals.
The database guide covers access errors, locks, corruption codes and journal preservation. Use it to identify the failure before Reset DB or repair. Restoring a workspace, importing an archive and restarting the platform are different operations.
Official sources
NinjaTrader recovery
Keep your recovery workflow ready
Ninja Watchdog monitors the trading environment and attempts configured platform, account and strategy recovery. Keep backup preservation and restoration checks alongside that workflow. Email alerts are available; SMS and WhatsApp are coming soon.