Hi, last week Microsoft has finally released the ReFS stability fixes KB4098787 (from KB4077525) for Windows Server 2016 and Windows 10 that fixes ReFS lockup problems with Veeam repositories. I wrote about the changelog a few weeks ago. Another change is that this update will be downloaded and installed automatically from Windows Update (although you can still get the standalone package from the Microsoft Update Catalog). As you may remember, the Windows Server 2016 version of the original package has been recalled due to an unrelated quality issue. But, in the known issues section of the updated article, there’s another issue around antivirus compatibility now. Could this be the reason why some users saw no improvement after installing the original patch… Although the more likely reason is lack of RAM on a repository server, as Microsoft is still working on optimizing ReFS memory pressure, and this particular fix looks to be scheduled for the April update.
Hi, last week Microsoft has finally released the ReFS stability patch KB4077525 (February 22, 2018) for Windows Server 2016 and Windows 10 that fixes ReFS lockup problems with Veeam repositories. In the “Last Word from Gostev“, he wrote that in the change log, there are just a couple of modest lines about ReFS performance improvements, some of the affected users will see performance improve from zero (due to file server lockups) to nominal. It just does not translate a real magnitude of the issue, and the complexity of bugs behind…
Hi, with the microcode included in the BIOS updates released to address Spectre (Variant 2), CVE-2017-5715. Dell is advising that all customers should not deploy the BIOS update for the Spectre (Variant 2) vulnerability at this time. They have removed the impacted BIOS updates from our support pages and are working with Intel on a new BIOS update that will include new microcode from Intel. If you have already deployed the BIOS update, in order to avoid unpredictable system behavior, you can revert back (downgrade) to a previous BIOS version (tables of BIOS updates for Dell PowerEdge Server Products). The BIOS can be updated using the iDRAC…
Last week, Veeam has launched a huge product licensing change that some of our customers have been asking for the per Virtual Machine licensing option. As you know, previously Veeam Software has sold their products for virtual infrastructure to end users strictly on per-socket basis. And most customers loved it because they did not need to worry about the number of VMs they are protecting. But in certain edge cases, such as heavy ROBO (Remote Office / Branch Office) environments, this was not a very good deal as end-users sometimes had to license 2 sockets running just a couple of VMs.