Migrate ESX hosts to new SAN array

Hello

Our company has bought a new SAN storage array and we are looking for an overview on the migration of our ESX SAN infrastructure existing to the new array with minimal downtime. Currently, we use EMX DMX and will migrate to EMC Clariion.

I thought that we could present the new table to the ESX host and then use SVMotion to move on the virtual machine, and then once we are full and everything is well, remove the old array. I don't know what the best solution practice to it would be...?

Currently, we are on ESX 3.5 U2 in all areas.

This sounds like a good idea? Any help is very appreciated!

Thank you!

-Mike

It is exactly what you need to do.

1. present LUNS of size equal to or greater than those on the existing table.

2 format LUNS as VMFS data new warehouses.

3 Svmotion VMs of new data warehouses.

4. wait for a whille and ensure that everything is fine and then delete the old warehouses of data.

Tags: VMware

Similar Questions

  • PowerCLI again migrate ESX host and new data store

    I have 250 VMs that need to migrate to a new cluster and newdatastores, however, I don't see where I can do both in the apowercli script. Does anyone have any suggestions?

    I am really new to powercli and I am usingpowercli6.

    Do you get any error messages?

  • New ESX host cannot see SAN fiber - Clariion

    Hello

    I spent about two hours, passing through communities and have tried various things without success... basically, I have a new ESX host that I've built, configured, and networked, but I can't see our existing SAN.

    The SAN is a Clariion CX3 - 10 c and it hosts all of our existing VMs (we currently have two hosts attached to the SAN)

    I have installed the CLI and Navisphere agent on the new host

    I have started to host and that you have ENABLED the two adapters Emulex HBA (host contains two HBAs installed) because they showed as disabled by default BIOS

    I have one of the HBAs connected to the fibre switch

    On the fibre switch, I have a flickering green light where I plugged the fiber cable, which makes me think, it is connected OK

    On the HBA, I have a green light and an orange light blink, which still makes me think the wiring is correct

    BUT I do not see the front Navisphere host, and the host cannot see all storage even after re-reading.

    Any ideas what to try next? I suspect that it is perhaps something to do with zoning - I must say the Emulex HBA how to find storage processors? If so, how can I go about it? From the BIOS by restarting the host and pressing ALT - E?

    Any help or advice appreciated...

    Assuming that hard zoning this site should provide you with some

    Help

    http://TechNotes.twosmallcoins.com/?p=16

    Also once the switch is zoned if the host is not listed on

    the Clariion Navisphere agent system has a config file that needs to be updated

    with the IP addresses of the SPs.

    You can also manually enter the host if necessary, but your

    probably zoning question.

  • Migration from old to new SAN SAN

    Hello. I was hoping someone could point me to a white paper or a procedure for Dell because I don't think that this is a rare situation.

    I have a PS6500 I need moved to a new PS6210. I use VMware with three hosts and I need the whole kit and the shebang to the new San. All procedures out there so I'm not reconstruct the pieces of suggestions of online?

    Thanks in advance,

    Hello

    There is no procedure formal whitepaper that it pulled out of the basic features of the PS Series table.  The ability to add/remove members to a live band.

    The 6500 will need to be updated at least 7.1.x firmware before trying to add in the 6210.  The 6210 is likely to 8.x firmware.  If so, you must upgrade the 6500 to 8.1.14.

    You'll want to create a temporary pool for the 6210.  I.e. "maint".   When you add in the 6210, it will be in the default pool.  Before you set the RAID policy, move the 6210 in the pool "maint".  When you select the Member, it invites you to configure the RAID, select No.  The menu in the middle of the screen will be "move Member".   Select, then you will see the pool "maint" you have created.  What to choose.  Now the 6210 is assigned to this pool.   Configure the other network interface, and then select the desired Member RAID policy.  Leave the RAID to finish the construction.   If you have not already set it to update the 6210 at least 8.1.14 now would be a good time to do so.  In addition, the latest version of the software is 9.0.

    If at this point you have two choices.  You can create volumes on the 6210 Member, format it with VMFS and use storage vMotion to migrate the virtual machines.   Alternatively, you can merge two pools together.  In the graphical interface under "Storage Pools", there is an option "merge pools".   Select the pool "maint" and when you select Merge pools, it will show the available pools to move it to.    The move will appear in the moment.  However, in the background, the space is balanced on to the 6210.  According to the amount of space in use, to move it could take some time.

    So if you have taken the first choice, once you have all the data passing above, you can remove this member.  Select the 6500, right of the mouse and select 'Remove member' ' this table will be reset to the factory and removed from the group settings.

    If you have merged the pools, once the space is balanced, you will create a new pool.  'temp' for example.  The select the 6500, right 'move the Member' of the mouse and select the pool "temp".   This will push the remaining data on 6500 the 6210.   Once the move is completed, use the option 'Remove member' to remove.

    Question: The 6210 is able 10GbE, you're going to be running to 10GbE?

    Kind regards

    Don

  • Migrate ESX hosts between vCenters

    Hello

    I was instructed to spend our ESX 3.5 hosts the old VirtualCenter 2.5 to a fresh vCenter 4.0.

    The problem lies in the migration of the ESX hosts without interruption of service. If I had the ability to paralyse an ESX or VMotion their stop, I would have done this, but the old VC2.5 is corrupted and does not allow this.

    I got 2 new boxes, a new box that will become the new VC4.0 and a new ESX 4.0 host.

    My plan is to migrate the hosts of the old VC2.5 to the new VC4.0 to disconnect the current vcenter and then simply adding them in the new VC4.0. After Google'ing a bit, I found that this is however not the easiest of tasks when I can not close the guests during the transition.

    Is it possible, such as disconnection, uninstall or remove users VC2.5 then import the ESX in the new VC4.0?

    Once the ESX is completed in vCenter 4.0, there VMotion and all the fancy stuff that are broken in our current configuration of VC2.5.

    When guests are over, they will also be cleaned and installation from scratch with ESX 4.0 Update 1 + firmware upgrades, which they have unfortunately not been considered with for a long time.

    Thanks in advance for answers!

    a simple disconnect/remove existing vCenter.  Then add the host to the new.  When you add the host, it will upgrade the agent of vpx and reconfigure for HA.

  • Migrate the ASM to new SAN drives

    Expert,

    We intend to migrate the ASM/OCR/VD disks in new storage EMC VMAX.

    Step 1: Migration OCR/VD to new disks online - Metalinl is a good document.

    Step 2: Migration of the new SAN disks ASM disks.

    Please, help us to migrate with minimal downtime. Good if we have the chance to migrate without interruption of service.
    Please provide hierarchical process / documents.

    AIX 5.3
    Oracle 10.2.0.4 (node 2 CARS)
    ASM - total 77 records
    Size of the DB - 1.6 to

    Help needed here.

    Kind regards
    Riaz

    Yes... This can be done online...

    Please follow MOS note:

    Exact to migrate ASM steps starts to SAN another without service interruption. * [837308.1 ID] *.

    Concerning
    Rajesh

  • Migration of servers to new host and SAN

    Hello

    Current configuration:

    2 x ESXi servers, local storage, share nothing.  License of VMWare Essentials

    New configuration:

    3 x SAN Eqllogic, ESXi servers. Essential Plus VMWare license

    I would like to make the transition to the new configuration with minimal downtime, we have invited a few large (> 1 TB) on one of the servers and I don't want them to be disconnected for more than a few minutes, then a migration cold is out of the question.

    I had a thought that I could put the license key more on the old servers and 1 new servers, set the new SAN on the old servers, use VMWare replication to replicate virtual machines among the old servers to the new server/storage, and then perform a recovery.

    I would then remove this old Vsphere server, add a new server and transfer the license, then perform the same task on the old server to 2nd.

    Once it is finished I remove the old server 2, add the new 3rd server, and move the license.

    Can someone tell me if this is possible, or suggest alternatives?

    Thank you

    Dean.

    Hi Dean,

    Replication (replication vSphere) VMware will be requires downtime when you are recovering from the old host to new host.

    How much time can you afford for downtime?

    The recovery process will turn off the source/protected VM on the current host (VM function how long it would normally take to perform a shutdown comments) and destination/recovery VM will be powered on to a new host (again, depends on VM normally, how long it would take for the operating system and services until then a normal diet on the process).

    vSphere replication requires vSphere Web Client and other requirements, as described here: 5.5 - replication requirements vSphere vSphere Documentation Centre

    You have a vCenter Server?
    What version of ESXi (and vCenter) do you use?

    If you don't have a vCenter Server yet, I suggest you install a vCenter server and add all the current 2 ESXi hosts + 1 new ESXi host.

    From there, you'll have an ESXi 3 host, then you can migrate current ESXi host for new.

    If you are using vSphere 5.1 + you can vMotion, even if the host do not have access to the same storage see this: library of vSphere 5.5 - Migration with vMotion in environments without storage shared

    Its quite simple, if you are using vSphere 5.1 +.

    -Make sure you have vcenter Server 5.1 + with vSphere Web Client

    -Add current hosts + 1 new hosts

    -Make sure the vMotion without requirement for shared storage are filled with VSphere 5.5 Documentation Center - requirements and restrictions for vMotion without Shared Storage

    -Perform vMotion without process Shared Storage of current host to the new host + local storage to SAN EqualLogic - you can start with small VM and VM less critical first if you are not sure.

    -Once all virtual machines have been migrated to the new host + EqualLogic SAN, you can do a maintenance on the current host mode, and then delete the vCenter Server (vSphere licenses will be retrieved)

    -Add the 2 remaining new hosts.

    If you are using vSphere 5.1 prior, you must present the SAN EqualLogic again 1 new host and current 2 hosts.

    Once current hosts can see the EqualLogic SAN, make a Storage vMotion (live migration records) local storage to the EqualLogic.

    For first migration vSphere 5.1, there are 2 ways that I can think of:

    1. with vMotion - without interruption

    There are certain requirements of configuration for vMotion work: Documentation Centre of vSphere 5.5 - Migration with vMotion

    Make sure your classes and new hosts are run in the same processor / EVC mode or matrix, you can check it out here: http://www.vmware.com/resources/compatibility/search.php?deviceCategory=cpu

    If they are on different EVC Mode, you can turn on the CEV on new hosts.

    The steps are:

    S ' ensure that virtual machines are in EqualLogic (you can use Storage vMotion)

    -Perform a vMotion from the current host to new host.

    -Once all virtual machines have been migrated, you can safely do a maintenance on the current host mode and remove the vCenter Server

    -Add the remaining 2 new hosts the vCenter.

    2. without vMotion - requires the interruptions of service commissioning

    It's cold migration but without migration of storage, must be less compared to downtime directly cold immigration to localdisk of shared storage.

    The steps are:

    S ' ensure that virtual machines are in EqualLogic (you can use Storage vMotion)

    -Turn off the virtual machines in the current hosts and migrate (cold) of the host-to-host former New (you can also drag the virtual computer and drop it to the new host).

    -Once all virtual machines have been migrated, you can safely do a maintenance on the current host mode and remove the vCenter Server

    -Add the remaining 2 new hosts the vCenter.

  • Migrate the host ESX to vSphere 4.0 Server 4.1

    Hi all

    I have 2 vSphere environments. A server vSphere 4.0, and 3 ESX 4.0 host. Another with vSphere 4.1 server with 3 hosts ESXi 4.1. I want to migrate ESX 4.0 mailboxes to the new server for vSphere 4.1. Assuming that I have licenses installed locally on the boxes, and I squared away vSphere licensing, what would be the best way to migrate the host?

    I would simply ' right click-> delete ', then 'right click-> add a host' on the Server 4.1?

    Thanks in advance.

    the best way to do so is in vCenter 1, right-click and disconnect the host and then delete host.  In vCenter2, "add host".  This will move the hosts and their guests to the new instance without interruption.

  • 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

  • Migration of data from records on Win2K8 cluster to a new SAN SAN

    I hope that someone here might have a clear answer to my question. We are currently working on a project to migrate all the data of a former SAN that stores our info Win2K8 Cluster (Quorum, MSDTC and SQL DBs) to a new SAN. I know that databases SQL, the plan is to simply detach the DBs with in SQL, stop SQL services, move the DBs from the old drive to the new location and then reconnect, we intend to reuse the drive letter, so that there will be real problems.

    What I'm having a hard time trying to figure out, is how to move successfully the readers of the page Web MSDTC and Quorum, would I simply create a new set and removing the current Quorum and MSDTC leads or is there a way to move the data on the page Web MSDTC and the Quorum of the current location reuse the old drive letters and stored it on the new San without having to change any configuration or break the cluster.

    All clearification would be much help.

    Thank you.

    Hi Vince,.

    This problem would be better suited to the TechNet community.

    Please visit the link below to find a community that will provide the support you want.

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

    Thank you.

  • Best way to migrate virtual machines to new ESXi hosts with a different configuration of networking.

    We currently have a cluster of 6 Dell machines that move VM 120 or so on ESXi 5.5. Networking consists of a dVswitch with 6 uplinks that map to 6 x 1gig physical NETWORK adapters on each host ESXi... These are grouped into 3 trunks / gal, so we have 2 GB by SHIFTING of the bandwidth and failover. The LAGS are configured as follows:

    LAG1

    Traffic to our (NFS) shared data store and management of ESXi. (vmk0)

    LAG2

    Access to the network of the VM - groups of different ports on different VLANS

    LAG3

    vMotion (vmk1)

    We just bought 6 new Dell machines that have connections fiber 2 x 10gig each. The idea is to bring together in a 20Ggig LAG by machine that will handle all of the traffic, so traffic NFS data store, network traffic from the VM, vMotion and traffic management ESXi.


    What is the best way to migrate the virtual machine in the cluster existing to the new machines? Many of the virtual machine are essential, so we cannot stop time.


    Can I create the new DELAY on existing dVswitch and put it as an auxiliary card? I'll be able to do it for all 3 of the above both above LAGS?


    Thanks for the info Alistar, it's almost here. The bit that was me stumping was that after establishing a new dVswitch I received messages that the new dvSwitch was not reachable on the old host, when I tried to migrate the virtual computer.

    The solution (with the permission of VMware Support) was that I need to add the two dVswitches to one of the old hosts, then assign a physical alternative on this host uplink to a temporary 3 uplink on the new dVswitch. I then tag all the relevant VLAN that uplink.

    This way I can first migrate the virtual machine to the new dVswitch networking so I can move the computer to the new cluster.

    Obviously I can only migrate from old to new cluster with a single host. each virtual machine must be a double for the host with 2 switches, and then to the new cluster. I also had to have the two dVswitches to the same version.

    Fortunately, I had a physical rising spare on the hosts of the old, otherwise I would have had to break one of the trunks and re-use of one of these uplinks.

    Oh and be aware, impossible to use the same names for groups of ports 2 DV switches, they must be unique!

    Nick

  • migrate virtual machines to new host

    How can I migrate easily all my virtual machines (12) on my current 5.1 ESXi host to new host ESXi 5.1... ?

    [1] put the former host's hard drive in the new host and perform an upgrade from 5.1 ESXi installation disk (the hard drives of the two hosts are the same)?

    [2] put HDD in the new host as a secondary, pop disk in the ESXi 5.1 installation disc to install ESXi 5.1 on the new host's hard drive, but migrate/import virtual machines from the data on the secondary drive (drive old host) store? the host of the former

    [3] pop in the ESXi 5.1 installation disc to install ESXi 5.1 on the new host's hard drive. Once completed, put the hard drive of the host of the former in the new host as a secondary drive and copy/import virtual machines from the data store on the secondary drive (drive old host) using VMware vSphere Client?

    [4] install ESXi 5.1 on the new host, he networked with the old host and use VMware vCenter Converter to import virtual machines from the old host?

    What might work is engaging the larger disk of 'old' to a SATA port once you have installed the disk again, ESXi. Attaching to a port USB probably won't work because VMFS volumes are not supported on USB devices.

    André

  • Mobile to a new server vCenter ESX host

    Hello.

    For several reasons (including the old server vCenter 2003 x 86) I would like to move our ESX host to a new server vCenter (version 4.1 under Windows 2008 R2). Our ESX environment using HA/DRS and resource pools.

    Is it possible to move the hosts to the new server without VM downtime?

    I think disabling HA/DRS and then disconnect the old vCenter servers, then adding them to the new. That would be possible, or is there a better way?

    And second, that things are lost that kind of operation? Data of performance and resources with Betclic, another?

    / Christian

    Hey there,

    The procedure is very simple:

    -Disable HA host monitoring

    -Disconnect the old vCenter host

    -Remove old vCenter host

    -Add the host to the new vCenter Server

    -You will be weather you are prompted to add all of the resources of the host with Betclic under a live of... the list resources or put all your VMS in pool root of the pole. Select them grafted in... so you can keep your resource pools. You can move the autour pools in the hierarchy on the new vCenter.

    -After you have moved all of your hosts, you can activate HA host followed once again and check that the DRS has the settings you want.

    You lose well obviously all performance data, but you can bring your pools of resources for the new vCenter.

  • Open a virtual machine in a san on 2 different esx hosts

    Hi, I have a Vsphere essentials, 2 Esx hosts and an Iscsi san, I need to connect the virtual machine in the two esx hosts (I know I don't have FT and HA), in order to launch the virtual machine never the first Esx and if first host, does not have the virtual machine on the second esx.

    I tryied to connect the virtual machine to the second host, but the Vsphere client tell me that's not possible, because the virtual machine is already present at the first ESX.

    There is a way to establish this setting?

    For some it may depend on your application, if you can run multiple instances of the same application? If it is a web application? It stores its data in files on the server, or it stores it in a database locally? or remote database?

    -VM on a local storage of the army, would not really recommended if you need so that it starts the VMS on host b quickly.

    -If the two hosts have access to permits it storage even say and what the application can really be run only once.  He could only save it to HostA and if it fails at some point that it will be released the lock, have it on the virtual machine and you will be able to manually register the virtual machine to host b and start the virtual machine.  However, you will not be able to really get ahead.

    -HA out of here, as if a host or power failure shuts on HostA, HostB will feed into the virtual machine down automatically

    -FT - here in the spectrum creates a VM ghost on the secondary host in levels (what happends on HostA happens on host b)

    -Another option to the other end of things has implemented Microsoft MSCS Clustering with iSCSI support I think.  You can run VMS with iSCSI to your San and clustered like this application.  Just note that with iscsi client it uses some CPU to create iscsi packets.

    -Web Cluster, Cluster database.    It doesn't matter if one of the nodes of web servers or the database nodes go down really that the user will be redirected to another node in the cluster so really no need for HA/FT.

    Of course, with some of the here above are expenses and pro / con of and there's a few ways to increase availability.

  • Mobile vcenter server in existing farm to new esx host

    Scenario of

    2 ESX host running version 3.

    1 ESX host running version 4

    New vm on vcenter server machine within the current cluster

    Existing vcenter server is a physical machine.

    How can I move my existing to my new host ESX cluster virtual vcenter server.

    In your original description I though you said "Existing vcenter server is physical machine" - so you say your vCenter server is already virtualized? If they are all machines - the esx3 2 and 4 1 under this environment vCenter esx execution? They share a common network for vMotion? Are you running vCenter 4?  If all this is true, you should be able to vMotion between ESX hosts - if they are not part of a commune vCenter environment but share common storage that Yes, you can simply turn off the virtual machine remove it form the inventory of existing cluster and then using the browser of data store to find the vmx file and add it to the inventory of the new server =

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

Maybe you are looking for