2 Gbps per data store

Similar Questions

• How many data store should be left to host his own execution

  Hi all

  I have EXSI 5.5 installed host recently. I'm going to create a new virtual machine on that host, but the data on this host store is about 2 TB and I want to put 1.8 to for my VM machine, so I only 0.2 TB left. The issue is with 0.2 left to there, that's enough to run its own code structures and data from the host? How to determine how much should be left? The same question for the memory and the processor.

  Could you please help with that?

  Thank you very much.

  Kind regards

  Thao

  ESXi is roughly Ligh weight. During Installation, the ESXi would automatically create the partitions. XXXX to hold (key code) bootbank, altbootbank, 4 Gigs vfat, store partition for tools and etc, that would be enough for the ESXi run and would not need anything else. A total of about 5 G of space is used and the rest should be left aside for you to create data stores to store virtual machines.

  From left to right on the space, ensure that you have left at least 20 to 30 GB per VM separately to run snapshots in your patch/maintenance cycles.

• Lost access to local data store

  Hi people:

  I have ESXi 6.0 running on an Intel S2600CWTS motherboard using the LSI SAS controller onboard and six readers Samsung 850 Pro SSD in a RAID 5 configuration.  This server is about a month and a half, and it worked fine for the first month, but in the last few weeks I started to do in the case where journal messages saying that ESXi has lost access to the data store, then, most of the time, about 15 seconds later access is restored.   Several times it took more time, which one crashed the server.  On these long, the motherboard Intel event log showed that a player had failed and began a regeneration and once the motherboard has shown that two different drives had failed, and it took both offline originally ESXi crashing.  On it that I was able to bring the two records back online via the RAID bios and everything worked fine again.  I suspect that I have hard disk problems because these discs are new and because different readers have been reported as failed, and also because no data has been lost even if 2 drives went offline at the same time.   I guess I could have a bad controller LSI, or a cable has come loose somewhere, but I expect to happen if it is really the case of data loss.

  I also noticed that lost access messages tend to appear in the log at the moment I start a virtual machine.  At first I thought that it would be one thing to flow, thinking a VM departure did a lot of IO, but this happens immediately, before even the bios of the virtual screen machine disappears, so I don't think that the virtual machine is actually reading the disc again.  In addition, as a precaution, I started the migration of some virtual machines on the server to the old server I still had available, and there is no lost access messages in the event log while that was happening, while about 50 megabytes per second of i/o has reached the disk during transfers.  I put the last patch on ESXi in mid-May, about two weeks before this started, and I begin to suspect that the patch may have something to do with it, because it seems to me that if something is happening between ESXi and the disk controller making hang up or lose interruptions during a short period of time , and I wonder if it goes pretty long if material in the motherboard sensors interpret this as some sort of hardware and simply brand failure according to readers I / O was hooked as bad then.

  Unfortunately I'm out of town now so I wanted more I had to the remote server, lest I do not not get back to the top.  I moved a couple of the most critical virtual machines from the old server which I was remotely start and transfer to virtual machines.  I also noticed that this issue tended to occur more frequently when I got to the top of the VCenter Server apparatus that any other (sometimes to others, but has happened every time I tried to start the device VCenter).  So who was the first that I moved to the old server, but strangely enough there is no error logged when I transferred the files, so the issue is not that ESXi had trouble reading the VMs vmdk file when I started it.

  I also wanted to ask you if there are any vibs for the LSI Megaraid controller on motherboard S2600CWTS I could install that would allow me to access the RAID controller without having to pick up the server and do it from the BIOS configuration screens, similar to how you can access the controller RAID from Dell while ESXi is running via a vib add-on.  So far I have not found one.

  My intention when I go to the server is to run an integrity check against the RAID 5 array via the controller and then use the AIMÉ ESXi utility on the data store to see if something is wrong here.  If not, then I guess I'll rewritten can patch.

  Ideas or suggestions welcome.

  Success!  I finally understood what the problem was corrected.  The problem is the fact that although the last vib driver LSI has been installed, for some reason any it would not automatically replace the default ESXi pilot lsi_mr3.  I did not notice that even though the latest driver package vib properly installed LSI controller was still using the original driver.  This could be considered by a 'esxcfg-scsidev - a' command showed that even "vmhba1 lsi_mr3 link-n/a sas.5001e67ca647e000 (0000:0: 00.0) controller LSI MegaRAID SAS Fury."  The second field after the controller (vmhba1) is the current manager used.  The pilot, which was to be used was: "vmhba1 megaraid_sas link-n/a unknown.vmhba (0000:03:00.0) Avago (LSI / Symbios Logic) Invader MegaRAID SAS controller.

  To fix this I had to disable the lsi_mr3 driver so that ESXi is forced to use it.  The procedure to do is the following:

  (1) make sure you have the new EXSi driver you want to use already installed.  I assume that bad things would happen if you have disabled the only driver who could run your disk controller.  Use this command to view the drivers installed: "esxcli software vib list" and you should get something similar to the following:

  [root@intelserver:~] esxcli list of software of vib

  Name Version Date seller installation acceptance level

  -----------------------------  ------------------------------------  ------  ----------------  ------------

  MegaRAID SCSI-sas 6.608.11.00 - 1OEM.600.0.0.2494585 Avago VMwareCertified 2015-07-19

  LSI - mr3 6.606.10.00 - 1OEM.550.0.0.1391871 LSI VMwareCertified 2015-06-19

  mtip32xx-native 3.8.5 - 1vmw.600.0.0.2494585 VMWARE VMwareCertified 2015-04-28

  ATA-pata-amd 0.3.10 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-atiixp 0.4.6 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-cmd64x 0.2.5 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-hpt3x2n 0.3.4 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-pdc2027x 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-serverworks 0.4.3 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-sil680 0.4.8 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-via 0.3.3 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  block-cciss 3.6.14 - 10vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  CPU-microcode 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  EHCI-ehci-hcd 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  elxnet 10.2.309.6v - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Emulex-10.2.309.6v - 0.0.2494585 VMwareCertified-2015-04-28 VMware esx-elxnetcli

  ESX-based 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  ESX-dvfilter-credits-fastpath 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  ESX-tboot 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  6.0.0 - 0.0.2494585 of xserver-ESX VMware VMwareCertified 2015 - 04 - 28

  IMA-qla4xxx 2.02.18 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-devintf 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-paremeter 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-TR-drv 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LPFC 10.2.309.8 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSI-msgpt3 06.255.12.00 - 7vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-hp-hpsa-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-lsi-lsi-mr3-plugin 1.0.0 - 2vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  LSU-lsi-lsi-msgpt3-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU lsi megaraid sas plugin 1.0.0 - 2vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  LSU-lsi-mpt2sas-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-lsi-mptsas-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  Misc-cnic-register 1.78.75.v60.7 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Misc-pilots 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  NET-bnx2 2.2.4f.v60.10 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-bnx2x 1.78.80.v60.12 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-cnic 1.78.76.v60.13 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-e1000 8.0.3.1 - 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-e1000e 2.5.4 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-enic 2.1.2.38 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-forcedeth 0, 61 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-igb 5.0.5.1.1 - 5vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  NET-IGB 3.7.13.7.14iov - 20vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-mlx4-core 1.9.7.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-mlx4-en 1.9.7.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-nx-nic 5.0.621 - 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-tg3 3.131d.v60.4 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-vmxnet3 1.1.3.0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  nmlx4-core 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nmlx4-en 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nmlx4-rdma 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nVMe 1.0e.0.35 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  OHCI-usb-ohci 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  qlnativefc 2.0.12.0 - 5vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  REST 2.0.2.0088 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  Ahci SATA 3, 0 - 21vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  ATA-SATA-piix 2: 12 - 10vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  NV-sata-SATA 3, 5 - 4vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  SATA-sata-promise 2: 12 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-sil24 1, 1 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-sil 2, 3 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-svw 2, 3 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-aacraid 1.1.5.1 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-adp94xx 1.0.8.12 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-3, 1 - aic79xx 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-bnx2fc 1.78.78.v60.8 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-bnx2i 2.78.76.v60.8 - 1vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  SCSI-DNI 1.5.0.45 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-hpsa 6.0.0.44 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-ips 7.12.05 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-megaraid-mbox 2.20.5.1 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-megaraid2 2.00.4 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mpt2sas 19.00.00.00 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mptsas 4.23.01.00 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mptspi 4.23.01.00 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-qla4xxx 5.01.03.2 - 7vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  UHCI-usb-uhci 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  VMware-esx-dvfilter-maclearn-1, 00 1.00 VMware VMwareCertified 2015-05-12

  xHCI-xhci 1, 0 - 2vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Tools-light 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  [root@intelserver:~

  Verify that the scsi-megaraid-sas driver is installed before proceeding.

  (2) to disable the lsi_mr3 driver do the following: "esxcli set of module system - enabled = false - module = lsi_mr3 '

  (3) reboot

  After restarting, do: "esxcfg-scsidev - a" to check megaraid_sas driver is assigned to your disk controller.

  I don't know how ESXi decided to prioritize if two or more drivers are applicable to a single hardware device, or if the installation of the new driver LSI process is supposed to disable or remove default lsi_mr3 driver and simply failed to do so.  Also, I don't know what's going to happen when I put on the next patch of ESXi, specially if the lsi_mr3 driver will be once more the priority.  If anyone knows how the driver installation process is supposed to work in this situation, please let me know.  I am so happy that I finally got this problem because the server has been seriously covered with the data store become unaccessable for 5 to 10 seconds every time a VM started or stopped, and the former driver at least once done something bad enough to deceive the controller into thinking that one of the disks has went wrong and began a RAID Resync.

• VMs of MAX in a data store: vsphere 5.5 (HA not configured.)

  Hi all

  I have a 5.1 vcenter where HA is not configured. I want to know what is the number max of vms in a data store (Powered on and powered at the same time).

  As this vcenter is no less with HA, does by default no that is 2048 as by maximum vsphere will be the same or not.

  in vmware drivers maximum, I found below.

  Config files on your virtual computer by the data store in a cluster HA: 2048 (without HA which is no?)

  Thank you.

  Hello

  Maximum limit of 2048 VMs running also apply to the VMFS5 file system.

  For turning off VMs, I think you can take numbers vCenter and cluster up to 15000 registered VMs and VMs 4000 clustered...

  See also this thread:

  http://www.yellow-bricks.com/2014/02/05/vSphere-HA-VMs-per-datastore-limit/

  Kind regards

  P.

• displacement of the VM in another data store

  Hello

  We organize 2 5.5 vSphere hosts (VMware vSphere Essentials 5 Licensed for 2 processors (unlimited cores per processor) physical.)

  One of our data warehouses has insufficient free space on the disk.

  I'd be happy if someone could give me a little advice what is the best way to move or copy a virtual machine in another data store.

  Already, I read after KB, but he has not understood completely.

  VMware KB: Move or copy a virtual machine in a VMware environment

  Kind regards

  Roland

  Your screenshot shows that you are on the right track.

  As soon as you have turned off the virtual computer the

  dimmed options get turned on even on the essential.

  See you soon.

• Create a custom attribute to model the growth rate of the data store used space

  I would like to see data warehouses are growing fastest of the environment in terms of GB per day or something similar.  Is it possible to use a custom attribute to apply a formula that measures the rate of growth of a store of data over time, which allows me to see what data stores fastest?

  You would look for an average simple mobile for a SM you describe. vC Ops does not simple moving average formulas for SMs at this time.

  Looks like you are looking for a "growth rate", but you really won't get it with the built-in attributes. You might look differently and look at the remaining capacity and the remaining time metric. Also, you could create additional widgets to view graphs of util % over the last 30-90 days to give a better picture of usage in GB, #VMs, etc.

  I also suggest to make a Top - N showing use the lowest of the remaining time metric and the remaining ability... This will give you your data warehouses that are more at risk.

• Delete a snapshot in ESXi 5 when data store is almost full

  I'm very skiddish on use or deletion of snapshots after a disaster, I had with them last year. So, I thought I would get your recommendation before you continue.

  I have a virtual machine running on the host with about 700 GB of total space on the data store. The virtual machine uses about 500GB and there is only a snapshot of the virtual machine. The virtual machine uses a disc thin provisioned. I received a warning that there is insufficient data on the space store and there are only about 120 GB left. Is it safe to remove the snapshot? Should we double the size of the virtual machine to "consolidate? The last time I did it with multiple snapshots and a lot less space, it's disaster.

  Edit: Here's what's on the data store (for this virtual machine). There is an another VM on the same data store which shows it takes 40 GB of space.

  

  Here's what it says on the storage to Apollo (the virtual computer name) under summary in vSphere:

  

  The basic disk can only 'baloon' upward only by the amount of data in the snapshot, which is 214 GB function provided screenshot and to be on the safe side, you have to assume that he will do. If you need to at least 214 (I'd Go 220) free on the data store for a safe removal-snapshot operation.

  Worse: these 214 GBs are given new, added after the creation of the snap. You the kickoff of the removal process. Basic disk to grow per GB 214. Currently, it consumes 355 GB so it will grow up to 569GB. Only one time all the data of the snap is committed to basic disk, the snapshot will be deleted. This is why you need some 220 GB free and available on the data store to start the removal process.

  Instant deletion on an engine out of VM might help a little, but looks like not as much as you want.

  If you shut down the virtual, pagefile will be deleted which will free up to 4 GB.

  Also if you delete a wink on the virtual machine performance, actually another cliché will be created to store the changes that VM is done during the delete operation. According to the rate of change of data within your VM and the time required for the delete operation, it will take little extra space on the data store as well. This need for extra space can be avoided by removing the snap while the VM is turned off.

  However, in your case the virtual computer power on off won't help

  Bottomline - if you can, find a way to get 220 + GB of free space on your data store before you delete the snapshot. Otherwise, the next option is VM migration to a different data store with storage vMotion (without interruption) and deletion of snapshots there (once again, potentially without interruption). A last - cloning in another data store that involves downtime.

  And you cannot clone to USB.

• Percent free on the data store

  So I have free data per cent with the VIProperty module but I'm running into a problem trying only to find warehouses of data with less than 20%.  It seems to only be comparing the first issue of PercentFree so missing a free with 5,86% data store.  I paint a white on a better way to compare these two values?

  $datastores = get-Datastore

  $datastores | where {$_.} Name - notlike ' Local * "- and $_. PercentFree - lt 20} | sort name | Select Name, PercentFree

  Results...

  Name PercentFree
  ----         -----------
  Datastore01 0.02%
  Datatsore02 19,24%

  The data property of the VIProperty module PercentFree store generates a string, for example ' 20.12%. It is difficult to compare. You better use the following definition that generates a numeric value.

  New-VIProperty -Name PercentFree -ObjectType Datastore -Value {
    param($ds)
  
    100*$ds.FreeSpaceMB/$ds.CapacityMB
  } -Force
  

• Complete data store during data transfer

  Hi all

  I'm having a serious problem with the ability to store data, if I transferred a huge amount of data to a virtual machine through SSH. The data store has a total capacity of 511 GB. During the process of transfer of the virtual machine stops, just when the data store is full. So the only solution is to detach other virtual machines from the data store, but it is not enough.

  We are using VMware ESX 3.5 and virtual machine is Ubuntu Server. Here is the configuration of the virtual machine:

  Memory: 1024 MB

  Processors: 1

  HardDisk1: 6 GB

  HardDisk2: 52GB

  HardDisk3: 230GB

  HardDisk4: 256 GB

  Storage distribution and capacity for the VM:

  # df h
  Size of filesystem used Avail use % mounted on
  / dev/map/vg00-VG00_ROOT
  3.4 G 2.6 G 621M 81%.
  No 495M 220K 495M 1% / dev
  No 500M 500M 0 0% / dev/shm
  No 500M 524K 500M 1% / var/run
  No 500M 500M 0 0% / var/lock
  No 500M 0 500 M 0% / lib/init/rw
  / dev/map/vg01-VG01_home
  5.4 G M 276, 4.8 G 6% / Home
  / dev/map/vg00-VG00_TMP
  1008M 34 M 924M 4% / tmp
  / dev/map/vg00-VG00_LOG
  1008M 53 M 904M 6% / var/log
  / dev/sda1 122 M 118 M 0 100% / Boot
  / dev/map/VG02-VG02_home_dpto
  479G 219 G 236 G 49% / home-Dept.

  HardDisk3 and HardDisk4 are mapped in a (VG02-VG02_home_dpto) LVM volume and its free space is 236 GB. Space free Dtx200: 4, 56 GB. I don't understand why. The problem may be caused by automatic generation VMDK:

  * ficheros00.platform.core.vmdk-> 6 GB

  * ficheros00.platform.core_1.vmdk-> 54 GB

  * ficheros00.platform.core_2.vmdk-> 241 GB

  * ficheros00. Platform.Core.-000002.vmdk-> 24 GB

  * ficheros00. Platform.Core_2 - 000001.vmdk-> 166 GB

  The first time, I got 20G of free space of the data store removing some residual VMs. Then I tried to copy a folder of 15 GB through the network by SSH from another server in files. It was the occupation during the first use: (just to compare)

  * ficheros00.platform.core.vmdk-> 6 GB

  * ficheros00.platform.core_1.vmdk-> 54 GB

  * ficheros00.platform.core_2.vmdk-> 241 GB

  * ficheros00. Platform.Core.-000002.vmdk-> 10 GB

  * ficheros00. Platform.Core_2 - 000001.vmdk-> 164 GB

  It seems 000002.vmdk and 00002.vmdk develop during the transfer of files, but they do not consolidate data. I don't know whether this is a normal behavior. I think that space used for ficheros00.platform.core-000002.vmdk-> 24 GB and ficheros00.platform.core_2 - 000001.vmdk-> 166 GB should be included in the ficheros00.platform.core_2.vmdk - > 241 GB and end of data transfer that they should disappear themselves.

  We calculate the initial free space before allocating hard disks of the virtual machine.

  In this data store, we currently have 2 VM:

  [root@hp585-01 eva4400:-02] # du-sh ficheros00.platform.core./
  472G ficheros00.platform.core

  [root@hp585-01 eva4400:-02] # du-sh lucus01.labo.core_1/
  36G lucus01.labo.core_1

  Any help would be appreciated. Thank you very much.

  Best regards

  Harry.

  Log files, I see that capture files two instant belong to basic disks on the two different data stores on this host ESXi 3.5 Update 3. In any case with being thick implemented basic disks, you should be able to delete snapshots in the snapshot with off the virtual machine Manager. If the virtual machine is still on when you delete the snapshots, you need more disk space for another, temporary snapshot (snapshot to help consolidate)

  When you have removed before snapshots, you did this with the virtual machine power on or power off?

  Turn off the virtual machine will be to free up disk space (the .vswp file is deleted) and merge data from snapshot (with only a single snapshot per virtual disk) in basic disks should not require additional disk space.

  Because the Snapshot Manager doesn't show pictures anymore after the failure of the attempt, you will need to create a new snapshot (to activate the button 'Clear all') and hit use 'delete all '. Because of the size of snapshots, it may require some time to merge data in basic disks, so be patient, even if the GUI user expires!

  André

  PS: Please check that the second VM on the data store does not work on snapshots too, who could fill the data store so that you remove snapshots of the virtual machine in question!

• Machines MSCS with RDM, how to change the data store?

  
  Hello world

  I'm having a problem of displacement of 2 machines with RDM disks.
  We have 2 guests ESxi 4.1 with virtualcenter, but no license for vmotion.

  This 2 machines is building a MSCS Cluster (Microsoft) (file server) with multiple disks (5) RDM,
  for a total area of 8.9 TB. Of course, for use with MS cluster, the WDR is with physical compatibility.

  The problem is that the local vmdk (and also rdm.vmdk files) for these 2 machines are on the local data store (a machine for each host) and I need to move them to the shared storage. But if I power off of a computer and trying to change with the ROW data store attached, I get an error because the VMFS of the commune dastore (block size = 1 MB) does not support these large files (up to 2 TB).

  I read a lot of articles
  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1031041
  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1026256
  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1002511
  and a few other discussions of communities.

  In accordance with article
  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1005241

  I tried to turn off the machine, remove the RDM, migrate to another data store, and then reconnect the RDM.
  There is a big problem with the last point, because I don't know how readd the RDM manually (vmfsktools?).
  I want to add an existing drive, but he was in local storage, and I don't want more no reference to the file in the local storage...
  According to the documentation of vmware for MSCS, the second node of the cluster disks can be added simply to add a drive existing and selecting the
  existing node. If it is no problem of shared storage, but the host cannot read local storage to another host...

  Any suggestion to migrate a computer virtual with RDM shared storage room? Thank you

  E' possibile disabilitare he LUN filtering per vedere UN RDM gia awarded:

  http://www.yellow-bricks.com/2010/08/11/storage-filters/

  Option da diabilitare temporaneamente in vCenter config.vpxd.filter.rdmFilter

  Andrea

• Data store show that 40 GB

  Hi guys,.

  I just installed vSphere ESXi 4.1.0 Update 1 on our new Dell R710 of EP include 2 TB of disk space.

  But here's my problem: when I go in the vSphere Client and have a look at the size of the data store, it shows only 40 GB. I reinstalled and got the same result.

  I would like to know or have that because it's the first time in I face this kind of problem and of course, to solve this problem?

  Best regards

  Johnny

  Maximum VMFS is 2 TB - 512 KB per LUN. Nothing more than that he would go crazy. I advise to divide your LUN to 1 TB each and you would not have any problem to access and set in the shape of your data store.

• Cannot add a new data store

  Let me preface this post by saying that I am an extreme noob to VMWare... Have only used MS HyperV in the past but looking to oust most of my hardware with VMWare on the recommendation of a colleague.

  On the problem.

  I have a server Dell PowerEdge 2900 with 32 GB of RAM and 8 TB of disk space.

  I installed ESXi yesterday and you can see my original data store, called "datastore1", which is only 325 GB.

  I try to add a new data store, but when I go to 'Add storage' in vSphere, select ' disk/LUN", the list is empty.

  I know I'm missing something, but don't know where to look.  What should I do to add a new datasore and subsequently more storage to my VMWare environment?

  DRM for all help!

  To add a data store storage must be allocated to the vSphere server.  There is also a size limit of 2 TB less 512 bytes per LUN for a vSphere.   Try a few small LUN and see if they appear as available when you add a data store.   I have included a link pdf maximum configuration for vSphere 4.1

  http://www.VMware.com/PDF/vSphere4/R41/vsp_41_config_max.PDF

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

  Twitter: http://twitter.com/mittim12

• Data store IO error

  Hello world

  I have managed to lose my data store. What I tried to do is to add a virtual machine rebooted my ESXi 4.1, after which he gave me a degraded RAID (don't know how my RAID touched or was it just a coincidence). I have ESXi with 2 Xeon Nehalem 2.0 GHz CPU, motherboard Supermicro, 24 GB of memory and 4 drives of 2 TB with Adaptec 2405 RAID 10. All are in the white list HCL. As ESXi not hired more 2 TB, I shared the RAID at two warehouses of 2 TB, I use only one (I hope that in a near future VMWare support for 4 TB aura).

  I SSHed into the console and interpreted some of the corrections suggested, but almost everything that I tried brings no results. It is the output of the last one I tried:

  ~ # esxcfg - scsidevs - f

  MPX.vmhba1:C0:t0:l0:2 /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:2 4c105d78-8e60d777 - 14 d 5-003048fbec1d

  MPX.vmhba1:C0:t0:l0:5 /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:5 be2e247c-159e44fa-e4d8-79515a8dcd67

  MPX.vmhba1:C0:t0:l0:6 /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:6 c5ef4974-b5423ceb-86e8-5fc6034bebb5

  MPX.vmhba1:C0:t0:l0:8 /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:8 e00f98e1-2bcc0c91-e7a2 - 3487611c 1557

  ~ # ls-l | grep vmfs

  lrwxrwxrwx 1 root root 49 26 August at 18:51 altbootbank - & gt; / vmfs/volumes/be2e247c-159e44fa-e4d8-79515a8dcd67

  lrwxrwxrwx 1 root root 49 26 August at 18:51 bootbank - & gt; / vmfs/volumes/c5ef4974-b5423ceb-86E8-5fc6034bebb5

  lrwxrwxrwx 1 root root 49 26 August at 18:52 scratch - & gt; / vmfs/volumes/4c105d78-8e60d777-14 d 5-003048fbec1d

  lrwxrwxrwx 1 root root 49 26 August at 18:51 store - & gt; / vmfs/volumes/e00f98e1-2bcc0c91-e7a2-3487611c 1557

  drwxr-xr-x 1 root root 512 26 August at 18:51 vmfs

  ~ # dosfsck - v /dev/disks/mpx.vmhba1:C0:T0:L0:2

  dosfsck 2.11 (March 12, 2005)

  dosfsck 2.11, 12 March 2005, FAT32, LFN

  Check the last sector of the file system, we can access

  Content of boot sector:

  ID of the system "MSDOS5.0".

  Byte media 0xf8 (hard drive)

  512 bytes / logical sector

  65536 bytes per cluster

  2 areas

  First FAT starts at byte 1024 (sector 2)

  2 fatty acids, 16-bit entries

  131072 bytes per FAT (= 256 sectors)

  Root directory begins at byte 263168 (sector 514)

  224 entries of root directory

  Data area starts at byte 270336 (sector 528)

  65515 data clusters (4293591040 bytes)

  18 sectors/track, 2 heads

  0 hidden sectors

  total 8386560 areas

  Reading of 32 bytes to 524288:Input / output error

  I followed this link with the commands 'day' as it has been posted for esx3.5 but no luck so far. I am a beginner total then all would be greatly appreciated pointers, suggestions or report errors about why and what does not work.

  My goal is to be able to read the data, connect with Veeam and move it to an external storage. Then wipe everything and move it back (I think my 4.0 to 4.1 upgrade was not very clean, so I just reinstall it, but before delete and recreate my RAID to return to State "Healthy").

  Thank you in advance!

  Post edited by: Dave.Mishchen...

  I shared the RAID at two warehouses of 2 TB, I use only one (I hope that in a near future VMWare support for 4 TB aura).

  VM ware HAS support for 64 to, they are called extensions.  The 2 TB limitation is not VM Ware, its how the charger startup and connection to the LUN works technology.  So someone else would have to design an update for file systems and LUNS, VM Ware will adopt, but this isn't a limitation of VM Ware, they already have a workaround solution.

  How to make it work is you can not take a drive and divide, you MUST create a disk full (created in RAID level).  Because the different partitions will not be displayed as unique readers.  So if you have a large RAID, and you create 2 drives her, a secondary disk free space that can be extended on the first, giving you 4 TB as a SINGLE data store.

  If there is a RAID on Board that could be your problem also.  SOME RAIDs, even when they say RAID, are really not capable of performance.  So it is very probably the IO is invading your RAID controller, and so it loses the ability to keep up with journaling and writing... etc... and that could be what is causing the RAID degraded become.  Some RAID integrated on the motherboard, is controlled by the CPU, it is not a controller for the RAID, so if your CPU is busy AND you have SATA (which is also controlled CPU) AND you have a lot of updates and writes, that leads to trolling, causing RAID to lose track of changes... and so you lose the RAID.  Which is another reason why you should check the hardware compatibility list, because otherwise you're taking a chance that it will work... that in your situation seems to be hit or miss.  Which tells me your motherboard / combo RAID is not enough to run ESX.  At the very least, get a PCIe RAID card... That will help you.  They are cheap (for those decent).

• root properties in the connected data store: error when accessing the date/time storage

  When you browse the properties my connected data store I get an error message when you try to read the value of the property of 'storage date/time': object doesn't support this property or method.

  Here is a minimal example:

  Dim oMyDataStore, MyProperty, oMyProperties
  
  Set oMyDataStore = Navigator.ConnectDataStoreByParameter ("TOC", "" & "C:\Program Files (x 86) \National 2012\Examples\Data\Example_data.tdm" & "" ')
  
  Set oMyProperties = oMyDataStore.RootElements (1). Properties
  
  For each MyProperty in oMyProperties
  
    Call MsgBoxDisp ("property name:" & MyProperty.Name & + "\n"&"property value:" & MyProperty.Value "")
  
  Next

  Why can I not access this particular property by default?

  Hi Phex,

  for the date/time properties, an object called UsiTimeDisp is returned. This object allows to that extend features of service as access to each part separately (day, year, hour, seconds,...) of your date/time value. If you want to print the value of time with MessageBoxDisp, you can use the VariantDate this object property.

  Your code might look like this then:

  Dim oMyDataStore, MyProperty, oMyProperties
  
  Set oMyDataStore = Navigator.ConnectDataStoreByParameter ("TOC", "" & "C:\Program Files (x 86) \National 2012\Examples\Data\Example_data.tdm" & "" ')
  
  Set oMyProperties = oMyDataStore.RootElements (1). Properties
  
  For each MyProperty in oMyProperties
  
    MyProperty.DataType = eTime Then
  
      Call MsgBoxDisp ("property name:" & MyProperty.Name & + "\n"&"property value:" & MyProperty.Value. ' ") VariantDate)
  
    On the other
  
      Call MsgBoxDisp ("property name:" & MyProperty.Name & + "\n"&"property value:" & MyProperty.Value "")
  
    End If
  
  Next

  I hope this helps.

  Good day

  Eva

• Connection to the AOP with several NIC data store

  I have a situation where I need to have the computer that is running the tiara to be connected to two different networks.  I have two NIC installed in the machine, NIC A and B NIC, we will call them.  The reason for this is that I use Diadem to access the server on a machine of AVL PUMA AO.  If I connect to the local network PUMA, PUMA sometimes breaks down, probably something to do with the IP address.  So PUMA has need to be on a network that is not a router.  My tiara computer must communicate with PUMA, as well as with local shared drives on our corporate network.

  In any case, I have the company LAN hung on A NIC and hung on NIC B PUMA network.  Tiara fails to connect when the two networks are connected, but connects to the data store no problem when that network PUMA is hung. Any ideas how to solve this problem?  It seems tiara is looking for NIC - A instead of NIC B, as appropriate.

  For reference, when the two NIC is connected, I can access other than readers, and separate computers to ping on both networks, without problem, is not a connection problem.

  Any help would be appreciated.

  -Russ

  I guess poth NIC have different IP.

  -Did you use IP instead of the server name.

  -Do you use RPC or CORBA to access the PUMA Server?

  -What version of DIAdem.

  You can create a log file when the connection has failed?

  Greetings

  Andreas