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

Similar Questions

• Cannot add the new data store

  VM dear supporters,

  My vSphere environment: 1 vCenter Server Foundation, 3 vSphere 4.0 Enterprise 5.0 and vSphere Client 5.0

  1. read the error message in the attachment:

  "hostdatastoresystem.queryvmfsdatastorecreateoptions...". »

  2. already the ESX02 reboot but still unable to add the new data store.

  New size of the data store = 3.1 TB

  Need to vmsupport on this subject.

  Thank you

  Hello

  Size Max LUN VMFS is 2 TB-512 MB in vSphere 4 (your hosts are in version 4), if you want to add 3.1 TB LUN first upgrade ESX hosts to version 5

  See you soon
  Artur
  

  Please, do not forget the points of call of the "useful" or "correct" answers

• Copy of VM to the new data store

  I need to copy an existing virtual machine to one datatstore to the other, initially, I thought that I would be able to register to the VM, clone the virtual machine and then unregister the virtual machine.

  Unfortunately the VM I will be copying is the virtual Center VM and therefore this action must be carried out while it is connected to a host and cloning is a feature of VC.

  Is the best method to use the New-TkeDatastoreDirectory and TkeDatastoreFile-copy to copy these through to the new data store?  I think I read earlier that it does not work or is very slow for large VMDK files?

  Thank you

  Alan

  Jobs published post PS converter. See the work of automation Converter Enterprise with ch

• 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

• Size = size of the VMFS data store VMDK?

  Is it possible to create a single vmdk equal to the size of a vmfs data store he created in or is it a load element used by vCenter/ESXi.

  I am using vSphere 4 and VMFS data warehouses are in format VMFS 3.33.

  You can't if it is the main drive of a virtual machine and the virtual machine configuration files etc receive on the same data store as the virtual machine directly to the output that the bat will need extra space for a brief amount. For a data reader, this should be possible since there should not be any files will use the space.

• Failed to get the disk partition information when you add the new data store

  Hello

  Update my ESX to version 4 Update 1 (4.0.0, 256968). Now, I'm trying to add a new data store to a cluster in vCenter and receive the following error message when I will review the current structure of the disc "error when configuring the host: failed to get the disk partition information. When I click back, then next, there's no error message but in the formatting window, I get the error "Object reference" not set to an instance of an object.

  I see this question has been asked before, but I can't seem to find an appropriate response. Anyone? The interface using CLI instead of vCenter isn't an option (alignment VMFS, workload and so on)

  I use Dell R900 with an EMC Symmetrix VMax SAN

  The size of the LUN I want to add is 741 GB

  Concerning

  Marius Aulie

  If you have a virtual machine for Windows test, you could do the following, to ensure that the logic unit number has a clean partition table:

  -set the LUN as a GROSS physical to virtual machine device

  -Run diskpart, select the drive and run the CLEAN command

  -detach the LUN to the virtual machine

  -try to create the data on the LUN VMFS store

  The size of the block of the data store where the VM test can be a problem with the above. Due to the size of the LUN, the size of the block of the data store must be at least 4 MB. Attach the LUN to a physical test system could be an alternative.

  André

• PowerCLI, vm of moving to the new data store

  Hello

  I have to move vm to a new data store

  What are the good commands powercli

  my version of my CV is 5.0xxxx

  Thanks for your help

  
  

  You can use the Move-VM cmdlet to move a virtual machine to another data store: for example:

  Move-VM - VM "MyVM1" - data store "MyDatastore1".

• Add the new data store

  Hello

  I'm sorry if someone already asked this question before.

  I'm just starting with VMWARE.

  my main at work gave me an old DELL Poweredge 2950 and asked me to install esxi 5 and set up a network and separate area to work with.

  This server got a limitation of 400 GB of HARD drive. I want to use the external USB HDD as additional storage. I got the rank of server 2 TB external HARD drive to use.

  in the start-up phase, is to recognize the HARD drive, but when I want to add as a data store, it does not show anything.

  is there a way I can use the HARD disc as data store extra or not. If I can, can someone please help me with this.

  Thank you

  Krishna

  Unless this HARD drive can be connected to a supported interface card you won't have much luck. You don't mention the interface - if "Server Grade" arrives as meaning 'external SAS port to support RAID card' then it should 'work '.

  From what you describe, I'm imagining a USB - this is not taken care of for a data store.

• Convert vmdk thin provisioned thick, no risk of lost data on vmdk?

  Dear all,

  I need to figure out if it is possible to inflate a vmdk who was originally also thin stocked but now for some reason, we believe that it must be thick, is it possible now?

  -Turn off the virtual machine

  -Go to the virtual machine folder in the data store, make right click the vmdk and inflate

  -power on the new virtual machine

  Is this necessary? If the machine with two virtual hard drives and they both are thin, can inflate us both during the window of time to stop?

  Please share any possible problems into above account in the light of the case.

  Kind regards

  Just a note: the article contains one sentence which IMO must be formatted in fat and Red:

  There should be no snapshots and the conversion is performed on the basic disk

  Check remove you / commit all active snapshots before trying to inflate basic disks!

  André

• Issue of SDRS to vCloud Director after you add the new data store to the Cluster of DTS

  Hi people,

  We use vCloud Director 5.5 in a vSphere full 5.5 environment.

  We have several DTS Cluster in vSphere and connected to vCloud Director.

  Following problem.

  When I add a data store to a Cluster of DTS and connect this to the corresponding storage profile data store, the storage profile is not available to vCloud Director more.

  After removing the new store data in the cluster of DTS, the profile becomes available again.

  Any ideas?

  Concerning

  Jean

  How did you the storage profile associated with the data store?  via c# client or vSphere web client?

  If you did the wrong way (c#) there no storage class label appropriate against it.

  A data cluster store has the storage class who would have all preparations of data contained inside.

  I think that you should check the service class is associated properly in vSphere web client (before adding to the DS Cluster).  Once it displays correctly, and then add the data store to the cluster.

• Move VM vcenter to the new data store

  Hello

  I have a cluster with 2 data warehouses and I must "empy"one for then reassign the disks on the SAN. " However I seem to be in a situation of catch-22 virtual machines, I need to move/migrate is the VM vCenter. I need to have propelled him down to move the data store, but then I have no way related to migration. I presume that this requires a manual move/copy of the vCenter VM file to a data to another store, but not sure of the consequences etc..

  THX

  Gerry

  Since you are using a business license you can Storage vMotion, VM of for the new store of data without any stop.

  Select VM-> click on migrate-> select change Datastore Option

• Can't see the new data store

  I created a new LUN on my NetApp storage system.   In VMware, the iSCSI initiator of software in "Static discovery" shows that the objectives have been discovered.  On the NetApp, one system "> iscsi initiator show" shows that the iSCSI HBA is properly connected to the storage system.  However, when I conduct a new analysis of data warehouses in vSphere client, the new LUN never appears so I can format it with VMFS.  Anyone know what could be the problem?

  Thank you!

  You introduce the LUNS to the host/initiator group?

  André

• VStorage different Motion - copy of the file on a data store vmdk

  Hi all

  Hoping that someone will be able to help with a problem I have right now.

  Configuration:

  NetApp SAN - vmfs data warehouses.

  Data for the migration store is synchronous to a recovery site.

  I planned a day to the next task to migrate a VMDK virtual machines to a non synchronous Datastore to synchronous data store.  When I arrived yesterday morning - the virtual machine has been turned on - but I couldn't access the console and migration was still sitting 89% full.

  Checked the Netapp Filer and found the copy of the snapshot is greater than the instant space on the volume.

  SnapMirror suspend and break.  Delete the copy of Netapp snapshot on the volume.  Once I had done this on the Netapp file server - virtual machine has begun to respond to ping and I was able to access the console.

  I restarted the VM Windows - to make sure everything was fine - as the date / time on the server was out of sync with the date and time - so again, I am happy that my virtual machine is now in place and running.

  Problem. : I migrated virtual disks - one both of the old data store to the new - no problems - until I'm gone make the last record and felt that there is not enough space on the data store - now it would have taken and further investigation found that the virtual disk I wanted to migrate — was already sitting on the new data store.

  Check the settings on the virtual machine shows that the file in question vmdk is still sitting on the old data store - but - I also have a copy of the vmdk - same size etc. - file sitting on the new data store.

  RVtools displays the disk on the new data as a Zombie VMDK store.

  Question: What vmdk file is the one I need to remove?  I think about the new data store - in addition, shown as a zombie in RVTools vmdk - also, shows only not the settings of the virtual machine.

  All find what vmdk file, the system uses permanently.

  Thank you very much

  Open the .vmx file and check the path to your vmdk here.

  If you can, backupo the VMDK at both ends before going any further.

  as the VC (and I hope that the .vmx), as well as RVtools indicate that the destination is a zombie. . I would lean towards this being the one to delete.

  In theory, if you use the browser to store data to try to remove a new and it's in use, you will get an error message, so if it removes OK, you should be good to continue from where you were before.

  Good luck.

• Disk groups are not visible cluster. vSAN datastore exists. 2 guests (on 8) cluster do not see the vSAN data store. Their storage is not recognized.

  http://i.imgur.com/pqAXtFl.PNG

  http://i.imgur.com/BnztaDD.PNG

  Do not know how even tear it down and rebuild it if the disk groups are not visible. The discs are in good health on each host storage adapters.

  Currently the latest version of vCenter 5.5. Hosts running 5.5 build 2068190

  Just built. Happy to demolish and rebuild. Just do not know why it is not visible on the two hosts and the disk groups are only recognized 3 guests when more are contributing. Also strange that I can't get the disk groups to fill in vCenter. I tried two different browsers (chrome and IE).

  I have now works.

  All the identical 5.5 relies on ESXi hosts. All hosts are homogeneous CPU/sum of the prospects for disk controller / installed RAM/storage.

  I have work. I had to manually destroy all traces of the vSAN on each single to help host node:

  (1) put the hosts in maintenance mode and remove the cluster. I was unable to disable vSAN in the cluster, I made on each node host (manually via the CLI below) then disconnected web client vCenter and return to finally refresh the ability to disable on the cluster.

  esxcli vsan cluster get - to check the status of each host.

  esxcli vsan cluster drop - the vSAN cluster host.

  storage of vsan esxcli list - view records in the individual host group

  esxcli vsan storage remove-d naa.id_of_magnetic_disks_here - to remove each of the disks in the disk group (you can ignore this using the following command to remove the SSD only falling each disc in this host group).

  esxcli vsan storage remove s naa.id_of_solid_state_disks_here - this is the SSD and all the magnetic disks in a given disk group.

  After that, I was able to manually add hosts to the cluster, leave maintenance mode and configure the disk groups. Aggregated data of the vSAN data store is correct now, and everything is functional.

  Another question for those of you who still read... How to configure such as the VM storage strategy that migrates towards (or inspired) the vSAN data store will immediately resume the default storage policy, I built for VSANs?

  Thanks for anyone who has followed.

• Thickness of thin formatting on the same data store?

  Hi all

  is it possible with vCenter to convert thick to thin disc on the same data store format?

  and how?

  Thank you very much

  VMware KB: Change the thick or thin provisioning of a virtual disk

  Please check the useful and accurate.

  Marc