Windows Server 2003 Clustering & Load Balancing phần 10 pptx

APPENDIX A Project Plan Sample 351 OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter A P:\010Comp\OsbNetw\622-6\appa.vp Friday, March 21, 2003 1:32:53 PM Color profile: Generic CMYK printer profile Composite Default screen Copyright 2003 by The McGraw-Hill Companies, Inc. Click Here for Terms of Use. I n this appendix, you look at creating a project plan for rolling out a high-availability solution. You see about 150 separate tasks set within a project that can be customized to your needs. The purpose of this appendix is to give you a tool to build your own project plan, if needed. HIGH-AVAILABILITY PROJECT PLANNING This appendix will be valuable to Project Managers, Team Leaders, Architecture Designers, and Supervisors. Anyone can use the appendix as an aid to help build a project plan for a high-availability solution. Again, you can use this appendix as a guide and change it as you see fit. Many times, I use templates for projects. Build the Project In this section of the appendix, you see all the sections you need to plan before you begin the roll out. First, get a vision of the project. Project Managers will call this a Scope Document, but I’ll keep it simple enough for anyone to follow here. In Figure A-1, I started a project plan on a Gantt chart. You don’t have to use Project 2000 to do this. The whole point is to organize everything, so you don’t forget any steps and you have a way to track what’s being done on the entire project. 352 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Appendix A Figure A-1. Viewing a Gantt chart P:\010Comp\OsbNetw\622-6\appa.vp Friday, March 21, 2003 1:32:53 PM Color profile: Generic CMYK printer profile Composite Default screen You must lay out the major tasks that need to be accomplished. In this appendix, we set up a project plan for a small company for a load-balanced solution with two nodes. 1. Group major tasks together. What are the major points at each transition of the plan? You need to start with a kick-off meeting. What about planning the design and getting a budget? Who will supervise the whole team? Who will work with all the teams within the group? You need to start thinking about people as resources. Where can you use them to get the project accomplished in a timely and accurate manner? 2. After you brainstorm the project, you need to commit it to paper (or electronically). You can group subtasks under major tasks. If you do this correctly, you’ll have a list like this: • Project Vision (Main Task) • Create the vision/scope document: this is used to start the documentation of the NLB solution you want to roll out. • Define and write the project vision statement and scope: you need to assign someone to do this (as a resource). This will most likely be the Project Manager, if you have one. • Identify business drivers and constraints: what is driving this project? The customer needs a Highly Available solution and you need to provide it for them. However, they might be unable to afford what you propose. • Identify critical dates: does this have to be done before December when everyone will be shopping online? • Gain vision/scope document approval: you need stakeholders to sign off on the document, so you can get funding and approval to move forward. • Plan the meeting: this is your kickoff meeting where everyone meets and the project begins. • Obtain vision/scope document approval and signoff: you need signatures on the documentation you created. The kickoff meeting could be the place to do it when everyone is assembled. • Create the conceptual design: now that you’re funded, you can begin the design. This can be done in many ways, but you can refer to the Visio diagrams provided within the book. • Planning (Main Task) • Define project structure: you can do this by explaining what you’re presently creating—the structure of the project. • Assign project team roles and responsibilities: this is an important task because you need to know what people will be available, what they’re going to do, and what their roles will be as the project progresses. Appendix A: Project Plan Sample 353 OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Appendix A P:\010Comp\OsbNetw\622-6\appa.vp Friday, March 21, 2003 1:32:53 PM Color profile: Generic CMYK printer profile Composite Default screen 354 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Appendix A • Assess customer infrastructure: you can’t deploy a project without having an idea on how your plan fits into it. This is critical to get the project solution to work. • Acquire reference materials and software tools: of course, you need to make sure you have documents, books, tools, and anything else you need to get the job done. • Assess and mitigate risks: what are the risks? Once you determine them, either make plans to back out of problems that occur (DRP) or get rid of risk altogether, if possible. • Implement the testing resources: you need to make sure you have enough to pilot the solution or set up a test lab. • Create a communications plan: communications are essential to success. If you’re out of the loop, you might find it hard both to get tasks completed and to get them completed on time. • Identify current network infrastructure: critical to the success of a load- balanced (or any other) solution. You must know the network layout and its data flows. • Physical network topology: WAN and LAN charts are needed to help the planning of the high-availability solution. • Protocol address management: you need to know the Layer 2 and Layer 3 (MAC and IP) addresses for the network if you’re to populate it with a load-balanced solution. • Remote access: will there be remote access to the NLB cluster? If so, then you need to plan it. • Network operations/performance management: covered in detail in Chapter 8. You must know who will monitor and maintain the solution once it’s in place. • Training: are your people ready to implement and maintain this solution? If not, then you must train them. • Identify current user environment: do you know who you have on the floor and how the new NLB cluster will affect them? What about web access or business partners? • Assess infrastructure readiness: is your infrastructure ready to put this new NLB cluster in place? Will you have enough ports in the switch? • Specify functionality to be delivered: you need to document what this solution will provide. • Build the master project plan: a master project plan contains smaller grouped plans. In other words, you can make this one the master project plan, and then you can add the high-availability implementation into this one once you’re ready to do it. P:\010Comp\OsbNetw\622-6\appa.vp Friday, March 21, 2003 1:32:53 PM Color profile: Generic CMYK printer profile Composite Default screen Appendix A: Project Plan Sample 355 OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Appendix A • Build the master project plan: now that you have the master plan, you need to build and document it. • Update the master project plan: Now that it’s ready to go or in the works, you need to keep it updated and manage it. • Developing (Main Task) • Create the logical design: now you need to develop the plan and the solution. This section is highly flexible and can be made to meet any needs your project has. • Server installation and configuration: this can be broken down further but, for this example, let’s keep it simple to the two nodes we’ll implement. • Install NLB node (select the first node): plan development. • Install NLB node (select the second node): plan development. • Install NLB drivers: plan development. • Configure the NLB drivers to design specifications: plan development. • Validate and approve logical design: now that you know what your install is going to be composed of, you need to make sure everyone else agrees with a peer review. • Validate logical design: check, validate, and then sign off on the logical design. • Implement the design into a pilot: this is where you can build the pilot based on the design you created. • Conduct the pilot: make sure you build a good pilot and you demonstrate it properly. • Complete the pilot and controlled introduction, and then document the results. • Move from controlled introduction to enterprisewide deployment. • Deployment (Main Task) • Deploy the system: now you’re ready to go! This is where you do the actual deployment. Again, this is something you can break down deeper, but for this plan, you can use the second half of Chapter 3 to fill in the various subtasks involved with NLB clustering. • Monitor user satisfaction: test the solution and see if it works. Is it better? Simulate failures and see how long you take to get it back together. 3. Now, populate Microsoft Project with this, if you have it. If not, you can make a simple spreadsheet to keep track of what’s listed. 4. Last, assign resources (this also includes people) to each task. This should complete a simple project plan for you. Again, modify this as you see necessary. Understand, this is a template to help you build your own project plans as needed. P:\010Comp\OsbNetw\622-6\appa.vp Friday, March 21, 2003 1:32:53 PM Color profile: Generic CMYK printer profile Composite Default screen OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter A Blind Folio A:356 P:\010Comp\OsbNetw\622-6\appa.vp Friday, March 21, 2003 1:32:54 PM Color profile: Generic CMYK printer profile Composite Default screen APPENDIX B Advanced Troubleshooting: Event IDs 357 OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Chapter B P:\010Comp\OsbNetw\622-6\appb.vp Monday, March 24, 2003 2:02:27 PM Color profile: Generic CMYK printer profile Composite Default screen Copyright 2003 by The McGraw-Hill Companies, Inc. Click Here for Terms of Use. I n this appendix, you look at Microsoft Cluster Server (MSCS) event messages. The intent of this appendix is to make it quick and easy for you to look up possible problems you might experience with your Windows-based high-availability solution. In this section, you look at Event IDs that appear in logs while working with high- availability solutions, such as clustering and load balancing. This appendix was created to consolidate the most-likely seen errors in one section of the book for easy reference. If you need to research some less-common events, you can search http://www.microsoft .com/technet. Event ID 1000 • Source ClusSvc • Description Microsoft Cluster Server suffered an unexpected fatal error at line ### of source module %path%. The error code was 1006. • Problem Messages similar to this might occur in a fatal error that could cause the Cluster Service to terminate on the node that experienced the error. • Solution Check the system event log and the cluster diagnostic log file for additional information. The Cluster Service might restart after the error. This event message could indicate serious problems that might be related to hardware or other causes. Event ID 1002 • Source ClusSvc • Description Microsoft Cluster Server handled an unexpected error at line 528 of source module X. The error code was 5007. • Problem Messages similar to this might occur after installation of Microsoft Cluster Server. If the Cluster Service starts and successfully forms or joins the cluster, they could be ignored. Otherwise, these errors could indicate a corrupt quorum logfile or other problem • Solution Ignore the error if the cluster appears to be working properly. Otherwise, you might want to try creating a new quorum log file using the -noquorumlogging or -fixquorum parameters, as documented in the Microsoft Cluster Server Administrator’s Guide. Event ID 1006 • Source ClusSvc • Description Microsoft Cluster Server was halted because of a cluster membership or communications error. The error code was 4. • Problem An error could have occurred between communicating cluster nodes that affected cluster membership. This error might occur if nodes lose the capability to communicate with each other. 358 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Appendix B P:\010Comp\OsbNetw\622-6\appb.vp Monday, March 24, 2003 2:02:27 PM Color profile: Generic CMYK printer profile Composite Default screen Appendix B: Advanced Troubleshooting: Event IDs 359 OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Appendix B • Solution Check network adapters and connections between nodes. Check the system event log for errors. A network problem might be preventing reliable communication between cluster nodes. Event ID 1007 • Source ClusSvc • Description A new node, ComputerName, was added to the cluster. • Information The Microsoft Cluster Server Setup program ran on an adjacent computer. The setup process completed and the node was admitted for cluster membership. No action required. Event ID 1009 • Source ClusSvc • Description Microsoft Cluster Server couldn’t join an existing cluster and couldn’t form a new cluster. Microsoft Cluster Server has terminated. • Problem The Cluster Service started and attempted to join a cluster. The node might not be a member of an existing cluster because of eviction by an administrator. After a cluster node has been evicted from the cluster, the cluster software must be removed and reinstalled if you want it to rejoin the cluster. And, because a cluster already exists with the same cluster name, the node couldn’t form a new cluster with the same name. • Solution Remove MSCS from the affected node and reinstall MSCS on that system, if desired. Event ID 1010 • Source ClusSvc • Description Microsoft Cluster Server is shutting down because the current node isn’t a member of any cluster. Microsoft Cluster Server must be reinstalled to make this node a member of a cluster. • Problem The Cluster Service attempted to run, but found it isn’t a member of an existing cluster. This could be because of eviction by an administrator or an incomplete attempt to join a cluster. This error indicates a need to remove and reinstall the cluster software. • Solution Remove MSCS from the affected node and reinstall MSCS on that server, if desired. Event ID 1011 • Source ClusSvc • Description Cluster Node ComputerName has been evicted from the cluster. • Information A cluster administrator evicted the specified node from the cluster. P:\010Comp\OsbNetw\622-6\appb.vp Monday, March 24, 2003 2:02:27 PM Color profile: Generic CMYK printer profile Composite Default screen 360 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Appendix B Event ID 1015 • Source ClusSvc • Description No checkpoint record was found in the logfile X:\Mscs\ Quolog.log. The checkpoint file is invalid or was deleted. • Problem The Cluster Service experienced difficulty reading data from the quorum log file. The log file could be corrupted. • Solution If the Cluster Service fails to start because of this problem, try manually starting the Cluster Service with the -noquorumlogging parameter. If you need to adjust the quorum disk designation, use the -fixquorum startup parameter when starting the Cluster Service. Both of these parameters are covered in the MSCS Administrator’s Guide. Event ID 1016 • Source ClusSvc • Description Microsoft Cluster Server failed to obtain a checkpoint from the cluster database for log file X:\Mscs\Quolog.log. • Problem The Cluster Service experienced difficulty establishing a checkpoint for the quorum log file. The log file could be corrupt or a disk problem could exist. • Solution You could need to use procedures to recover from a corrupt quorum log file. You might also need to run chkdsk on the volume to ensure against file system corruption. Event ID 1019 • Source ClusSvc • Description The log file X:\MSCS\Quolog.log was found to be corrupt. An attempt will be made to reset it or you should use the Cluster Administrator utility to adjust the maximum size. • Problem The quorum logfile for the cluster was found to be corrupt. The system will attempt to resolve the problem. • Solution The system will attempt to resolve this problem. This error could also be an indication that the cluster property for maximum size should be increased through the Quorum tab. You can manually resolve this problem by using the -noquorumlogging parameter. Event ID 1021 • Source ClusSvc • Description Insufficient disk space remains on the quorum device. Please free up some space on the quorum device. If no space exists on the disk for the quorum log files, then changes to the cluster registry will be prevented. P:\010Comp\OsbNetw\622-6\appb.vp Monday, March 24, 2003 2:02:27 PM Color profile: Generic CMYK printer profile Composite Default screen [...]... 302–304 Server 2000, Highly Available databases with SQL, 21 Server 2003, building load balanced cluster with, 304–313 Server 2003 clustering and load balancing, 17–18 Windows Server 2003, 17–18 Windows Server 2003 Enterprise servers, 17 Server 2003, designing clustered solution with Windows, 123 designing cluster solution with Windows Server 2003, 137–177 designing NLB solution with Windows Server 2003, ... (Network Load Balancing) , 196–201 Windows Server 2003 NLB software rollout, 184–196 Windows Server 2003 rolling upgrade, 124–137 Server 2003 NLB solutions, building Highly Available, 304–313 Server 2003 solutions, building Highly Available, building load balanced cluster with Server 2003, 304–313 Server Administrator account, SQL Server Virtual, 234 Server drive considerations, Cluster, 61 Server in... solution with Windows Server 2003, 177–184 managing NLB (Network Load Balancing) , 196–201 Windows Server 2003 NLB software rollout, 184–196 Windows Server 2003 rolling upgrade, 124–137 Windows Server 2003 rolling upgrade, 124–137 planning rolling upgrades, 127–134 planning rolling upgrades with management, 124–127 rolling upgrade going live, 134–135 Windows Server 2003 rolling upgrade, 136–137 Windows Services,... Windows 2000 clustering and load balancing, 10 17 Windows 2000 Clustering Services, 10 14 Windows Server 2003 Cluster Services, 146–159 cluster tips, 175–177 designing cluster solution with, 123, 137–177 designing NLB solution with, 177–184 as load balancer, 181 NLB software rollout, 184–196 Windows Server 2003, designing clustered solution with, 123 designing cluster solution with Windows Server 2003, 137–177... instance), 237 SQL Server component planning, 232–235 shared components of clustered SQL Server, 234–235 SQL Server Virtual Server Administrator account, 234 SQL Server Virtual server IP addressing, 234 379 380 Windows Server 2003 Clustering & Load Balancing SQL Server Virtual server names, 233–234 SQL Server in clustered solution, installation and configuration of, 244–253 SQL Server Network Name,... 196–201 Windows Server 2003 NLB software rollout, 184–196 Windows Server 2003 rolling upgrade, 124–137 Clustered solutions, installation and configuration of SQL Server in, 244–253 Clustered SQL Servers, shared components of, 234–235 Cluster.exe command-line administration, 100 101 Clustering defined, 3–5 failover and failback, 10 11 pros and cons to, 5–6 stateless vs stateful, 12 Clustering and load balancing, ... ❖ L Load balanced configurations, building Highly Available, 289–314 building Highly Available Server 2003 NLB solutions, 304–313 predesign planning, 290–304 Load balanced solutions, designing clustered and, 203–229 Load- balanced third party solutions, designing, 33–34 Load balancers hardware, 105 software, 105 Windows Server 2003 as, 181 Load balancing defined, 3–5 pros and cons to, 5–6 Server 2003. .. Manager, using, 196–198 375 376 Windows Server 2003 Clustering & Load Balancing NLB (Network Load Balancing) , managing, 196–201 using NLB commands, 198–201 using NLB (Network Load Balancing) Manager, 196–198 NLB (network load balancing) , port rules and priority assignments, 16 NLB nodes, mixing, 299–300 NLB software rollout, 108 –118 configuring cluster parameters, 110 113 configuring Host Parameters,... rollout, 108 –118 planning software rollout, 61–67 precluster system customization and configuration, 67 102 where to begin, 44–45 Windows 2000 Advanced Server NLB installation, 119–122 Clustered solutions, designing with Windows Server 2003, 123 designing cluster solution with Windows Server 2003, 137–177 designing NLB solution with Windows Server 2003, 177–184 managing NLB (Network Load Balancing) ,... and cons to, 5–6 stateless vs stateful, 12 Clustering and load balancing, Server 2003, 17–18 Clustering and load balancing, Windows 2000, 10 17 Windows 2000 Clustering Services, 10 14 Clustering Services install preinstallation checklist, 141–142 installation, 94–99 preinstallation checklists, 93–94 Clustering technology, 1–41 Clustering with NT 4.0, 9 Clusters adding new members to Application Center . project. 352 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Appendix A Figure A-1. Viewing a Gantt chart P:10CompOsbNetw622-6appa.vp Friday,. with each other. 358 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/ 222622-6 / Appendix B P:10CompOsbNetw622-6appb.vp Monday,. profile. Microsoft Cluster Server requires network connectivity. 368 Windows Server 2003 Clustering & Load Balancing OsbNetw / Windows Server 2003 Clustering & Load Balancing / Shimonski/