|
OMG, how dare you are, really suggesting such an abomination of a guerilla-backup method to innocent users and even worse, all this in good faith helping people. I have to reassure the previous concern and hopefully no-one who relies on their backup does follow this method.
This is exactly why Apple tries so hard to hide the inner workings of all these technologies from the user, so they won't mess around this badly and still except it to work flawlessly.
To address the actual problem; It does not seem as if you had a full understanding of how a file system works and how it is managed by the OS. Luckily this method will only break your backups and not the live data itself, I believe, but it will break. Believe me, I've seen enough file system getting damaged by using them in the intended manner and even so badly that Disk Utility couldn't repair it.
Why do you think, the dialog that Mac OS X presents to you if you disconnect a external drive with a mounted file system is one of the rare occasions the red exclamation mark icon is used, accompanied by a very harsh and dismissive explanation of how badly the user screwed up. They're not joking by telling you that "recently saved data may be lost".
If you want to get a feeling of what an effort it takes to organize all the files applications read and modify in your home directory run this command from the command line: `sudo fs_usage diskimages-helper'.
Every of these activities change the internal structure of the file system inside the sparse bundle. To get a copy of your FileVault image that at least the journal should be able to repair reliably, the whole rsync operation must complete without any one of these operations interfering with the backup process.
Maybe "it seems to work" is enough for you, but I have to remember this for the next recruitment…
Feuermurmel
 |