permit request for the data store

I recently bought a license of data store for my virtual machine host. My question is, can I just replace the current key on existing servers with the key data store? Also, is the key to good for the 2008 and 2012 on the host servers?

Hello

Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

See you soon.

Tags: Windows

Similar Questions

  • ESXi 5.5 only 4 TB usable for the data store

    Hi all

    Although in vSphere Client 5,46 TB of capacity is visible, I can only use 3.64 TB to a data store.

    Configuration:

    -HP Proliant Microserver N40L

    -HP Smart Array P410/512 MB BBWC, FW 3.66 Controller

    -4 x 2 TB as a Raid5

    HP-ESXi - 5.5.0 - iso - 5.72 A

    I read a lot of articles on > limits of 2 TB of older versions of ESXi or controllers, limitation of 4 TB of c# vSphere Client, old firmware and esxi driver problems, etc.

    But I could not understand the problem.

    The P410 controller shows 5.5 TB:

    ~ # esxcli hpssacli cmd - q "controller connector = 1 see the config.

    Smart Array P410 in slot 1 (sn: PACCRID110510NR)

    Array A (SATA, used space: 0 MB)

    logicaldrive 1 (5.5 TB, RAID 5, OK)

    then 2I:0:5 (port 2I:box 0:bay 5, SATA, 2 TB, OK)

    then 2I:0:6 (port 2I:box 0:bay 6, SATA, 2 TB, OK)

    then 2I:0:7 (port 2I:box 0:bay 7, SATA, 2 TB, OK)

    then 2I:0:8 (port 2I:box 0:bay 8, SATA, 2 TB, OK)

    MS (Vendor ID PMCSIERA, model SRC 8x6G) 250 (WWID: 5001438013D9F37F)

    ESXi obviously knows the same size:

    ~ # Esxcli storage core devices list

    NAA.600508b1001ca5e68adc0bc4bc508d6e

    Full name: Serial Attached SCSI disk HP (naa.600508b1001ca5e68adc0bc4bc508d6e)

    Definable display name: true

       Size: 5723091

    Device type: Direct access

    Multichannel plugin: NMP

    Devfs Path: /vmfs/devices/disks/naa.600508b1001ca5e68adc0bc4bc508d6e

    Vendor: HP

    Model: VOLUME LOGIC

    Review: 3.66

    SCSI level: 5

    (etc.)

    But does that 4 TB:

    ~ # df h

    Size of filesystem used available use % mounted on

    VMFS-5 T 3.6 2.1 T 1. 5 t 58% / vmfs/volumes/mainstorage

    vfat 249.7 M 177.2 M 72.6 M 71% / vmfs/volumes/aeda2aeb-c934ad60-46ce-cb77abdfabaa

    vfat 249.7 M 175.9 M 73.9 M 70% / vmfs/volumes/c8ace7e9-a96a5914-16 d 4-a697ad4634d9

    vfat 285.8 M 191.4 M 94.4 M 67% / vmfs/volumes/55d7af6e-a25f7c97-c3ec-6805ca0de93c

    I tried to increase the size of the data store, last used area was 11720890367 and last sector was 11720890510 which doesn't really seem to translate into an increase of 1.8 to.

    Thanks for your help.

    DC

    Your output, it shows that there are two partitions vmfs

    3 10229760 3907029134 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

    4 3907031040 11720890367 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

    A partition with 1.8 to and another with 3.8 to.   That's the reason why you see only 3.8 to

    I don't know why the 1.8 to vmfs volume is not list anywhere (which does not appear in the list of file system of storage of esxcli also). Do you have any before partition created manually. If you think that if there is no data in this 1.8 to vmfs partition you can remove it by using the partedutil command and then use this free space to extend the existing 3.8 to. But do not forget before you delete the partitiaon

  • get support scsi LUNS for the data store?

    I've been delving into the different classes available to HostSystem.queryHostConnectionInfo () and none of the properties appear to contain the id of naa I see when I look at LUNS on an HBA.  How do you get to LUN support for a data store?

    Figured it out.  For anyone else who wants to know:

    I created two actions, one to return a hash of the id of naa-online data store object and another action to return a hash of the naa-online drive scsi id

    // actions
    //getDatastoresKeyedByLUN
    var o_diskHash = new Properties();
    
    for each (var scsiDisk in u_host.config.storageDevice.scsiLun)
    {
      //System.log("-> LUN: " + scsiDisk.canonicalName);
      for each (var dataStore in u_host.datastore)
      {
      if (dataStore.info.hasOwnProperty("extent"))
      {
      for each (var scsiDiskPartition in dataStore.info.vmfs.extent)
      {
      if (scsiDiskPartition.diskName == scsiDisk.canonicalName)
      {
      o_diskHash.put(scsiDisk.canonicalName, dataStore);
      }
      }
      }
      }
    }
    
    return o_diskHash;
    
    // getScsiDisksKeyedByLUN
    var o_diskHash = new Properties();
    
    for each (var scsiDisk in u_host.config.storageDevice.scsiLun)
    {
      o_diskHash.put(scsiDisk.canonicalName, scsiDisk);
    }
    
    return o_diskHash;
    
    // in workflow
    for each (var can in dstoreMap.keys)
    {
      System.log(dstoreMap.get(can).name + "(" + lunMap.get(can).canonicalName + ")");
    
    }
    
  • Name of device for the data store list

    Need help with this simple script

    $datastores = get-Datastore-location "CXXV. Where-Object {$_.ExtensionData.Info.GetType ().} Name - eq "VmfsDatastoreInfo"}

    $myColCurrent = @)

    ForEach ($store in $datastores)

    {

    $myObj = "" | Select-Object Name, devicename

    $myObj.Name = $store.name

    Write-Host $myObj.Name

    $myObj.devicename = $store.ExtensionData.Info.Vmfs.Extent.DiskName

    Write-Host $myObj.devicename

    the name of the data store is writtenl properly but the devicename is empty and get this warning:

    WARNING: The 'Accessible' type of data store property is obsolete. Use the property 'State '.

    Strange thing is that the Script works lab powercli linking the vCenter lab. But gives the error in the production powecli server to vcenter prod.  powercli and vcenter server versions are the same.

    Help is greatly appreciated

    The extended property is an array.

    Try to change this line

    $myObj.devicename = $store.ExtensionData.Info.Vmfs.Extent.DiskName

    in this

    $myObj.devicename = [string]: join (",",($store.ExtensionData.Info.Vmfs.Extent |) %{$_. DiskName}))

    You can safely ignore the warning messages, or may disable them with the Set-PowerCLIConfiguration cmdlet and the DisplayDeprecationWarnings switch.

  • Cannot download the files of the virtual machine for the data store

    Hello

    I get an error message "connection to the server timed out" while I'm trying to download the files from the virtual computer from the data store.

    Although the ESX and my laptop are on the same network, I get this error message.

    Please let me know if I need to take care of something.

    Thank you.

    I think that hard & .vsmp be used & locked is why you are unable to download it. Try to download the file, whereas the VMs system is turned off

    vcbMC - 1.0.6 Beta

    Lite vcbMC - 1.0.7

    http://www.no-x.org

  • Increase the volume for the data store

    Hello

    Someone recognizes this problem?

    When you try to increase a volume of data store in vSphere4 we get the following message: "error during the configuration of the host. Failed to get the disk partition information.

    We use a MSA2324 of HP storage as a storage (data store) to our servers of vSphere. I increased the volume of the utility interface HP Storage manager 1.5 TB to 2.2 TB. So far so good. But when I try to increase the datastore in vSphere, this error message occurs.

    I've done this before, but now it doesn't seem to work. We have 25 active servers attached to this data store. I REALLY want to increase this volume online. It will probably work if I stop all virtual servers, restart the server VSphere and then increase the volume.

    Concerning

    Magnus

    Maximum supported LUN size is 2 TB minus 512 b.

    ---

    VCP MCSA, MCTS Hyper-V, VMware vExpert 2009, 3/4

    http://blog.vadmin.ru

  • Maximum of storage for the data store?

    Hello

    I have a server configuration with a hard drive 2 TB Raid 1 mirror set. I installed hypervisor on it without any problem. When I go to configure a virtual machine, I can't put the main virtual C drive beyond 256 GB or 0.25 TB. A few reasons why this is happening?

    The drives are SATA.

    Thanks in advance for your comments.

    Hello

    because you have formatted your VMFS Datastore with a block of 1 MB, which will result in a maximum size of 256 GB.

    Reformat your VMFS with a bigger unit.

    See:

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

    Concerning

  • Command or a script required for the data store, the identifier of NAA and multipath

    The following script/command gets me politics multichannel on a csv file, however, I need to also identify the "Datastore" name with the number of naa.

    Get-cluster 'windows 01' | Get-vmhost | Get-scsilun - luntype disc | Export-csv c:\lun_multipath.csv

    any help would be appreciated.

    Try something like this

    $datastore = get-datastore
    
    $disks = get-cluster 'windows 01' | get-vmhost | get-scsilun -luntype disk$entry = @()$output = @()ForEach ($disk in $disks){  $entry = "" | Select DataStorename, HostName, Canonicalname, Multipathing  $entry.datastorename= $datastore | Where-Object {($_.extensiondata.info.vmfs.extent | %{$_.diskname}) -contains $disk.canonicalname}|select -expand name  $entry.HostName = $disk.VMHost.Name  $entry.canonicalname=$disk.canonicalname  $entry.multipathing=$disk.multipathpolicy  $output += $entry}$output | Export-csv c:\lun_multipath.csv
    
  • View the number of paths and the political path for each data store

    Hi all

    Seem to be stuck on this one. and all that seems to be able to find through topis and scripts for the air path setting. All I have to do is list each data store to its policy of access road and the number of path for the data store on the host computer.

    I'm gussiing it uses the get-vmhoststorage cmdlet?

    Any help much appriciated.

    Phil

    Try something like this

    Get-VMHost | %{
         $esxImpl = $_
         $_ | Get-ScsiLun | where {$_.LunType -eq "Disk"} | %{
              $_ | Select @{N="HostName";E={$esxImpl.Name}},
              @{N="Path";E={$_.CanonicalName}},
              @{N="Policy";E={$_.MultiPathPolicy}},
              @{N="Number";E={($_ | Get-ScsiLunPath).Count}}
         }
    }
    

    ____________

    Blog: LucD notes

    Twitter: lucd22

  • Stats for each data store

    I am writing a script to determine the way to read and write rates, the average number of read and write average requests read and write latency for each data store.

    I tried to do two different ways, with my numbers to end 0.

    $startdate = (get-Date-time Minute 7 - 0 - 0 second). AddDays(-1)

    $enddate = (get-Date)

    $datastores = get-datastore

    {foreach ($DS in $datastores)

    #1

    = [string] $dswriterate ([Math]: Round ((($DS.datastore.write.average |))) Measure - Object - average value). Average), 2))

    #2

    = [string] $dswriterate ([Math]: Round ((($DS.write.average |))) Measure - Object - average value). Average), 2))

    }

    I understand that Get-Stat does not work with a store of data entity.  It would be great if I could get help with that!

    That is right.

    You can use my Get-Stat2 function to retrieve available data store counters.

    See monitor the size of your vDisks

    With the QueryMetrics switch you can see which parameters are available.

    See the usage statistics for the data store

  • Machine virtual IOPS / s report, how to display the name of the data store?

    Hi guys

    I am new to the Foglight community, this is a great tool, and I learn a lot.

    Currently I am trying to create a simple table that will show me metric of my VMware environment: Virtual Machine name, Datastore IOPS and data store.

    However I can't find how to include data store name in the table, because it is not a measure of the Virtual Machine. I think I need to expand the scope of my table to include VMware Datastore, but I don't know how to do this.

    -Mark

    Check the options available it seems that it can be done with WCF (the frame behind the Foglight dashboards).  We recommend generally customers who plan to build views WCF take adequate training or our PSO people engaged in it.

    In any case I can help show a quick example of how it's done.

    Please try this on a local/test server.

    Go to Configuration > definition >

    Make sure that you are in my definition, and click the icon to add a view. then choose from the tables and trees - oriented line table

    Give a name to the view, go public and make a portlet/reportlet and apply

    Switch to the configuration tab and click the change for the lines and choose a query

    Under query, expand the VMware and scroll down

    Until you can select the query for virtual machines

    And press the set button.

    Your view should look like this

    Now you must select the columns.

    Each column has a value you can edit and there is a button + to add additional columns.

    Lets start with the name of the virtual machine - click on the button to change to your default column and choose the context.

    Click on the drop down menu to enter key and choose the current line (virtual vmware machine)

    Click on the drop down menu to access path and scroll down until you can select the name and then click on set.

    You have created a table that lists the names of all virtual machines.

    You can click on save. and then click test, choose a time and click the result. A new window will open a show the list you of virtual machines.
    From here you can continue to add additional columns, each time choosing the key entry in the current line and the path to the metric/string to display.

    For example, the name of the data store.
    I change the module

    Click the configuration tab and click the icon to add a column

    For the column value, that I chose defined context once again, the key input is the current row and for the path, I expand the node for the data store

    And scroll until I see the Proprietename

    If you save and test you will see the result

    Keep adding columns and the data you want, notice that you have arrows that allow you to control the order of the columns.

    Note that you can click Show advanced configuration properties

    This will give you the opportunity to see the properties of the extra table, such as header - giving you the opportunity to give a more meaningful name (name of the data store, the name of the virtual machine, etc.) to the column header.

    You can now go you drag and drop the table edge/report and under my eyes, you will see your new view

    Drop it in the main view

    I hope this has given you the starting point to build this table.

    As I said, I strongly recommend going through our WCF training if you plan build more custom views or hire software Dell PSO Organisation to help build you views that correspond to your need.

    Best regards

    Golan

  • 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. :-)

  • VMX file larger than the maximum size supported by the data store

    Hi all

    I seem to be getting a strange error trying to a virtual machine that is located on a snapshot VMFS5, to the data store format.

    The virtual machine (VMDK and VMX file) is installed on a thin provisioned 2 TB datastore which has the value VMFS5 formatting.  It is a data store new with no other VM on it.  I had problems in the past with the datastore block sizes (1 MB, 2 MB, 4 MB, 8 MB on VMFS3), however, I thought that VMFS5 got rid of the question, since it's all blocks of 1 MB and all files in the virtual computer are on the same data store.

    The error I get indicates that the VMX file is too large for the data store (used Im saying "unspecified file), however, if I do the independent 2 TB disk snapshots through the fine.  The virtual machine has two virtual disks, a 50 VMDK of GB and a thin 2 TB VMDK (200 GB used).  I tried fast vMotioning the VMDK and VMX to other data formatted VMFS5 stores and still get the same error.

    I'd appreciate any help and ideas.

    Thank you

    Travis

    Although the block size limit is party, maximum 2 TB file size less 512octets still exists. Since a Flash disk can grow waist put in service the basic disk more overhead for the metadata, the maximum size of virtual disk - to be able to create snapshots - is 2032 GB.

    See "calculation time system required by the snapshot files" at http://kb.vmware.com/kb/1012384

    André

  • Copying files to the data store

    I use the server ESXI 4.0 and a few Linux VM running. I would like to ask if there is a way to copy any file to any directory VM on the host main data store. If there is a way could someone please suggest some tips.

    You can use the data store browser (right-click on the icon for the data store).

    Or VMware Converter.

    Or enable SSH and SCP or FastSCP.

    André

  • best way to put up a second NETWORK adapter for the data on NAS Server store

    I want to add a second NETWORK card if I can get the best possible performance for when I move the data store of the ESXi host to the NAS (which will also have a dual NIC). What is the best way to set up the NETWORK card on the ESXi host to achieve?

    PS - I am aware that I am limited to the real network speed of 1 Gbps and conditions and I agree with that (any of the virtual machines are eager resources or production).

    SOLVED... I think so. JPM300 got on the right track, but I was still not clear on it so I googled all this involving and finally landed on an iSCSI with MPIO configuration. I ended up as a result of this article (I use a Synology DS415 +, but the steps are pretty universal): How to use iSCSI targets on VMware ESXi with Multipath i/o - SynologyWiki. The article is old but always worked perfectly for me. I checked the two paths/NIC are used simultaneously, but I did not actual test to see if I have 200 MB/s of bandwidth (I've seen 80 MB/s when the cloning of virtual machines to the new iSCSI data store using vmfstools).

    I ran into a problem where the second path is not added during the alternating market; I removed the path shown and then was able to add the second path, then the first path again.

    Hope this helps someone.

Maybe you are looking for