Don't impose any constraints on your problem you don't need to.
Like what are you backing up to? $400 for a 1T ssd or $80 fo a 2T usb3 spinny disk.
If you are backing up while the db is being updated, you need to make sure updates are queued until the backup is done. don't mess with that process. personally I would assume the db is always being updated and expect that.
Are there rules for thumb for deciding when you can dump a whole database and when you’d be better off dumping groups of tables? I have a database that has around 100 tables, some of them quite large, and right now the data directory is well over 100GB. My hunch is that I should divide and conquer, but I don’t have a clear sense of what counts as “too big” these days. Nor do I have a clear sense of whether the constraints have to do with overall size, the number of tables, or machine memory (my machine has 32GB of memory).
