Data store renamed after failover

Similar Questions

• Data store missing after the reconstruction of the raid array

  One of the players in my raid array has failed a few days ago.

  I had a spare drive in the table so the controller immediately began the process of rebuilding and all servers were running throughout.

  When the reconstruction has been completed (I checked this via the user interface of raid array and the newspaper), I had to stop the server to remove disc defective (not replaceable chassis hot) and when I restarted the server, the data on the raid array store isn't there anymore.  I also checked through the raid controller interface that I removed the (defective) drive and that the table was always in a ready state when he came.

  In vsphere client, when I click on the storage... Add link, the server sees the material but if I click then it tells me that it will be re - format the volume.  See attachment.  I have most certainly does not take the next step and reformat.  Simply, I took the screenshot and regularized.

  I found these instructions, but they are for an older version of ESXi and am unsure if they are correct for ESXi 6.0.0 338124

  VMware KB: Lack of data store after the reconstruction of the RAID disk/LUN

  Here are the steps I should follow?

  If these aren't the right instructions can you tell me the version which is for ESXi 6.0.0 338124 that I couldn't find anything either.

  Thank you

  Hi ThompsG,

  Yes, there are two data stores for the virtual machine located on the RAID array.  The virtual machine itself was stored in a different data store that was not in the raid array.

  I spent about 48 hours last week, including this morning, trying to coax ESXi recognizing volumes, with no luck.  Finally, I gave up and I removed the virtual computer hard drives that were on the corrupt data store.  Then the virtual machine came without problem.

  Finally, since I have everything on these 2 volumes backed up to a cloud provider, I have recreated the two data stores in the raid array and began the restoration process. It is currently running and has about 16 days left to go.

• Local data store renaming problem with the cmdlet set-datastore

  Hiya,

  I just started using powercli to configure my ESX Servers 4.1i.

  Most of my script version works fine - but I can't rename the local data store.

  I do a get-data store based on the name that works very well, I then pipe series-store data with a new name-, but it just seems to ignore the order and leave it with the old name.

  No error message is produced.

  I pasted in the results of the "get-data store" (just to show that it exists) and the results of the 'get-datastore piped to set-data store", below.

  I'm sure I'm missing something really obvious - but I do not know what?

  [vSphere PowerCLI] D:\powershell > get-datastore-name 'test1' | fl

  
  DatacenterId: Datacenter-ha-datacenter
  Datacenter: ha-datacenter
  ParentFolderId: Folder-ha-folder-datastore
  ParentFolder: datastore
  DatastoreBrowserPath: vmstores:\ohst213vmh.blah.co.uk@443\ha-datacenter\test1
  FreeSpaceMB: 64207
  CapacityMB: 64768
  Accessible: true
  Type: VMFS
  ExtensionData: VMware.Vim.Datastore
  ID:-Datastore-4d4c2877-c48e1465-b0be - 00237d 358458
  Name: test1
  UID: /[email protected]:443 / Datastore = Datastore-4d4c2877-c48e1465-b0be-002
  37d 358458.

  [vSphere PowerCLI] D:\powershell > get-datastore-name "test1" |-store game data-name 'test2' | fl

  
  DatacenterId: Datacenter-ha-datacenter
  Datacenter: ha-datacenter
  ParentFolderId: Folder-ha-folder-datastore
  ParentFolder: datastore
  DatastoreBrowserPath: vmstores:\ohst213vmh.blah.co.uk@443\ha-datacenter\test1
  FreeSpaceMB: 64207
  CapacityMB: 64768
  Accessible: true
  Type: VMFS
  ExtensionData: VMware.Vim.Datastore
  ID:-Datastore-4d4c2877-c48e1465-b0be - 00237d 358458
  Name: test1
  UID: /[email protected]:443 / Datastore = Datastore-4d4c2877-c48e1465-b0be-002
  37d 358458.

  See you soon

  Jordan

  When you add a server ESX to vCenter, agent VirtualCenter (vpxa) service is installed on the ESX Server.

  All actions you take in the vSphere ESX server customer or a PowerCLI script when you are connected to the vCenter, passed through this vpxa service. This service manages the resources on the ESX Server.

  To avoid problems when you change some resources directly from the COS of ESX, vpxa services locks these resources.

  That's why you can not change the datastorename when you are connected directly to an ESX Server that has been added to a vCenter.

  BTW, if you connect a vSphere client directly to the ESX Server, you will see the same phenomena as what you see in your script PowerCLI.

  If you need to change the datastorename locally on the ESX for some reason, you can try to remove the ESX Server with Remove-VMHost to vCenter, connect to the server with Connect-VIServer ESX, make your changes and add it to the vCenter with Add-VMHost.

• Data store rename using replace?

  I am trying to rename more than one store of data at once.

  Scenario:

  Have a number of local ESX hosts with several warehouses of data, in this case two. Now I would like to rename from the default datastoreX to & lt; Server name & gt; vmfsX. So that the number remains the same but the data store is replaced.

  for example, datastore1 becomes esx1vmfs1, and datastore2 becomes esx1vmfs2.

  Yes, I could simply run two commands because all the servers that I'm building will have only two data stores, but this is not the point and I'm trying to improve my skills of PowerShell. Since I did a change of name of the files in a file system quite easily, I thought I could try the same approach method replace.

  So the code I started with:

  $vmhost = Get-VMHost -Name MyESX.company.com
  $vmhostshortname = $vmhostname.Split(".")[0]
  $dsname = $vmhostshortname + "vmfs" 
  
  Get-DataStore -VMHost $vmhost | Where-Object { $_.Name -like "datastore*" } | Set-Datastore -Name { $_.Name -replace "datastore", $dsname }
  

  Returns:

  Set-Datastore : 11/02/2010 3:16:38 PM    Set-Datastore    52d79783-f475-a27f-1ec7-2f84b214241e     $_.Name -replace "datastore", $dsname ' is invalid
   or exceeds the maximum number of characters permitted.
  At line:1 char:92
  + Get-DataStore -VMHost $vmhost | Where-Object { $_.Name -like "datastore*" } | Set-Datastore <<<<  -Name { $_.Name -replace "datastore", $dsname }
      + CategoryInfo          : NotSpecified: (:) [Set-Datastore], ViError
      + FullyQualifiedErrorId : Client20_MoServiceImpl_Invoke_ViError,VMware.VimAutomation.Commands.SetDatastore
  

  It's basically trying to define the data store to all characters between the brackets.

  Then I tried this instead,

  Get-DataStore -VMHost $vmhost | Where-Object { $_.Name -like "datastore*" } | % { $newname = $_.name -replace "datastore", $dsname; Write-Host $newname; Set-Datastore -Name $newname }
  

  Returns:

  Set-Datastore : Value cannot be found for the mandatory parameter Datastore
  At line:1 char:169
  + Get-DataStore -VMHost $vmhost | Where-Object { $_.Name -like "datastore*" } | % { $newname = $_.name -replace "datastore", "$dsname"; Write-Host $newname; Set-Datastore <<<<  -Name $newname }
      + CategoryInfo          : NotSpecified: (:) [Set-Datastore], ParameterBindingException
      + FullyQualifiedErrorId : RuntimeException,VMware.VimAutomation.Commands.SetDatastore
  

  So apparently not to evaluate $newname or at least it stays together.

  I checked that $_. Name of the data store is a string object.

  If I replace it outside the line, as below, it works as expected.

  $dslist = Get-Datastore
  $newname = $dslist[0].Name -replace "datastore", $dsname
  

  I'm sure that I'm either missing something simple, or there is another way to do it, but I'm jiggered if I can get by.

  Try this way, that should work

  $vmhost = Get-VMHost -Name 
  $vmhostshortname = $vmhost.name.Split(".")[0]
  $dsname = $vmhostshortname + "vmfs" 
  
  Get-DataStore -VMHost $vmhost | Where-Object { $_.Name -like "datastore*" } | %{
       $_ | Set-Datastore -Name ($_.Name -replace "datastore",$dsname)
  }
  

  The problem with your last attempt, is that it has no DatastoreImpl object in the hose that can server as a value for the parameter - data store.

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Data store lost after SAN restart / modify LVM. EnableResignature

  Hi all

  We just had a blackout (planned) and once we have start the SAN and the ESX, one of the LUN seems to have disappeared. I tried to anyone she / it presents another ESX, it seemed that the server did not recognize that it was formatted in vmfs. He would see only as a new partition and asked to formatted it again. After several hours of research and testing, I was able to get my store of data by changing the value of LVM. EnableResignature to 1. Rescan HBAS and he was there like an old snag-00000002-DataStore name... From there a creation of computer virtual and added new disc, from the existing drive and pointed at my old vmdk files. I have no idea of the will what exactly is and if I can set it to 0 (or I'll lose all my vm once again) and why a data store had this problem?

  Any idea?

  That's right, don't let not the will option is enabled.
  This event does not occur very often.

  http://blog.laspina.ca/

• Disc SSD data store unavailable after reboot

  I have a Kingston SSD drive installed in a Dell T620 SAS (Controller H710) basket bottom. It is configured RAID 0 (disk). Therefore, it is OK, and I created a data store using the full disc. It works very well in the virtual machine that it is assigned to you. However, when I reboot and look in the configuration of the storage is not there. I can add and it remembers. The bad news is that the virtual machine, it is affected to cannot start as long as I add back in manually.

  A look at the list of devices, it shows that mounted. The difference between it and other readers is it says unknown partition format, it also says non - ssd.

  I'm just against a unit of failure in charge here? I do not see the SSD drives listed in the list of supported devices, but I hardly find this page.

  < small mug shot >

  Why he let me a second hard drive configured to use the rest of a store of data and then not start because there is not enough room for the Swap and not remove the second disk hard when I tell him?

  < / small rant >

  Hi Lou

  Why do not connect you to a port SATA (my last one)?

  This seems to fix. Also, he appeared as an SSD and remembered all the stuff.

  I guess it has to do with the SAS/RAID connection. Will try another drive to be sure.

  Lou

• Increase in size of data store ESXi after increasing the size of the LUN

  Hi all

  Scenario is as follows.

  Remote site with Dell r710 ESXi 4.1 servers 2, 1 Dell MD3200i SAN with 12 600 GB drives.

  Initially when I implemented the San, I created 2 LUNS with 1 TB in each LUN.

  Now, we ran into a situation where we have 1 server which is now need more than 1 TB of sapce on it.

  I've reconfigured the table and now have a unit number logic that I spent in 2 TB to 1 TB and I now need to increase the store of data on the ESX Server.

  If I increase the size he reformatted the LUN whole or just the free space that I create?

  I don't want to remove any exisitng s VM on the SAN.

  maximum size of a vmfs is 2 TB-512 b only. extend wouldn't format the LUNS. Look at this blog: http://www.yellow-bricks.com/2009/03/26/resizing-your-vmfs-the-right-way-exploring-the-next-version-of-esxvcenter/

• VM shows always refers to the old data store after storage vMotion?

  All the:

  We have recently set up a SAN Equalogic and plugged into our environment vSphere. We are moving our VM to SAN storage, off the coast of local disk. After treatment of a virtual machine, we always show the reference to the old data store on the summary page when you look at this VM. However, when we look at the settings, HARD drive shows that the vmdk file is infact on the SAN?

  Is there a reason why it would still showing upward for both?

  Thank you

  (1) check if the virtual machine has snapshots and maybe its pointing to the old datatore

  (2) check if any ISO is mounted on the virtual machine to the old data store

  After the screenshot of the VM folder by browsing the old data store

• Dell virtual disk are larger. You want to increase the size of the data store.

  Hello

  I started the implementation of a server ESXi 5.5 Update 1 this week. I didn't know Dell shipped the server with two virtual disks instead of one. I realized this _apres_ that I had already created the data store and setup a few virtual machines to the breast. I called Dell who sent specific instructions to increase the removal of the second (empty) virtual disk and add it to the main. In the end, I increased the single VD from 2 TB to 3 TB and I want to give the remaining space in my store of data.

  I tried to follow the article here that explains how to do this via the CLI.

  Well, he did not altogether. Fortunately, I was able to recover my datastore my setting start and end sectors to their original numbers. But I'm still left with this almost 1 TB of space that I can not attribute to the data store. After that I reread storage adapters in the client, the new Dell disk size resulted under measurement devices. Click on "increase...". ", generates the following error which led me on the way to the CLI method:

  Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" to object "ha-datastoresystem" on ESXi '[myservername]' failed.

  I will paste my notes that I took everything by jobs. Things have exploded the rails when I put 4 partition size to the largest size. Any help, please?

  ---

  I use that as a guide:

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2002461

  
  

  1 use start hardware device management tools to increase the capacity of additional disk to the device. For more information, commit your hardware provider.

  This has been done. The new size of the virtual disk is 2791,88 GB (TB 2,79188)

  
  

  2. open a console to the ESXi host.

  Pretty simple.

  
  

  3. get the DeviceID for the data store to change.

  ~ # vmkfstools Pei "/ vmfs/volumes/datastore1 / '.

  System file VMFS-5, 60 extending on 1 partition.

  File system label (if applicable): datastore1

  Mode: public

  Capacity 1971926859776 (blocks of files 1880576 * 1048576), 1042688245760 (994385 blocks) prevail, max size of the 69201586814976 file

  UUID: 534e5121 - 4450-19dc-f8bc1238e18a 260d

  Partitions split (on 'lvm'):

  NAA.6c81f660ef0d23001ad809071096d28a:4

  
  

  A couple of things to note:

  a. the device for Datastore1 ID is: naa.6c81f660ef0d23001ad809071096d28a

  b. the number of Partition on the disk is: 4 ' [...]: 4 "»

  c. the prefix, "naa," means "Network address authority" the number immediately after is a single logical unit number.

  4. Enter the amount of disk space available on the data store.

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 1. 8T 865.4 G 971,1 G 47% / vmfs/volumes/datastore1

  
  

  5 team of the device identifier, to identify the existing partitions on the device by using the partedUtil command.

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  ~ #

  
  

  According to the table in article KB

  4 13711360 3865468766 251 0 - primary #4, type 251 = 0xFB = VMFS, 13711360-3865468766 areas

  | |        |          |   |

  | |        |          |   \---attribut

  | |        |          \---type

  | |        \---se finishing sector

  | \---a starting from sector

  partition \---Numero

  
  

  Also note how the number of section start the old end sector number is + 1.

  
  

  6 identify the partitions that need to be resized and the size of the space to use.

  We want to resize partition 4. I don't really understand the last part of this sentence, however. Read more.

  
  

  7 the number of sector end you want for the target data store VMFS partitions. To use all out at the end of the disc space, remove 1 of the size of the disk in the areas as described in step 5 in order to get the last usable area.

  ESXi 5.x has a command to do this:

  ~ # partedUtil getUsableSectors "/ vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a".

  1 5854986239

  This means that we want 4 Partition of "naa.6c81f660ef0d23001ad809071096d28a" to be:

  13711360 - 5854986239 (i.e. the end of the disc)

  
  

  8 resize the partition containing the target VMFS Datastore using the command partedUtil, specifying the original existing partition and the desired end sector:

  Using the above information, our command is:

  resize # partedUtil ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 5854986239

  
  

  9 step 8, the partedUtil command can report the warning:

  He did not. Displacement.

  
  

  10. the tables of partitions have been adjusted, but the VMFS data within the partition store is always the same size. Now there is an empty space in the partition where the VMFS data store can be grown.

  
  

  11 launch this v vmkfstools command to perform a refresh for VMFS volumes.

  Fact.

  
  

  12 reach the VMFS Datastore in the new space using the command - growfs vmkfstools, specifying the partition containing the VMFS Datastore target twice.

  vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 '.

  
  

  It did not work. I got an error:

  / vmfs/volumes # vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' /vmfs/devices/disks/naa.6c81f660ef0d «»

  23001ad809071096d28a:4 ".

  Cannot get device head way /dev/disks/naa.6c81f660ef0d23001ad809071096d28a:4 information

  
  

  Also the partition was very different to what I asked:

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 1560018942 251 0

  
  

  I fixed it by running these commands:

  ~ # partedUtil resize ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 3865468766

  ~ # vmkfstools v

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  Update:

  Since it was such a new machine, not in active production, we have safeguarded the VMs management off the ESXi host. Then flattened the virtual disk, recreated, and then created a store of data with the right size. (TPG this time, naturally.) We put the management of virtual machines on the data store. For Windows virtual machines, we have restored the using AppAssure. Everything is ok now.

  Need to add a new item to the list of punch: check what Dell has done the configuration of the virtual disks. :-)

• Kickstart: Local data store destroyed do not reinstall it

  I noticed that when I reinstall ESXi 5 on a server already built, the previous local data store is not destroyed.

  I said to make a 'install' and 'overwritevmfs '.

  install - firstdisk = mptsas, local - overwritevmfs

  in the upper part of the kickstart but the store of previous local data remains.

  I tried to use clearpart

  clearpart - alldrives - overwritevmfs

  Yet the local data store of the previous generation, as well.

  Part of my process of kickstart is to rename the store local data (datastore1) to a meaningful name that includes the hostname so if I reinstall, the data store rename fails (since there is no datastore1 on the 2nd install).  Also, I need to know the name of the data store, as I'm checking out the files ' / ' when installing (via oem.tgz) and move before the first reboot in the section post % (or they will be gone). The only persistent location is the local data store. This also effects kickstart for resettlement syslog that goes to the local data store as well.

  Suggestions on how do I delete a data store local existing during the installation (unless you delete the RAID and re-create)?

  -JC

  I wrote the following script to rename the local old data store ESXi 5.0 using Primo-kickstart script:

  _____________________________________________________________________

  AcceptEULA

  #clearpart - firstdisk = cciss, local - all - overwritevmfs # removes all partitions on local drive (for G1 blade servers) but will not erase the label VMFS

  clearpart - firstdisk = hpsa, local - all - overwritevmfs # removes all partitions on local drive (for G6 blade servers) but will not erase the label VMFS

  install - firstdisk = hpsa, local - overwritevmfs

  rootpw SECRET

  reset

  % include/tmp/networkconfig

  % pre - interpreter = busybox

  # extract information network startup

  VMK_INT = "vmk0".

  VMK_LINE = $(localcli réseau ip interface ipv4 get | grep "${VMK_INT}")

  IPADDR = $(echo "${VMK_LINE}" | awk '{print $2}")

  NETMASK = $(echo "${VMK_LINE}" | awk '{print $3}")

  GATEWAY = $(esxcfg-route | awk '{print $5}')

  DNS = "10.130.0.21,10.130.0.22."

  Hostname = $(nslookup "${IPADDR}" | grep adresse | awk '{print $4}')

  echo ' network - bootproto = static - addvmportgroup = false - device = vmnic0 - ip = ${IPADDR} - netmask = ${MASK} - gateway = ${GATEWAY} - nameserver = ${DNS} - hostname = ${HOSTNAME} "> / MC

  p/networkconfig

  firstboot % - interpreter = busybox

  # Extract the host name of the host number

  # Example: HC - moon01.tapkit .net = ' 01, sc - moon02.tapkit .net = ' 02, sc - moonNN.tapkit .net = 'NN ',.

  HL ='hostname-s | WC-c"

  hostNum = $(nom d'hôte-s | cut-c'expr $hl-2'-'expr $hl-1')

  # Rename the local data store to something more meaningful

  # Find the current local data store NAME (exclude all the SAN HSV200 data store)

  DatastoreName = "$(liste étendue d'esxcli stockage vmfs |) grep ' esxcli - trainer = csv - format-param = fields = "Device, model" list of basic storage device | grep - v "HSV200". grep - v "Device". cut - d-f1' | AWK '{print $1}')'

  NewDataStoreName = "datastore$ hostNum.

  # Rename the data store

  Vim - cmd hostsvc/datastore/rename $DatastoreName $NewDataStoreName

  # copy % first startup script newspapers to persistent data store

  CP /var/log/hostd.log "/ vmfs/volumes/$NewDataStoreName/firstboot-hostd.log".

  CP /var/log/esxi_install.log "/ vmfs/volumes/$NewDataStoreName/firstboot-esxi_install.log".

  # Needed for configuration changes that cannot be performed in esxcli (thank you VMware)

  reset

  _____________________________________________________________________

  I hope this helps...

  A big thank you to William Lam for his great contribution: http://www.virtuallyghetto.com/2011/07/automating-esxi-5x-kickstart-tips.html

  Gilles Marcil

• Renamed after failback data store

  I use a SAN 3PAR and after failing with MRS 4.1 for the protected site of origin the data store used by SRM, which was named "ESX_LUN_4" before the restoration, is now named "snap-171a27e9-ESX_LUN_4" on the ESX servers.  However, the name of logic on the SAN unit number still seems to be the original name "ESX_LUN_4".

  Can someone tell me how to restore the name of data store for one, original ESX_LUN_4?  I can just rename it or who will create more problems?  I tried a new analysis of the storage, but the data store name remained the same.

  Thank you.

  V.

  This is an expected behavior. Given that ESX detects the store of data replicated as a snapshot, in order to mount it, the volume must be resigned. Name of the resigned from the data store begins with the word "snap". You can rename it back without any problem.

  You can also configure SRM to rename the data automatically store. This is done by setting the parameter called SanProvider.fixRecoveredDatastores in the advanced settings of MRS, (located in the SAN provider section). The SRM service restart is required after the change.

  Good luck.

  Michael.

• Flat VMDK files after trying to delete files from data store

  I tried to delete a VMDK file in a data store, because I thought that it was not in use, and I need space. I couldn't get the VM you are looking for the name of the VMDK file, so I thought that the VM has disappeared. Turns out that someone had renamed the virtual machine, when it was actually being used, so I could not remove the VMDK file.

  I searched for the files with Powershell in a data store, and that's how I found this mysterious file in the first place.

  After giving me the error that it couldn't be deleted, the file does not appear in the search more and the name of the file has been replaced by *-dish. VMDK, I think, and the column by specifying the Type just said file, instead of virtual disk. In addition, files not included in the research more.

  Today, a day after, everything is back to normal. Everyone knows this behavior before and could tell me what happened?

  Each virtual disk is actually 2 files: VMname.vmdk and VMname - flat hard

  Unfortunately, the data store browser displays only the VMname... VMDK, but it gives the properties of VMname - flat hard. Use PuTTY, connect to the ESXi host via ssh, navigate to the folder of the virtual machine and use: the - lahtr to list the contents of an authoritarian way. You can also run: - ch to check actual use.

• Relocation of the unusable VCenter Server after data store

  I needed to move the VCenter server only US planes of the DataStore has located on SAN1 to B data store located on SAN2 because we were retiring SAN1. After connecting directly to the VMhost which housed the vCenter Server VM, closing the vCenter Server and remove the vCenter Server inventory, I scoured data store A and moved the server vCenter to B data store directory. "After the copy is completed, I added the back inot inventory of vCenter Server, it works, toldi it"I moved"and received an error message indicating the file vCentersrvr.vmdk ' was absent.

  A review of the content directory for vCenter data store b shows no vCentersrvr.vmdk, but rather lists a file called vCentersrvr - flat hard. The type of file, the file is listed as "file". I tried to rename this gall and turn on/off the VM, but still no luck. Here are my questions:

  1. Can I save this installation? The original directory no longer exists (it was deleted automatically after the copy of the file).
  2. If I can't save this installation, can I just rebuild a new vCenter Server and Add (2) hosts that are currently managed by the vCenter Server server has failed?

  There is another method to recreate the descriptor VMDK files. http://www.phdvirtual.com/VMDKstubgenerator

• Rename files within the data store

  Hi all

  I'm trying to rename some folders and files in my local data store.

  That's what I see in my local data store

  /

  TestBiz-(il s'agit d'une machine Virtuelle)

  . SDD.SF

  TestNav-(il s'agit d'une machine Virtuelle)

  Apps

  images

  TestBiz contains

  TestBiz01.vmdk

  TestBiz01 - 000001.vmdk

  TestBiz01.vmx

  TestBiz01.nvram

  VMware.log

  TestBiz01.vmsd

  Now my problem is the following.  The names of the two virtual machines must be lit.  TestBiz must be TestNav.  If I rename not only the record, but the files themselves who will break my servers?

  I am aware of the mixture to the top, but I don't want others in the future to get confused.

  Any help would be great

  Thanks in advance

  Welcome to the community,

  There was a current discussion on VMs rename (change the name of files and folders in data warehouses) which also contains links to some articles in the KB. However, in your case, the virtual machine has an active snapshot, and you should definitely remove the snapshot before you rename the virtual computer!

  BTW. where the virtual machine is managed in a vCenter server environment, you can automatically rename the virtual machine by changing the name of the virtual machine in the inventory of the GUI and then he migrate to another data store.

  André

• Data store 6.0 VMWare not recognized after the last batch of hotfixes installed on HP custom image

  Hello guys,.

  Maybe you can help me:

  I installed VMWare 6.0 on a server HP ML350 G9 with image OEM offered custom HP, ESXi - 6.0.0 - 2494585-HP - 600.9.3.30.2.

  This works perfectly.

  Now I am trying to apply the latest available official patch (ESXi600-201507001), but it seems to kill some important VIB

  VIBs installed: VMware_bootbank_esx - base_6.0.0 - 0.11.2809209, VMware_bootbank_lsu-lsi-lsi-mr3-plugin_1.0.0-2vmw.600.0.11.2809209, VMware_bootbank_lsu-lsi-megaraid-sas-plugin_1.0.0-2vmw.600.0.11.2809209, VMware_bootbank_misc - drivers_6.0.0 - 0.11.2809209, VMware_bootbank_sata - ahci_3.0 - 21vmw.600.0.11.2809209, VMware_bootbank_scsi - hpsa_6.0.0.44 - 4vmw.600.0.0.2494585, VMware_bootbank_scsi - mpt2sas_19.00.00.00 - 1vmw.600.0.0.2494585

  VIBs deleted: Hewlett-Packard_bootbank_scsi - hpsa_5.5.0.106-1OEM.550.0.0.1331820, LSI_bootbank_scsi - mpt2sas_15.10.06.00.1vmw - 1OEM.550.0.0.1198610, VMware_bootbank_esx - base_6.0.0 - 0.0.2494585, VMware_bootbank_lsu-lsi-lsi-mr3-plugin_1.0.0-1vmw.600.0.0.2494585, VMware_bootbank_lsu-lsi-megaraid-sas-plugin_1.0.0-1vmw.600.0.0.2494585, VMware_bootbank_misc - drivers_6.0.0 - 0.0.2494585, VMware_bootbank_sata - ahci_3.0 - 21vmw.600.0.0.2494585

  The next time I reboot the server, the data store is not available, no more and I have to do a restore. I suspect that the new bootbank_hpsa is the origin of the problem.

  So, how to install the latest patch without losing the data store connectivity?

  Thank you

  What should work, is to download the latest driver hpsa in the/hpq/latest/esxi-600-devicedrivers Indexand install it just after the connection of the host (prior to restart it). The .zip file contains a bundle off line as well as the .vib file.

  André