Hi Lukas,
Hope you're doing well.
Potential Causes and Solutions:
- If the replication via Storage Replica is not configured correctly or there are issues with the replication health, it could prevent the failover from executing as expected. Ensure that the replication is in a healthy state and that there are no underlying issues with the network or storage that could be impacting the replication process.
- The error might be related to the cluster configuration. Ensure that all nodes have the correct quorum settings and that the cluster is configured to handle the stretched cluster scenario properly.
- The error could be related to resource ownership within the cluster. Verify that the resources are configured to move correctly between the nodes and that there are no restrictions or dependencies preventing the move.
- Go through the Failover Cluster configuration and Storage Replica settings to ensure everything is set up correctly. Pay special attention to the quorum configuration and the replication health.
- Review the cluster logs and event viewer for any additional error messages or warnings that could provide more context to the issue.
Best Regards,
Ian Xue
If the Answer is helpful, please click "Accept Answer" and upvote it.