Nested ESXi 5.1 and iSCSI Shared Storage

Similar Questions

• Best practices for Exchange 2003 with VMWare ESXi 3.5 and iSCSI SAN

  Hello guys,.

  Here's the Q? We have 1 physical Exchange 2003, the HOST of 4 and 1 iSCSI SAN with LUN 3, 1 for data, 1 for VMWare and 1 for SQL, if we're going to virtualize it, I don't know where to put data Exchage and newspapers. I do not think that that is a good practice to put together the data but I do not have another SAN. So, what can I do?

  Thank you.

  We have 813 mailbox.

  I agree with cainics, start an average size and go from there.  I know it's a production mail server and you can not exactly 'play' with the settings because this requires time, but if you do the VM too big, you would have nothing left for other virtual machines.

  I would go 2 vCPU and at least 4 GB of RAM, maybe 8GB.  There must be parameters for the Exchange mailbox 813 and X users # to implement your environments in order to get an idea of the amount of RAM that will be... 4GB seems minimal to me, but 8 GB would probably be better like that.

• vMotion (without shared storage) between two hosts with different vSwitches standard s VM

  I can VM vMotion (without shared storage) between two hosts with different vSwitches standard? The vSwitches on these two hosts have different names and number of NIC, but have the same name of portgroup.

  
  Thank you.

  Yes, you can in a Storage VMotion to one Esxi to another with no shared storage...

  It is important the portgroup bears the same name... This is the reference for the VM...

• High availability without shared storage?

  
  Hi all

  We have created two new 5.1 without any network vMotion ESXi servers and no shared storage. Client asked for high availability of virtual machines. There are few things that we can look at in this situation as FT and HA, but I know that they will not work without shared storage. VSA is also another option in this case, but it is not flexible and has more limitations than benefits.

  Just check there at - there another solution we can us to provide high availability for virtual machines.

  Thanks in advance for the help.

  Greetings

  Nick

  Without storage shared (or ASB), it is difficult to provide high availability. Maybe vSphere replication is an option, if you can accept the loss of the latest changes, when it comes to the last line.

  André

• move VMs from the local shared storage

  We are running ESXi 4.1 with local storage that we did experiments with VMware. Close have 2 new purchased hosts with a SAN for the shared storage, hopefully, they will arrive at the end of January. I need to build a couple of virtual machines to take care of a few issues until our new VM environment is set up. If I create a new virtual machine on my host with local storage and that you want to move to new hosts and the shared storage the arrival of our new purchase, I guess I can do it with vMotion? Other methods too? Also, is there anything I need to worry as move us VMS local shared storage storage and a new host of ramifications?

  Thanks for helping a newbie, Tom

  You will need Enterprise or Enterprise Plus access to Storage vMotion. vMotion moves a virtual machine from one host to the host running but no storage.

• Upgrade and migration of 3.5.0upd0 to 4.0upd1 and shared storage iSCSI

  Hi people,

  I've got 2 ESX host: Alpha and beta. Two of them are connected to a cabin of iSCSI with some created shared storage drive (all VMFS3 v3.31). And both had ESX 3.5.0 update0

  I migrated all the VMS running in the Alpha host for shared storage and made host Beta to run (clones cold or simply reassign files). Then I bâtait Alpha from scratch and I installed vSphere 4.0 in it. I also created in its local storage space bit a new virtual machine with vCenter4 inside. It has worked well.

  Then I had to migrate Beta and its virtual machines, too. I first tried to manage the host with vCenter4, but it is not backward compatible.

  So I'll use the host update utility to upgrade beta I saw in a video tutorial, but my doubts are...

  • Option 1:

  Disable all virtual machines managed in host Beta.

  Configure the iSCSI client in Alpha, add storage shared cabin and try to manage the virtual machines already extinct. This reduces the time to downgrade.

  Upgrade Vmware Tools in the virtual machines (v4 to v7 type VM). Required reboots.

  Upgrade host Beta (with no SMV in there and unplug the cable of iSCSI) vSphere4.

  Connect and configure the iSCSI version beta customer.

  Manage the host with the new vCenter4 Beta.

  Configure the vMotion, DRS etc. in both hosts.

  • Option 2:

  Disable all virtual machines managed in host Beta.

  Upgrade host Beta (with no SMV in there and unplug the cable of iSCSI) vSphere4. Downgrade time increases.

  Connect and configure the iSCSI version beta customer.

  Upgrade Vmware Tools in the virtual machines (v4 to v7 type VM). Required reboots.

  Manage the host with the new vCenter4 Beta.

  Configure the vMotion, DRS etc. in both hosts.

  Which option is the best? Maybe is it possible to apply a third? What do you think?

  Thanks in advance.

  without loss of performance?

  Yes. VM with v4 works very well.

  The only problem is that you lose some new features, like the new drivers and FT.

  Note also that Standalone VMware Converter 4.x can also convert between v4 and v7 and vice versa.

  André

• ESXi 4.1 iSCSI Shared Datastore

  I'm under ESXi 4.1 with Windows Storage Server and iSCSI software targets three servers to store my data stores.  I've been using dedicated iSCSI LUNS for each ESXi server and it was working great (MPIO and RR is awesome too).  I am planning for disaster scenarios, and I wonder if there was nothing wrong with the help of a store of iSCSI data shared between servers.  I do not have vMotion, so I can't migrate directly from one host to another, but I installed a test data store and it spread over three ESXi servers.  I moved a virtual machine for the data store that is shared and I am able to add to the inventory on all three servers.  I can also start the virtual machine to any host, but its status (Powered On / Off / suspend) appears only in the home that I started in.  You see problems with this configuration?  I would like to share my stores of existing data with other hosts, so I can't add all virtual machines to the inventory on all servers.  Then I can implement a poor-mans vMotion and start the virtual machines from any host.

  Thanks in advance!

  Hello

  There is absolutely no problem sharing a LUN between several ESXs iSCSI. In fact, this is used to create a cluster.

  You do not look to have a vCenter. I don't know, what if it's a good idea to have saved several guests at the same time isolated virtual machines. I'd say recording each virtual machine to a single host only.

  If you want to move a virtual machine, stop it, remove the host inventory, enter it on the new and start it.

  In case of crash, register the VMs failed for the remaining guests and start them.

  Good luck.

  Franck

• Two servers vCenter and shared storage

  Hi all

  Is it possible to have two vCenter environment, vCenter 5.1 and 5.5 vCenter and each vcenter has two esxi hosts to vCenter 5.1 a 5.1 host esxi and vCenter 5.5 has esxi hosts.

  All four hosts to access the same shared storage (SAN).

  VCenter hosts different access to the shared storage will damage the virtual machines on storage?

  Thank you...

  Essentially access a data store from multiple hosts that are running different versions. However, in the case of these hosts are not managed by the same server vCenter Server, it is your responsibility to ensure that guests will not access the same VMs (records) system and maximum supported are not outdated storage vMotion tasks, for example simultaneous for a data store...

  Also don't forget that functions like the control of storage i/o may not work as expected.

  André

• vSphere high availability with no shared storage? And general problems with VMware partner supplier

  
  HA can function without shared storage?

  It may not by the availability of vSphere manual.  However the global VMware partner who sold me on VMware solution said that the shared storage is not required for HA.

  This is the same guy who told me that I would not need to buy Windows Server licenses because everything was included in the package (vSphere Essentials Plus).  Now, I have no Windows license, no shared storage and a customer who will not be happy that we did not include these costs in the citation for this project.

  HA can function without shared storage?

  No.... you need a storage shared for HA.

  This is the same guy who told me that I would not need to buy Windows Server licenses because everything was included in the package (vSphere Essentials Plus).  Now, I have no Windows license, no shared storage and a customer who will not be happy that we did not include these costs in the citation for this project.

  Maybe your partner speak the vCenter Server Appliance that is included on vSphere Essentials Plus and you can use this device to manage your vSphere, ESXi without need a VM of Windows (with Windows license) to install the vCenter server.

• Nested ESXi 5.5 lab for the SRM demo with iSCSI

  Hi all

  I was wondering if it is possible to install ESXi in ESXi 5.5 5.5 make recovery of the Server Tier - 1 Microsoft with Site Recovery manager?

  So level 1 server applications are: Exchange Server, SQL Server, SharePoint Server and AD DC servers with 5 x test Win 7 desktop.

  The external data store to the VMFS will take place by iSCSI NAS connected to the physical server.

  Any suggestion and input would be greatly appreciated.

  Thank you

  One thing you'll want to do is to make sure that use you VSphere switches distributed on your cluster nested to ESXi hosts so that you can use the network i/o control (NIOC). For me, I put iSCSI to high priority traffic and everything to normal priority.

  With the help of the NIOC will allow your cluster nested in order to operate more fluidly than without it.

  My SRM 5.x laboratory is fully nested - probably not supported in a production environment where supported VMware should however.

  Here's a blog post of Ather Beg on its results by using the nested NIOC and ESXi hosts - it is the reduction of the spikes that Ather blog article shows that made work nested ESXi hosts networks so much better:

  http://atherbeg.com/2014/02/04/why-enabling-NIOC-network-IO-control-in-a-home-lab-is-a-good-idea/

  Datto

• Dell VRTX + vCenter 5.5 + Shared storage is ESXi host import issue in vCenter. Help, please!

  All,

  I have two VRTX to be used for lab purposes that I am currently in configuration.

  Blades feature 4 VRTX with a shared storage infrastructure. Each blade has 5.5 installed on ESXi.

  I configured the shared on the VRTX storage, and all the blades can go very well.

  The question I'm currently facing is when you add the vCenter for managing ESXi hosts.

  Add the first host goes without a hitch. However, add any later host fail, because vCenter finds datastore attached hosts to have the same identifier.

  The error message is (see the attached screenshot): ' Datastore 'Main Shared-storage' is in conflict with a store of data that exists in the data center which has the same URL (ds: / / vmfs/volumes/xxxxx /), but is supported by different physical storage.

  Someone knows how to fix this?

  Thank you.

  Thanks for the reply.

  I think that I have found a workaround.

  First of all, this link does not address my particular issue.

  See, it's a whole new vCenter device installation and configuration. Only one of the four hosts to add host has been added.

  Still, the problem is that each ESXi host is a blade VRTX (M620), which has access to the data store created on the shared storage of VRTX.

  Basically, each host is editing the data store shared even (the only data store created on the shared storage), which works very well except for vCenter complain when you import the hosts.

  In any case, my resolution was as follows:

  -Add the first host with the attached and mounted data store

  -Remove the data store and detach the controller shared by other guests before adding in vCenter

  -Re-attach the controller shared and set up the data store via vCenter once guests have been added

  -Re-configure each host for vSphere HA if necessary

  Thank you.

• OBIEE Disaster Recovery can be configured without CARS and shared storage?

  Hi people,

  As say the topic, I'm looking for advice on disaster recovery. What I find in the docs pointing me to the high availability configuration, or maybe I'm simply not find the docs I'm looking for. And it always points to the RAC, etc. of shared storage. My database is already configured to Dataguard and I want to do things this way, with a recovery site which isn't always upwards and a part of a cluster (although it's very well as long as the CAR is not involved), I'm looking for some feedback on how people do things. I have 11.1 now, but will be upgrading to 12.2 soon.  Just a straight stitch to the documentation would be useful if I'm missing just that.

  Thank you

  -Adam

  Since you have already configured Dataguard and in a DR situation, you will be switching/switch on your course in standby mode and it will active db. All this is fine. You can do the same with instances of weblogic OBIEE. You can clone your binaries installed using tools provided by Oracle cloning, or build binaries from weblogic with the accurate determination of drive on your Dr. use the pack of weblogic server and then unzip tool to archive your entire weblogic domain and it Unarchive in your prepared DR server.

  Now, you have to just challenge the hostname (s) of your domain to point to your database JDBC data sources and weblogic.

  To facilitate the task, you can change the host name used by weblogic to host alias that can be remapped in DNS during DR. Similarly, you can change the JDBC connection string so that it can automatically select the active database as long as you use a database instead of a SID service name in the connection string.

  You will need to regularly make a pack on your weblogic domain in order to maintain an up-to-date backup of your domain proximity. Similarly, if you have reports that are stored on the file system, they must also be backed up regularly so that they can be restored.

• ESXi host has not recognized the VM in the shared storage

  Hello

  We have installed ESXi host on our Blade Server and add the storage as a NFS storage device. There are in the NFS storage machine, Machine virtual files were there. But the ESXi host doesn't recognize any of the Virtual Machines.

  Could someone help me how to configure the file Vmdk to access via the ESxi host with out any resettlement.

  Kind regards

  Raghavendrachari

  If you go down each of the RHEl and VM1 files you should be able to add the vmx files to inventory

• VMWARE HA and shared storage

  Dear friends

  I have two questions regarding vmware HA.

  (1) vmware HA can be used with NFS (for example a pc linux with nfs shares)

  (2) if I understand vmware HA ensures restoration between different hosts ESX share the same files vmdk via a shared iSCSI or SAN or NAS storage. What happens if the shared storage goes down? Can someone tell me how we can provide HA for the shared storage?

  Thank you

  (1) Yes

  2 HA) cannot do anything to help you with the failure of your shared storage space.  You will need to protect on the backend storage through some type of redundancy/replication.

  -

• Shared storage problem

  I did a few tests using Virtual PC on my PC and I was able to lay 2 ESXi gets and a shared stoarage a FreeNas or a virtual NAS Nas4Free-based.

  I was able to use iSCSI or NFS data warehouses.

  Now I have the possibility to use a HP ML350 host with a lot of RAM running ESXi 5.5 U2 free version.

  I can easily create my invited ESXi virtual desktops, but I can't make them use a shared, nor based on iSCSI or NFS storage.

  I tried to use 2 vSwitches but (virtual) invited ESXi cannot access NFS shared storage or iSCSI.

  My NAS (virtual) seeks to work end e I can access either iSCSI and NFS shares from a Windows virtual machine.

  Is there a directive to set up virtual hosts ESXi and/or the vSwitch for shared storage?

  I would use a dedicated vSwitch not connected to a physical NETWORK adapter to avoid iSCSI or NFS traffic in my main LAN.

  Should I?

  Concerning

  Marius

  The vSwitches to which the ESXi invited are attached must allow the promiscuous mode and forged passes.  See http://www.virtuallyghetto.com/2013/11/why-is-promiscuous-mode-forged.html.