Daily Material Library Maintenance: Refresh, Rebuild, Back Up, and Migrate the Database

Large material libraries need regular maintenance. Use the right action for each situation so you avoid unnecessary full rebuilds.

1. Check Database Status First

Open database statistics and check file counts, image counts, pose counts, other feature counts, and disk usage. This tells you whether data exists and whether search features have been generated.

2. Use Refresh When Folder Content Changes

If files were added, removed, renamed, or replaced in indexed folders, refresh the database. Enable file-change detection when files may have been replaced without changing names.

3. Use Rebuild When Search Is Abnormal

If search data is missing, counts do not match, or a strategy behaves abnormally, rebuild the corresponding index. Rebuild only the needed strategy when possible.

4. Watch Progress While Tasks Run

Indexing, face recognition, pose extraction, OCR, and rebuild tasks can take time. Watch the task progress area and wait for completion before checking results.

5. Back Up or Migrate the Database Regularly

The database stores indexing records, notes, labels, collections, and search data. Back it up before large maintenance, migration, or risky cleanup.

6. Repair database.db Only When It Is Damaged

If the app detects corruption or cannot open database.db, use the repair tool. Repair is for damaged database files, not normal search refresh.

How to Choose the Right Action

• New folder: add folder.
• Existing folder changed: refresh.
• Search strategy missing or abnormal: rebuild.
• Database file damaged: repair.
• Moving to another disk or computer: back up and migrate first, then refresh paths.

Common Cases

• If results are missing after copying files in, refresh the folder.
• If image search is unavailable, rebuild image strategy data.
• If the database grows after cleanup, shrink it after removing unwanted records.