Device Type Best Practice

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
jensenjl
Posts: 1
Joined: Tue Jun 24, 2008 8:35 pm

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
User avatar
anton (staff)
Site Admin
Posts: 4021
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Wed Jun 25, 2008 5:20 pm

It's extrelemely BAD idea to use SPTI for the hard disk. It's so bad we've removed this ability from the latest builds. However it should not fail either. Please send us back zipped logs from the target machine.

For your case - use flat image file for the best performance and IBV if you need CDP and De-Duplication features from it.
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
Post Reply