vMotion vCenter 6.x vcsa to another host

I know I've done this before, but I just wanted to confirm that vMotion'ing my vcsa will not cause any disruptions in the vcenter service.  It's a 3 node cluster.  I don't want my vcsa living on the same gear as my production vms.  

Disruptions?

Best practices tips with a 3-node cluster and a version 6.x  vcsa appliance?  

Am I correct and assuming I don't want the vcsa living on the same host with production vms?


Thanks in advance!!
Chris
LVL 16
Chris HInfrastructure ManagerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I know I've done this before, but I just wanted to confirm that vMotion'ing my vcsa will not cause any disruptions in the vcenter service.  It's a 3 node cluster.  I don't want my vcsa living on the same gear as my production vms.  

none.

Best practices tips with a 3-node cluster and a version 6.x  vcsa appliance?  

none really, other than make sure it all works! VCSA is no different to any other VM.

Am I correct and assuming I don't want the vcsa living on the same host with production vms?

Why not, you going to build a Host just for a single VM - VCSA - rubbish!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Chris HInfrastructure ManagerAuthor Commented:
The reason for isolating from production is that we've had some weirdnesses that we've yet to troubleshoot.  On more than one occasion, we had the host housing the VCSA fail, but not completely fail.  This eventually resulted in a hung host, an unreachable vcenter and a bunch of unmigrated vm's.  I either had to use the shell to kill the vms and then register them on the surviving host(s) or power off entirely and bring back up.

The architect before me created a bunch of vms and was using scheduled tasks to create daily snapshots (Good God man...).  This eventually ended up with a ton of event errors, 30 deltas that wouldn't purge and a murdered SAN.  

I appreciate your response!

Thanks!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
vCenter

From novice to tech pro — start learning today.