The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Moderators: anton (staff), art (staff), Anatoly (staff), Max (staff)
Code: Select all
$server.ExecuteCommand( 0, "restoreHAPartnerNode", $params)
Code: Select all
#$server.ExecuteCommand( 0, "restoreCurrentHANode", $params)
Code: Select all
$params = new-object -ComObject StarWindX.Parameters
$params.AppendParam("deviceID",$device.DeviceId)
$params.AppendParam("partnetTargetName",$partnerTargetName)
$server.ExecuteCommand( 0, "restoreHAPartnerNode", $params)
In such an instance, the replacement storage would be completely blank: no partitions, nothing. And I want to know what process to follow, to re-establish StarWind replication via command line, under such circumstances. I have not found StarWind documentation to cover this. Did I overlook it?"how to recreate and re-synchronize replica images, in the case of a host or device failure."
I wasn't concerned about the script blanking the partition. I was concerned about the script being able to handle a partition that is already blank due to external causes such as hardware failure -- which is, after all, one of the things StarWind is supposed to be able to protect us from, right?Your concern about a partition being recreated completely blank does not have any grounds, as what you see as "restoreHAPartnerNode/restoreHACurrentNode" is the internal parameter of the service and does not mean the partition is going to be blanked.
Code: Select all
Import-Module StarWindX
$server = New-SWServer -host 127.0.0.1 -user root -password starwind -port 3261
$server.Connect()
if ( $server.Connected )
{
foreach($device in $server.Devices)
{
$device
}
$server.Disconnect()
}
else
{
"Server not connected"
}
Under data migration I meant creating a new device on server 2 (if we assume server 2 was faulty), connecting it via iSCSI and copying all information from the old volume on server 1 to the new HA device on server 2.
Guys, sorry for interrupting your discussion, but I think you forgot about one thing, wallewek.wallewek wrote:Well,THAT was interesting...
It looks to me that, in a (Server 2016) two-host cluster, if I stop the StarWind VSAN service on one host, it automatically stops that service in the other host as well! Am i imagining things? Kind of makes me wonder how we are supposed to proceed, if we want to keep the cluster online while taking one host offline for maintenance.
In other news, I tried another approach for optimized copying and swapping of a cluster hard drive. No joy, again. And even though even though I took the one cluster host offline and tried to stop the SW VSAN service, I wound up with a crashed cluster, including all guest VMs.
Next try will have to be a full, un-optimized raw copy of a host hard drive from the "good" host. The only question is, what do I have to do, to let me copy that drive without file access conflicts?
-- Ken
Hello wallewek,It looks to me that, in a (Server 2016) two-host cluster, if I stop the StarWind VSAN service on one host, it automatically stops that service in the other host as well! Am i imagining things? Kind of makes me wonder how we are supposed to proceed, if we want to keep the cluster online while taking one host offline for maintenance.