Upgrade of a single host with Shared Storage

Similar Questions

• Using the odd drive with shared storage

  We have deployed a 15-node cluster with shared storage.  When we issue a df - h, we see the root filesystem and / mnt mounted file systems.

  We also see the file of each of the other systems the datanodes on the local storage of the each other.  For example...

  / mnt/SCSI-123abc is mounted on the server server01

  / mnt/SCSI-456def is mounted on server02

  Under/mnt on the server server01, we also see/mnt/scsi-456def under the root file system, not mounted as its own file system.

  Under/mnt on server02, we also see/mnt/scsi-123abc under the root file system, not mounted as its own file system.

  Is this a problem of storage configuration, or is this something that the BDE has decided when it deployed?

  Thank you

  Steve

  BTW, you can add your script hack or the scripts that I have provided in the /opt/serengeti/sbin/format-disk.py file in the node template, and then after that the empty cluster is created, the mount point/mnt/bigdata1... are there the/mnt/bigdataN.

• Move the virtual machine from one host to another with shared storage

  Hello

  I have a question on how to move a virtual machine from one ESX 4 host to a host ESXi 5.  These hosts have access to the same shared storage but the ESX 4 host is outside the network and host ESXi 5 is inside the network so vMotion is not an option.  They are in different groups.  I know that there must be an easy way to move this virtual machine, but for the life of me, I can't find it.  I guess I have remove the virtual machine from the external cluster but how to make the virtual machine in the internal cluster?

  Thanks in advance...

  If both host access to the data store even where VM's store, just stop the virtual machine, remove inventory on ESXi 4, go to ESXi 5 vSphere vSphere, browse the data store where the VM is stored, do a right-click on the .vmx file and add to the inventory.

• Update / fixes ESXi single host with VCSA running on it.

  We have just updated since the free version of ESXi 5 by ordering the Kit of Essentials. In the process, of course, we were able to deploy vCenter Update Manager (which has been the main motivation, like patching manually the free version seemed to be quite a pain). We have a Windows host that has installed the Update Manager, and we have a VCSA running on the single instance of ESXi, we deployed to date. We were able to install the plugin on the viClient and scan the ESXi host for patches with success (a need a good number). But, we're stuck trying to install the patches... us when trying to restore the host, we get: "the operation is not supported on the selected inventory items. Check events for the objects selected for the operation.

  The host says:

  The 10.0.1.80 host has a virtual VMware vCenter machine

  Device server with VMware vSphere update

  Manager or VMware vCenter Server installed. The

  Virtual MACHINE needs to be moved to another host for the

  consolidation to proceed.

  error

  28/08/2014-16:21:32

  Clean up the entity

  10.0.1.80

  root

  Looking at this logic, for the host switch to maintenance mode, the VCSA should have been suspended (apparently, actually moved), which would avoid in turn patches / updates to the deployment. Am I correct in thinking, that we have a second host and networked storage? Made a Kit Essentials / license provide for the possibility of vMotion from one host to another? It wasn't really clear... Yes, the web site says "vMotion" is included in most Essentials, but find it me hard to imagine any point to a facility in ESXi stream without the ability to vMotion between one system and another guest...

  Welcome to the community,

  And since you have only an ESXi host and your vCSA is running on this host, you cannot patch this host with Update Manager for reason that already know you: the host should be the maintenance mode.

  Add about another host, with Kit Essentials without vMotion functionality, you can try using a data store of shared storage between two hosts, stop the vCSA on first host and switch the vCSA on the second host... and finally the first host patch.

• View Load Balancing Hosts with local storage

  Hello

  After the use of VMWare for server virtualization, it is time to move to the next step.

  We are in the middle of a display driver 5 :-)

  At the moment I have 2 host vmware (esxi 5) with storage connected to a San.

  My "master VM" is in the SAN and connected to two hosts.

  A pool is created and data warehouses them are selected for the pool.

  The replicas are created on two local data stores when I set up the pool.

  At the time, my drivers 10 users working on a related Clone which is located on the local storage.

  The strange thing is that all users are running on a single host.

  East on the host with the most free space.

  When I remove the data store, the virtual machine is created on the other host.

  After adding it, are all the vm on the store with the largest disks again.

  How can I configure display to use the two hosts?

  This is a normal behavior of View Composer to put desktops on the storage the largest space available. You can change this behavior by adjusting storage approval settings. Take a look at this blogpost:

  http://www.simonlong.co.uk/blog/2011/02/09/VMware-view-4-5-rebalance/

• Share resources between the 2 ESX 4.0 hosts without shared storage

  Hello guys,.

  I have the following question, I want to clarify.

  Imagine that we have 2 host ESX 4.0 with more functional license acquired (HA, VMotion, DRS, etc.)

  The two physical servers are identical. Don t have access to any kind of shared storage (San, no iSCSI, NAS no, etc.)

  In host #1 I installed all the virtual machines using local storage.

  Is it posible to use the host #2 resources (memory and CPU) to give more power to accommodate #1.

  My doubt is if it is posible to have a VM installed in local HD in home #1 and using RAM or / and CPU host # 2.

  Just do a cluster between the two hosts to empower the host #1 resources (not use DRS or functions of Vmotion)

  Let me know if I explained in a good way or not.

  Hope someone can clarify this for me.

  Thanks in advance

  It is not possible, even if you have the shared storage.

  There is no possibility that allows you access to CPU and memory of 2 resources different hosts.

  See you soon,.

  ~ Jean

  ~ Don't forget to points, if you found the useful answer

• Two hosts to shared storage? MSA2012sa MD3000

  Hello

  I work for a small company with a two ESX 4.0 host custer. I currently have a StoreVault (NetApp) S500 with 12 x 500 GB sata discs. It is average in motor for the type of virtual machines that we are running and the performance my end users need. In these difficult economic times we can afford a nice Beefy fibre channel SAS SAN. Since there are only two ESX hosts that need access to this storage, I was hoping I could get a MD3000 Dell, HP MSA2012sa, or similar. Can these devices be setup in order to have the two connectivity SAS for the same LUNS for vmotions and DRS ESX host? These tables attached direct seems like the best way to get a shared storage (2 knots) and / 3 GB/s sas and 15K. Please, share your ideas.

  I am part of the QA of VMware engineer and I was tested with the DELL MD3000 SAS and HP MSA2012sa with ESX4.0 storage array and all of them are listed in the HCL.

  ESX4.0 support VMotion, Storage VMotion, DRS and HA in the SAS of DELL MD3000, MSA2012sa HP and IBM DS3200 storage Bay.

  You need to have supported hardware to install FT.

  -Laurent.

• ESX host with local storage recommended for the host partition table?

  Hi all

  I know that the best practical partition table should look like this:

  Mount Point	Partition	Size	Description
  		/ dev/sda (primary)
  / Boot	ext3	250 MB	Change of extra space for upgrades
  N/A	SWAP	1 600 MB	Change the maximum size of Exchange service console
  /	ext3	5120 MB	Change of extra space in the root
  		/ dev/sda (Extended)
  / var	ext3	4096 MB	Create partition to avoid an overflow of root with log files
  / tmp	ext3	1024 MB	Create partition to avoid an overflow of root with temporary files
  / opt	ext3	2048 MB	Create partition to avoid overfilling root with the log files of VMware HA
  / Home	ext3	1024 MB	Create partition to avoid an overflow of root with agent / user files
  	vmkcore	100 MB	Pre-configured

  However with a system with local storage would you set it up the same way, and whatever it is must be amended to change to get ESX to write log files to the different partitions?  I would like to configure it for future expansion for when the enterprise package is configured.

  Yes, I would set up the same way with an ESX with local storage server and nothing needs to be changed for the vmekernel right at the partition/var - unless of course you want to write to a log server that you need to change a configuration file to point to the server logs.  If you talk to the ESX Enterprise license you willnot have to change partiition table-

  Also on something else if you don't have a SAN/NAS storage you will also need to create a VMFS partition on the local data store to host your virtual machines

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Configure a cluster of vsphere with 2 host with internal storage shared via HP LeftHand - doubts

  Hi, I'm trying to create a two-node esxi cluster. These nodes will share their internal storage with HP Lefthand Appliance (HP StoreVirtual VSA). I need the first steps to create the cluster, or better, the macro blocks, IE:

  -install esxi on each node
  -install Virtual Center and create the vmware cluster

  -Deploy the VM VSA...

  I have a lot of doubts because of the reason why I can't have (installation of the HP guide said) virtual machines on other than the VM VSA itself VSA data store. How can I configure things? Creating first two warehouses of data, deploy VCenter on a data store, create the cluster, deploy VSA VM on the other data store...

  Can you help me please?

  DL380G5 host as the location for the ODM is ok, but you may need to upgrade the host in any case since v12 FOM requires ESXi 5.0 or newer.

  ... what happens if the update fails and the hypervisor does not start more?

  I know we can't answer a question with a question. Anyway, how do save you virtual machines on this host now?

  It is true that the VSA VM cannot be migrated, but I can migrate the VCenter to a to another data store when I will have created the DATA of VSA data store (one that the hypervisor consider as an iSCSI target), I'm good?

  I'm sure that it is correct. Unless I'm missing something, vCenter Server is just another virtual machine running on the cluster VSA VSA does not require vCenter Server to run.

  André

• 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é

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

• Upgrading to ESX 4.0 host autonomous with local storage to ESXi 4.1 on a USB

  We have a stand-alone host with a single raid array that is local to the server at a remote site from ours.  The question of what I've done research, you need to reformat the raid array if you install ESXi 4.1 on this host.  Since there is no shared storage, the only option would be to copy the data from one server to another, or maybe install ESXi on a USB key.

  It seems to work fairly well in a test environment.  Are there warnings that I may have missed when I take a system that can be started locally on ESX 4.0 and change it to boot from a USB key with ESXi 4.1?  In my test environment, I know that you can not install ESXi 4.1 on a USB key, if this system had ESXi 4.1 installed on the local disk.  He ended up giving me the GROUP when he discovered another ESXi installation.

  Thoughts?

  Matt

  As you may have noticed a new ESXi installation will wipe away the installation partition.  If you have just a single Bay, then you'll want to go to the root of the USB.  If the data store was on a LUN or a separate table, then you'd be OK to install ESXi on ESX.  As long as the boot order is set correctly, you'll be fine.

  In my test environment, I know that you can not install ESXi 4.1 on a USB key, if this system had ESXi 4.1 installed on the local disk. He ended up giving

  me the GROUP when he discovered another ESXi installation.

  What kind of system did you use for testing?

  Dave

  VMware communities user moderator

  Now available - vSphere Quick Start Guide

  You have a system or a PCI with VMDirectPath?  Submit your specifications to Officieux VMDirectPath HCL.

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

• Migrate virtual machines from HP G7(single host) for HP G8 (Cluster) without shared storage

  Hello

  I have 2 esxi host (hp dl 380 G8) and put them in a cluster and other host esxi (dl 380 g7) and I have no shared storage and use local disks just now I must spend my VM G7 server a cluster of the G8 but I want to know I can join my cluster g8 g7 and migrate web vmware machines without any downtime?

  I want to know can migrate without downtime with localdisk? I have no shared storage

  Best regards

  BAbak

  can I join g7 to my cluster of the g8

  You can mix into clusters hosts all desired, even Intel and AMD at least that you enable EVC on the cluster (of course, HA or DRS require shared storage compatible/CPU). However, you need not to have even just cluster hosts to migrate virtual machines through vMotion between them.

  migrate web vmware machines without any downtime?

  Don't know what this "web vmware' but yes, because ESXi 5.1, you can use"enhanced vMotion"to live migrate virtual machines without service interruption from one host to another, even without shared storage:

  Migration with vMotion in environments without shared storage

  The usual vMotion requirements apply. Also you can only live migrate virtual machines from the old host to the new hosts because of different generations of CPU (and back as long as you don't have bike powered virtual machines on new hosts).

• Cannot use local shared with replica storage of SSD

  So I had my environment from view for a while and everything works fine, but I have a question on how discovers works with the local replica SSD disks.  I read in the forums and in the document architecture and design if you use a local SSD to store your replicas (that will give you a performance gain), you cannot have your host in a cluster, thus renouncing HA and all the features that come with in a cluster of ESXi.

  However, I meet me a further restriction that I couldn't find any mention of in the forums or documentation, namely that you cannot store the clones in a shared storage if you have a replica on the local disk.  Whenever I got to the stage of commissioning and selected a FC LUN shared as the storage for the linked clones container, the pool would tell me that there not available and there no validation.  However, if I create a LUN that ONLY the host which I use to store the replica on the SSD has access to, then the commissioning is fine.  So my question is this: Why can't place clones related on the shared with a local replica disk storage?  I understand that I will not be able to use the features of the HA, but I would rather just a LUN shared for all clones related to the ease of administration (instead of having to create one for each host).  If someone could tell me what I'm doing wrong or explain to me why this is the case, it would be great.

  OK, I found the documentation indicating that "If clone related data warehouses are shared, the replica data store must be shared. Replicas can reside on a store of local data only if you configure clones all connected on warehouses of local data on the same ESX host. "Who is on page 14 of the document storage considerations see here: http://www.vmware.com/files/pdf/view_storage_considerations.pdf. However, it does not explain why this is, he said only that it is so.

  So as a result of this requirement, it is logical that linked clones on a present at a single ESXi host LUN would support, but without link clones on a LUN present at multiple ESXi hosts.

  Dave