locked
Storage Spaces Direct 2Node Cluster break by kb4034661 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    our system is also affected by the shared vhds snapshot issue. After reading many articles the KB4034661 should resolve that.

    Have a look at https://social.technet.microsoft.com/Forums/en-US/0d6cddde-3ff3-4a50-a627-6ad7bf7667fd/cannot-create-checkpoint-when-shared-vhdset-vhds-is-used-by-vm-not-part-of-a-checkpoint?forum=winserverClustering&prof=required

    also https://forums.veeam.com/microsoft-hyper-v-f25/backing-up-a-windows-failover-cluster-with-shared-vhdx-t22483-75.html

    After implmenenting the first Node with the mentioned KB update, the storage replication brokes.

    I found out that the cluster configuration was not in sync and that was the issue. So i tried to fix this with "Start-StorageNode FQDN -ForceQuorum" which should place the cluster settings as authorative.

    

    That had no success with the update implemented, after removing the update from the system i was able to sync the storage again.

    The second try was to implement the update on both systems, and then try to sync again, that also did not worked.

    Here comes now the clue: the repair of the cluster configuration, after removing the updates again, did not succeeded.

    So in my sittuation there is currently just 1 system which got correct storage.

    Has anyone a similar sittutation after updating the system?

    I'm currently planning to remove the cluster node and place it in again to make a full sync with the latest known version which supports shared vhds snapshots, which was before 31. december 2016.

    Regards


    • Edited by NVO88 Thursday, August 31, 2017 8:11 AM
    Thursday, August 31, 2017 7:59 AM

All replies