Hi,

Sure, I will keep you posted.

Thanks for your update. I will log an internal testing request.
Yet, I'd like to mention that such a setup is supported, so I can't provide any realistic ETA for the answer.

You are speaking to a living person who is trying to help, so I would appreciate some respect. How I can find balans?! I can't advise on that, as it is an empirical process. Setting too small results in too many operations too large might be not optimal for upload. What I see people do is split tape...

I had discussed your request internally. The tape redirector was not tested with 2025. I will log an internal request and see what can be done about it.

1. How to cancel the stuck replication jobs? Try restarting the service. 2. I have tapes the size of that under a full control by the PS scripts. Let's say they are of 50GB each. During cloud replication each tape splits for 10MB blocks that generates a lot of blob operations at a cloud level. At t...

There is a recommended size for the upload to the cloud (e.g., 4 GB).
Tweaking the JSON is about finding the balance.

The size is imposed during tapes' creation, and you can split it in the config.json file.
Try restarting StarWindService.

Sadly, no P2V for the 32-bit version anymore. Try older versions of disk2VHD.

No worries.
StarWind VTL requires the specific HPE driver to operate. Could you please try installing it?

Thanks for your update! Can you please install the HPE drivers https://www.starwindsoftware.com/resour ... ended%20to ?

If you can manage StarWind VTL through the GUI, then you might have a TRIAL or commercial key. In both cases, you can get support (for commercial only if you have an active support contract, though). Please also let me know what drivers you have for the HPE Tape driver Could you please pull the logs...

Try the software that supports instant recovery.

Good point, but, sadly, the Free version does not allow for the console.

Form what I found out recently, 32 bit does not exist, unfotunately.

We discussed your request internally, and interoperability with WSL was not tested and is not considered a production scenario.
The system does not align with what we recommend for the setups.