Storage Spaces
1 TopicSemaphore 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 now I faced issues with "semaphore timeouts" reported by the Macrium backup solution and Ned Pyle and Vlad helped me to narrow down that the issue is not a SMB issue but infact a problem with the storage subsystem. Here Storage Spaces consisting of two WD Red Plus 6 TB. mirrored, ReFS 3.6. In previous releases of Windows Server the issue also affected the scenario when clients tried to backup to a SMB share causing the same issue. This improved over releases Now only one issue remains. Here is the Feedback hub item. https://aka.ms/AAbm84d Scenario: Hyper-V Host Hosting various VMs one VM data disk (VHDX) is located on a Storage Spaces Pooling using Dedup (dedup will run outside backup times) When the backup application runs it will write the data from this vhdx via Block Level (tested with or without CBT) to a file share (driveletter A) The timeout will occour reproducibly and so preventing a backup. If I try the same and do not use the SMB Share located on a volume on the Storage Spaces Pool the backup is fine. Source: VM > Data disk (driveletter N) located on Storage Pool 1 volume (driveletter H) Target: SMB Share (driveletter A) located on Storage Pool 1 Error: semaphore timeout more details in the feedback hub from our investigation unaffected builds Windows Server 2019 LTSC 1809 17763.x Windows Server vNext LTSC b20215 affected builds: all other Windows Server vNext / 2022 LTSC the issue happen when the backup data amount is large (20-40 GB will work fine)Solved2.9KViews0likes5Comments