You need to use CreateHA_2.ps1 and set the parameter called $storageName to the imagefile you need to convert to HA:

No worries at all.

Can you share your sample script that produces that unexpected output?

By the way, if you qualify for our NFR license (free with GUI console operational), you can request that from our team here.

Did you make sure the tape with the barcode SWB1O00A existed in the initial library?

Is your VHDX fixed or dynamic?

With StarWind VSAN, you would need at least one Windows box to run the software if it's not implying usage of ESXi, where a CentOS based appliance can be used instead. You could then present storage as iSCSI targets to your Ubuntu servers.

The issue was due to a very big number of parts the tape was broken into at the moment of tape creation. To avoid this, make sure to create a tape either as a solid one or break it into bigger parts (gigabytes or dozens of GB).

Ah, now I get it.
It looks like the issue is still there, as reported by several users. The R&D team is looking into it.

That parameter sets the number of synchronization sessions that will exist on that particular sync connection. With fast links (i.e. 10Gbps+) you can have more than 1 sync session per link.

Sorry, I did not quite get your last post. Do you mean the problem persists after the downgrade back to 11456?

Nice to hear Disk2VHD worked for you and your issue looks to be resolved. I thought I did tell you the option, and that was Local File. Anyway, just in case of any future need you may try that.

It looks like for now you would need to downgrade to avoid this issue.

An update for the community here. The issue with too much storage consumption was preconditioned by disabled automatic defragmentation option at the time of the device creation. If anybody happens to stumble upon that here is an instruction on how to overcome this: 1. Stop the StarWind service to en...

In your snippet you use only one Sync interface and one heartbeat interface. No wonder the sync operation runs via just one link :) Try adding the required interfaces as comma separated values: $syncInterface="#p2=192.168.248.2:3260,192.168.249.2:3260,192.168.250.2:3260", Also, you may wan...

I believe someone from the community has done that for sure. In my previous post in this topic I suggested a workaround for that. It will not be able to convert a VM as a whole, but will take care of separate disks you would then get attached to a newly created Hyper-V VM.