It has been stated in one of the Webinars (I think) that this will never be the case. Firstly there is no need and the downside would be slow and sluggish files running into GB's in size and that is something which would turn me away from RM.
There are many ways to back up your entire genealogy collection and a bit of searching for "best practices" would stand be of great benefit to you rather than messing up a good genealogy program.
Well if it is true that that this will 'never happen' then it certainly simplifies a decision for me. If this is 'never' going to be included then RM will never adhere to common database programming 'Best Practices' of having all related data included in the backup so a 'Full Recovery' can be accomplished with only the database backup.
I keep hearing about all this worry about file size and sluggishness yet I work with databases on a routine basis that contain large media based objects within the database themselves and there is no performance issue. I would much prefer a slower backup that could be restored from a single file, or single command, and that maintained at least a relative folder structure than the pain of multiple backup files and trying to match everything back up again.