Everyone safe and healthy here! I hope everyone else reading this is too. FileVault and QRecall play just fine together ... now. In the very early days of OS X, FileVault was implemented as a special mount point, backed by a hidden disk image file that handed the encryption. This complicated things in numerous ways for QRecall. First, QRecall captures volumes, and your home folder was now on a different volume. You couldn't capture files for another user if they weren't logged in. And if you restored your files, FileVault might make them all disappear when you logged in again. *sigh* Mac OS X Lion (10.7) introduced FileVault 2 (officially known as "FileVault," with the earlier version being referred to as "Legacy FileVault"). FileVault 2 encrypts the entire volume at the block level and is completely transparent to the filesystem and QRecall. If you want the same level of protection for your QRecall archive, you can enable encryption. (Make sure you make a backup copy of your encryption keys and keep them safe.)
|