?
Solved

vSphere, XenDT, Server Upgrade Path

Posted on 2015-01-25
7
Medium Priority
?
267 Views
Last Modified: 2015-02-07
We currently have vSphere 5.0 hosting VM's on HPDL360 with Citrix XDT 5.6 providing VDI.

The hosts are pretty much maxed out during the day.

We have the fortune of having an HP 7000 series chassis and two blades.  My plan is to buy one more blade, and enough RAM to take all three to 384GB.  This should give us 2.5x the GHz and 50% more RAM than we have currently.

I'm trying to think of the best way to migrate from the old to the new hardware will keeping everything up.

An important point is that XDT 5.6 will NOT talk to vCenter 5.5, so I have to keep vCenter 5.0 up until I can get Citrix XDT 7.6 up on the new blades.  Fortunately I have another vCenter license and enough ESXi license to run two of my three blades and those two can handle my full load.

My current plan is to stand up two new blades on ESXi 5.5 and stand up vCenter 5.5.  Then stand up the virtual security and backup appliances in vSphere 5.5.

I will then begin to power down servers (not related to Citrix XDT 5.6) in vSphere 5.0 and discover them in vSphere 5.5 on the SAN, boot them, update vhardware, etc.  I’m not sure, but I don’t think you can move machines from vSphere 5 to vSphere 5.5.

Then I'll stand up the new Citrix XDT 7.6 infrastructure inside vSphere 5.5.  I'll test XDT 7.6 until all users are happy and then decommission the XDT 5.6 infrastructure.  Then decommission the vSphere 5.0 infrastructure, move the old hosts to the DR site, set them up in vSphere 5.5 as an SRM recovery site.


That's my plan, but I'd love to hear if I'm missing something if there are better ways.  One bonus question.  I have two virtual Citrix Netscalers (VPX).  Any input on moving them from vSphere5.0 to 5.5?
0
Comment
Question by:whoam
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 122
ID: 40569840
, but I don’t think you can move machines from vSphere 5 to vSphere 5.5.

Completely compatible, no issues.

If the VMs are on a SAN, just deregister from the Inventory on 5.0, and register them in the inventory on 5.5. (right click the VMX, add to Inventory).
0
 

Author Comment

by:whoam
ID: 40569851
Andrew,
Thanks.  Yeah, that's what I meant by discover them on the SAN.  I just don't think there's a way to go to vCenter 5 and push them to vCenter 5.5 or pull them from vCenter 5.5.

Thanks
0
 
LVL 122
ID: 40569857
Simple, if they are already on the SAN.

1. Power the VMs OFF.

2. De-Register from the vCenter 5.0 inventory.

3.  vCenter 5.5, browse the SAN datastores and Register the VMs.

4. Done.

see my EE Articles for examples, Step 6 shows how to register a VM

HOW TO: Clone or Copy a virtual machine in VMware vSphere Hypervisor ESX/ESXi 4.x or ESXi 5.0

HOW TO: Select the right answer to "I Moved It" or "I Copied It" in VMware vSphere (ESXi)
0
Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

 

Author Comment

by:whoam
ID: 40582745
Andrew,

I'm sorry to pick nits, but what I was talking about not being able to do is vmotions/storage motion from vCenter 5.0 to vCenter 5.5.  Deregistration/discovery is simple.  I've done it too many times to count.

Now, on to the Netscalers.  Understand these are network appliances.  So my questions there revolve around virtual networking not really virtual hardware.  I'm thinking that if I keep my vSwitch names and vLANs the same from vSphere 5.0 to 5.0 they should come over fine.  I've just never moved a VPX before and would love to hear from someone who has.

May just have to open a case with Citrix.
0
 
LVL 122

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 40582756
I'm sorry to pick nits, but what I was talking about not being able to do is vmotions/storage motion from vCenter 5.0 to vCenter 5.5.  Deregistration/discovery is simple.  I've done it too many times to count.

Correct at present, things may change in the future, with future releases of vSphere, and vMotion and Storage vMotion between different Datacenters.

Now, on to the Netscalers.  Understand these are network appliances.  So my questions there revolve around virtual networking not really virtual hardware.  I'm thinking that if I keep my vSwitch names and vLANs the same from vSphere 5.0 to 5.0 they should come over fine.  I've just never moved a VPX before and would love to hear from someone who has.

As the changes are occurring outside of the VM, it does not matter, but the Virtual Machines *MUST* be on the same network as before, so if that involves a vLAN change on the virtual machine portgroup, it needs to be in place.

The OS within the VM however, does not know, about the vSwitch, vLAN, all that matters is it's connected to the correct network.

So virtual machine portgroup, vSwitch name - does not matter.

Just ensure that it's connected to the same network as previous, how you present that on the host, is up to you.
0
 

Assisted Solution

by:whoam
whoam earned 0 total points
ID: 40584550
Citrix said to see CTX200278 which talks about a known issue and workaroung for VPX on 5.1 and 5.5.
0
 

Author Closing Comment

by:whoam
ID: 40595434
All points to expert, just adding in my notes for other readers
0

Featured Post

Introducing Priority Question

Increase expert visibility of your issues by participating in Priority Question, our latest feature for Premium and Team Account holders. Adjust the priority of your question to get emergent issues in front of subject-matter experts for help when you need it most.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.
Suggested Courses

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question