VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
4 Replies Last post: Nov 11, 2009 1:40 AM by vJerry  

SRM 4 and iSCSI connected volumes in Guest OS supported ? posted: Oct 20, 2009 1:53 PM

Click to view vJerry's profile Novice 5 posts since
Sep 15, 2009

Hi there,

My customer wants to have volumes connected via the MS iSCSI initiator in the Guest OS, because of vss snaps etc. We using DELL EQL PS6000E and Host Intergration Tools of DELL.

Is this supported when we want to protect these VMs with SRM 4? I think the initiator config must be reconfigured at the recovery site also, with different target IP ?!

Hope there is an answer out there.

Thnx and greetings,

Jerry.

Click to view tWiZzLeR's profile Hot Shot 149 posts since
Apr 6, 2004
I'd be interested in hearing the answer to this questiona as well. We also have a Dell (EqualLogic) PS5000XV SAN and in order to properly quiesce the snapshots for SQL and Exchange servers we must use the MS iSCSI initiator inside of the guest VM for the data volumes that SQL and Exchange are installed on and then use the Auto-Snapshot Manager Microsoft Edition (ASM/ME). The C: volume can still be stored like a normal VM on a VMFS shared volume.
Click to view Murraych's profile Novice 2 posts since
Nov 6, 2009
I'm in the process of testing this now. We have an MS Exchange server in a VM at one of our smaller sites that used the MS iSCSI initiator to connect to it's dedicated LUN's where the exchange data is stored.

What I have set up is replication of the Exchange LUN's, and in the inventory mappings of the protected site, I've set the maps for the iSCSI NIC's.

I figure the last step is a custom command to run before the Failover VM comes online to bring up the Exchange LUN's on the failover array. Am investigating this now.

Oh, also there is going to be the issue of the MS iSCSI Initiator needing to be told to look at a different target portal IP address...
Click to view Smoggy's profile Hot Shot 187 posts since
Nov 9, 2005
In theory this might be possible if you could enable the functionality via a script (powershell for example) and place that script using a callout step in the recovery plan either as a command step or actually a post-power on vm step. Powershell can be used to invoke/run scripts within VM's and in the imminent update it can invoke bat files and vbs files as well.

From the SRM side SRM itself can only protect disks it can "see" vmdk's/RDMs.

SRM cannot "see" or manage disks visbile only when the VM is "ON" such as MSFT iSCSI disks as they are not visible until after a VM has been recovered and powered on and they are also not controllable via the SRA's.

hope that helps,
Lee

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities