ESXi

 View Only
  • 1.  Virtual Machine/ RDM Issue

    Posted Aug 11, 2010 01:45 AM

    Guys

    In the past, during our disaster recovery tests, we have (as an example) created SAN-based snapshots of datastores with VM's based on those datastores.

    One VM in particular, is a file-server which has some disks attached to it as RDM's.

    In the old 3.X ESX environment, we were able to fire up a copy (SAN snapshot) of this VM in our alternate site and basically re-add the RDM mappings back into the VM using Venter with reference to its LUN:X number/location for each volume we were reattaching.

    i.e - HARD DISK #4

    Datastore: PRD_DT2/SERVERNAME/SERVERNAME_4.VMDK

    SCSI (0:4) HARD DISK 4

    RDM LUN ID 210

    This has consequently changed in ESX 4.0 (with the link being an overly complicated vml...link) and I want to ensure that when we run this same snapshot test again, that the VM has all of its RDM reattached to it, the same as it was running in production.

    Is there a way to run a script or a command that exports the configuration of this particular VM (with all of its attached hard disks, some of which are rdm's and some are standard vmdk mappings) and then when we perform our SAN snapshot copy of the VM we re-run the RDM add-ins, rather than manually adding them via vcenter one by one once the VM has been added into the inventory?

    let me know if I'm not making sense here...



  • 2.  RE: Virtual Machine/ RDM Issue

    Posted Aug 11, 2010 06:17 AM

    hi

    I can't make script. But I can suggest you run ls command under /vmfs/devices/disks

    You should get UUID name list with vml name list.

    If you need more info, you can read this link.

    http://geeksilver.wordpress.com/2010/08/09/vmware-vsphere-4-1-vs-esx-3-x-storage-identifier-understanding/

    Hope it helps.






    - Silver

    My Vmware blog: http://geeksilverblog.com[http://geeksilver.wordpress.com/2010/08/09/vmware-vsphere-4-1-vs-esx-3-x-storage-identifier-understanding/]