iSCSI-R3 Enterprise

[To-M]

I have seen this error before related to sometimes either with different initiator settings not matching the Target or you need to increase the MaxRecvDataSegmentLength and MaxXmitDataSegmentLength to 65536 under Hardware Tools(ALT+CTRL+W) -> Tuning optons -> iSCSI Daemon options. Also have seen this with bonding issues but since you have had an increase in I/O with changing the WB feature for the Target Volume this would eliminate network related issues.

Thanks for assisting with the LSI selection for Johhny

[Raudi]

Thank you for the fast answer! I have changed the values, are they already active after changing them, or must i do a restart?

Stefan

[To-M]

Should be immediate but maybe both need to be restarted. We are trying to work with VMware but as you know this will take some time (they are a big company). So allot of testing will be on users and our engineers. Thanks for helping! I also want to move all VMware postings to the VMware section of the Forum. So I may move this later to that section incase you need to find it.

[Raudi]

O.k. a result i will see tomorrow after the next backup of my system. During backup and after the backup when ARCserve updates his database i got the most errors.

At the support they told me aready that you are working on a VMware certification, when you get this, this will be great! Then we can use it at our customers. This is only a test enviroment, so a certification is not important...

Stefan

[To-M]

Thanks! Any information on this helps our engineers big time!!

[Raudi]

At night during Backup i still got the errors, i try again what happens after restarting the storage...

Stefan

[fivefive1978]

I haven't tried using the VMWare iSCSI software initiator but we are having very good luck using the iSCSI HBA's from QLogic in the VMWare host systems.

Search for my posts to see the setup I have.