solved,
for whatever reason we had to manually create a registry key.
Computer\HKEY_LOCAL_MACHINE\Cluster\WVR
new registry key: ConfigStore
(Computer\HKEY_LOCAL_MACHINE\Cluster\WVR\ConfigStore)
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello everybody,
we're running a two-node clustered file server. The nodes are virtualized and the storage for the file server is connected via iSCSI. We now extended the failover cluster to a four-node stretch cluster. The two new nodes are located in a different site. This new site has its own iSCSI storage. The nodes all run Windows Server 2019 Standard.
Extending the cluster and configurating site-awareness worked fine. Enabling storage replica however isn't working at all.
When trying to configure storage replica via the cluster gui we get the following error:
The same thing happens when trying New-SRGroup via PowerShell:
No matter what we do, we get the error "The requested object could not be found" for the drives specified by driveletter, by uniqueId and even the local drives. The replication drive and the log drives are all in available storage. The source drive is connected to the file server role.
Running a Test-SRTopology works fine if we connect the log drive on site one to the file server role, so that it is shown as online. Test-SRTopology gives zero errors or warnings.
Running "Test-Cluster" in Powershell does also not result in any significant warnings. The only warning, we get is network related, that we only have one cluster communications network. Since we disabled cluster communication on the iSCSI Network.
Any help getting storage replica to work would be greatly appreciated.
solved,
for whatever reason we had to manually create a registry key.
Computer\HKEY_LOCAL_MACHINE\Cluster\WVR
new registry key: ConfigStore
(Computer\HKEY_LOCAL_MACHINE\Cluster\WVR\ConfigStore)