Storage VMotion in LUN protected with SRM

Similar Questions

• I can storage vMotion two popular VMS with shared disks?

  I have an ESX 3.0.2 Server with local storage and two ESX 3.5 with fiber channel SAN servers. Two VM sharing disks and run it on the computer with only the local storage. Can I use storage vMotion to move these to a 3.5 servers and more at the SAN?

  If not; can I migrate the servers (when closed) to the SAN and 3.5 servers without breaking the links on shared disks?

  If you close the virtual machines and migrate them, you should be able to access the disks - as the sVmotion update pointers in the vmx file.

  If you upsize and lose access to the disk, you will need to do is open the.vmx file for each virtual computer and update the path specified for each disc, not too hard to fix at all. -If you don't like that, you can simply remove and re-add the disc in the VM properties

• Storage VMotion failed - LUN "Ongoing resource of use"

  I had a VM, sitting on an oversized LUN, so I reduced the size of the LUN.  The result is a corrupt VMDK.  It's nice that I can rebuild not the end of the world.  The problem is that when I right click on the virtual machine, that it only allows me to "Migration complete" - I can't delete the virtual machine.  If I select a full Migration it will fail to 33% with the error "the virtual disk is either corrupt or not a format supported."  If I tried to remove the source LUN or destination LUN I get an error "resource is in use.  So my question is how do I get rid of this virtual machine and these LUNS so I can start again.

  I'm on ESX 3.5 U4 on CF to FAS2020. Let me know if you need more information.  Thanks for any help!

  Always disconnect shows upward in the inventory.  This part of a cluster?  Disconnect the server. Remove the host ESX to vCenter.  Then, add it in.  Sometimes, remove the server from the cluster is enough, but you may need to remove the vCenter server.

  -KjB

  VMware vExpert

• Storage vMotion fails with the error below

  I'm trying to run a virtual machine's storage vMotion. It fails with the error below.

  This method is disabled by 'moref = 17705'

  #1 method - manually remove the entry from the VCDB.

  • Stop the Service of VC.
  • Connect to the SQL Instance.
  • Run the SQL for VCDB.
  • Select * from VPX_VM WHERE name LIKE '% VM_Name % '.
  • Note the ID of VM in column 1.
  • Validate the stale entry.

  Select * from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = "vm - ID".

  • Remove obsolete entries.

  delete from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = "vm - ID"

  • Start the VC service.
  • Try Storage vMotion.

  Method #2-si this does not work, save the *.vmx file once again which will fix the problem.

  Note: To do this, you will be required to server unavailability.

  • Power off the virtual computer.
  • VM unregistered inventory.
  • Navigate to the path of the data store and VMX re-register.
  • Start the virtual computer.
  • Try Storage vMotion.

• Storage test 55 certification vmotion, storage vmotion fails with "Could not lock file" on the virtual machine during storage vmotion

  In my view, that it is a known problem in ESXi 5.5 Update 2 release notes, someone knows a solution yet? This is an excerpt from the release notes:

  • Attempts to perform live storage vMotion of virtual machines with RDM disks can fail
    Storage vMotion of virtual machines with RDM disks can fail and virtual machines can be considered in turned off of the State. Attempts to turn on the virtual machine fails with the following error:
    
    Cannot lock the file
    
    Workaround: No.

  VMware support for the record said that the patch will update 3, it is known as an intermittent problem. Finally, it happened to me on the 9th attempt.

• Storage VMotion for a virtual machine with SAN LUNS attached to it. They are all going to?

  Hello

  Don't know which section of this post, so sorry if its wrong.

  We are eager to Storage VMotion of our SQL VM. These are our SAN 3040 of NetApp. In the virtual machine (windows 2003), they have also connected to the network SAN NetApp 3040 LUN.

  What I need to know is, if we tried to do the other (NetApp 3170) SAN Storage VMotion problems due to the fact that its storage not only fast vMotioning of VMs its self, but also the LUN or LUNS will remain on 3040, and the virtual machines moved to the 3170?

  Who is?

  If more info should help just shout!

  Cheers in advance...

  Rik

  RDM's Raw card device.

  As I posted earlier, you need to move data to the Raw LUN for LUN Raw new either through data copy inside the VM if you map the new LUNS brutes who him or copy.

• Storage vmotion and SRM

  Hi guys,.

  Another question.

  How SRM cope with moving LUNS replicated and not replicated virtual machines?

  In blog of eppings duncan, he created agreat SRM FAQ. Inside, he mentions the following:

  What happens if you move one of the virtual machine that is protected in a data store that is not part of the current protected group of the virtual machine?

  Protection is revoked for the virtual machine. There will be a small yellow

  triangle associated in the protection group. This will be true

  even if you move (for example, storage VMotion) the virtual machine to a different

  store data that is replicated to the recovering site.

  If at this point, how do you take the virtual machine out of the protection group or add the virtual machine in the protection group?

  Thank you

  DC

  A new analysis of storage using the Array Manager Setup Wizard will clarify this point.

  See you soon

  Tim Oudin

• All protected LUNS must be identified separately within the Group of Protection of SRM. But this isn't the case!

  Hello

  I installed the latest version of SRM in our environment. We have 2 IBM midsize v7000 storage on primary site and disaster. We use array based replication.

  I have configured groups of consistency for all LUNs replicated through v7000 storage.  All LUNS are replicated successfully. I installed the last IBM midsize SRA on two SRM server. There is no problem...

  Everything is ok. But; When I try to create protection MIS group, I couldn't see LUN separately. If you look at the images below, you will understand what I mean;

  I have four different coherent group on v7000.

  

  The SRA has been installed successfully.

  

  I see all the cohesive group of v7000 under the SRA through SRM.

  

  IT'S MY PROBLEM! All LUNS must be separately! But I see a group of data store! It must be like on the right side. I want to create different Protection Group all LUNS. But I couldn't choose lun separately.

  who knows what is wrong?

  

  Thank you.

  Check if any of your virtual machines have VMDK on all LUNS, because you'll be able to create a Protection Group separately for each single logic unit number if a virtual have virtual disks on more than one logical unit number.

• 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

• Storage vmotion with several virtual disks

  I have a couple of virtual machines with virtual disks on them.  I have a need to pass one of the virtual disks in a different lun while leaving others in the current location.  I would like to move this disk without impact on our users, which means that I like to keep the operational machine.  I did several Vmotions storage with great success.  I want to know is if there is a way to use Storage Vmotion and tell him to move only a single virtual disk on a multi VM disk.

  Does anyone know if there is a way to do this?

  Thank you!

  Download and install the RCLI.

  Run the sVMotion intereactive mode.  This will guide you through the process with the ability to move the individual disks.

  command line must start with

  SVMotion - interactive

  If you feel this or any other answer was 'useful' or 'proper' Please consider awarding points

• double control system - storage vmotion with or without storage in common?

  If I have a cluster of existing (vsphere 5.1), where 5 guests are all connected to the FC storage, and then I create a new cluster (managed by the same vcenter) with its own storage space, and leaders of each group DO NOT access other cluster storage:

  I can storage vmotion a computer virtual from one cluster to another?

  Y at - he of the opposition? Takes if press the company or company longer? The servers are in the same cluster, or is simply to be managed by the same sufficient vcenter?

  Hello

  It is possible to check this: VMware vSphere 5.1

• Storage vMotion possible with ESXi Std Edt or not?

  Hi all

  We have two implementations of VMware with ESXi Standard edition licenses installed on the two site. A site has vCenter Server Foundation edition while the other has vCenter Server Standard Edition.

  The problem is that the site with vCenter Std and vSphere 5 Std doenst allow storage vMotion (see image below)

  

  While, on the other hand, site 5 Stnd vSphere with vCenter Foundation allows storage Vmotion (see image below)

  

  How is it so that vSphere Stndard this edtion of different characteristics in different places?

  I had recorded the call and found the solution... VSphere 5.0 and 5.1 gives really different set of features with the same Std license vSphere.   Take a look at the link for options available with vSphere 5.0 and 51 below.

  1 compare vSphere 5.0 editions

  Compare the editions of vSphere VMware for Cloud Computing, server and data center virtualization

  VSphere editions 2 - compare 5.1

  Compare VMware vSphere editions: managed Virtualization & amp; Cloud Computing

  For a test, I used the same Standard edition server with 5.1 key to it has worked well with Storage vMotion Option available :-)

• VM have been storage vMotioned to another data store, and now I have 3 VM with white "!" inside a red square and I want to understand the cause of this.

  VM have been storage vMotioned to another data store, and now I have 3 VM with white "!" inside a red square and I want to understand the cause of this.

  Can you try to make a vmotion host and see if it gets resolved? If not, can you close the virtual machine and start again? I have seen this problem before and a stop and start resolved.

• Storage vMotion with zero eager thick

  Hello

  In version 5.0, with the GUI, when you want to svmotion a virtual computer, you have three choices for storage: zero lazy thin / thick / thick zero eager.

  We have a lot of virtual machine in lazy mode thin / thick and want to convert it to thick eager without interruption of service.

  In Powershell, smovtion is ' Move-VM cmdlet. It has the possibility of "DatastoreStorageFormat" who don't accept that end/thick for the parameters (from the documentation).

  After a few tries, moving a VM thin with the cmdlet and "thick" in setting create a vmdk in "zero lazy thick."

  Some try with "EagerZeroVirtualDisk_Task" of the API too, but a problem with a lock on the file. It is not really clear in the documentation, but I think that the virtual machine must be poweredoff in order to use this feature.

  Is there a way to powercli to a storage vMotion and (re) create vmdk zeroing eager mode thick?

  Try it like this

  $vm = Get-VM -Name MyVM $destinationds = Get-Datastore -Name MyTargetDS $HardDisks = @(Get-HardDisk -VM $vm)
  
  $spec = New-Object VMware.Vim.VirtualMachineRelocateSpec $spec.Datastore = $destinationds.Extensiondata.MoRef
  
  1..$HardDisks.Count | %{
      $newFilename = "[" + $destinationds.Name + "]" + ($HardDisks[$_ -1].Filename.Split(']')[1])
  
      $objBackinginfo = New-Object VMWARE.Vim.VirtualDiskFlatVer2BackingInfo    $objBackinginfo.DiskMode = "persistent"    $objBackinginfo.eagerlyScrub = $true    $objBackinginfo.FileName = $newFilename
      $objDisk = New-Object VMware.Vim.VirtualMachineRelocateSpecDiskLocator    $objDisk.DiskID = $HardDisks[$_ - 1].Id.Split('/')[1]
      $objDisk.DataStore = $destinationds.Extensiondata.MoRef    $objDisk.diskBackingInfo = $objBackinginfo
      $spec.Disk += $objDisk
  }
  $vm.ExtensionData.RelocateVM_Task($spec, "defaultPriority")
  

• Storage vMotion - WITH RDM? - Or will they ignored most of the time?

  Hi all - I have a storage vMotion, 5 hosts in the cluster - five or 6 virtual machines with RDM are pinned to specific hosts for the love of the DRS, but I want to go where the readers of the OS, then to VMDK is one San to another. If the virtual machine has a C:\ drive on the data store, all the other disks on the virtual computer is through physical RDM. ALL I need to move is the c:\(VMDK) in the process of storage vmotion.

  Time without are connected and work today to the ESX host in the cluster, all hosts are sized to see the RDM.

  My question is, when we go to perform the storage vMotion, how to avoid such failure? the RDM are my concern in the past, I think I remember a machine do not migrate when he had attached RDMs.

  any comments or thoughts would be really useful.

  Nick

  You can also move the ROW pointers with the data store 'change' - Assistant. Just be sure to select "same as source" for the format of the target disk. If you choose thick or thin, the RDM will be transformed into a VMDK, but with "same format" simply the ROW pointer is moved to the new data store.

  -Andreas