Sync data warehouses on hosts

Similar Questions

• Internal data warehouses DMZ hosts?

  Hi all

  I hope I'm posting in the right section, and this makes sense.

  We currently manage two groups separated, managed by vcenter.  One for all our internal servers and one for our DMZ servers.  We have our guests DMZ nic 1 and nic 2 combined for the console, vmkernel, and data warehouses.  Two of these network adapters are connected to our internal network.  We then nic 3 dmz1 and nic 4 on dmz2.  Each set of network interface cards is assigned its own vswitch.

  Data warehouses for all customers of vm on the DMZ cluster are NFS targets on our internal network of san. Each guest virtual machine is only affected 1 network card with access to it's special DMZ.

  My question is about safety.  We have been operating this way for awhile, but my networks/security guy is concerned that in some way, the virtual machine can be hacked to access all the cards that are connected to the host, or the virtual machine can be hacked and someone might potentially have access to in-house on our SAN data.

  What are the best practices for this scenario?  Should I currently have security vulnerabilities?  Assuming that this configuration is ok, can I give my guy from network to facilitate his concern for information?

  Our san is a Netapp.

  Edit: misspelling of nic4 for dmz2

  Hi SLCSam

  The way I understand how ESXi handles this (and someone please correct me if I'm wrong)

  Is that ESXi handles all the traffic of independent disk of the virtual machine.

  That's why the only VM knows how to send SCSI comarnds to her hyperviser who then rewrote the comarnds and sends it to the virtual disk files.

  This is why each VM has access to its own virtual disk and nothing else on the data store.

  So if one of the VMS is hacked, data on this virtual machine will be on display, but that's all.

  The virtual machines that are running on these clusters are all independent computing environments. And do not have access to each of the other files.

  Consider as turning several independent servers. It cannot write to other discs except via CIFS or similar.

  From what you wrote, you have nic1 and nic2 as a trunk serving admin. and drive networks

  You have 2 different DMZ then nic3 and nic2

  Nic2 therefore seems to be linked to the network disk in the DMZ.

  It is a major problem. Since then, if one of the virtual machines in the DMZ is compromised, VM said could speak to the SAN via NFS (since they are on the same layer 2 network) and this will expose the hard for other virtual machines (possibly internal) files.

  This assumes that there no VLAN involved. Because if the DMZ and the disc of the net are on different VLANS this problem does not occur.

  If it is typo and the network admin and the drive is on nic0 and nic1 or there is configuration of VLANS to separate the traffic of layer 2, then there is no problem with this Setup, even if a virtual DMZ computer is hacked.

  Concerning

  Cyclooctane

• Data warehouses, the host and Cluster list

  Hello

  I'm fairly new to PowerCLI. Is there a way to list Cluster and ESX host, datastore in that order?

  Also someone point me to resources on how to explore .net objects that can be questioned?

  Thank you

  The Export-CSV should be at the end of the script:

  & { foreach ($Cluster in (Get-Cluster)) {
      foreach ($VMHost in (Get-VMHost -Location $Cluster)) {
        $VMHost | Get-Datastore |
        Select-Object -Property @{Name="Cluster";Expression={$Cluster.Name}},
          @{Name="VMHost";Expression={$VMHost.Name}},
          @{Name="Datastore";Expression={$_.Name}}
      }
    }
  } | Export-Csv -Path DatacenterInfo2.csv -NoTypeInformation -UseCulture 
  

• Removal of host SDR data warehouses

  Hello

  I have a scenario where I want to migrate to a host and the VM between two clusters. I unfortunately had a number of DTS data warehouses attached to the host, no virtual machine is running from these storages of data on this host... I'm trying to disassemble stores but as expected get the error indicating that data warehouses are part of a cluster of EIM.

  Is it possible to no disturbance delete Host data warehouses.

  Thank you

  Steve

  So, what you want, remove some cluster DTS data warehouses and pass a host of a DRS cluster to another's is?

  Try the following steps:

  (1) remove the DTS cluster data warehouses, just move the data store outside the cluster for DTS;

  (2) move the host to the new DRS cluster target, if you have virtual machines running on it and cannot put the host in maintenance mode, you will need disconnect host, remove from the inventory and then add the host again to the new cluster.

  (3) If you wish, add data warehouses to the DTS of the new DRS cluster cluster.

• 5.5u2 ESXi host will not mount CF data warehouses

  I am the admin in a test lab, so many times I have to "make do" with what I have for the material.  I recently reassigned a R910 Dell with 64 GB memory in a 5.5u2 ESXi host.  It has some storage SAS (2.5 to) and some (CT 11) directly connected FC storage and some FC HBAs for use by VMs to send data to the tape library.

  Recently, we had a power failure, and this host does not reconnect to the CF storage when she returned to the top.  (Duty to "make do" with what I means not having is not the capabilities of UPS).  I can tell the host of HBA see it properly and sees the LUNS on RAID controllers, but refuses to mount.  I go through the add storage Wizard, and he sees that there is a store of data storage VMFS, but always refuses to mount.  I also tried to remove the redirection to the two FC HBA that have been set up for this purpose, but it made no difference.

  I have now three users unable to work because they cannot access their virtual machines on storage of this FC.  I can't even transfer them off to use the SAS storage form.

  I think it might be the cause file system damage, but I'm not sure.  Someone at - it suggestions?

  Have you ever tried to set up data warehouses from the command line (see, for example, http://kb.vmware.com/kb/1011387)?

  André

• Rename local data warehouses of ESXi host

  Hello

  How to rename local data warehouses of 5.0 ESXi hosts.

  Is it simple; Vsphere Client > right click on the local data store > rename?

  Or host must be in maintenance, or reduced, something like that?

  Thank you

  Mihir

  The ESXi host internally uses the data UUID store rather than its "friendly" name

  Example: / vmfs/volumes/3dfd1a21-63969d0d-8d9b-004328272635 /.

  That is why - as mentioned in the other responses - rename a datstore can be done at any time without affecting the functionality.

  André

• Reallocate data to the host warehouses

  Hi all

  I recently one of our hosts migrated from one Cluster/Datacenter to another in vCenter. My problem is that all data stores that have been assigned to the host of the original Datacenter Cluster / are always assigned and mounted. I already disassembled all data warehouses, but I need to be able to assign data warehouses in the new data Center/Cluster.

  Is it possible and if yes, how is. Have done some research online, but have not been able to find measures to do... maybe because I can't!

  Any information would be appreciated!

  I don't know if I understand! This I understand you want to stop the ESXi host using 'old' data warehouses', is that correct? In this case you need to detach/remove the warehouses of data/LUN from the host, storage system anyone, then rescan the storage card on the host computer and - eventually - cleaning the LUN mounted. See for example http://kb.vmware.com/kb/2004605

  André

• The number of heartbeat for the host data warehouses is 0, which is less than required: 2

  Hello

  I have trouble creating my DRS cluster + storage of DRS, I have 3 hosts esxi 5.1 for the task

  First, I created the cluster, no problem with that, so the DRS storage was created and now I can see in the Summary tab

  "The number of heartbeat for the host data warehouses is 0, which is less than required: 2".

  I search the Web and there are similar problems when people has only a single data store (the one that came with ESXi) and need to add another but in my case... vcenter detects any...

  In the views of storage I see the store of data (VMFS) but for some strange reason the cluster not

  In order to achieve data warehouses minimum (2) can I create an NFS and map it in THE 3 esxi hosts? Vcenter which consider a play config?

  Thank you

  You probably only have local data warehouses, which are not that HA would require for this feature (pulsations datastore) to work properly.

  You will need either 2 iSCSI, FC 2 or 2 NFS volumes... Or a combination of the any of them, for this feature to work. If you don't want to use this feature, you can also turn it off:

  http://www.yellow-bricks.com/2012/04/05/the-number-of-vSphere-HA-heartbeat-datastores-for-this-host-is-1-which-is-less-than-required-2/

• Host does not see some data warehouses

  I add a new host in a cluster of ESX 4.  ISCSI Storage Adapter on all hosts (old and new) detects all available Lun, 10 in total.  However, 2 of the LUNS appear not in the list of data stores in the new host.  Thus, guests see 10 stores of data.  Guests are running live virtual machines that reside on the 2 "missing" data warehouses.  The new host sees only 8 of the 10 stores of data.

  I see the text "detected can be a snapshot" and "not open device"4c19dd2e-f64dfcc4-f94f-a4badb4fcdb6"to probe: no such target on the map.

  "in/var/log/vmkernel.  What to do with these averages of message?

  4126) LVM: 7165: found device naa.60a98000572d4374433450444335486d:1 can get to be a snapshot:

  18 June-15:47:28 corpesx2 vmkernel: 0:00:03:39.125 cpu16:4126) LVM: 7172: questioned disk ID:

  18 June-15:47:28 corpesx2 vmkernel: 0:00:03:39.226 cpu16:4126) Vol3: 1488: could not open device "4c19dd2e-f64dfcc4-f94f-a4badb4fcdb6" to probe: no such target on the map

  18 June-15:47:28 corpesx2 vmkernel: 0:00:03:39.226 cpu16:4126) Vol3: 608: could not open device "4c19dd2e-f64dfcc4-f94f-a4badb4fcdb6" open volume: no such target on the map

  18 June-15:47:28 corpesx2 vmkernel: 0:00:03:39.226 cpu16:4126) SFS: 3702: pilot no. FS claimed device '4c19dd2e-f64dfcc4-f94f-a4badb4fcdb6': unsupported

  June 18 at 15:47:30 corpesx2 vmkernel: 0:00:03:40.594 cpu2:4098) NMP: nmp_CompleteCommandForPath: command 0 x 12 (0x410007114b80) for device NMP 'mpx.vmhba1:C0:T0:L0' failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 5 0 x 24 0 x 0.

  June 18 at 15:47:30 corpesx2 vmkernel: 0:00:03:40.594 cpu2:4098) ScsiDeviceIO: 747: command 0 x 12 for the device "mpx.vmhba1:C0:T0:L0" has no sense H:0 x 0 D:0 x 2 P:0 0 valid x-data: 0 x 5 0 24 x 0 x 0.

  I see the text "detected to be a snapshot" and "Could not open device.

  "4c19dd2e-f64dfcc4-f94f-a4badb4fcdb6" to probe: no such target on

  adapter

  "in/var/log/vmkernel.  What to do with these averages of message?

  It could be due to various reasons:

  1. lost on the host partition table.  Check with fdisk-lu < devname >

  2 LUNS can be detected as snapshot.  -> esxcfg-volumes - l should show snapshot volumes.

  esxcfg-volumes - M < Datastore UUID >

  This will force up the volume.

  vmkfstools v

  to refresh the storage.

  then if all goes well, you should be good to go.

  3. corruption of LUN. -> Please contact VMware support or support from the SAN vendor to fix it.

  Please consider awarding point if this information is useful.

• Share data warehouses between clustered hosts

  Hello, we had initially a cluster of ESX consisting of two guests who had shared access to different VMFS LUNS on an iSCSI SAN.

  Recently we bought an additional server, and additional storage and we have some problems to get the extra VMFS LUNs to be recognized by all hosts. The additional LUN is recognized by all hosts after a new analysis to Configuration-> storage adapters, but it seems that data warehouses can be added only for the storage of an individual host and not shared by the cluster?

  Adding the extra VMFS LUNS to a host works very well but they are not immediately recognized by the other guests and whenever you try to add data to them warehouses they insists on formatting the LUN and treating it essentially as a data store different.

  Since there is no problem sharing data between hosts warehouses in the original configuration, I wonder what setting it is necessary to enable sharing between all hosts in a cluster of data store? Thanks in advance!

  Probably, you have LUNS in different ways for each ESX Server (or the new ESX). If any information logical unit number (Lun ID, wwwn, etc.) is not the same for all ESX host tend to view this as a snapshot LUN.

  If you can't find what's going on, you can try a workaround (not too recommended but should work in your environment): go to the ESX configuration tab, click Advanced settings, and look for LVM. DisallowSnapshotLun option under LVM. Change it to 0, click OK and perform a new analysis. Repeat this for all of your guests.

  Please let us know if it works.

  Marcelo Soares

  VMWare Certified Professional 310/410

  Technical Support Engineer

  Chief Executive Officer of the Linux server

• If I put in place an openfiler VM as a data store iSCSI &amp; vmfs on two ESXi hosts, both ESXi hosts can access two data warehouses?

  If I put in place an openfiler VM as a data store iSCSI & vmfs on two ESXi hosts, both ESXi hosts can access two data warehouses?

  The reason why I ask, is that I have two hosts ESXi ESXi 4 running.  I do my backups with ghettoVCB, which I modified to create thin backups on one of the drives the.  I then wput them to the server, which causes them to become thick.  Directly targets the backup in a vmfs iSCSI on the server in the face shop.  It would save a step and the vmdk backup should remain thin.

  Thank you!

  The short answer is Yes. If you allow the ESX servers to see the LUN. This setting is configured to the Openfiler.

• displacement of the configurations of lab manager between the ESX server host computers / data warehouses

  Hello

  Is it possible to move configurations of lab manager between the ESX server host computers / data warehouses? I don't see an option in the library & gt; Clone library. Thank you!

  Recently, I used SSMove to migrate our datastore LM set a new LUN.  It's really simple to use.  This KB gives complete instructions on SSMove http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1006694&sliceId=1&docTypeID=DT_KB_1_1&dialogID=8456583&stateId=0%200%209407965

  See you soon

  Paul

• ESX host managed by VirtualCenter servers all see the same SAN LUNS / data warehouses

  Scenario of

  I have two separate deployments of VirtualCenter (in the same physical location) VCA and VCB with each deployment management 5 x ESX hosts (10 in total).

  All 10 hosts are allowed to look at the same SAN LUNS / data warehouses?

  Or I have to isolate five VCA hosts and five guests to their own SAN LUNS VCB / data warehouses?

  Box293 wrote:

  Basically, we have our direct environment and we are on the beta program for VI4.

  I want to turn off a virtual machine in the direct environment and then pull it out of the inventory.

  Then I want to go the VI4 Beta and browse the data store and add this virtual machine to inventory.

  These two environments may see the same LUNS / data warehouses.

  I did and it works however I want to make sure that it is an approved practice.

  You can do that normally without any problems. Even if the virtual machine is in a different datacenter inventory and there Powred-Off. You can map the logic unit number on the VI4 and add to the inventory of the VI4 another host.

  Recently, I did this practice to migrate from host with virtual machines in a different subnet to the host who knows the same setting SAN LUN in the other subnet.

  Best regards

  Hussain Al Sayed

• Cluster data warehouses

  I would like to create a dashboard that displays a list of all VMWare clusters and for each handset display data warehouses that are used for each of them. Looking for a way to create the dashboard without slipping each store data in the dashboard.

  1 is it possible with a query of the user interface?

  Data > VMWare > centers > (name datacenter) > cluster > (cluster name) > ESX host > (host name) > storage > data warehouses

  If you want the names and what may not be a little cleaner that I would try this, it also removes the need for the additional query keep things all neat.

  cluster = server.get ("QueryService").queryTopologyObjects("!) VMWCluster')

  output =]

  (cluster in clusters)

  {

  data warehouses = cluster.esxServers.datastores

  for (data in data warehouses store)

  {

  map = [VMWCluster:cluster.name, VMWDatastore: datastore.name]

  output. Add (Map)

  }

  }

  return output

• ESXi 4.1 upgrade to ESXi 5.5 while all virtual machines and data warehouses

  We have two servers ESXi 4.1.0 348481 (Essentials) and we need to upgrade to ESXi 5.5 for support of Windows Server R2 2012. We intend to use the interactive upgrade. We want to ensure that the virtual machine is preserved. More precisely VMFarm001 where ESXi is installed in the same data store as VMServer1. VMServer1 is our largest server and cannot be migrated to another data store easily because we are not allowed for vMotion.

  The following layout

  VMFarm001

  Dell PowerEdge R710

  Data store:

  Storage1 - 1.36 TB

  VMServer1 - MS Server 2003

  Install ESXi

  Storage2 - 1.82 TB

  VMServer2 - MS Server 2008 R2

  VMServer3 - MS Server 2008 R2

  VMFarm002

  HP ProLiant ML350 G5

  Data store:

  Storage1 - 95GB

  Install ESXi

  ISOs

  Storage2 - 1.82 TB

  VMServer4 - MS Server 2008 R2

  VMServer5 - MS Server 2008 R2

  I have a feeling I'm worried for nothing given that option during the ESXi upgrade and keep the VMFS datastore.

  Thank you

  Yes, that's correct.

  I recently finished the upgrade of lots of stand-alone hosts ESXi 4.1 (with local storage only) to 5.1 and all were successful. The same process applies to 5.5, so you shouldn't have a problem with preservation of VMFS data warehouses (and all virtual machines).