thanks actually what I realized is that the system goes up by crashing that means that it keeps crashing but somehow going forward in the install procedure until we have a stable system so far the system has been stable, although for some reason we can´t seem to connect more than 2 machines in a clu...

what crashed was the ENTIRE server

I´ll send the logs: sorry I had forgotten we are not supposed to send lengthy logs over here

We are trying to implement a simple failover solution. As requested we read the manual but is not working. In fact, as soon as we connect the volume with microsoft´s iscsi initiator the system crashes. We are running 2003 SP2 with Veritas 5.0 attached to a RAID-5 subsystem IBM EXP15 with 5 hard-disk...

you mean I need to create a iscsi target BEFORE I create a cluster?

If that´s true that explains why I´m having such a hard time creating one.

Being a newbie truly sucks.

But other than regular windows clustering, do you know of another solution that might be easier to implement?

2 servers sharing a db: if one falls the other picks up

as simple as that

maybe 2003 windows clustering would do the trick?

Hi

We are searching for a failover software to run on 2003 SP2 that will not cost us an arm and a leg.

So far we only found solutions that were too expensicve or too simple.

What do you recommend? Thanks!

I sent to support from email alcosta@kviar.com

please read and tell me if you find anything unusual ok?

Hi folks I´d like to suggest (if it already exists just tell me cuz I haven´t found it!) to starwind somehow disconnect gracefully from an image should a shutdown start in windows 2003 See, the problem is all the pages in our website (kviar.com) comes from an image in a SCSI array. That image ALWA...

Hi folks We´ve been having a real problem when trying to remove a SCSI device from an initiator using starport. More than often the initiator just crashes with a beautiful blue screen. Also, if for some reason we have to reboot the initiator, the volume gets corrupted to the point of having to rebu...

yes, it´s going to run on the client side. basically it will connect to the volume should the server using it crashes, and use the volume accordingly. the volume will be the type that cannot be shared, as to prevent being used by more than one initiator and therefore corruption will be (at least th...

Hi Since it appears that it is impossible using crappy M$ tecnology to implement a true cluster without getting horrible volume corruptions, we have to retort to good ol´failover techniques right? If that´s the case, we are wondering if there´s some kind of script, development language, component...

Actually I can access the volume with a certain degree of security it from geting corrupted as long as I do it from just ONE initiator However, if I try a 2nd initiator it says "The file or directory is corrupted and unreadable." So, only the FIRST initiator gets a readable volume: the SEC...

actually that might be the problem, as we were having corruption problems with all the images we created (and despite dataplow´s best efforts!) we may have decided not to allow clustering

if that was the case, can that be changed, or we´d have to create the image all over again?

thanks!

you are right: here it goes 3/10 3:43:23.278 b1c Srv: Accepted iSCSI connection from 192.168.0.199:2670. (Id = 0x27) 3/10 3:43:23.278 b1c C[27], FREE: Event - CONNECTED. 3/10 3:43:23.278 b1c C[27], XPT_UP: T3. 3/10 3:43:23.288 528 C[27], XPT_UP: Login request: ISID 0x801234567890, TSIH 0x0000. 3/10 ...

I´m sending it over email in zipped format as requested in this forum 3/9 18:17:42.774 >> CLanguager::LoadLanguage(language=0x409) 3/9 18:17:42.894 << CLanguager::LoadLanguage(language=0x409) 3/9 18:17:42.894 Failed to query registry ShowSplash value. 3/9 18:17:42.894 CStarPortApp::CheckLicense: Li...