SQLite Backup Software
SQLite backup software helps businesses preserve databases used by desktop applications, internal systems, and embedded software. Handy Backup automates the copying, scheduling, storage, and recovery of SQLite database files, including consistent database copies prepared with SQLite's native backup tools.
Combine SQLite's built-in backup methods with Handy Backup to maintain recurring database backups on local drives, NAS devices, external storage, or cloud services, without manually transferring files after every update.
Download Trial
How Handy Backup Works with SQLite Databases
SQLite is an embedded database engine that stores data in local files rather than requiring a separate database server. This makes SQLite databases convenient to manage, but copying a database file while an application is writing to it may produce an inconsistent backup.
Handy Backup works with SQLite through file backup tasks and external commands. It does not require a dedicated SQLite plug-in. For databases that remain active during backup, SQLite's native tools can first generate a consistent database copy, which Handy Backup then saves to the chosen destination.
File Backup
Copy SQLite database files using the Computer data source. This method is suitable for databases that are closed or for consistent copies already created by SQLite's own tools.
Pre-Task Commands
Run an external command or script before the backup task to create a consistent SQLite database copy. Configure Handy Backup to wait until the command finishes before copying the result.
Important: SQLite databases in WAL mode may use additional files, including -wal and -shm. Copying only the main database file while the database is active can omit recent changes. For running databases, use a SQLite-native backup method rather than relying on ordinary file copying.
Advantages of Handy Backup for SQLite
Automatic Database Backup
Schedule SQLite backup tasks daily, weekly, monthly, or at custom intervals. Handy Backup can run a database preparation script before copying files, reducing repetitive manual operations.
Local, Network, and Cloud Storage
Save database copies to external drives, NAS devices, FTP/SFTP servers, Google Drive, Amazon S3, and other online backup destinations. Store backups separately from the application that uses the database.
Database Recovery and Migration
Restore a saved SQLite database file to its original folder or choose another destination for migration, testing, or creating a separate application environment. Handy Backup provides a guided restore task for locating and retrieving previous copies.
Back Up More Than SQLite
Manage SQLite database copies alongside application files, documents, email, and other business data from a single interface. Separate backup tasks can have their own schedules, destinations, and recovery settings.
Logs, Versions, and Notifications
Monitor completed backup operations, configure email notifications, and retain multiple database copies. Versioning helps maintain historical recovery points instead of keeping only the most recent backup.
Recommended Solution
Lifetime license
Handy Backup Professional
The Professional solution automates SQLite backup and recovery, alongside managing any other user-type and specific data you utilize in your daily operations. Experience seamless SQLite online backup functionality with our solution.
Three Native SQLite Backup Methods
SQLite provides its own methods for generating consistent database copies. Handy Backup can incorporate the resulting files into automated backup tasks, allowing you to combine database-level consistency with flexible scheduling and storage management.
1. SQLite .backup Command
The SQLite command-line shell provides the .backup command, which uses SQLite's Online Backup API to create a database copy. It is a practical option for Windows scripts and automated backup workflows.
For example, the following command creates a copy of an application database:
sqlite3.exe "C:\Data\app.db" ".backup 'C:\SQLiteStaging\app-backup.db'"
The destination folder must already exist, and the account running the command must have permission to write to it. Handy Backup can execute a batch file containing this command before saving the resulting database file.
2. SQLite Online Backup API
The Online Backup API allows an application to copy a running SQLite database into another database file. It is useful for developers who want to create consistent copies directly from their software without closing the database.
An application can save a database snapshot to a designated folder, while Handy Backup periodically copies that folder to independent storage. The API can also copy data in stages to reduce the time the source database is locked during individual read operations.
3. SQLite VACUUM INTO
The VACUUM INTO command creates a consistent, compact copy of a live SQLite database in a separate file. It is useful when you also want the resulting database file to be rebuilt and compacted.
Example:
sqlite3.exe "C:\Data\app.db" "VACUUM INTO 'C:/SQLiteStaging/app-vacuum.db';"
The output file must not already exist as a populated database. If the command is scheduled repeatedly, use a suitable output filename or prepare the destination before execution.
See the SQLite VACUUM documentation for its requirements and limitations.
Which method should you choose? The .backup command is a convenient starting point for scheduled Windows tasks. The Online Backup API is suitable for application-level integration, while VACUUM INTO creates a compact database copy. All three methods prepare database copies that Handy Backup can subsequently store and manage.
How to Back Up SQLite Automatically with Handy Backup
The following example uses SQLite's .backup command and the Handy Backup Computer data source. It creates a consistent database copy before the file backup starts.
Step 1. Prepare a SQLite Backup Script
Install the SQLite command-line utility if it is not already available. Create a folder for temporary database copies, such as C:\SQLiteStaging, and save the following example as C:\Scripts\sqlite-backup.bat.
@echo off "C:\Tools\sqlite3.exe" "C:\Data\app.db" ".backup 'C:\SQLiteStaging\app-backup.db'" exit /b %ERRORLEVEL%
Replace the example paths with the actual location of sqlite3.exe, your database, and the staging folder. Test the batch file manually and verify that the resulting database opens correctly before adding it to an automatic task.
Step 2. Create a Backup Task
- Launch Handy Backup and open the New Task Wizard.
- Choose Backup and enable Advanced mode to access pre- and post-operation actions.
- On Step 2, select Computer and choose the database copy in C:\SQLiteStaging as the backup source.
Step 3. Configure Storage and Automatic Execution
- Configure the backup schedule, encryption, compression, and version retention as needed.
- In Pre-, Post-Operation Actions, select Run a program before running the task and specify your SQLite backup script.
- Enable Wait for the program before proceeding so the SQLite copy operation finishes before Handy Backup begins copying the resulting file.
- Name the task, complete the wizard, and run a test backup. Verify both the SQLite copy and the stored backup.
Important: The script must complete successfully before Handy Backup copies the SQLite database. If the SQLite command fails, a previously created file may still exist in the staging folder. Check command results and configure your workflow to prevent an outdated copy from being mistaken for a current backup. The wait option controls execution order; it does not replace script error handling.
Once configured, the workflow can run automatically: SQLite prepares the database copy, and Handy Backup saves that copy to the selected destination.
For additional information about running external programs before and after a task, see the Handy Backup User Manual.
Back Up SQLite Files Without Running a Script
If the application using SQLite is closed and all database changes have been written to disk, you can back up its database files directly with Handy Backup. This approach is useful for local desktop applications and other systems where database access can be paused during copying.
- Open Handy Backup and create a new backup task.
- Select the Computer data source.
- Locate the SQLite database file, commonly using extensions such as .db, .sqlite, or .sqlite3.
- Choose the destination, schedule, and other task options.
- Complete the wizard and test the resulting backup.
Note: File extensions alone do not indicate whether a SQLite database can be safely copied while in use. Close the application or use a SQLite-native backup method when the database may have active transactions.
Where to Store SQLite Database Backups
Handy Backup lets you keep SQLite backup copies outside the application folder and choose storage according to recovery needs. Local storage can simplify routine restoration, while NAS and cloud destinations provide additional recovery options if the original computer becomes unavailable.
For databases that change frequently, consider retaining multiple historical copies and periodically checking whether the stored database can be opened and queried successfully.
SQLite Backup Restore and Migration
Handy Backup can restore previously saved SQLite database files to their original folder or a different location. This allows you to recover application data, prepare a test database, or move a consistent database copy to another computer.
- Open Handy Backup and create a new Restore task.
- Browse to the backup destination and select the backup.hbi index file.
- Choose the SQLite database copy you want to restore.
- Review the restore location. In Advanced mode, use Change Location to select another destination if necessary.
- Complete the wizard and run the restore task.
Important: Before replacing a database used by an application, close the application and ensure that no other process is writing to the database. A restored SQLite file should not be substituted into an active database environment without following the application's recovery procedure.
Restoring a Database Created by SQLite Native Tools
If your backup task saved a database copy created with .backup, the Online Backup API, or VACUUM INTO, Handy Backup restores that file like any other file backup. You can then place it in the appropriate application directory and use the database according to the application's requirements.
After restoration, verify database integrity and test the application's access to the restored data before returning it to regular operation.
SQLite Backup for Business Applications
SQLite is used by desktop programs, embedded applications, development tools, and internal business software. Handy Backup can help manage recurring copies of the database files and other application data from the same backup interface.
Desktop Applications
Schedule copies of SQLite data used by local Windows applications, together with related configuration files and documents.
Application Databases
Combine a database snapshot generated by the application or SQLite command-line tools with scheduled file backup and independent storage.
Development and Testing
Maintain DB copies for application testing, troubleshooting, migration, and recovery verification without working directly on production data.
Multiple Data Sources
Include SQLite database copies, office documents, application files, and other business data in a coordinated backup plan.
FAQ About SQLite Backup Software
Can Handy Backup back up a SQLite database automatically?
Yes. Handy Backup can run scheduled tasks to copy SQLite database files or consistent database snapshots created with SQLite's native backup tools. You can configure a pre-task command to prepare the database copy before Handy Backup saves it to local, network, or cloud storage.
Is it safe to back up SQLite by copying the database file?
Copying a SQLite database file is generally suitable when the database is closed and no transactions are in progress. For active databases, ordinary file copying can produce an incomplete or inconsistent copy, particularly when WAL mode is enabled. SQLite's .backup command, Online Backup API, or VACUUM INTO provides a more appropriate method for creating a consistent database copy while the application is running.
Does Handy Backup have a dedicated SQLite plug-in?
No. Handy Backup does not have a dedicated SQLite plug-in comparable to its MSSQL plug-in. SQLite databases can be included in ordinary file backup tasks, while SQLite's own tools can prepare consistent copies of running databases before the task begins.
How do I back up a SQLite database while it is in use?
Use SQLite's .backup command, Online Backup API, or VACUUM INTO to create a consistent copy of the running database. Handy Backup can run a script containing the SQLite backup command before starting the file backup task. Enable the option to wait for the external program to finish so the resulting database copy is ready before Handy Backup reads it.
What is the difference between SQLite .backup and VACUUM INTO?
The .backup command uses SQLite's Online Backup API to create a database snapshot. VACUUM INTO creates a consistent copy while rebuilding and compacting the database. Both methods can be used before a Handy Backup task. VACUUM INTO is useful when a compacted copy is desirable, while .backup is a straightforward choice for command-line backup automation.
Can I save SQLite backups to NAS or cloud storage?
Yes. Handy Backup can save SQLite database copies to NAS devices, network folders, external drives, Amazon S3, Google Drive, Dropbox, FTP/SFTP servers, and other destinations. Create a consistent database copy first when the source database is active, then use Handy Backup to transfer and retain it.
Can I restore a SQLite database to another computer?
Yes. Handy Backup can restore a saved SQLite database file to another location. Before using the restored database, confirm that the destination application can access it, that file permissions are correct, and that the application is not actively writing to the database being replaced.
Does SQLite backup require an ODBC driver?
No. An ODBC driver is not required when Handy Backup copies SQLite database files or snapshots prepared with SQLite's native tools. The Computer data source can be used for this workflow, while SQLite's command-line utility or application API handles database consistency when necessary.
Can Handy Backup retain previous versions of a SQLite database?
Yes. Backup versioning can preserve multiple SQLite database copies created at different times. For active databases, each retained copy should be generated using a consistent SQLite backup method. Configure retention according to database size, update frequency, and recovery requirements.
Which Handy Backup edition should I choose for SQLite backup?
Handy Backup Standard can be used for SQLite file backup tasks, including copies prepared by an external SQLite command. For more extensive business backup requirements involving other databases, applications, or multiple network computers, consider Small Business or Server Network according to the required features.
Automate SQLite database backups, choose independent storage, and manage recovery alongside your other business data with Handy Backup.
See also:
Capterra′s Rating:
"Great product, very simple and effective backup program"