ESXi 4: error in live migration (VMotion) to the different data store (Local SATA to iSCSI SAN)

Similar Questions

• Impossible to migrate from windows 2008 to the different data store

  Hai

  When I try to migrate the computer to the different data store I get the error

  "[error caused by file hard to]."

  Thank you

  Concerning

  R.Ramji

  Hello

  first move this virtual machine to another host and try to migration of storage. still, the problem you then close restarts the virtual machine host and try storage vmotion.

  It should work. If the problem continues after the error log.

• After the migration of ESXi 4.1 to 5.0 Update 1, ESXi containing the missing data store

  I intend to upgrade to an ESXi 4.1 production host, but I want to run through an upgrade of test on a separate machine. I created this using a virtual machine and the upgrade went well. However, now when I insert my vSphere client, I don't see the data store that contains data to my VM.

  Before migrating to 5, I had 2 drives, a disk of 4 GB for ESXi, and a 40 GB drive for the data of the VM installation. I could see and access times stores via the 4.1 vSphere client, but once the upgrade only the VM data store is available. Is there a reason that this is the case?

  I've updated but has not changed the partitions of data store. I have selected to migrate and keep the VMFS store, which was VMFS-3. I also tried to add the store drive 4 GB with the customer data, but an error message: "the selected disk already has a vmfs data store or the host cannot perform a conversion of partition table.
  Select another disk.

  I found this article on error message: http://KB.VMware.com/kb/2000454 , but I never actually removed from the data store. With the help of the 5.0 ESXi update I can see the VMFS store on 4 GB drive, which should have about 3.2 GB of available disk space (the rest being used by the hypervisor).

  Recommended someone else try esxconfig-volume - the list, and then use the output to a mount (http://communities.vmware.com/message/1666168#1666168), but the list command had no output at all.

  I searched through the forums and Google but you saw nothing.

  ESXi 5 has a different architecture, and I think that the problem is the size of the disk (too small) and the partition of scratch required.

  Have a look here:

  • http://pubs.VMware.com/vSphere-50/topic/com.VMware.ICbase/PDF/vSphere-ESXi-vCenter-Server-50-installation-Setup-Guide.PDF (page 153)
  • http://communities.VMware.com/message/1848769
  • http://KB.VMware.com/kb/1033696
  • http://blogs.VMware.com/ESXi/2011/03/OPS-changes-part-5-scratch-partition.html

  HTH

  Sam

• Move-VM error: VM must be managed by the same VI servers as the destination data store

  I work with 2 ESXi servers and a single vCenter server with vSphere 6.0 Update 1 b; and PowerCLI 6.0 Release 2

  I have an a datacenter, cluster, vCenter and a vDS.  I need to pass the vCenter data store to another and get the error message:

  "Move-VM VM you are moving should be handled by the same server of VI as the destination container and the data store.

  Code looks like the following:

  $vctObj = to connect-viserver $vctIPaddress

  $esx1Obj = to connect-viserver $esx1IPaddress

  $esx2Obj = to connect-viserver $esx2IPaddress

  $vmObj = get-vm-name $vmname - Server $vctObj

  $destDSobj = get-datastore-name $destDSname

  Move-vm - vm $vmObj Datastore - $destDSobj - 'End' DiskStorageFormat

  I can migrate successfully from the virtual machine to vCenter data store through the VI Client, but PowerCLI left me speechless.

  Maureen

  Try to use the Server parameter on the Get-Datastore line

• Migration of all the catalog items to a different data store in the same storage profiles

  Hello

  is any possibility to migrate everything in the catalog (time and iso files) to a different data store that has the same profile (Silver) storage group?  Because I have 2 groups of data store with the same profile of storage (Silver) and I want to delete one of this cluster.

  I found this kb: http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2058094 but it speaks solely of media files of migration between different storage profiles.

  Have vCD 5.6.4

  You happen to use rapid Provisioning?  This is probably the only problem I can think of.

  Environments that have no linked Clones or shadows created from them, you can just Storage vMotion them between the same storage policy data warehouses.  Just make sure that the data store or a store of data clusters are visible in vCloud Director first of all in the framework of this storage policy.

  When you use linked clones, I don't remember the exact process... I think that I have in my office somewhere (I'm at home now).

• ESXi 5.0 servers don't recognize that same NFS share to the same data store

  I have a setup of vSphere 5.0 running VMware Workstation 8.  I have two ESXi servers that are accumulating the same NFS share (with the same IP address and the same directory path), but for some reason, they don't recognize it as the same data store.  I deleted and added to the data store again and checked that I am getting the same way on both nodes.  However, vSphere don't let me use the same name when I ride sharing NFS as a data store on the second node. vSphere changes the name of "NFSdatastore" to "NFSdatastore (1)" and will not let me change, say that the name already exists.

  The NFS file server is a VM of 2.99 OpenFiler, which IP 192.168.0.100 (and is in DNS as "openfiler1").  The path is "/ mnt/vsphere/vcs/datastore.

  The NFS mount works great as a data store on the two servers ESXi, except for the fact that vSphere sees two data stores.  I have a Red Hat VM running on each of them, and when I browse the data of each ESXi Server store, I can definitely see two configs VM, as well as a few ISO images that I put on the NFS share.  However, I can't vMotion as he complains about not being able to access the configuration file and the file virtual disk (vmdk) of the other node.

  On the OpenFiler, the directory/mnt/vsphere/vcs/datastore is the property of "ofguest" in the "ofguest" group, and the permissions are "drwxrwsrwx +".  All files under the directory are also held by "ofguest" in the group "ofguest".  Vmx files have permissions "rwxr-xr-x + ', and the vmdk files have permissions ' rw +-

  I did a lot of Google search, read best practices, etc.  Any help is appreciated.

  UPDATE: he Figured out - leakage / on one of the paths of NFS mounting.  DOH!

  Maybe this can help you:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1005930

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1005057

  Concerning

• try to start the bonjour service, but get the error message: windows could not start the Bonjour service on local computer

  error message
  Windows could not start the Bonjour service on local computer
  Error 5 access is denied

  I have Vista Home.

  This prevents me to update I have tunes.

  Completely uninstall iTunes. Download the update manually from Apple or here. Restart the system and then install the software you have downloaded.

• ESXI 5.1 "the disc is not thin-provisioned" after copying to the new data store vmdk

  I wanted to create an external backup as a 2nd VM ready-to-run on the 2nd data store.

  I've removed all snapshots, stop the machine virtual and exported the OVF file to a computer, adjusted to the size of the original virtual machine starts in Gparted to update the partition and restart. All very well.

  I then tried to deploy the OVF in the data store alternative (235GB slim, thickness according to the deployment of 250 Wizard). I tried both thick and thin but the error message "cannot deploy the OVF. The operation was cancelled by the user.

  I then manually downloaded the VMDK & OVF file to the 2nd data store and tried to inflate but then received the message "a specified parameter was not correct. The disc isn't thin provisioned. ».

  It seems I have dealing with the same thing, as this is the document here (http://pubs.vmware.com/Release_Notes/en/vsphere/55/vsphere-vcenter-server-55u3-release-notes.html).  However, I have no idea what to do now... and I'm worried because it seems that my backup plan may not work if I can't restore an OVF/VMDK from a disk of visas.

  The solution to the first problem here: https://communities.vmware.com/message/2172950#2172950 that solved my problem 2nd too.

• List not updated virtual machines after the migration of the virtual machine to a different data store

  My vSphere infrastructure 5 uses several data stores.

  Two data warehouses are associated with NFS on different NAS shares.

  I migrate VM to a data to another store.

  The navigation data store, I see that the files are moved from the old data store to the new and that no file belonging to the migrated VM still does exist on the old data store.

  If I look at the list of VMs on the old data store, I still see the old VM.

  I see it in the list of the virtual machine on the new data store as well.

  I checked that no .iso no pagefile is in the old data store.

  How can I update the list of the virtual machine on the old data store?

  Above all, how can I safely delete the old data store by ensuring that the virtual machine works very well on the new data store and I don't lose anything?

  Concerning

  Marius

  This use of data store 'Phantom' is usually observed, if the current configuration of the virtual computer points to the 'old' data store (diskette, CD-ROM) or the virtual machine contains snapshots where - at the time where tone have been created - the VM has had these references. Once the snapshots are deleted from data store 'ghost' will go away from summary of the virtual machine.

  André

• ESXi 4.1 reinstall without loss of data in the system data store

  Hello world

  because of incorrect tape device configuration (see more low http://communities.vmware.com/thread/289847?tstart=0), I have to reinstall Esxi 4.1 in the same place where the system partition is also home to the Oracle data disk (I didn't have the choice because the system starts on the table of great raid with SSDS, there was no such thing which allow me to pre partition the RAID disk into several partitions and choose) only a small partition to install ESXi files), what happens if I reinstall ESXi with the method of "REPAIR"? will be large files within the system data store destroyed or intact?  Help, please.  Any suggestions are greatly appreciated.

  When you do a normal installation of ESXi, the whole installation drive is wiped regardless of the existing partitions that exist.  With a repair only install ESXi system partitions are left.  Any data store must be perserved and after the repair, you can save any virtual machines that were welcomed on this data store.  If the repair not proceed with the installation (for example, if the data store exists in the first 900 MB of storage), then you will get a warning in this sense and a new facility (wipe the entire disk) is performed.

  So with a repair, you should be fine, but I want to take a backup without worrying.

  Dave

  VMware communities user moderator

  Now available - vSphere Quick Start Guide

  You have a system or a PCI with VMDirectPath?  Submit your specifications to Officieux VMDirectPath HCL.

• Migrated virtual machine appears in the two data stores

  Hi all

  A bit of background on our installation first. servers ESX 3.5 vcenter 4.0 (just improved 2.5) + 2 + 2 data warehouses configured in 1 box of MSA.

  Here is what happened. I've migrated a VM from A to B data store using "Migrate" in vSphere client on vCenter.

  On the vSphere client, virtual machine displays now two data warehouses. In the browser data store, the vme even appears in the two data stores. Datastore shows 20 GB to 20 GB provisioned and 0 GB to 20 GB used. B displays 20 of 20 put into service and used 20 20 GB.

  Migration seems to have succeeded. I migrated about 10 other vm and they reside only on a data store. All virtual machines are working properly. I tried to migrate the computer back to A virtual. He showed only a data store. But the problem appeared again when I migrated the vm to B. I tried to move the virtual machine back and forth between servers ESX, no difference.

  Any ideas? The virtual machine is working well, and it is not necessarily a critical problem. But it's annoying, because I intend to reorganize the data store has and the fear it could cause a problem.

  Thank you so much in advance!

  anything mounted on the CD/DVD drive, as an ISO which can be on A Datastore?

• alleged connection to the data store local preventing vmotion

  I have a VM that signals a connection to the local data store on its host, and therefore can't do vMotion elsewhere.  The virtual machine has two virtual drives, which are both on a SAN storage.  The virtual machine has been previously connected to an ISO on the local data store, but it has since been replaced by client device.  He always insists that he's using something on this data store, however.  I've looked through the vmx file and don't see any reference to it.  I also tried to remove the data store, but he claims that the file system is in use.  The hosts have been recently updated to esxi 6.0 U2, and it's the only VM that now seems this behavior.  Any suggestions on what could be the cause?  It is a server important enough in this environment, and be locked into a single host makes me a little anxious.

  Turns out it was because of an old cliché.  If you get an ISO from a data store and take a snapshot, the virtual machine will keep a link to that store of data even after changing the client machine.  As soon as you delete the snapshot, this relationship goes, and access to this database is therefore more a review when searching valid hosts.

• ESXI 6.0, problem of data store local ssd

  Hi all,

  I have a desktop pc (HP Elite 8200), i7 cpu, 1 x 250 GB HARD drive, 1 x 240 GB SSD... (240 GB do datastore with name SSD), there, installed free VMware ESXI 6.0 on 250 GB HARD drive.

  Yesterday to buy second SSD 240 GB, I want to increase datastore 'SSD' with the second disc, but the process is hang. No warning, no error... but can extend the data store. Trying to

  create the new datastore with second SSD, but still hang processes. Maybe someone has a similar issue?
  

  I try to change SATA cables - does not work for me, try to detach an SSD - works for me... Finally reinstall ESXI 6.0 U1 with ESXI 6.0 U2 - this work for me.

  successfully create datastore with 2 x 240 GB Kingston SSD.

• How to migrate Office persistent link clones of workstations for the new data store

  Hello. We have clones of persistent link to view running in the environment from our view. We need to migrate these desktops to new storage. Rebalancing is out as this will include a refresh operation - destroy anything and everything installed in c:\ of the user. Is there a method to migrate Desktop clone link persistent to a new data store, while keeping the office in the same exact state (i.e. c:\ is not updated).

  Thank you

  Never say impossible. I came across the solution when I read the article by Duncan Epping:

  http://www.yellow-bricks.com/2012/03/15/Dr-of-view-persistent-linked-clone-desktops/

  I have that for my situation. Basically, replicate data from view in the new storage warehouses. Set up data warehouses replicated without re-signing with the cluster of ESXi. Turn the power off and unsubscribe the vCenter view workstations. Save the workstations from the data store replicated/mounted to vCenter and power over desktop computers.

  VCenter, nothing dramatic has happened if she sees just as vm being unregistered and re-recorded activity from the same exact data store (the same UUID). View Admin is happy because he sees just the events as desktop computers that have been turned off and then subsequently in reverse. Nothing has changed regarding the database to view ADAM, we still use the same data warehouses.

  I have already tested before for a scenario of View DR, and he succeeded. Between remembering who and Duncan's article helped me to adapt the same process for this. Nothing is impossible

• Storage Vmotion to a new data store get UUID and MAC change to hot after reboot

  Hello

  I have a strange thing that happened on my vcenter.

  Just do a vmotion hot storage between two data store.

  I reboot the virtual machine and received no message to validate if I moved or copied.

  When the virtual machine is restarted, I see that changing the UUID and MAC address.
  Make me an error with an application running on it.

  Did anyone see that already?

  We do some testing and solution for this problem is to download the VM's vmx file on the local system and apply these settings:

  If you want to change the setting always or always create , power off the virtual machine and change its configuration (.vmx) file. Remove the line containing uuid.action = "crΘer" or uuid.action = 'keep'.

  The configuration line such as this to keep the UUID and MAC after vmotion: uuid.action = 'keep '.

  Reupload the file on the data store and restart the virtual machine