Why splitting them makes sense.
WHY SPLIT
Databases change constantly and are small. Files change rarely and are large.
Backing up both at the same frequency either wastes storage or under-protects your data.
A SENSIBLE ARRANGEMENT
Database: daily, or more often
Files: weekly, or after changes
This gives good data protection at modest storage cost.
THE RISK
Restoring files from one date and a database from another leaves the application inconsistent.
For a straightforward rollback, restore both from matching dates. Where only data was lost, restoring the database alone is correct and safe.
Know which situation you are in before restoring.
WHEN DATABASE-ONLY IS RIGHT
Content deleted in error A bad import Data corruption Anything where the files are fine
WHEN BOTH ARE NEEDED
A failed update that changed both A compromise A migration gone wrong
KEEPING TRACK
Label your archives with dates clearly, so matching pairs are obvious.
