"invalid partner info" creating Replica

[Tarass (Staff)]

ETA maximum 1 week.

[chameleon]

Hello,
I am having the same issues with the invalid partner info error. Can you run the vsan servers on two Hyper V VMs? That is what I'm trying to do. I have tried the patch/fix via the software manager that was provided in this thread and I still had the same issue. I am trying to set up a replica so that I have HA CSVs. The two VMs will act as the VSAN providing an HA ISCSI target. I have downloaded the latest version of StarWind on 10/15/2015. Let me know if I can provide more information. The weird thing is that it does create a header file and img file on the replica server but they seem to be incomplete.

Thank you,
Regards,

[chameleon]

Hello Everyone,
I will need to retract my original Post. I was trying to use just one network interface for synchronization and heartbeat. You "can do" this if you check the free select box in the network interface selection window(Obviously not intended to work in this fashion). I currently don't have a secondary network interface to my offsite location so I was really just trying to cheat the system and actually use the same network interface for synchronization and heartbeat. Apparently this is not allowed. I have now tested it on local virtual machines using our domain network and a private network I set up through Hyper-v and it has worked flawlessly. Not sure if this will help anybody, considering this may not be the true issue with the original poster, but I figured might as well post this so no one else has to waste time figuring this out.

PS. I have also been able to recreate the error on the local VMs using the "unsupported configuration".

UPDATE:
I have successfully added the HA Device to the single network environment. I added a pretend private subnet to both VM's and then removed the interface after the replica was set up. I did get an error about manually synchronizing but this is because of the pretend private subnet not communicating. I just removed the subnet from the interfaces in the starwind manager and then Synchronized the device and waaaaaaahhhhlllaaaaa. Now this may not be the best practice because we are still creating a single point of failure. I have nic teaming implemented on both Hyper-v servers allowing for a redundant network connection backup to slightly address this issue. At this point in my HA/DR solution if this network goes down I'm up ^&%$ creek without a boat so this is ok for now. I will do some more testing tomorrow to see if there are any other concerns or issues in using this setup. Any comments or questions are highly valued and appreciated. Thank you.

PS: Remember to install MPIO as a feature on all servers that will be Accessing this HA Device. You will also need to enable iSCSI in the MPIO manager.

Regards,
Chameleon

[Anatoly (staff)]

waaaaaaahhhhlllaaaaa.

Well, if that works for you - it works for me)
Let us know if you need anything else