iScsi Auto Failover

[To-M]

Looks that we might be able to make it next week. Keep in mind that we have so many tests to run that if any issues arise we may need additionally time. But so far we are on schedule for next week.

[robertdalco]

Hello All and T-Mo,

So now it is next week. What will I specifically need to put on my order to make sure I get the correct revision to do iSCSI failover? Does it require any additional licensing/cost for the iSCSI failover feature?

Even if there isn't a requirement to list specifically, I still would like to put it on the order.

Thanks,

Robert

[To-M]

It will be in DSS only so there will be no license part number for this and all updates for DSS will have this feature for free as well.

I have a version that you can test before the official release if you wish to test it. Just email me.

[Robotbeat]

What number build has the iSCSI failover enabled? (i.e. the engineering-stage builds)

[To-M]

zooom

build_3145_RC4

[robertdalco]

So now I am pushing it.

With this latest build. Can I have two units locally configured for iSCSI failover and still mirror to a remote unit asynchronously?

Robert

[To-M]

We only have synchronous Volume Replication (Block Level) for iSCSI and FC volumes - asynchronous is for our Data Replication (File Level). Also you can only replicate 2 servers for iSCSI Volumes Server A to Server B.

[zeki893]

So is there any updated documentation for this? Like explaing how it works and how it should be setup. Also how will licensing work? Do i need to buy 2 dss licenses?

[To-M]

For the iSCSI Auto Failover you will need 2 DSS modules only, there is no additional license fees for this. Below is a Quick Start guide for the Auto Failover.

Auto Failover Quick Start Guide:

1. Set up volume replication and start the replication task on the primary system.
2. On both systems, create a new target with exactly the same name and assign the LUN by clicking on the "+" button.
3. In the GUI menu, SETUP -> Network, configure bonding using eth0 and eth1.
4. Connect the cable from eth0 to the first network switch and the cable from eth1 to the second one.
5. Do the same as above on the secondary system.
6. On both systems, configure the virtual IP on the bond and select it as an auxiliary interface.
7. Select eth2 as the auxiliary on both systems (it there must be 2 auxiliary interfaces selected on every system).
8. In Function: Failover configuration: on the primary, enable primary mode and on the secondary, enable the secondary accordingly.
9. Select one failover task and click on Apply in function failover tasks on primary system.
10. Click on Start, in Function: failover manager on the primary system.
11. Check the status in Function: Failover status; all must be OK and in Task status, the destination volume must be consistent.
12. Please (either connect or log on?) connect log on to the mirror target with iSCSI initiator using the virtual IP.
13. Create a partition and format the iSCSI disk.
14. Test the Failover function by clicking on Manual Failover in Function: Failover Manager on the primary system.
15. Afterwards, the secondary system must show "active" mode in the node status in Function: Failover status.
16. In order to test Failback, please click on "Sync volumes" in Function: Failover manager on the secondary system.
17. Once both systems are in sync, the Failback button will be activated. Please check Task Status in Function: Failover status on the secondary system; it must show both volumes as consistent.
18. Click on the Failback button in Function: Failover manager on the secondary system.
19. Afterwards, the primary system is back in active mode and ready for failover.

[pfeifferl]

Thank you for explanation!

Question: I want to test the fail-over before I buy a second DSS machine - is it possible with DSS Lite or the demo CD?

regards,
Lukas