Failover service won't start

[andrewa]

Thanks for you reply but my replication has been working fine with source and destination settings remaining as they should.

I think I may have discivered what the problem is but not sure if this is a bug or a known issue.

It would appear that after upgrading to V6 you had to change the iSCSI daemon option from the default SCST to IETD in order to see LUNs/datastores previously created with Open-E v5 and formatted as datastores by Vmware, the iSCSI failover service will not start!

Even when volume replication is consistent, iSCSI target names and SCSI IDs set to be identical, the fail-over service will not start if you are running with the IETD iSCSI option.

You need to switch to SCST and create new or re-format existing volumes in order for VMware to see the LUNs/Datastores, both of which require a large maintenance window and moving of VM data files in order to fix.

Not sure if there is some way of re-signaturing the disks rather than re-formatting but hopefully someone will be able to assist on this one. I vaguely remember seeing something somewhere about it but can't find it now!


Thanks

[webguyz]

I was getting ready to redo my DSS server and get ready for Citrix Xenserver which means setting my ISCSI to IET from the SCST I currently have. From what your telling me is if I do this I will not be able to do autofailover since the volumes are IET, is that correct? Ouch!

Can anyone from Open-E verify that?? If thats true then I won't be able to use Xenserver with DSS 6 because I need to ultimately need have autofailover to a second DSS.

[webguyz]

Latest versions of DSS V6 now support SCST so there is not need to switch to IET for the ISCSI daemon when using Xenserver.