T
teamsebo
Hello,
because after adding the Failover Cluster feature, our HPE MSA unfortunately does not come online as a CSV, I removed the Failover Cluster Featur (initially) until it was clearly clarified with (for example, HPE), which is why the storage in the MSA on the two Cluster node does not come online as cluster shared volume.
Since then, however, we have had a "new " problem with the originally flawless replication, see event log:
The changes for the virtual computer "DATEV-VM " could not be replicated because due to the state of Hyper-V no replication can be accepted on the replica server. (Virtual computer ID: F9F15ABC-EBC7-49CC-9125-9689C45986)
Rebooting both Hyper-V didn't take any time: Four Ethernet interface (with static private IP addresses from the same network) are currently activated. Name resolution of Hyper-V hosts and ping works. The Kerberos authentication port is activated or shared in the firewalls.
Currently, we only drive backups on a daily basis, so that in the worst case, a whole day of data would be lost! We need at least again the previously flawless replication to the second Hyper-V at the 5 minute interval.
Since I am personally currently unknown, why replication can no longer be activated and there is no longer any guarantee on the part of HPE, I may also seek advice from colleagues on joint containment and remediation or Troubleshooting.
This is the message (in german language):
f.e.: In which event logs is the following Further narrow down so it can be fixed? I can log in as (domain) administrator or was signed in with it when I got this message while activating replication. The VM did not exist before and was redesigned for testing.
Or any other hints to solve asap?!
Thank you in advance
DL
Continue reading...
because after adding the Failover Cluster feature, our HPE MSA unfortunately does not come online as a CSV, I removed the Failover Cluster Featur (initially) until it was clearly clarified with (for example, HPE), which is why the storage in the MSA on the two Cluster node does not come online as cluster shared volume.
Since then, however, we have had a "new " problem with the originally flawless replication, see event log:
The changes for the virtual computer "DATEV-VM " could not be replicated because due to the state of Hyper-V no replication can be accepted on the replica server. (Virtual computer ID: F9F15ABC-EBC7-49CC-9125-9689C45986)
Rebooting both Hyper-V didn't take any time: Four Ethernet interface (with static private IP addresses from the same network) are currently activated. Name resolution of Hyper-V hosts and ping works. The Kerberos authentication port is activated or shared in the firewalls.
Currently, we only drive backups on a daily basis, so that in the worst case, a whole day of data would be lost! We need at least again the previously flawless replication to the second Hyper-V at the 5 minute interval.
Since I am personally currently unknown, why replication can no longer be activated and there is no longer any guarantee on the part of HPE, I may also seek advice from colleagues on joint containment and remediation or Troubleshooting.
This is the message (in german language):
f.e.: In which event logs is the following Further narrow down so it can be fixed? I can log in as (domain) administrator or was signed in with it when I got this message while activating replication. The VM did not exist before and was redesigned for testing.
Or any other hints to solve asap?!
Thank you in advance
DL
Continue reading...