Start
Back up before the computer makes the decision for you.
A recovery plan protects access when an update, disk failure, lost computer, or damaged local database interrupts normal operation.
Create a usable backup
- Stop changing state. Pause configuration edits and note whether any live strategies or open positions exist.
- Use the backup or export action in the current app. Follow the displayed instructions and protect the exported file.
- Store two copies. Keep one encrypted copy offline and another in a separate trusted location.
- Label the backup. Include the date and app version without putting a password or secret in the filename.
- Test recovery. Confirm the backup is readable and that you understand the restore steps before an emergency.
Know what must be reconciled after restore
A local backup can restore Gimmer state, but an exchange or wallet remains an external source of truth. After recovery, compare local positions, pending orders, balances, allowances, and connected accounts before restarting any strategy.
Do not blindly resume automation
If orders were submitted after the backup was created, the restored local state can be older than the exchange. Reconcile first so the strategy does not act on a false position or balance.
Restore deliberately
- Install a compatible current Gimmer release.
- Choose the restore or import path and provide the protected backup.
- Unlock the restored workspace with the correct recovery credentials.
- Verify strategy definitions, exchange connections, wallet address, history, and runtime configuration.
- Reconcile external accounts, then resume in simulation before live execution.
Do not overwrite the only backup while troubleshooting. Create a working copy and preserve the original bytes.
Back up again when risk changes
- Before and after major application updates.
- After changing wallet or exchange connections.
- After creating or materially changing important strategies.
- Before migrating to another computer or operating system.
- Whenever the existing recovery copy can no longer be verified.