An unknown error occurred while validating the server
22-Dec-2017 02:11
You recieve the following error: This does not occur if you have at least three nodes in the cluster.
This issue occurs because of a by-design code change in Windows Server 2016 for asymmetric storage clustering behaviors.
This is expected behavior during initial sync and can safely be ignored. If you see this behavior during ongoing asynchronous replication, investigate the partnership to determine why replication is delayed beyond your configured RPO (30 seconds, by default).
Under rare and usually unreproducable circumstances, rebooting a server that is in a partnership leads to replication failing and the rebooted node logging warning event 4004 with an access denied error.
This may occur when some error condition prevents removal of replication or when you reinstall the operating system on a computer that was previously replicating data.
To fix, you must clear the hidden Storage Replica partition off the disks and return them to a writeable state using the but you should not skip restarting the server if requested by the cmdlet.
Status: A process has requested access to an object, but has not been granted those access rights. Begin Processing() Test-SRTopology : Object reference not set to an instance of an object. Test SRTopology Command This is caused by the cluster functional level still being set to Windows Server 2012 R2 (i.e. Storage Replica is supposed to return a specific error here but instead returns an incorrect error mapping. If Cluster Functional Level = 9, that is the Windows 2016 Cluster Functional Level version needed to implement Storage Replica on this node.
Guidance: Possible causes include network failures, share creation failures for the remote replication group, or firewall settings. At line:1 char:1 Test-SRTopology -Source Computer Name nodesrc01 -Source Volume Name U: - ... If Cluster Functional Level is not 9, the Cluster Functional Level will need to be updated in order to implement Storage Replica on this node.
Test-Sr Topology cmdlet does not accept IP address as input for target computer name parameter. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Category Info : Invalid Argument: (:) [Test-SRTopology], Exception Fully Qualified Error Id : Test SRTopology Failure, Microsoft. This is not supported in Storage Replica; you must pick a different volume to replicate.To add the storage, you can run the following command on the node in the second site: This will not work with node local storage.