Choose a plan for your local data
Select the situation that matches your goal. Follow the steps to review storage, save a backup, or prepare a restore.
Selected plan
Review storage growth
Understand how many telemetry rows are retained and how their serialized record size changes across time periods.
Open Telemetry Storage Footprint and choose the locally recorded period you want to inspect.
Compare entry counts and estimated megabytes across hourly, daily, weekly, and monthly rows.
Use average serialized bytes per entry to explain record-size differences, then use Analyse app databases for wider backup-coverage and cleanup review notes.
Protect first Before clearing site data or changing databases, export the backup type that covers the history and setup you need and retain it outside the browser.
This planner does not inspect storage, read files, delete data, or change retention. Your choice stays on this page and resets when you reload.
What each storage view actually tells you
OctoMonitor separates storage evidence from recovery files. The Telemetry Storage Footprint report groups locally retained telemetry by hour, day, week, and month. Analyse app databases produces a read-only Data Backup Report. Backup exports create the files used for recovery.
- Telemetry Storage Footprint counts records and estimates their serialized JSON byte size. It does not measure browser quota, remaining free space, IndexedDB overhead, file-system allocation, or future growth.
- Data Backup Report counts app-data areas, highlights omissions or cleanup review notes, and changes nothing. It is not a restorable backup file and does not clear data.
- The browser storage estimate is used only when a guarded Replace restore needs temporary staging headroom. It is not exposed as a general storage dashboard and may be unavailable in some runtimes.
Telemetry retention
History grows while recording is enabled. OctoMonitor does not currently offer a general retention-days setting or automatic telemetry cleanup.
- Do not manually delete IndexedDB records. Direct deletion can leave related stores, reports, migrations, or recovery evidence inconsistent.
- Deleting a saved report definition does not delete telemetry or device-event history.
- Use only an app-provided, clearly scoped cleanup action. Diagnostic-log, report-history, or cache actions do not mean telemetry history was removed.
Protect data before changing storage
Create and retain the recovery file before browser storage clearing, repair, migration, database deletion, or Replace restore. A successful analysis report is useful evidence, but it cannot restore the data it describes.
- Essential Backup protects setup, configuration, and execution history; it excludes telemetry and device events.
- History/Data Archive includes telemetry, device events, and execution history, with an optional date range for history. Full Backup combines setup and history in one file.
- Replace restore requires a verified Safety Backup before current app data can be cleared or overwritten. Keep a downloaded recovery copy outside the browser.
- API keys, passwords, session tokens, secure-sync secrets, and temporary handoff state are intentionally excluded and must be re-established separately.
Finish backups and install protected updates
Long operations show their current phase and progress while you use other pages in the app. Keep the browser or PWA open until the final file is saved and verified.
Interrupted exports offer a fresh file retry, an original-file retry where available, or browser staging that can resume completed, verified sections. An incomplete file is not a finished backup.
- Follow the recovery actions in Backup & Restore before starting again.
- For a protected update, export the Safety Backup requested for that target version and wait for verification.
- A normal Full Backup or database analysis does not unlock a pending update.