Backup and Recovery

Document ID: M17-CERT-001-D9

Audience: Company administrator and IT liaison (office deployments)

Last updated: 2026-08-12

Applies to: Jakten Platform 2.0

1. Scope

This guide covers customer-controlled backup for Jakten Platform deployments. jakten.net does not store your project, Estimate, or Risk data — recovery depends on backups you maintain.

Standard deployments use host-local SQLite product stores. No external database purchase is required for the standard customer-hosted profile.

Profile	Where your data lives
Single-user	Your Windows PC
Office	Office server running Platform Server

2. What to back up

Single-user deployment

Back up your Jakten Platform application data folder on the PC where Platform is installed. This includes company databases, risk data, estimate data, and documents for your deployment.

Office deployment

Back up on the server — all three SQLite product stores plus documents:

Item	Typical path (Windows Service)	Notes
`platform.db`	`%ProgramData%\Jakten\PlatformServer\data\platform.db`	Platform identity, projects, licensing, publication handles
`estimate.db`	`%ProgramData%\Jakten\PlatformServer\data\estimate.db`	Estimate commercial data
`epc-risk.db`	`%ProgramData%\Jakten\PlatformServer\data\epc-risk.db`	Risk analytical data
Documents tree	`%ProgramData%\Jakten\PlatformServer\documents\`	Reports, logos, migration backups
Configuration	`%ProgramData%\Jakten\PlatformServer\config.json`	Server settings (no secrets in tickets)

If present, include SQLite WAL companion files (-wal, -shm) from the same backup window, or stop Platform Server briefly for a consistent file copy.

Also back up:

Platform Server data and configuration
Server configuration file supplied with Platform Server

Your IT team should store backups off the server according to company policy.

An optional enterprise Tier-A deployment (SQL Server for Platform plus host-local SQLite product stores) requires coordinated SQL Server backups in addition to estimate.db and epc-risk.db. Tier-A is not the standard customer profile; obtain an approved deployment and recovery plan from Jakten before using it.

3. Backup procedure (office server)

Schedule during a low-use window.
Stop or quiesce Platform Server if your backup tool requires consistent SQLite files.
Copy platform.db, estimate.db, epc-risk.db (and WAL companions if used), documents storage, and configuration.
Store backups on separate storage (network share, backup appliance, or cloud backup).
Test restore periodically to a non-production location.

4. Recovery procedure (office server)

Stop the Jakten Platform Server Windows Service.
Restore platform.db, estimate.db, and epc-risk.db to the configured paths (same backup window).
Restore documents and configuration to the original locations (or update configuration if relocating).
Start Platform Server.
Confirm the service is running and a workstation can sign in and open Risk and Assurance workspaces.

Contact [email protected] if licensing must be reconciled after hardware replacement.

5. Single-user recovery

Close Jakten Platform.
Restore your application data folder from backup (includes platform.db, estimate.db, epc-risk.db, and documents).
Relaunch Platform and sign in.
Run Administration → Licensing → Validate if prompted.

6. What Jakten can help recover

Jakten can help with	Jakten cannot restore
Subscription and activation status	Project data
Activation key re-issuance (support process)	Risk models and simulations
New installer download link	Local files not in your backup

Guide	Purpose
Office Deployment Guide	Server setup
Company Administrator Guide	Licensing validation
Troubleshooting Guide	Post-restore errors
Deployment Overview	Standard customer-hosted deployment