Convert a RDM

Similar Questions

• Convert a RDM a VMDK (virtual disk)

  We are currently running vSphere/ESX 4 and EMC SAN.  Our SAN is replaced by an updated model.  Dell/EMC will perform the data migration and recently told us that if we want to keep our RDM they would be able to copy their bit to bit.  Which means that we cannot change our size of the LUN.

  They told us to move our existing data to LUN more (or less) that we need to convert our RDMs VMDK.

  We currently have three separate virtual computer that will connect to a RDM on SAN (Exchange, SQL, and a file server).

  Is it possible to convert the RDM in VMDK?  If so, how?

  I searched the forums and has been unable to find an answer.

  Keep your support ticket opened until the problem is solved - you did update the VMware Support?

• Help with converter and RDM

  Hello.

  I need to convert a virtual machine that has a disc RDM.

  That's what I did.

  First convert the machine with stand virtual converter only, but excluding disc RDM.

  Then, when the new VM is ready I just add the RDM disk, but windows does not detect it.

  After that I have rescand disks but nothing happens.

  I added the new drive virtual and physical also.

  Why the STRP operating system does not detect the new disk?

  Thank you...

  Yhe comments should see the disc RDM (both physical and virtual).

  Make sure that your have remove old drivers comments (for example the HBA driver) and you have installed the latest VMware tools.

  Then, add the RDM and rescan the drive.

  André

• Convert physical RDM to RDM virtual disc Exchange

  Hi all

  I need to convert a shared disk (SAN LUNS) used by Exchange 2007 SP1 of RDM physical to virtual RDM, I would like to have a confirmation fo this strategy:

  1. Turning off the virtual Exchange Server computer

  2. Remove the disc in the virtual machine configuration vRDM mode (not the disc, of course)

  3. Fix the disc in mode pRDM

  4. Turn on the virtual machine

  Question:

  This stratey is correct?

  could I have a problem with the disc will type?

  Thanks in advance

  Angelo

  Hello.

  That's it – you can document the file mapping according to how many of them you have.  The procedure is also documented in KB 1006599.

  Good luck!

• Convert the RDM virtual disk

  I have two or three of Phsyical MSY and want to conver in VMDK... What is the process to do this?

  I got your PM, basically just treat your virtual machines of RDM, such as a physical server and convert it through the process and it will be automatically created in VMDK format.   Just make sure you select the disks attached to RDM and it can convert.  Which requires you have enough storage space, but the same process as you did with the physical server.

  If you found this information useful, please consider awarding points to 'Correct' or 'useful '. Thank you!!!

  Kind regards

  Stefan Nguyen

  VMware vExpert 2009

  iGeek Systems Inc.

  VMware, Citrix, Microsoft Consultant

• Convert iSCSI RDM NFS VMKD

  OK, a littlebit background.  I have two ESX environments: a cluster of older hardware that running ESX 3.0 and Virtual Center 2.0 and a cluster of newer hardware running ESX 3.5 and 2.5 Center Virtal.  On older hardware, are virtual machines with iSCSI RDM.  I want to convert them in VMDK of NFS and export/import in the new cluster of ESX servers.

  Now the time for the question: is it still possible?  If so, how should I do?  I read on the vCenter Converter but I have not really found a definitive answer to my question. 

  You can clone the virtual machine. When you do this, a ROW will be converted to a VMDK instead.  If you choose a NFS datastore as a destination, your work is done.

  -KjB

  VMware vExpert

• convert physical RDM to virtual RDM

  is there any document to change physical RDM to RDM virtual to a virtual machine?

  I think http://kb.vmware.com/kb/1006599 is what you are looking for.

  André

• Problem of cluster Failover MS after physical RDM conversion to VMDK

  Hello

  Last week I had to migrate 7 x 2-nodes virtual MS Failover clusters to a new data center. All clusters have been configured with the configuration of the cabin and all shared disks were in physical RDM mode.

  The target data center does not RDM disks so I had to convert all RDM disks VMDK files and use config before the migration of the IPC.

  I used vmkfstools to convert VMDK eagdrzeroedthick RDM files.

  5 clusters have been migrated successfully, but two cluster got strange question even if the procedure for all groups was the same.

  So in two groups, I have a problem where the second node in the cluster can not put online some of the shared disks. The first nodes in the clusters have no problem with the disks/SSP.

  But when I try to failover of all services, the second node may not bring online disc 1 or 2 shared, even if she can put the other shared disks online.

  VMKernel.log is not errors or warnings. I checked the configuration of virtual machines and everything seems OK.

  Any ideas what I could check?

  Just in case anyone else is facing the same problem.

  I could not find the root cause of the problem, even if it's without a doubt the conversion that triggered the problem. However, we found quite a simple solution - added new shared VMDK files, copied the files over and replaced the defective discs.

• Migration of storage with RDM

  I images migration towards a new framework for storage. Things work really well, but I hit came across a few images which have been implemented several there are many moons with RDM. The kicker is that they are in physical compatibility mode, so I can't just migrate and convert them to a vmdk. Any thoughts on an approach to migrate? Only the approach that comes to mind is to use VMconverter. This would require a little time to stop, so I'll have to postpone this possibility. I have a lot more flexibility on when I can migrate images if I could use the motion of storage because it requires downtime for images. At least there are only a small number who fall into this category but are images that are among the largest disc attached to like 500G - 1 TB...

  Buck

  Buck - I realize this post is old, but I came across it and thought I would fill you in on how to migrate LUNS RDM in physical compatibility mode.  I read so many messages saying it's impossible, but it's actually much easier than you think, but the virtual machine must be turned off.  Here's how:

  (1) log into the ESX console as root

  2) go to your virtual machine folder: / vmfs/volumes/vmfs-volume-freindlyname/vm-folder.

  (3) locate the pointer to your disk file, this isn't the file - vocation, it's the servername_1.vmdk, it's only a few KBs, inside he does nothing but point to the real disk file, which in this case will be servername_1 - rdmp.vmdk.  It is the file servername_1 - rdmp.vmdk maps of the e/s to the real lun which is still represented by ESX as something like vml.xxxxxxxxxxxxxxx and can be found in/vmfs/devices/drives.

  The source that you want to migrate (with this method, it is in fact a copy which is good, because the source is always left intact) can be a virtual disk, virtual rdm or physical rrdm, it is not «question, you will always use servername_x.vmdk as source file in the command string, you're about to see...»

  but before I continune, if you want to migrate LUNs compatibility mode physical to a new lun to physical compatibility mode, be sure to have configured the lun so that ESX can see.  If you convert virtual RDM of RDM physical mode, the same applies.  If you convert it to a virtual drive, just be sure to have a volume of vmfs with enough space to accommodate the new drive.

  (4) it is here:

  To migrate and convert physical RDM in virtual disk:

  vmkfstools-i servername_1.vmdk/vmfs/volumes/vm record/name of the server - newdisk_1.vmdk

  To migrate and convert physica RDM virtual RDM, there are two methods

  -in vi edit customer of VM VM settings, remove the drive mapped to vocation, off voltage then re - add a new hard drive by selecting the same disk make sure you only select virtual fashion, connect you and see all your data and mount points are the same.

  -from the ESX prompt in the folder of the virtual machine on the VMFS volume:

  vmkfstools-i servername_1.vmdk d rdm:/vmfs/devices/disks/vml.xxxxxxxxxxxxxxxxxxxxxxxx/vmfs/volumes/vm record/servername_1 - rdm.vmdk

  To migrate a new physical RDM physica RDM:

  vmkfstools-i servername_1.vmdk d rdmp:/vmfs/devices/disks/vml.xxxxxxxxxxxxxxxxxxxx/vmfs/volumes/vm record/servername_1 - rdmp.vmdk

  EXPLAINED command strings:

  vmkfstools-i is import-command clone

  the servername_x.vmdk is the source, the x will be held for the command of the unit, in my example I use this 1 which means that it is the second disc on the virtual computer.  the first disc file is servername.vmdk, it is generally always the system disk.

  the-d is the disc type for the destination you are converting to

  the rdm (p) is part of the type of drive saying the destination disk is gross, virtual or physical disk mode (the p stands for physics course)

  folder/servername_1 - rdm.vmdk/vmfs/volumes/vm tells us where to store the raw disk mapping file, I chose to put it in the folder of the virtual machine as you can see, you can put it on any vmfs filesystem, I like to keep things neat and clean.

  Hope you find this useful, don't let anyone tell you that you cannot migrate a physical RDM.  His false information.  This is how its done.

• Storage vMotion and RDM

  I have a question for you about storage vMotion. I have a virtual machine with a vmdk file and a RDM. I want to storage vmotion the vmdk file. There is also a file associated with the ROW pointer. How this pointer file is reassocie to the RDM? I'm evacuating small LUNS and move virtual machines to the largest lun.

  On page 199 and 201 of the basic ESX Administrator's Guide, it states that, if I select "same as Source for a RDM, only the mapping file will be migrated. Have you done this before? I just wanted to see if anyone in the field has had an experience with this process.

  7. If you chose to move the virtual machine configuration file and virtual disks, select a disc format, and then click

  Next.

  Description of the option

  Same as Source to use the format of the original virtual disk.

  If you select this option for a RDM in physical or virtual drive

  compatibility mode, only the mapping file is migrated.

  Thin provisioned using the format thin to save storage space. The thin virtual disk use as

  storage space because it needs for its initial implementation. When the virtual disk

  needs more space, it can grow in size up to its maximum allowed of capacity.

  This option is not available for RDM in physical compatibility mode. If you

  Select this option for a virtual RDM compatibility mode, the ROW is

  converted to a virtual disk. RDM converted virtual disks cannot be

  converted into RDM.

  Thick allocate an amount fixed disk space for the virtual disk. The virtual

  drive in thick format does not change its size and from the beginning

  occupies the entire data store space for her.

  This option is not available for RDM in physical compatibility mode. If you

  Select this option for a virtual RDM compatibility mode, the ROW is

  converted to a virtual disk. RDM converted virtual disks cannot be

  converted into RDM.

  Thank you

  Savoy6

  Hi Savoy6,

  When you sVmotion a virtual machine with a disc RDM, the pointer file is re-created on the new location and points to the raw LUN.

  Take a look at this kb for more information.

  It may be useful

  Concerning

  Franck

• Storage vmotion a VM with so many vmdk and RDM for NFS

  I try a virtual machine that has so much Storage VMotion vmdk and RDM disks to a NFS data store.

  I do NOT need convert the RDM disks just move the pointer with the VMDK file will be converted.

  Is this possible?

  Now if I try this hot svmotion, I get an error on the RDM which set out the following "virtual disk" drive hard 3' is a direct access mapped LUN that is not supported on the data store 'myEMCNFSds'.»»

  If I try this svmotion cold then I get no warning, but it seems that svmotion is trying to convert the RDM NFS drive.

  Is your RDM in physical compatibility mode?   Check out this article KB http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001856

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

• Windows has managed to VMFS

  The Situation: The deployment of my Exchange Server I created for my mail store and TLogs separate LUNS.  I mapped as RAW LUN and allowed Windows to manage.  I think that this might have been the wrong choice for backup reasons.  VMFS is starting to look like a much better choice because, when I save the Exchange with Backup Exec server and the VMWare Agent it allow me to backup not only the virtual machine but the additional LUNS as well.

  Question: Would it be possible to upgrade/migrate these Windows managed VMFS LUNS so I can capture in my DR Backups which will have to be shipped off-site.  This solution would not only apply to the Exchange Server, but a few other servers in production as well.

  You can see in http://www.vmware.com/pdf/vsphere4/r40/vsp_40_admin_guide.pdf (page 197).

  But it's pretty simple.

  Try on a small virtual machine first to see how works.

  Then you can use on your virtual Exchange computer. Be sure to have space enoght on the destination data store.

  A clone is also able to convert your RDM disks vmdk disks, but I suggest (if you want to use a clone) to do with the virtual machine off.

  André

• Convert VMDK to RDM

  What is the best way to convert VMDK to physical RDM. ? in the process of the esx upgrade, but I would like to convert vmdk to RDM.

  ESX 3.02, vcenter 2.5.

  Thank you.

  There are a few methods.  You can use VMware Converter, you can turn off the virtual machine and a migration to cold for a new logical unit number, or you could do a new LUN sVMotion.

  .. .but since you 3.0.2, you cannot use sVMotion

• convert RDM VRDM

  Hi guyz,

  I'm not used to working with raw device mappings, but I have a little problem somewhere.

  I searched the forums, but I've still found all the answers.

  I need to convert a raw device mapping to a virtual raw device mapping.

  The reason for which it has been used a RDM is not clear to me, the database running on this partition is only the larg of 20 GB or something like that.

  It is necessary for reasons of backup (veeam)

  You can select the physical mode or virtual RDM when you create the RDM.

  Stop the virtual machine, remove the ROW of your config and add the LUNS, and this time,.

  use the virtual rather than physical.

  -KjB

• Physical RDM virtual RDMs taken in charge in vSphere 6.0

  Anyone know if this process in KB 1006599 works in vSphere 6.0 +?

  VMware KB: Switching between physical and virtual compatibility modes in ESX/ESXi, a mapping of raw data

  We are about to move a bunch of RDM to VMDK, but we need to convert physical to virtual RDMs first (you can live storage migration [to VMDK] with virtual RDM but not medical examinations). The other part of the story is that we are running vSphere 5.5 and are about to upgrade to vSphere 6.0

  KB wrote on October 17, 2014 and I wonder if this is still the method support in vSphere 6.0 and that it has not been updated; or if it is no longer supported, in which case I have to do the migration before the upgrade?

  Thank you

  I see no reason why this will not work in vSphere 6, given that the procedure is simply to remove the physical RDM disks and add them again as RDM virtual disks... In my view, that the KB is just outdated.