Database != Files
Please stop thinking of a database as files.
Most of what a database does happens in the memory of the running process and only gets written to disk "some time" later.
Use Database tools to do Database things.
Quote
I am trying to design a backup strategy ...
IMHO,
nobody should have a
Backup Strategy.
What you need is a
Recovery Strategy.
Of course, your Backups, which you take for pretty-much
no other reason, form a significant
part of that but, on their own, Backups are actually pretty useless.
First, find out - from your business; this isn't something you can decide in isolation - what your Recovery Objectives are. That comes down to two, basic metrics:
How long do you have to get a broken database back up and running, and
How much Data are you allowed to lose in the process of doing so.
Only then can you start thinking about how you're going to
meet those objectives. Backups are not the only option. They have to be there, as a last resort, and you have to
guarantee that they will work (and that will be
far more likely if you use the Right Tools for the Right Job).
Regards, Phill W.