v8 using Storage Pool as backing store fails?

[kpielorz]

Hi,

We last looked at StarWind when it was v6. We ran into an issue way-back-then that due to block size differences you couldn't put StarWind data on Windows storage pools.

So we're trying v8 at the moment. I have 2 * 2012 R2 servers. I create a Storage Pool comprising of 2 * 4Tb SATA drives on each host.

I then get StarWind to create a target on one of them (e.g. 64Gb) - and setup replication for it on the other node. The device is created fine, and the initial sync completes Ok.

However - if I then map that target (to say, a Windows client) - the moment it's mapped and you try to write any data to it - StarWind says one of the partners is out of sync, and the client ends up timing out / hanging etc.

If I repeat the test - but just create a 'standard' NTFS volume on one of the disks - it appears to work OK.

Should I be able to use a Storage Pool as backing store in v8?

Thanks,

-Karl

[Anatoly (staff)]

StarWind functioned well in such config in our lab.

May I ask you to provide me with next information:
· StarWind service logs at the time of the issue from all problematic SAN boxes
· Windows Application and System logs (in *.csv format) on the time of the issue from all problematic SAN boxes
· Detailed network diagram of SAN system
· Description of the actions that were performed before/at the time of the issue
· Approximate time frames when the issue happened
 

I`d appreciate if you`ll separate the logs from different servers into the different folders