Device Type Best Practice
Posted: Tue Jun 24, 2008 8:45 pm
Hi,
I've been trying to find out what device type works best in a given scenario and have come up short.
I'm trying to use StarWind for an SQL server and virtual server .vhd's. I have the target server configured with a 540GB RAID10 and a 140GB RAID 1 logical drive array.
I created 2 SPTI devices for each array with 1 connection and exclusive access. I then connected to the devices from each server using the Microsoft iSCSI initiator.
Once they appeared in the client server I was able to format them and see them with a new drive letter and even get some files on them.
However, when I access them via Windows Explorer or through a DOS prompt the system essentially hangs and I have to power it off to get a repsonse.
So, am I using the correct device type for this scenario or should I be using an image file or IBVolume or something else?
Thank you,
Jamie Jensen
I've been trying to find out what device type works best in a given scenario and have come up short.
I'm trying to use StarWind for an SQL server and virtual server .vhd's. I have the target server configured with a 540GB RAID10 and a 140GB RAID 1 logical drive array.
I created 2 SPTI devices for each array with 1 connection and exclusive access. I then connected to the devices from each server using the Microsoft iSCSI initiator.
Once they appeared in the client server I was able to format them and see them with a new drive letter and even get some files on them.
However, when I access them via Windows Explorer or through a DOS prompt the system essentially hangs and I have to power it off to get a repsonse.
So, am I using the correct device type for this scenario or should I be using an image file or IBVolume or something else?
Thank you,
Jamie Jensen