Comments

  • Bitlocker, VSS + Secondary Drive
    David,

    Thanks for the reply. That's a good blog post for whole drive encryption options and the problems with CCB / Block-Level / VeraCrypt.

    Out of the VeraCrypt use-cases listed, this one applies to my secondary internal drive: "Encrypt a non/system partition/drive, standard VeraCrypt volume > file backup of the mounted encrypted volume, do not use block-level (do not force VSS)"

    EXPERIENCE: When attempting Block-Level backups with this configuration the non/system drive created VSS event ID 12293 errors. It also created NTFS errors ID 3221487753 (but I believe that's only a side-effect since chkdsk reports no errors and the /f option reported no corrections). It was also discovered when deleting shadow copies that none existed on the non/system drive (confirming VSS never completed). Only the encrypted system drive had a shadow copy.

    EXPERIENCE: I have also tested and confirmed that a VeraCrypt encrypted system drive does work with Block-Level and VSS. Just don't configure the backup to touch the non/system drive or VSS fails.


    QUESTION:
    The blog however doesn't seem to answer the original question asked about Bitlocker (or does it?):

    Will CBB Block-Level backups (and VSS) work on a PC configured with both an encrypted system drive AND an encrypted (non-system) secondary internal drive using Bitlocker?

    Has Cloudberry ever tested that setup? Can anyone in the forums confirm that this setup works for them?

    I'm trying to avoid spending time and money reconfiguring a working system to use Bitlocker and then discovering that CBB doesn't support this configuration either.

    I'd be thankful to learn of anyone's experience with this,
    TWolf