RAID Array / Disk Performance with Bitlocker - unexpected results
I've doing some testing on a system to identify the impact that Bitlocker Encryption has on the read/write performance and the results have been interesting to say the least; I'm hoping someone can help to explain my findings. I'm using an entry level server with quad core Xeon E-2224 CPU and 16GB RAM which has Windows Sever 2016 Standard installed - and it's a totally fresh Windows install with all of the latest relevant drivers are installed. My storage array is configured through the integrated controller on the motherboard and is across 4 x 10TB WD Enterprise disks configured as follows: RAID Level RAID5 Legacy Disk Geometry (C/H/S) 65535/255/32 Strip Size 64 KiB Full Stripe Size 192 KiB Disk 0 WDC WD102KRYZ-0 Disk 1 WDC WD102KRYZ-0 Disk 2 WDC WD102KRYZ-0 Disk 3 WDC WD102KRYZ-0 I've provisioned a single large logical volume and I've created two partitions for my testing as follows: Drive Capacity File System Allocation Unit Size Y: 100 GB NTFS 4096 bytes Z: 25,600 GB NTFS 8192 bytes I ran an array of tests (results attached) on the volumes before encryption, then reformatted and encrypted the volumes and same tests again. The results have been very interesting, I was expecting to see a small performance hit across all tests due to Bitlocker, but what I found was that some tests had a drastic performance decrease, in some cases up to 50%, and surprisingly some tests showed an increase in performance, in one case an increase of 60%. Can anyone help to explain this? I'm thinking of running the tests again with another product to see if I get similar results, but what I'm using is fairly robust/reliable from my experience. Findings are in the spreadsheet attached.
Error trying to turn on Bitlocker
We have a VM of Server 2019 for our file server. The data drive had Bitlocker turned on but our MSP accidentally turned it off, unencrypting the drive. Now when I try to turn BL back on I get an almost immediate CRC error. The data drive is working normally, chkdsk and SFC didn't find any errors. When I search for this problem I only find references to people working with drives that already have Bitlocker turned on but are trying to use autounlock. None seem to be for people like me that had BL working properly until it got turned off and now can't turn it back on.Bitlocker Conflicting with Windows Local Backup
Hello Everyone, Im currently managing the Backups over various different editions of Windows Server, and one common theme im finding is that Bitlocker does not always like to play nice with Windows Local Backup. At the moment im trying to resolve an issue in which bitlocker locks itself after being left for longer periods of time, meaning the drive target of the Backup cannot be accessed, leading the drive to fail until someone signs into the server. Would anyone have some sort of script that would allow the drive to be woken up per say so that it does not lock?
SCCM Bitlocker Policy for Removable Device Encryption
We have just upgraded to SCCM 2006 and are testing the Bitlocker policies. We have successfully got fixed device encryption working but we are having real problems with Removable device encryption. With RD Encryption enabled, whenever I plug a USB device in it asks if I want to encrypt the device, if I tell it to encrypt it immediately errors saying it cant encrypt as the device contains system boot information. We have GPO setting for user and machine to disable Deny read/write access to removable devices. Removable disk encryption is 'greyed' out in Bitlocker mgmt. Has anybody got any experience of this
