Back up your database exports
Backora protects files, and a database export or dump is a file. Schedule your database engine's own export job to write to a folder Backora watches, and that export is backed up, versioned and verified automatically.
Works with any export format
A SQL Server .bak, a MySQL or PostgreSQL dump, a Tally company data folder — if it lands as a file in a protected folder, it is backed up the same way as any other file.
Versioned exports, not just the latest
Each backup keeps the export as it was at that point, so an export corrupted today does not overwrite a good one from yesterday in Backora's history.
Tally is recognised automatically
Setup looks for common Tally data locations on the computer and offers to include them, since Tally is how many Indian businesses keep their books.
What this page does not claim
- This is not a live database backup tool: Backora does not connect to SQL Server, MySQL, PostgreSQL or any other database engine, and does not take an application-consistent snapshot of one that is running.
- There is no point-in-time database recovery. Recovery is only as recent as your last export.
- Restoring a database from its backed-up export file is done through your database engine's own restore process, not by Backora.
Questions about database backup
How often should the database export run?
As often as you can tolerate losing data between exports. Backora backs up whatever the export job produces, on the schedule you set for the export itself.
Will Backora restore my database for me?
It restores the export file to disk. Loading that file back into the database engine is done with the engine's own restore tool.
Does this work for Tally data specifically?
Yes — Tally stores its company data as files, and Backora's setup detects common Tally folders and offers to protect them directly, no export step needed.