hihiy
Contributor
Contributor

How can I divid View VC from Server Consolidated VC?

dear all,

In our IT environment, vCenter Server is only ONE for View and Server Consolidation (ESX3.5U3). Its means, we share the same vCenter Server between View and vSphere ESX.

How can I isolate separately VC, one for View and another for ESX without impact each configuration???

And, my VC is a physical machine and its database is default installed.

thanks a lot.

hihiy

0 Kudos
11 Replies
mittim12
Immortal
Immortal

Can you go into more detail as to what you mean by seperation? Do you want to have a VC for View and then a seperate one for vCenter?






If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

0 Kudos
hihiy
Contributor
Contributor

I wanna have two VCs. One for View and another one for ESX.

0 Kudos
mittim12
Immortal
Immortal

This could be easy if you are using floating pools. If floating pools are utilized you could stand up the second vCenter, add your temples, connect up View environment, and then simply redeploy everything into the new vCenter. That is provided you are using some sort of solution to capture profiles so they would be copied back down once the new VM's are created.

If you are using dedicated pools then you will have to take into account the mappings for user to VM and any user data disk you may be dealing with. This could probably still be done but you would have to script the VM to user assignments once you had everything moved over via storage vmotion or a redeploy.






If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

0 Kudos
eeg3
Commander
Commander

It will probably be more difficult to move View to another vCenter setup than it would be to migrate your normal ESX hosts to another vCenter server.






____________

blog.eeg3.net | Useful VMware-related Links

If you found this or any other post helpful, please consider the use of the Helpful/Correct buttons to award points.

Blog: http://blog.eeg3.net
hihiy
Contributor
Contributor

I do not do any storage vmotion. And we deploy the persistent pool for there 100 v-desktops.

There is ONE vCenter manages 4 hosts in the lab. Two run lots virtual hosts-windows2003. Two have 100v-desktops. I wanna a 2nd vCenter to manage these two view esx hosts and re-add into view manager.

Do you mean, I can deploy a new vCenter and add it into view manager. I manual mapping the assignment between users and desktops one by one?

0 Kudos
hihiy
Contributor
Contributor

Good idea.

0 Kudos
mittim12
Immortal
Immortal

100 persistent desktops is a lot try and move over. As the other poster said it may be far simpilier to move over the server environment depending on the number of server VM's you have. Just out of curiosity why do you want to seperate them into two vCenters? Easier to manage that way?






If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

0 Kudos
eeg3
Commander
Commander

From my dealings with VMware support, they've stated it is best practice to separate the two environments. For instance, when vCenter 4.1 was released, it wasn't even compatible with View Composer.






____________

blog.eeg3.net | Useful VMware-related Links

If you found this or any other post helpful, please consider the use of the Helpful/Correct buttons to award points.

Blog: http://blog.eeg3.net
0 Kudos
mittim12
Immortal
Immortal

Yeah, that has actually be the case with ever major release of ESX and View the last couple of times. Always having to wait on View so that you can upgrade your ESX environment. Having multiple vCenters would help in that case but I'm hoping on this last release they will stay on the same schedule. I could see it being extremely beneficial if you have two groups managing the environments and want to seperate them out. If you are the only one running the enviroment it could be a pain to seperate them out.






If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

0 Kudos
hihiy
Contributor
Contributor

1. The vCenter is a physical machine, it is need to migrate into a virtual machine.

2. The view is upgrade from 3 to view4. Its recommand managed in separate vc.

3. View and ESX Maintenan by different team

thank you mittim12.

0 Kudos
mittim12
Immortal
Immortal

Thanks for letting me know your reasons. We are in the middle of a project that will take us from 150 to 200 desktops into about 1000 desktops. Given the large number of desktops that are planned I have been considering the move to multiple vCenters with dedicated VDI and dedicated servers. Just weighing my options and getting feedback from other people at the moment.






If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

0 Kudos