Hi Boris, sure. Short version is below, please let me know if anything needs to be clarified:
1. modify the CreateHA(two nodes).ps1 script by changing both `$firstNode.CreateImage` and `$secondNode.CreateImage` from `$true` to `$false`:
Code: Select all
...
$firstNode.CreateImage = $false
...
$secondNode.CreateImage = $false
...
2. run the script and allow it to fail
3. modify the CreateImageFile.ps1 script by setting the same values for `path`, `fileName`, and `size` as used in the CreateHA(two nodes).ps1 script. Comment out the lines that create device and create target (lines 14-22, I believe). Run this twice (with appropriate modified values), once for each node.
4. open _HA.swdsk file belonging to the created HA device and change the value for `sync_status` from `0` to `1`. This needs to be changed in the corresponding _HA.swdsk file on each node:
Code: Select all
...
<sync_status>1</sync_status>
...
5. restart StarWindVSA.service on primary node
6. restart StarWindVSA.service on secondary node
7. open StarWind Management Console GUI and watch the devices sync
This appears to work in my lab. Is anyone else able to replicate this? Does anyone else see a reason this workaround should not be used (until a solution is released)?
Oh, two additional things, one minor, one potentially larger:
1. Should this thread be in the StarWind VSAN section of the forum rather than the V2V Converter section?
2. It is concerning to me that `user` and `starwind` work for the `-user` and `-password` arguments of the `New-SWServer` command, even though I have changed the password for the root user account in Cockpit. Leaving default user/password open to scripting sure looks like a security hole.