|
#1
|
||||
|
||||
Same answer at present. We just haven't had time to do thorough testing with it. It should work...
__________________
--Dave Nanian |
#2
|
|||
|
|||
Should work meaning it's just copying the un-encrypted files to another disk/sparsebundle? So if one was to restore, the drive would be un-encrypted and the user would have to re-enable FileVault 2?
I know this is new, just wondering what you meant by "it should work". |
#3
|
||||
|
||||
Encryption is a properly of the underlying drive structure. It's supposed to be totally transparent to us. So, if the drive is encrypted and we copy to it, the result will be encrypted. Similarly, if the source is encrypted and the destination is not, the backup won't be encrypted.
__________________
--Dave Nanian |
#4
|
|||
|
|||
Enabling FileVault 2 creates a second "Recovery HD" partition, that I believe stores the encryption keys (and the login screen that is shown at boot).
I'm interested to hear what others suggest for backing up a FileVault'd system. Do I need to backup the Recovery HD in addition to my encrypted system partition? I just finished my first pre-FileVault SD clone. Now I'm off to enable FV. |
#5
|
||||
|
||||
We don't back up (and don't see) the recovery partition...
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|