@dafyre Exactly 🙂 That is the reason why this feature was created

@minion-queen said in Upgrade your outdated hardware with StarWind HyperConverged Appliance:

@coliver said in Upgrade your outdated hardware with StarWind HyperConverged Appliance:

@tim_g said in Upgrade your outdated hardware with StarWind HyperConverged Appliance:

No public pricing means they try to squeeze out as much as possible on a per-customer basis. I'm guessing heavy commission based sales.

That's unfortunate.

GroveMarketPlace is reselling StarWind we can get you pricing. Just email me [email protected]

No MSRP without contacting someone means no business from me.

As for Homelab 3 node scenario, you could choose either 3-way or 2-way replication.
3-Way replication means you have 3 copies of the data across all three hosts. 2-way replication in 3 node cluster means that:
target1 is on Node1 & Node2
target2 is on Node2 & Node3
target3 is on Node3 & Node1

And there is no need to partition the drive. We'll place a container file and mirror them across nodes.

That's a very good post that covers information people don't often think about after deploying vCenter. Additionally, it's something helpful when studying for the VCP-DCV. Thanks for sharing!

@Tim_G said in XP: Options in virtualization setup:

Oh should have I posted my reply on SW instead?

He sees it here, too.

Since i've previously attempted on testing the VTL to Cloud Replicator, I would like to mention that there can be a possible error in the process. Just so noone rings the alarm beforehand, it's quite simple to overcome the "Setup failed to install Microsoft .NET Core. Error 3010" by either rebooting the node, or installing the .NET core before installing StarWind.

After getting in touch with them, I was actually surprised that they were kind enough to take that into account in one of their future releases and mention to have that fixed.