calibre Backup Library Not Working: How to Protect Your Books

When a calibre backup appears to finish but misses books, covers, metadata, custom columns, plugins, or preferences, the backup usually captured only part of calibre's data. The most common causes are copying the wrong folder, excluding metadata.db, backing up while calibre or a syncing service is still writing files, overlooking the separate configuration folder, or trusting a cloud copy that has not finished synchronizing. The safest response is not to reinstall calibre or rebuild the library immediately. First identify what is missing, make a small controlled backup, and prove that you can restore it without touching the working library.

1. Confirm the Symptom With a Small Safe Test

Before changing settings, determine whether the problem is an incomplete backup, an incomplete restore, or a misunderstanding about which data belongs in the library folder. These problems can look identical when you open a copied library and discover missing information.

1.1 Create a recognizable test book

Use an existing DRM-free book or a harmless document you are permitted to copy. Add it to calibre and give it unmistakable test data:

• Change the title to include the words Backup Test
• Add a distinctive tag such as backup-check
• Assign a temporary cover
• Add a short comment in the metadata
• If you use custom columns, enter a unique value in one
• Confirm that at least one readable book format is attached

Open the book from calibre to confirm the format is actually present. Then close the viewer and wait for any active jobs to finish. This single record lets you check the book file, cover, standard metadata, custom metadata, and database state without reviewing a large library manually.

1.2 Record the active library location

Click the calibre library button in the main toolbar and note the path of the current library. If you maintain several libraries, switch through them and record each location. A backup of one library does not automatically include every other library unless your backup method explicitly selects them.

Open the active library folder in your operating system's file manager. At its top level, you should see metadata.db and folders organized around authors and books. A book folder normally contains one or more e-book formats and may contain files such as a cover image and an OPF metadata backup.

Success looks like this: you know the exact active library path, the test book appears in calibre, and its files appear beneath that same library folder. Stop changing settings if this check reveals that your backup software was simply targeting an old or different library.

1.3 Restore to a copy, never over the working library

A backup is not proven until it has been restored and inspected. Restore the backup into a new empty test folder. Do not overwrite the active library. In calibre, use the library menu to switch to the restored folder as an existing library, then check the test title, cover, tags, comments, custom-column value, and book format.

If the restored copy works, the backup is usable. Switch back to the original library and stop troubleshooting. If something is missing, note exactly what failed before proceeding. Avoid broad descriptions such as calibre not working. A missing plugin requires a different fix from a missing EPUB or blank metadata.

2. Back Up the Correct calibre Data

The central distinction is between the calibre library folder and the calibre configuration folder. They serve different purposes and may be stored in completely different locations.

2.1 Understand the library folder

The library folder contains the books managed by that library and the database describing them. Its most important components are:

• metadata.db, which holds the library's central metadata and structure
• Author and book subfolders containing EPUB, PDF, AZW3, MOBI, or other formats
• Cover files stored with individual books
• Per-book OPF files used as metadata backups
• Other files deliberately attached to book records

Copy the entire library folder recursively. Do not select only metadata.db, and do not select only the author folders. The database and book folders must belong to the same snapshot. A newer database paired with older book folders can reference files that are absent. Older database contents paired with newer folders can leave books unlisted even when their files exist.

Success looks like this: the backup contains metadata.db at its root and the complete author and book folder tree from the same backup run.

2.2 Understand the configuration folder

The configuration folder stores preferences and supporting data rather than the main book collection. Depending on how you use calibre, it may include plugin configuration, installed plugins, interface preferences, conversion defaults, device settings, news recipes, saved credentials or account-related settings, templates, and Content server configuration.

Open calibre's configuration directory through Preferences > Miscellaneous > Open calibre configuration folder. Back up that folder separately if you want to preserve your setup. Copying only the library does not guarantee that plugins, application preferences, server users, conversion defaults, or interface customizations will return.

Because direct restoration of a configuration folder is not the same as restoring an ordinary library, keep a dated copy and test cautiously. Do not replace a current configuration folder while calibre is open.

Success looks like this: your backup plan has separate, clearly labeled copies of the library data and configuration data. Stop if the supposedly missing books are present and only application settings were absent.

2.3 Use Export or import all calibre data when appropriate

calibre includes an Export or import all calibre data function. It can package selected libraries together with settings and plugins. Although this function is commonly used when migrating to another computer, it is also useful for creating an occasional self-contained recovery snapshot.

1. Disconnect any e-reader or phone if the menu command is unavailable.
2. Open the menu attached to the calibre library button.
3. Select Export or import all calibre data.
4. Choose the option to export all calibre data.
5. Select every library that should be protected.
6. Choose a new empty destination folder with enough free space.
7. Wait for the operation to finish before copying or disconnecting the destination drive.

Do not assume that a successful export message proves every source file was healthy. Test the export by importing it into empty temporary locations, preferably on a separate user account, spare computer, or controlled test installation. Do not import over your active library merely to test it.

Success looks like this: the imported test contains the expected libraries, books, covers, metadata, settings, and plugins. Once confirmed, stop changing calibre preferences.

3. Prevent Partial or Inconsistent File-Level Backups

If you use File Explorer, Finder, a command-line copy tool, backup software, or an external-drive utility, treat the library as an active database rather than an ordinary folder of unrelated documents.

3.1 Close calibre before copying files

Wait for conversions, metadata downloads, news downloads, device transfers, and other jobs to finish. Stop the Content server if it is running from the main application, close open metadata dialogs, exit the e-book editor and viewer when they are working with library files, and then quit calibre fully.

On Windows, check Task Manager if files remain locked. On macOS, confirm calibre has disappeared from the Dock's running indicators or Activity Monitor. On Linux, check your desktop's process viewer or use a process-listing command if necessary. Avoid forcing the process to end while jobs are still writing data.

A live-copy tool may copy metadata.db at one moment and book folders several minutes later. Closing calibre produces a more consistent snapshot and reduces file-locking and timing problems.

Success looks like this: the copy completes without locked-file, sharing-violation, or changed-during-copy warnings, and the restored test library opens normally.

3.2 Check operating system permissions and exclusions

A backup can appear successful while silently skipping unreadable files. Review the backup application's report for access-denied messages, exclusions, path-length problems, invalid filenames, unavailable mount points, or insufficient destination space.

• On Windows, verify that the account running the backup can read the entire library and write to the destination.
• On macOS, check whether the backup application needs access to protected folders or removable volumes.
• On Linux, confirm ownership, read permissions, mount state, and free space on both filesystems.
• In antivirus or endpoint-security software, look for quarantined files or blocked backup activity rather than disabling protection permanently.

Compare the source and destination using file counts and total sizes, but do not treat matching totals as a complete restore test. Filesystem allocation and backup compression can produce different reported sizes.

Success looks like this: the backup report shows no skipped calibre files, and a restored copy contains the recognizable test record.

3.3 Treat cloud synchronization as transport, not proof

OneDrive, Dropbox, iCloud Drive, Google Drive, Syncthing, and similar tools can copy backups off the computer, but synchronization introduces timing and conflict risks. Avoid allowing a sync client and calibre to modify the live library simultaneously. Database files are particularly vulnerable to conflict copies and partial synchronization.

A safer pattern is:

1. Keep the active calibre library on a reliable local disk.
2. Close calibre and any process accessing the library.
3. Create a dated local backup or calibre data export.
4. Place that completed snapshot in the cloud-synchronized folder.
5. Wait until the provider reports that synchronization is complete.
6. Periodically download or restore a snapshot to a non-synchronized test folder.

Be careful with files-on-demand features. A cloud folder may display filenames even though the full file contents are not stored locally. Before relying on a restore, mark the required backup for offline availability and confirm it has downloaded completely.

Do not use a cloud conflict copy of metadata.db as a casual replacement for the current database. Preserve both versions and test on copies first.

Success looks like this: the completed snapshot exists locally and remotely, has no unresolved sync status, and restores successfully outside the synchronized folder.

3.4 Avoid using a NAS as the active library

A network-attached storage device can be a backup destination, but the active calibre library should remain on a local filesystem. Network filesystems can behave differently with locking, file replacement, latency, and simultaneous access. Those differences can cause errors that resemble backup corruption.

Copy a closed, consistent library snapshot to the NAS instead of opening the primary library directly from it. If several people need access to books, use the calibre Content server for browsing and downloading rather than sharing direct write access to the library folder.

Success looks like this: calibre works from its local library, while the NAS stores dated backup copies that can be restored independently.

4. Check the Library Before Blaming the Backup

Sometimes the backup faithfully copies an already incomplete or inconsistent source library. Check the source before repeatedly changing the backup destination.

4.1 Run Check library

Open the library menu and use Library maintenance > Check library. This can identify mismatches such as missing formats, missing covers, unexpected files, malformed paths, or folders that do not correspond cleanly to database records.

Review the report before deleting anything. Extra files may be harmless personal files, while missing formats may indicate that the source library had already lost content. Save screenshots or notes so you can compare the source with the restored backup.

Success looks like this: the source library has no unexplained missing formats or covers, and its database corresponds to the files beneath it.

4.2 Use Restore database only for a damaged database

If metadata.db is missing or damaged, calibre can rebuild it from the OPF metadata files stored in book folders. This is a recovery operation, not a routine backup step. A rebuilt database may not recreate every database-only feature, saved search, user category, custom recipe, or per-book conversion preference exactly as it existed.

Before restoring the database, close calibre and make a complete copy of the damaged library. Perform recovery on the copy whenever possible. Do not rebuild a healthy database merely because one cover or one book format is missing.

Success looks like this: the copied library opens, expected books return to the list, and sample files open correctly. Stop once recovery works, then create a fresh full backup.

4.3 Separate source-quality problems from backup problems

If a restored book exists but will not open, test the same format in the original library. A malformed EPUB, incomplete PDF, failed conversion, or zero-byte source file will remain defective after a perfect backup. Check the relevant calibre job details for conversion or import errors.

Likewise, metadata downloaded from an online source may differ from metadata already stored in the library. A backup should preserve the library's current state. It is not expected to rerun metadata downloads or recreate a cover that was never successfully saved.

Success looks like this: the same book and format behave consistently in both the source and restored libraries. If both copies fail identically, troubleshoot the source file rather than the backup.

5. Use Logs and Diagnostic Tools When the Failure Is Unclear

Most backup failures can be resolved without command-line tools. Diagnostics become useful when calibre closes unexpectedly, a plugin interferes, the export job fails, or the library produces inconsistent errors.

5.1 Read job details first

Open calibre's Jobs panel after an export, conversion, metadata download, or other failed operation. View the detailed log and look near the first reported error, not only the final failure message. Record the source path, destination path, filename, and operation involved.

For file-level backup software, inspect its own activity log for skipped files and retry failures. calibre cannot report files excluded by a separate backup application.

5.2 Start the graphical interface in debug mode

Advanced users can run calibre's graphical interface with diagnostic logging by using calibre-debug -g. Reproduce only the relevant failure, then save the output. On macOS, calibre's command-line tools are inside the application bundle, so the full tool path may be required.

For device-detection problems, calibre-debug --debug-device-driver can help, but device detection is not normally relevant to a library-folder backup. Use it only if a connected device prevents access to the export command or if your supposed backup is actually a device transfer.

The command-line tool also supports exporting all calibre data. This is useful for controlled diagnostics, but the graphical export is easier for most readers. Avoid experimenting with undocumented commands against the only copy of a library.

Success looks like this: the log identifies a specific inaccessible path, plugin error, locked file, failed disk, or malformed source. Fix that cause and repeat one controlled test instead of changing unrelated settings.

5.3 Test without third-party plugins

If an export or normal calibre shutdown fails only after installing or updating a plugin, temporarily disable the suspected plugin and repeat the small test. Do not remove every plugin at once because that makes the cause harder to identify.

Plugins stored in the configuration area are different from books stored in the library. A library-only copy can be complete even when a plugin is missing after restoration.

Success looks like this: the export or shutdown succeeds with one plugin disabled. Keep that plugin disabled while checking its official support information, and stop modifying unrelated preferences.

6. Run a Clean Temporary Test Before Reinstalling

Reinstalling calibre generally does not repair a backup that points to the wrong folder or excludes part of a library. A clean temporary test provides better evidence and does not risk the primary collection.

1. Close calibre and make a read-only safety copy of the current library.
2. Create a new empty folder on a local disk.
3. Create a small temporary calibre library in that folder.
4. Add two permitted test books and edit their metadata and covers.
5. Close calibre completely.
6. Back up the entire temporary library using your normal method.
7. Restore it into a second empty local folder.
8. Open the restored folder as an existing calibre library.
9. Check every book, format, cover, and metadata field.

If the temporary library restores correctly, the backup method works in principle. The original problem is probably tied to the original library's location, size, permissions, cloud status, filesystem state, or internal consistency. If the temporary test also fails, focus on the backup application, destination drive, permissions, or exclusions.

Do not delete the main library, rebuild its database, reinstall calibre, or change many preferences until this test identifies which side is failing.

6.1 Verify the external backup drive

Check the destination drive's free space, filesystem health, connection, and safe-ejection history. Try copying a large unrelated test file to the drive and opening it again after reconnecting. If the drive disconnects, reports input-output errors, becomes read-only, or repeatedly corrupts files, replace it before trusting another calibre backup.

Keep more than one backup generation. A single external drive connected continuously to the computer can be affected by accidental deletion, malware, power problems, theft, or hardware failure. A practical arrangement includes the working library, a local or external backup, and another copy stored separately.

7. Quick Fix Checklist

• Confirm the active library path from calibre rather than relying on memory.
• Make sure every calibre library is included, not just the default library.
• Copy metadata.db and all author and book folders together.
• Back up the separate configuration folder if settings and plugins matter.
• Wait for jobs to finish and close calibre before a file-level copy.
• Stop the Content server before copying the live library folder.
• Review backup logs for skipped, locked, unreadable, or excluded files.
• Keep the active library on a reliable local filesystem.
• Do not let calibre and a cloud-sync client write the library simultaneously.
• Wait for cloud uploads and downloads to finish before testing.
• Run Library maintenance checks if the source already seems incomplete.
• Restore into a new folder instead of overwriting the working library.
• Open several restored books and inspect covers, tags, comments, and custom columns.
• Check external drives for errors and maintain multiple backup generations.
• Stop changing settings as soon as the controlled restore succeeds.

8. Frequently Asked Questions

8.1 Does copying the calibre library folder back up everything?

It backs up the books, covers, library metadata, custom columns, and other data stored inside that library. It does not necessarily preserve application preferences, plugins, server settings, conversion defaults, or every account-related setting. Back up the calibre configuration folder separately or create an Export all calibre data package if those items matter.

8.2 Why does my backup contain book folders but calibre shows an empty library?

The restored folder may be missing metadata.db, calibre may be opening a different folder, or the database may be damaged. Search the restored copy for metadata.db and verify that it is at the top level beside the author folders. If it is damaged, preserve the restore and use Library maintenance recovery only on a copy.

8.3 Can I back up calibre while it is open?

Some snapshot-based backup systems can capture open files consistently, but an ordinary file copy is safer when calibre, its Content server, editors, and active jobs are closed. Closing the application reduces the chance of copying the database and book files at different points in time.

8.4 Is Export all calibre data better than copying the library folder?

They serve overlapping but different needs. A complete folder copy is simple, transparent, and convenient for frequent backups. Export all calibre data can package selected libraries, settings, and plugins into a self-contained snapshot. Many users benefit from frequent closed-folder backups plus occasional full-data exports.

8.5 How often should I back up my calibre library?

Base the schedule on how much work you can afford to repeat. If you add books or edit metadata every day, make daily automated backups and retain several generations. Less active libraries may need weekly backups. Create an extra backup before large metadata edits, bulk conversions, plugin changes, database recovery, or operating system maintenance.

8.6 How do I know the backup is genuinely usable?

Restore it into a separate empty folder, open that folder as a calibre library, and inspect a representative sample. Confirm that recent and older books appear, multiple formats open, covers display, custom columns retain their values, and the test book created earlier is complete. If you also backed up settings, test those separately without replacing the only working configuration. A successful restore is the point at which you should stop troubleshooting and document the working procedure.