pkw0815
asked on
Prevent ESX Server from taking over temporarily available iSCSI targets
I have one san with 4 software iSCSI targets managed by Star Wind iSCSI from Rocketdivision.
Three of them are targets for GSX Servers, which are suspended every night when they are backed up.
Now I set up a new ESX Server which uses the 4th target - ok until here.
In the night when the 3 targets get available because of the backup ESX Server "catches" them all and when the GSX VM's come back their targets disappered.
How can I prevent VMware's ESX Server from taking over temporarily available iSCSI targets?
Three of them are targets for GSX Servers, which are suspended every night when they are backed up.
Now I set up a new ESX Server which uses the 4th target - ok until here.
In the night when the 3 targets get available because of the backup ESX Server "catches" them all and when the GSX VM's come back their targets disappered.
How can I prevent VMware's ESX Server from taking over temporarily available iSCSI targets?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This can be done by "masking" the targets on your SAN controller so that they can only be seen from certain initiators.
How this is done for your box specifically, I can not tell.
On some iSCSI controllers, you can assign the iSCSI initiators to a group, then map that group to a LUN. This way, the LUN is only visible to the initiators you defined in the group.
ASKER
@HeinoSkov
Thanks a lot - either the new version of MS iSCSI Initiator did it or I did something wrong in my first try. Anyway.
@robocat
Thanks too for your response - since HeinoSkov's solution helped me I didn't try yours.
Thanks a lot - either the new version of MS iSCSI Initiator did it or I did something wrong in my first try. Anyway.
@robocat
Thanks too for your response - since HeinoSkov's solution helped me I didn't try yours.
ASKER