Hello florian,
There is really nothing stupid in what you have done. That's why we actually run the forum - to share the knowledge and spread best practices of StarWind implementation.
1. Truly, Disk Bridge reserves the entire physical disk (not the partitions) and reserves it for using via iSCSI. If you need to allocate a separate partition or part of the partition, you can use Image File Devices or Mirror (RAID-1) devices.
2. Also, Please note that if you are creating concurrent connection and data read/write mode by simultaneous access of several initiators to the same image file or an image file, this is not recommended. This will cause data corruption and make the data inside the file inconsistent.
In order to avoid this, you can do one of the following:
- Either create separate image files per every initiator and allow one
connection only per image, or
- Use Cluster services (such as MS Cluster Service), dedicated SAN file
systems (Data Plow SFS, etc.) or software, allowing NTFS to be used as SAN
file system (MetaSAN, or alike).
You can refer to the documentation on using MetaSAN and Dataplow to share
iSCSI targets:
http://www.starwindsoftware.com/images/ ... etaSAN.pdf
http://www.starwindsoftware.com/images/ ... nd_SFS.pdf
Please let us know if that helps.
Thank you
Rob