I dislike the idea that I can't just make automatic copies of my database, like I do every other file, in a standard "backup changed files on my hard drive" backup system. While I am no database expert, it seems to me that a bit-by-bit binary backup, that I would restore post computer failure, ought to work regardless of hardware changes. If that isn't the case, it seems to be because it is designed in, and I'd like the reason why. At the end of the day, that's something I'd need to hear from a Lone Wolf staff, not speculation.
You can ABSOLUTELY backup your database doing normal backups. However, the caveat is that you definitely should NOT be running Realm Works when you do so. If you do, then the ability to recover that backup is not guaranteed.
This is a standard thing with all professional-grade database systems. If the database is running and in use, you can grab a snapshot of it, and it will USUALLY be valid, but that's not guaranteed. The only way to GUARANTEE the integrity of the backup is to make sure that the database is in a "quiet" state with zero activity of any sort going on. And the only way to guarantee that is to do it when there are no clients accessing the database (i.e. product is shutdown) OR when the product itself goes into a "safe" state where it can perform the backup.
Since you're comfortable playing things a little fast and loose in your environment, the above considerations may be perfectly reasonable to you. Just as long as you're fully aware of the implications. If you want to be 100% certain the backup is valid, there are only two ways to achieve that, so either retain multiple backups in case is invalid or ensure the database is "quiet" as outlined above.
From our perspective, though, we're only going to advertise the ways that are GUARANTEED to safeguard data for user. The last thing we want a user to do is take a shortcut without realize the risks and end up with lost data as a result.
Hope this makes sense!