v8 using Storage Pool as backing store fails?
Posted: Wed Mar 04, 2015 9:05 am
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
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