appstack in several data stores

Similar Questions

• POS supports several data stores?

  
  I noticed that a limit of 2 TB data store VPD and 8 to VIENNA. Can I create several data stores if I the size of the data more than that?

  Thanks in advance.

  Hello

  I Don t think it is possible to go to more than 8 GB in the Advanced edition. I Don t find anything in the documentation to go further than 8 GB.

  But if you need multiple data stores, you can go up to 10 devices POS by vCenter.

  VMware KB: vSphere Data Protection (WTP) FAQ

  Frank

• Several data stores?

  Hello.

  I create a configuration on my VM project and future document.

  I run x 4 company vSphere5 hosts running on a Dell R710 all connected to a Dell EqualLogic PS6100XS for their shared iSCSI storage.

  Looking at best practices and not knowing the correct limits of data warehouses... What is the best Setup here. It is better to create a large (7 by TB) Volume and transfer this to vSphere as storage... Or...

  Create several data warehouses (each 1 TB in size) for use with Storage vMotion?

  Thank you

  J.

  Theres more to it than just the workload, IMO.

  You must consider that usually get you slightly better performance (5-10%) with several data warehouses/LUN, simply because there is more available queues.

  Also, several data stores means that you have more options to make backups, prioritization, etc.  Finally, you also have more possibilities for reproduction in the future.

  I would * not * create a unique 7TB data store.  I'd be more likely to create a smaller data warehouses from 7-10 and broadcast my virtual machines around on them.

• Displacement of the VM attached to several data stores

  ESX 5.1.  I'm moving from one SAN to another.  I have a Windows VM file server that is attached to the "OS" data store which is 100 GB (for the OS, program installation, etc.) and the data store 'Data' that is 500 GB (where the file real stock data is stored).  On the new San, I created new warehouses of data, "New_OS" and "See you."

  What is the best way to move my data to the new data warehouses?  I know that I can use storage VMotion to move the virtual computer, but who will attempt to move the 'BONES' and 'Data' to 'New_OS' correct?  (Which of course will not work, since there is not enough space.)  I think that I have to remove 'Data' of the existing virtual computer, move it to 'See you' via a browser data store, move the computer virtual using VMotion, then add "you see?"  This sounds more complicated than it should be.  Am I missing something here?

  Thank you.

  Am I missing something here?

  Yes, it lacks the 'Advanced' option in Storage vMotion which will allow that move you each hard to a data store different... to do this, just follow the screens of Storage vMotion and select the data store, click on advanced and for each virtual hard disk and virtual machine configuration file, select the data store you want.

  Take a look at the documentation: http://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vsphere.vcenterhost.doc/GUID-A15EE2F6-AAF5-40DC-98B7-0DF72E166888.html

  Store the configuration of virtual machines and disks files in different places.

  one Click Advanced. b For the virtual machine for each virtual disk configuration file, select Browse and select a data store or cluster storage DRS. c (Optional) If you selected a cluster DRS for storage and do not use Storage DRS to this virtual machine, select Disable DRS storage for this virtual machine and select a store of data within the storage DRS cluster. d Click Next.

• Storage VMotion for several data stores

  I'm looking for some advice and assistance with the help of the vSphere PowerCLI to SVMotions.

  I found that I can use virtual vmname Get-machine | Move-VM - datastore (Get-Datastore datastorename) that has worked very well and I was ready to roll. However, it occurred to me that I can only refer to a data store in the cmdlet and some of our virtual machines have their drives located on different data warehouses.

  So I set up a test VM with two disks of different data warehouses and began a SVMotion. The result was that it has migrated all disks in their separate data warehouses in a single folder on the target.

  What I need to be able to do is to migrate a disk and leave the other in its original location, or migrate two disks of different locations in two different places again. As you can do if you switch the machine virtual and migrate through the graphical interface, moving storage with advanced options (and probably what you can do via the graphical interface with the virtual machine in vSphere).

  I've got ESX 3.5 Update 5 with vCenter 2.5 update 6 If no GUI in VirtualCenter and the free snap option not taken in charge is not an option.

  Is there a way to do it with the PowerCLI or am I limited to migration the data store's unique virtual machine?

  Thank you very much.

  This can be achieved using the. RelocateVM_Task() method of the VirtualMachine SDK object

  See the code below:

  $configDatastoreName = "DataStore_01"
  $HardDisk1DatastoreName = "DataStore_02"
  $HardDisk2DatastoreName = "Datastore_03"
  
  $vm = Get-VM VM001
  
  $spec = New-Object VMware.Vim.VirtualMachineRelocateSpec
  #Get MoRef for Destination datastore for Config files
  $spec.Datastore = (Get-Datastore $configDatastoreName | Get-View).MoRef
  
  #for each disk specify where the vmdk files should be placed.
  #If a vmdk should NOT be moved, enter its CURRENT datastore
  #If you forget to specify a disks location, it will be moved to the datastore
  #specified in $spec.Datastore
  
  #HardDisk 1
  $objDisk = New-Object VMware.Vim.VirtualMachineRelocateSpecDiskLocator
  $objDisk.DiskID = $vm.HardDisks[0].Id.Split('/')[1]
  $objDisk.DataStore = (Get-Datastore $HardDisk1DatastoreName | Get-View).MoRef
  $spec.Disk += $objDisk
  
  #HardDisk 2
  $objDisk = New-Object VMware.Vim.VirtualMachineRelocateSpecDiskLocator
  $objDisk.DiskID = $vm.HardDisks[1].Id.Split('/')[1]
  $objDisk.DataStore = (Get-Datastore $HardDisk2DatastoreName | Get-View).MoRef
  $spec.Disk += $objDisk
  
  #When all harddisks are specified call the RelocateVM_task()
  $vm.ExtensionData.RelocateVM_Task($spec, "defaultPriority")
  

  -

• Using several data stores, cannot migrate the vmx file in a data store

  I am host migration between 3.5 and 4.0, and part of the migration requires me to vmotion data to a single shared LUN data warehouses.  From there on, I import the virtual machine in 4.0 and using the script to migrate the two VM disks at different stores of data below.  The problem I have is that the configuration (vmx) file not migrated and is left on the shared storage LUNS.  Anyone knows how to go beyond this?

  The Script:

  $VMDisk = 'disk 1 '.

  $VMName = 'TestVM '.

  $TargetDS = get-Datastore - VMHost (Get-VMHost-$S.id Id) | Where-Object {$_.} Name - like "PMV"} | "" FreeSpaceMB tri-objet-descending | SELECT name - first of all 1

  $vm = get-View - ViewType VirtualMachine-filter @{"Name" = $VMName}

  foreach ($dev in $vm. Config.Hardware.Device) {if ($dev. DeviceInfo.Label - eq $vmDisk) {$diskId = $dev. Key}}

  $spec = new-Object VMware.Vim.VirtualMachineRelocateSpec

  $diskspec = new-Object VMware.Vim.VirtualMachineRelocateSpecDiskLocator

  $diskspec. Data store = (Get-Datastore-name $TargetDS.Name |) Get - View). MoRef

  $diskspec.diskId = $diskId

  $spec. Disk = @($diskspec)

  $task = get-View ($vm. RelocateVM_Task ($spec, "lowpriority"))

  OK, I think I understand your problem now.

  I fear that in the current construction of PowerCLI, the Move-VM cmdlet does not destinations of individual data for each virtual hard disk store.

  With the RelocateVM_Task method, it is possible.

  The following script moves a guest at 3 different data warehouses:

  -the. VMX file for DS2

  -hard disk 1 for DS3

  -hard drive 2 TB DS4

  $vmName = "MyGuest"
  $vmxDS = "DS2"
  $osDS = "DS3"
  $dataDS = "DS4"
  
  $vm = Get-VM -Name $vmName
  
  $vm.Extensiondata.Config.Hardware.Device | %{
       if ($_.DeviceInfo.Label -eq "Hard disk 1"){
            $osDiskId = $_.Key
       }
       elseif($_.DeviceInfo.Label -eq "Hard disk 2"){
            $dataDiskId = $_.Key
       }
  }
  
  $spec = New-Object VMware.Vim.VirtualMachineRelocateSpec
  
  $osRelocate = New-Object VMware.Vim.VirtualMachineRelocateSpecDiskLocator
  $osRelocate.Datastore = (Get-Datastore -Name $osDS).Extensiondata.MoRef
  $osRelocate.diskId = $osDiskId
  
  $dataRelocate = New-Object VMware.Vim.VirtualMachineRelocateSpecDiskLocator
  $dataRelocate.Datastore = (Get-Datastore -Name $dataDS).Extensiondata.MoRef
  $dataRelocate.diskId = $dataDiskId
  
  $spec.Disk = @($osRelocate,$dataRelocate)
  $spec.Datastore = (Get-Datastore -Name $vmxDS).Extensiondata.MoRef
  $spec.Host = $vm.Extensiondata.Summary.Runtime.Host
  
  $task = Get-View ($vm.Extensiondata.RelocateVM_Task($spec, "lowpriority"))
  while("running","queued" -contains $task.Info.State){
       $task.UpdateViewData("Info")
       sleep 5
  }
  

  BTW, you can use the cmdlet Set - hard disk to a virtual disk that is specific to a data store.

  But as I understood what is not possible in your environment.

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Migration of storage when the virtual machine has several data stores

  How can I (or can I) use Storage vMotion on ESX4.0 U1 to migrate part of a virtual computer to a new data store?  I have a virtual machine with 5 data stores attached and move 1 data warehouses to a LUN of larger size.  What is the best method?

  On the "Select the data store" window, click on the button "Advanced". You can specify the location of each VMDK and configuration files.

• Storage vMotion a VM except disk that is in another data store

  Hello

  I'm looking to convert a large number of virtual machines clones related to thick.  I decided the best way to do this is probably a simple a storage vMotion, but all the virtual machines have a secondary drive that is in another data store.  I have to make sure that disk #2 stays at its current location, while the machine virtual (Config and disk #1 files) are transferred to a new data store data store.

  I figured out how to move a virtual machine complete or a single disc but not a virtual machine under a disc.  I am able to make it through the advanced options of puissancela vSphere client so I guess it is techinically possible.

  Pointers or other ideas would be greatly appreciated.

  Kind regards

  Ty-

  You will need to use the API method, see for example Re: using several data stores, cannot migrate the vmx file in a data store

• get the data store with details of mapped cluster

  Hi with the script below, I am able to do data store maps on which the cluster and its host details... but I'm having multiple LUNS how to write for everyone to get to each store data below the output...

  Get-data store 'testdatastore ' | Get-VMHost | Name,@{N="cluster select '; E={$_| Get-Cluster}}, version

  Output:

  Version of cluster name

  10.0.0.0 testcluster 5.1.0

  Desired output:

  I need the name of output data store because I check for several data stores... can someone help me to get .csv exit foreach datastore as below

  Data name cluster version store

  testdatastore 10.0.0.0 testcluster 5.1.0

  testdatastore 1

  10.0.0.1 testcluster2 5.1.0

  What type of data store?

  I'm asking because there is no mentioned properties (. ExtensionData.Info.Vmfs.Extent) for data warehouses is of type NFS:

  PowerCLI C:\Windows\system32 > ((get-datastore_iscsi*).ExtensionData.Info.Vmfs.Extent). Diskname

  NAA.60a9800042594835695d453439742f53

  PowerCLI C:\Windows\system32 > ((get-datastore_NFS).ExtensionData.Info.Vmfs.Extent). Diskname

  So, you'll need probably something like this:

  Get-Datastore. % { $ds=$_; Get-VMHost - Datastore $ds | Select @{N = 'Data store name'; E = {$ds. Name}},@{N="NAA '; E = {if($ds.) Type - such as 'NFS') {'NFS'} elseif($ds.) Type - as "VMFS") {[String]: join (", ($ds.ExtensionData.Info.Vmfs.Extent|% {$_.}))} DISKNAME}))}}}, name, @{N = 'cluster'; E={$_| {Get-Cluster}}, version}

• 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é

• Help adding extensions to a VMFS data store

  Hello people,

  I am working on some automation for creation of data store and must be able to add extensions to a data store.  The initial creation of data store works well enough at this point, but I'm a little puzzled about how to add additional extensions.  In my example, I am using the navi cli to make the LUN UID off the coast of the Bay of EMC, then format it correctly for the canonical name the host for the creation of data store.

  I read a little about the extendvmfsdatastore here , but I am not able to separate the part "add the measure" of "questioning the existing data store and remove references to pass."  If someone has an extract whose orders must be performed and the text to pass to the .extendvmfsdatastore method, I'd be very happy.  I know measure in several data stores fall into disgrace with VMware, but I can't migrate 10TB data storage immediately.

  Thanks in advance!

  Brent

  omitted variable section

  **********************

  to connect-viserver $VC - https protocol-$VC_USER the username-password $VC_PASSWORD

  Import-CSV C:\PowerShell\VNX_buildout\TEST-DSCreate\Test_DSCreate.csv | {Foreach}
  $LUN = $_.alu
  Naviseccli-address = $UID $VNX_ADDRESS-User $password-VNX_USER_NAME $VNX_PASSWORD-scope 0 lun-list-l $LUN - uid. out-string
  $UID = $UID. Replace (":", "")
  $POS = $UID. IndexOf("6006")
  $UID = $UID. Remove (0, $pos)
  $CN = $UID. Substring (0.32)
  $CN = "naa. $CN ".
  write-host "CN = $CN - Array MONDAY = $LUN"
  New data store - VMHost $ESX_HOST-name $_ .datastr-path $CN - Vmfs-confirm: $false
  DataSet datastore store-$_.datastr - storageiocontrolenabled $true

  # Add the extensions of vmhbax:C:T:L or naa.xxx or?
  }

  I have reviewed the procedure I used, seems that there is an easier way to do it.

  You can try this version of the script?

  $esxName = "MyEsx"
  $tgtDSName = "MyDS"
  $freeLUN = "naa.6005076801801a34d000000000000078"
  
  $esx = Get-VMHost -Name $esxName
  $dsToBeExtended = Get-Datastore -Name $tgtDSName -VMhost $esx $dsSystem = Get-View $esx.ExtensionData.ConfigManager.DatastoreSystem
  $available = $dsSystem.QueryAvailableDisksForVmfs($dsToBeExtended.ExtensionData.MoRef)
  $lun = $available | where {$_.CanonicalName -eq $freeLUN}
  if($lun){
      $options = $dsSystem.QueryVmfsDatastoreExtendOptions($dsToBeExtended.ExtensionData.MoRef,$lun.DevicePath,$true)
      $dsSystem.extendVmfsDatastore($dsToBeExtended.ExtensionData.MoRef, $options[0].Spec)
  }
  

  If the LUN that you pass the $freeLUN variable is not free, the script will not call the extendVmfsDatastore method

• How to migrate to VMDK all store data in another data store

  How would be migration of VMDK script all store data in another data store.

  No, then you must use the Move-VM cmdlet. But this cmdlet moves all files to the destination data store.

  The alternative is to use the method RelocateVM_Task , which allows more flexibility to define what that goes where.

  It is a good example of your thread has called using several data stores, can not migrate the vmx in a data store file

• Clone VM and problem with selection of data store

  Hello

  When I tried to clone a virtual machine that has distributed records in several data stores, I never had the chance to select the store multiple data for the clone, he asks only for the unique data store and discharge all vmkdks to this one, is it possible that I can choose several data stores?  for example: I want to drive D: to E: drive to datastoreC c, datastoreB: diving in datasoreA

  Thank you

  Beatrice

  Hi Alain,

  When you run the clone operation, when you are prompted to select the destination data store, don't you have an Advanced button? If you click on it, you should have access to a menu where you can choose a different destination for each virtual disk.

  Concerning

  Franck

• Clone VM runs on several data warehouses

  Hi all

  I have a virtual machine that spans 2 data warehouses and I don't know how it happened like this:

  I cloned a VM from a template.  The model is in my store of data VOL3.

  In the summary for my VM tab, it shows that it is connected to and VOL2 VOL3 data warehouses.  When I sail both VOL2 VOL3 data warehouses, I see all the files associated with the virtual machine on VOL3, so I do not know why the VIC is reported as connected to VOL3?  It has only 1 drive, and who connects to a single vmdk on VOL2

  Some notes when I cloned the virtual machine template, I forgot that I had the CD connected to a .iso on the VOL3, maybe that's the question?  I unplugged the virtualCD, but no change?  It doesn't seem to be hurt anything at the moment, but I guess it could complicate things on the road.

  Thank you

  Chad

  I think that the reason that you see your vm split into several data stores is the .iso file, presented during the configuration of the virtual machine. Instead of unplugging the drive (which has the .iso file) change the cd configuration to use a client device.

  I hope this helps.

  Best wishes / Saludos

  Por don't favor no olvides calificar las responses that you were should o ayuda valiosos.

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

  ________________________________________

  Nicolas Solop

  VCP 410 - VCP 310 - VAC - VTSP

  My Linkedin profile

  Join the Virtualizacion en Español group in LinkedIn

  ! http://feeds.feedburner.com/WetcomGroup.1.gif!

• 'VM to data store' map shows inaccurate data

  We have a set of cluster HA with several data stores, all shared by the hosts in the cluster.  On the level "VM to the data store", I noticed that some hosts had lines connecting to two different data stores.  I assumed it was because the hard drive was on a data store, while the CD image has been stored on another.  In order to fix this, I went through and set all CD-ROM comments to "client".  While it worked for some customers, others are still on display as it is connected to two different data stores.

  Someone has any idea how to solve this problem?  We prefer that all the files of configuration of each guest, etc stored on the same data store.

  Take a look at one of your virtual machines with this double connection data store and see what files are on data warehouses. Also look at the data store that VC said that the virtual machine is located. I have seem a while ago when you create a new virtual machine and choose to add a virtual disk to another data store, virtual machine configuration files and files of delta snapshot in a data store, and the vmdk on another (if this is the case!).

  If your re - direct your shots, you will probably see this other data store must be referenced in the .vmx file in a configuration setting called WorkingDir =

  Thank you

  Neil