Hello everyone.
Can you confirm me that VCSA 7 does not support external database. Is there any KB that explains it
What is more advisable if I have 2 sites put 1 vCenter to control the 2 sites or put 1 vCenter in each site.
Can you tell me the pros and cons.
Thank you very much in advance
Hi @xorraadeu
look, I already explained what you ask. But we can dig deeper into it. 🙂
You can choose between 3 options in your case.
Option 1: One vCenter, manages 2 virtual Data Center (pre-production, production)
Option 2: Two vCenter, each managing one Data center (pre-production, production)
Option 3: Two vCenter in Enhanced Linked Mode, each managing one Data center (pre-production, production)
-------------------------------------------------------------------------------------------------------------------------------------------------------
With Option 1, you log in to your vCenter and can manage both Data centers together with their clusters, vms, etc.
Pros: one SSO domain for users, one single vCenter license, ease of management, simplified updates
Cons: if vCenter lost connection, VCSA is damaged, disaster happens you'll have to recover your VCSA VM first (restore from backup, new deployment, etc.)
-------------------------------------------------------------------------------------------------------------------------------------------------------
With Option 2 you need to log in to each vCenter to control your pre-production/production data centers. The first vCenter is not aware of the existence of the second.
Pros: if something happens to a vCenter in pre-production, it doesn't affect your production vCenter. 2 vCenters are separated and data can't be compromised if one vCenter has a problem ( strictly separated SSOs, VMs from pre-prod can't be migrated to a prod due to human error, etc etc).
Cons: ease of management (you have 2 SSO domains for users, 2 single vCenter licenses, need to plan updates for 2 VCSA/vCenter, etc.)
-------------------------------------------------------------------------------------------------------------------------------------------------------
With Option 3 you will have kinda best of both worlds, but it comes with its price shield. 🙂
Pros: one SSO domain for users, ease of management for prod/pre-prod due to a single pane of glass, simplified migrations, etc.
Cons: 2 single vCenter licenses, need to plan updates for 2 VCSA/vCenter and coordinate them for both vCenters,
plus
everything else I described in my previous answer.
Please don't forget to accept this as an accepted solution or give me a KUDO if you find this post useful! Thanks!
It means a lot to me, I mean we all here take the time to give the answer and some people just use it and not even a thank you.
Not Kudos, no answer accepted, or even a thank you. We are not paid here to help, and if people ignore us, most of us stop helping site visitors. 🙂
Separate vCenter for each site
Pros - If once VC is down the manageability of other site is still independent since its managed by other VC .
Cons- Additional License of the Second vCenter
Same vCenter for both site
Pros- Same license , cost reduction
I dont see any Cons here
Regards
Harry
Thanks
Harry
Hello mannharry,
Thanks for the reply.
If I have a site that is production and I have another site Preproduction and if the production site falls I have to pass it all preproduction in this case it is better to have 2 vcenter.
Each site has one 600 mv.
What do you mean by "The deployment model should ideally be medium".
What would be the correct aqruitecture 1 vCenter for each site.
Post edited to remove comments of obvious little interest.
Hi @xorraadeu
Can you confirm me that VCSA 7 does not support external database. Is there any KB that explains it
External MS SQL DB was possible with a Windows vCenter. Since VMware brought VCSA, it uses vPostgres and external DB is not possible anymore.
https://blogs.vmware.com/vsphere/2016/03/getting-comfortable-with-vpostgres-and-the-vcenter-server-a...
What is more advisable if I have 2 sites put 1 vCenter to control the 2 sites or put 1 vCenter in each site.
Can you tell me the pros and cons.
- Pros:
You can have 2 vCenters in Enhanced Linked Mode, so you can manage them through a single pane of glass. Linked mode is used when there are two vCenters and they are linked together to achieve centralized management. It will show all your Inventory in both the vCenters. vCenter 1 and vCenter 2 can see each other's inventory.
But by using a multi-site SSO the users/permissions will be replicated.
Cons:
Management complexity increases. Reliability of inter-site link. Upgrade needs planning. There is a potential danger that after upgrading to a major version your ELM gets broken (already experienced twice).
Regarding sizing problems and how to find the right size:
- Use the reference guide or architecture, sizing guides, reference architecture, design guides
- Follow the sizing guides from the vendors
- Check your current workloads to correctly size your environment. (with vROPS for example)
Use a calculator (https://vsantco.vmware.com/, https://wintelguy.com/vmcalc.pl,)
Sizing Tools
VMware Configuration Maximum Tool by VMware
vSphere Cluster Sizing Calculator by Josh Odgers
VMware VMFS Datastore Sizing Calculator by Samir Roshan
vRealize Operations Manager Sizing by VMware
vSAN ReadyNode™ Sizer by VMware
--
Please don't forget to accept this as an accepted solution or give me a KUDO if you find this post useful! Thanks! 🙂 It means a lot to me.
Hello leka85,
Thank you for your reply.
I understand that it is better to have 1 vCenter at each site.
Can you tell me more pros and cons in having better 1 vCenter in each site and not 1 vCenter for the 2 sites.
Hi @xorraadeu
look, I already explained what you ask. But we can dig deeper into it. 🙂
You can choose between 3 options in your case.
Option 1: One vCenter, manages 2 virtual Data Center (pre-production, production)
Option 2: Two vCenter, each managing one Data center (pre-production, production)
Option 3: Two vCenter in Enhanced Linked Mode, each managing one Data center (pre-production, production)
-------------------------------------------------------------------------------------------------------------------------------------------------------
With Option 1, you log in to your vCenter and can manage both Data centers together with their clusters, vms, etc.
Pros: one SSO domain for users, one single vCenter license, ease of management, simplified updates
Cons: if vCenter lost connection, VCSA is damaged, disaster happens you'll have to recover your VCSA VM first (restore from backup, new deployment, etc.)
-------------------------------------------------------------------------------------------------------------------------------------------------------
With Option 2 you need to log in to each vCenter to control your pre-production/production data centers. The first vCenter is not aware of the existence of the second.
Pros: if something happens to a vCenter in pre-production, it doesn't affect your production vCenter. 2 vCenters are separated and data can't be compromised if one vCenter has a problem ( strictly separated SSOs, VMs from pre-prod can't be migrated to a prod due to human error, etc etc).
Cons: ease of management (you have 2 SSO domains for users, 2 single vCenter licenses, need to plan updates for 2 VCSA/vCenter, etc.)
-------------------------------------------------------------------------------------------------------------------------------------------------------
With Option 3 you will have kinda best of both worlds, but it comes with its price shield. 🙂
Pros: one SSO domain for users, ease of management for prod/pre-prod due to a single pane of glass, simplified migrations, etc.
Cons: 2 single vCenter licenses, need to plan updates for 2 VCSA/vCenter and coordinate them for both vCenters,
plus
everything else I described in my previous answer.
Please don't forget to accept this as an accepted solution or give me a KUDO if you find this post useful! Thanks!
It means a lot to me, I mean we all here take the time to give the answer and some people just use it and not even a thank you.
Not Kudos, no answer accepted, or even a thank you. We are not paid here to help, and if people ignore us, most of us stop helping site visitors. 🙂
Separate vCenter for each site
Pros - If once VC is down the manageability of other site is still independent since its managed by other VC .
Cons- Additional License of the Second vCenter
Same vCenter for both site
Pros- Same license , cost reduction
I dont see any Cons here
Regards
Harry