Forum Discussion
Solved
Semaphore timeout when running a backup where source and destination is on the same Storage Space
Dear Server / Storage Team, I am running a lab with Windows Server 2022 LTSC preview to get familiar with the new or changed features but also to help you hunting issues. For a very long time...
I have enabled Background Optimization but this did not negatively affect anything.
II have reinstalled the server from Scratch because of this issue
https://techcommunity.microsoft.com/t5/windows-server-insiders/issue-b20251-b20257-b20262-b20270-b20282-b20287-formatting-a/
I will report back when MR 8 is released and I can leverage CBT and Encryption again, but in this case it seems to be more an application issue causing the overload / write latencies on the Storage Space to cause the semaphore timeout.
here are the logs from the session with Ned Pyle RahulTK
https://1drv.ms/u/s!ApTx3d3fhinPhLQQzXJ847miz7kMQw?e=ry73Ei
II have reinstalled the server from Scratch because of this issue
https://techcommunity.microsoft.com/t5/windows-server-insiders/issue-b20251-b20257-b20262-b20270-b20282-b20287-formatting-a/
I will report back when MR 8 is released and I can leverage CBT and Encryption again, but in this case it seems to be more an application issue causing the overload / write latencies on the Storage Space to cause the semaphore timeout.
here are the logs from the session with Ned Pyle RahulTK
https://1drv.ms/u/s!ApTx3d3fhinPhLQQzXJ847miz7kMQw?e=ry73Ei
RahulTK This week I have upgraded to Macrium Reflect 8 which enabled all the previous features like CBT and encryption and it still works like a charm.
This means the issues with the setup
2 HDDs with Storage Spaces Mirror where source vhdx and backup target (filebased) are stored on a ReFS volume with enabled Dedup gives no headaches.
From my trackings I'd say it has been fixed in b20313