As I continue on my training for the Design exam, i'm seeing a common theme of DB separation from the actual Infrastructure application, ie vCenter, VUM, View, and so on and so on.
My questions are pertaining the common protection schemes for the DB's of the VMware INF application tier. Assuming I am picking a DB product, such as SQL for my Databases for these apps,and also assume I have at least 3 or 4 INF Applications that require DB's, would this be considered the best practice design:
1. Centralized DB MS Failover Cluster, RDM's, and VM to host affinity. Build instances off of the same core DB Failover cluster for each application vCenter, VUM, View, etc.
2. INF Applications themselves would sit in the same cluster with normal HA/DRS rules in place.
A lot of the design information i'm gathering is also a bit confusing. As you know you certainly don't want to price your solution out of the ballpark where your customer gets sticker shock. I would think that the above would fly for an enterprise type solution, but how would you handle a smaller business who wants VDI for example? I don't mean like small office, 30 people..etc..but a business that has say 200 people, 150 of those would be VDI. Would you still consider the MGMT cluster and centralized DB type solution? I'm guessing yes looking at the POD and BLOCK design guideline.
My questions are pertaining the common protection schemes for the DB's of the VMware INF application tier. Assuming I am picking a DB product, such as SQL for my Databases for these apps,and also assume I have at least 3 or 4 INF Applications that require DB's, would this be considered the best practice design:
1. Centralized DB MS Failover Cluster, RDM's, and VM to host affinity. Build instances off of the same core DB Failover cluster for each application vCenter, VUM, View, etc.
2. INF Applications themselves would sit in the same cluster with normal HA/DRS rules in place.
A lot of the design information i'm gathering is also a bit confusing. As you know you certainly don't want to price your solution out of the ballpark where your customer gets sticker shock. I would think that the above would fly for an enterprise type solution, but how would you handle a smaller business who wants VDI for example? I don't mean like small office, 30 people..etc..but a business that has say 200 people, 150 of those would be VDI. Would you still consider the MGMT cluster and centralized DB type solution? I'm guessing yes looking at the POD and BLOCK design guideline.
Last edited: