![]() ![]() Three-step process for the capacity planning cycle One could also plan to add the third DC after 3 or 6 months if budgets are tight.Īdding Active Directory-aware applications might have a noticeable impact on the DC load, whether the load is coming from the application servers or clients. The solution would be to start with three DCs. ![]() For example, if one DC is required to support the load, but the estimate is that the load will be doubled in the next year and require two DCs total, there will not be enough capacity to support fault tolerance. Once an estimate N is derived, plan for scenarios that include N – 1, N – 2, N – x.Īdd in additional servers according to organizational need to ensure that the loss of a single or multiple servers does not exceed maximum peak capacity estimates.Īlso consider that the growth plan and fault tolerance plan need to be integrated. Historical data, if collected, will help with this assessment. Each will require a “guess” as how much the load on Active Directory will grow. This may include a strategy of upgrading or adding hardware in a staggered fashion, or a complete refresh every three to five years. Plan for growth over the course of the hardware lifecycle for the enterprise.Anything greater may hide the actual peaks and anything less may be distorted by “transient spikes.” It is recommended to look at this in either 30 minute or hour intervals. Plan for the peak busy period of the day.For example, memory becomes cheaper, the cost per core decreases, or the price of different storage options change. Optimization will occur over multiple hardware lifecycles as hardware costs change.Capacity planning is a continuous process and you should regularly review how well the environment is meeting expectations.But even if your Active Directory environment is installed on Windows Server 2003 x86 (now beyond the end of the support lifecycle) and has a directory information tree (DIT) that is less 1.5 GB in size and that can easily be held in memory, the guidelines from this article are still applicable. The Windows Server platform is an 圆4 based architecture.Readers have read and are familiar with Performance Tuning Guidelines for Windows Server 2012 R2.Throughout this article, the following baseline requirements are expected: Baseline requirements for capacity planning guidance Active Directory Domain Services (AD DS), a mature distributed service that many Microsoft and third-party products use as a backend, becomes one the most critical products to plan correctly to ensure the necessary capacity for other applications to run. Increased attention to power consumptionĪdditionally, the approach is shifting from a server-based capacity planning exercise to a service-based capacity planning exercise.The following changes in system architectures have challenged fundamental assumptions about designing and scaling a service: Over the last several years, capacity planning guidance for scale-up systems has changed dramatically. This is about “defensive driving,” Active Directory-style. Performance alert thresholds indicate that client experience is currently suffering and immediate steps are needed to address the issue.Īs an analogy: capacity management is about preventing a car accident (defensive driving, making sure the brakes are working properly, and so on) whereas performance troubleshooting is what the police, fire department, and emergency medical professionals do after an accident. The difference is that when a capacity management threshold is continually exceeded (a one-time event is not a concern), adding capacity (that is, adding in more or faster processors) would be a solution or scaling the service across multiple servers would be a solution. Whereas, to be notified of abnormal performance incidents, a monitoring alert threshold might be set at 90% over a 5 minute interval. In capacity planning, an organization might have a baseline target of 40% processor utilization during peak periods in order to meet client performance requirements and accommodate the time necessary to upgrade the hardware in the datacenter. Minimize the time spent troubleshooting performance issues.Properly implement and operate an environment.They are closely related, but quite different. Goals of capacity planningĬapacity planning is not the same as troubleshooting performance incidents. This topic is originally written by Ken Brumfield, Program Manager at Microsoft, and provides recommendations for capacity planning for Active Directory Domain Services (AD DS). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |