Tài liệu Windows Server 2008 Inside Out- P29 doc

Confi guring Print Settings for a Clustered Print Server You can confi gure a printer for a clustered print server by completing the following steps: 1. In Failover Cluster Management, expand the node for the cluster you want to work with by double-clicking it. If the cluster you want to work with is not listed, connect to it. 2. Expand the cluster’s Services And Applications node. 3. Right-click the clustered print server and then select Manage Printers. This opens Print Management with a Failover Cluster Management interface. 4. Under Print Management ensure that the clustered print server or the cluster node is listed. If it is not, right-click Print Servers and then select Add/Remove Servers. Type the host name or IP address of the clustered print server and then click Add To List. 5. Right-click the clustered print server and then click Add Printer. This starts the Add Printer wizard. 6. Follow the prompts to create the shared printer. This is the same wizard that you use with nonclustered servers. After you’ve added the printer, you can manage it as you would any other printer. Managing Failover Clusters and Their Resources 1367 Chapter 39 Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. A sk three different people what their idea of a disaster is and you’ll probably get three different answers. For most administrators, the term disaster probably means any scenario in which one or more essential systems, services, or applications cannot operate and the prospects for quick recovery are less than hopeful—that is, a disaster is something a service reset or system reboot won’t fi x. To ensure that operations can be restored as quickly as possible in a given situation, every network needs a clear disaster recovery plan. In this chapter, I’m not going to mince words and try to explain why you need to plan for disasters. Instead, I’m going to focus on what you need to do to get ready for the inevitable, because worst-case scenar- ios can and do happen. I’m also going to discuss predisaster preparation procedures. Preparing for a Disaster Chapter 38, “Planning for High Availability,” went into detail about planning for highly available, scalable, and manageable systems. Many of the same concepts go into disas- ter planning. Why? Because, at the end of the day, disaster planning involves imple- menting plans that ensure the availability of systems and services. Remember that part of disaster planning is applying some level of contingency planning to every essential network service and system. You need to implement problem escalation and response procedures. You also need a standing problem-resolution document that describes in great detail what to do when disaster strikes. Developing Contingency Procedures You should identify the services and systems that are essential to network operations. Typically, this list will include the following components:  Network infrastructure servers running Active Directory, Domain Name System (DNS), Dynamic Host Confi guration Protocol (DHCP), Terminal Services, and Routing and Remote Access Service (RRAS)  File, database, and application servers, such as servers with essential fi le shares or those that provide database or e-mail services  Networking hardware, including switches, routers, and fi rewalls Preparing for a Disaster . . . . . . . . . . . . . . . . . . . . . . . . 1369 Disaster Preparedness Procedures . . . . . . . . . . . . . . . . 1373 CHAPTER 40 Disaster Planning 1369 Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Use Chapter 38 to help you develop plans for contingency procedures in the following areas:  Physical security Place network hardware and servers in a locked, secure access facility. This could be an offi ce that is kept locked or a server room that requires a passkey to enter. When physical access to network hardware and servers requires special access privileges, you prevent many problems and ensure that only autho- rized personnel can get access to systems from the console.  Data backup Implement a regular backup plan that ensures that multiple data- sets are available for all essential systems, and that these backups are stored in more than one location. For example, if you keep the most current backup sets on-site in the server room, you should rotate another backup set to off-site stor- age. In this way, if disaster strikes, you will be more likely to be able to recover operations.  Fault tolerance Build redundancy into the network and system architecture. At the server level, you can protect data using a redundant array of independent disks (RAID) and guard against component failure by having spare parts at hand. These precautions protect servers at a very basic level. For essential services such as Active Directory, DNS, and DHCP, you can build in fault tolerance by deploy- ing redundant systems using techniques discussed throughout this book. These same concepts can be applied to network hardware components such as routers and switches.  Recovery Every essential server and network device should have a written recovery plan that details step by step what to do to rebuild and recover it. Be as detailed and explicit as possible and don’t assume that the readers know any- thing about the system or device they are recovering. Do this even if you are sure that you’ll be the one performing the recovery—you’ll be thankful for it, trust me. Things can and do go wrong at the worst times, and sometimes, under pressure, you might forget some important detail in the recovery process—not to mention that you might be unavailable to recover the system for some reason.  Power protection Power-protect servers and network hardware using an uninter- ruptible power supply (UPS) system. Power protection will help safeguard serv- ers and network hardware from power surges and dirty power. Power protection will also help prevent data loss and allow you to power down servers in an appro- priate fashion through manual or automatic shutdown. Implementing Problem Escalation and Response Procedures As part of planning, you need to develop well-defi ned problem escalation procedures that document how to handle problems and emergency changes that might be needed. You need to designate an incident response team and an emergency response team. Although the two teams could consist of the same team members, the teams differ in fundamental ways. Chapter 40 1370 Chapter 40 Disaster Planning Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.  Incident response team The incident response team’s role is to respond to secu- rity incidents, such as the suspected cracking of a database server. This team is concerned with responding to intrusion, taking immediate action to safeguard the organization’s information, documenting the security issue thoroughly in an after-action report, and then fi xing the security problem so that the same type of incident cannot recur. Your organization’s security administrator or network security expert should have a key role in this team.  Emergency response team The emergency response team’s role is to respond to service and system outages, such as the failure of a database server. This team is concerned with recovering the service or system as quickly as possible and allow- ing normal operations to resume. Like the incident response team, the emergency response team needs to document the outage thoroughly in an after-action report, and then, if applicable, propose changes to improve the recovery process. Your organization’s system administrators should have key roles in this team. Putting in a UPS requires a bit of planning, because you need to look not only at serv- ers but also at everything in the server room that requires power. If the power goes out, you want to have ample time for systems to shut down in an orderly fashion. You may also have some systems that you do not want to be shut down, such as routers or servers required for security key cards. In most cases, rather than using individual UPS devices, you should install enterprise UPS solutions that can be connected to several servers or components. After you install a UPS, you can confi gure servers to take advantage of the UPS using the management software included with the UPS. You can then confi gure the way a server reacts when it switches to battery power. Typically, you’ll want servers to start an orderly shutdown within a few minutes of switching to battery power. In your planning, remember that 90 percent of power outages last less than 5 minutes and 99 percent of power outages last less than 60 minutes. With this in mind, you may want to plan your UPS implementation so that you can maintain 7 to 10 minutes of power for all server and network components and 60 to 70 minutes for critical systems. You would then confi gure all non-critical systems to shut down automatically after 5 minutes, and critical systems to shut down after 60 minutes. Creating a Problem Resolution Policy Document Over the years, I’ve worked with and consulted for many organizations, and I’ve often been asked to help implement information technology (IT) policy and procedure. In the area of disaster and recovery planning, there’s one policy document that I always use, regardless of the size of the company I am working with. I call it the problem resolution policy document. SIDE OUT Using and confi guring a UPS Putting in a UPS requires a bit of planning, because you need to look not only at serv- ers but also at everything in the server room that requires power. If the power goes out, you want to have ample time for systems to shut down in an orderly fashion. You may also have some systems that you do not want to be shut down, such as routers or servers required for security key cards. In most cases, rather than using individual UPS devices, you should install enterprise UPS solutions that can be connected to several servers or components. After you install a UPS, you can confi gure servers to take advantage of the UPS using the management software included with the UPS. You can then confi gure the way a server reacts when it switches to battery power. Typically, you’ll want servers to start an orderly shutdown within a few minutes of switching to battery power. In your planning, remember that 90 percent of power outages last less than 5 minutes and 99 percent of power outages last less than 60 minutes. With this in mind, you may want to plan your UPS implementation so that you can maintain 7 to 10 minutes of power for all server and network components and 60 to 70 minutes for critical systems. You would then confi gure all non-critical systems to shut down automatically after 5 minutes, and critical systems to shut down after 60 minutes. Preparing for a Disaster 1371 Chapter 40 Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. The problem resolution policy document has the following six sections:  Responsibilities The overall responsibilities of IT and engineering staff during and after normal business hours should be detailed in this section. For an orga- nization with 24/7 operations, such as a company with a public Web site main- tained by internal staff, the after-hours responsibilities section should be very detailed and let individuals know exactly what their responsibilities are. Most organizations with 24/7 operations will designate individuals as being “on call” 7 days a week, 365 days a year, and in that case, this section should detail what being “on call” means, and what the general responsibilities are for an individual on call.  Phone roster Every system and service that you’ve identifi ed in your planning as essential should have a point of contact. For some systems, you’ll have several points of contact. Consider, for example, a database server. You might have a sys- tem administrator who is responsible for the server itself, a database administra- tor who is responsible for the database running on the server, and an integration specialist responsible for any integration components running on the server. Note The phone roster should include both on-site and off-site contact numbers. Ideally, this means that you’ll have the work phone number, cell phone number, and pager number of each contact. It should be the responsibility of every individual on the phone roster to ensure that contact information is up to date.  Key contact information In addition to a phone roster, you should have contact numbers for facilities and vendors. The key contacts list should include the main offi ce phone numbers at branch offi ces and data centers, and contact numbers for the various vendors that installed infrastructure at each offi ce, such as the building manager, Internet service provider (ISP), electrician, and network wiring specialist. It should also include the support phone numbers for hardware and software vendors and the information you’ll be required to give in order to get service, such as customer identifi cation number and service contract information.  Notifi cation procedures The way problems get resolved is through notifi cation. This section should outline the notifi cation procedures and the primary point of contact in case of outage. If many systems and services are involved, notifi cation and primary contacts can be divided into categories. For example, you may have an external systems notifi cation process for your public Internet servers and an internal systems notifi cation process for your intranet services.  Escalation When problems aren’t resolved within a specifi c timeframe, there should be clear escalation procedures that detail whom to contact and when. For example, you might have level 1, level 2, and level 3 points of contact, with level 1 contacts being called immediately, level 2 contacts being called when issues Note The phone roster should include both on-site and off-site contact numbers. Ideally, this means that you’ll have the work phone number, cell phone number, and pager number of each contact. It should be the responsibility of every individual on the phone roster to ensure that contact information is up to date. Chapter 40 1372 Chapter 40 Disaster Planning Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. aren’t resolved in 30 minutes, and level 3 contacts being called when issues aren’t resolved in 60 minutes. Note You should also have a priority system in place that dictates what types of incidents or outages take precedence over others. For example, you could specify that service-level outages, such as those that involve the complete system, have priority over an isolated outage involving a single server or application, but that suspected security incidents have priority over all other issues.  Post-action reporting Every individual involved in a major outage or incident should be expected to write a post-action report. This section details what should be in that report. For example, you would want to track the notifi cation time, actions after notifi cation, escalation attempts, and other items that are important to improving the process or preventing the problem from recurring. Every IT group should have a general policy with regard to problem resolution proce- dures, and this policy should be detailed in a problem resolution policy document or one like it. The document should be distributed to all relevant personnel throughout the organization, so that every person who has some level of responsibility for ensur- ing system and service availability knows what to do in case of an emergency. After you implement the policy, you should test it to help refi ne it so that the policy will work as expected in an actual disaster. Disaster Preparedness Procedures Just as you need to perform planning before disaster strikes, you also need to per- form certain disaster preparedness procedures. These procedures ensure that you are able to recover systems as quickly as possible when a disaster strikes and include the following:  Backups  Startup repair  Recovery disks  Startup and recovery options  Recovery Console Performing Backups You should perform regular backups of every Windows Server 2008 system. Backups can be performed using several techniques. Most organizations choose a combination of dedicated backup servers and per-server backups. If you use professional backup Note You should also have a priority system in place that dictates what types of incidents or outages take precedence over others. For example, you could specify that service-level outages, such as those that involve the complete system, have priority over an isolated outage involving a single server or application, but that suspected security incidents have priority over all other issues. Disaster Preparedness Procedures 1373 Chapter 40 Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. software, you can use one or more dedicated backup servers to create backups of other servers on the network, and then write the backups to media on centralized backup devices. If you use per-server backups, you run backup software on each server that you want to back up and store the backup media on a local backup device. By combining the techniques, you get the best of both worlds. With dedicated backup servers, you purchase professional backup software, a backup server, and a scalable backup device. The initial costs for purchasing the required equipment and the time required to set up the backup environment can be substantial. However, after the backup environment is confi gured, it is rather easy to maintain. Centralized backups also offer substantial time savings for administrators, because the backup process itself can be fully automated. With per-server backups, you use a backup utility to perform manual backups of indi- vidual systems. The primary tool for performing per-server backups is the Windows Server Backup utility, which is discussed in Chapter 41, “Backup and Recovery.” Because this tool is included with Windows Server 2008, there is no initial cost for implementation. However, because the backup options are fairly limited, the process may require more time than using centralized backup servers. Using Startup Repair Like Windows Vista, Windows Server 2008 has several automatic repair features. If the boot manager or corrupted system fi le is preventing startup, the Startup Repair wizard is started automatically and will initiate repair of the server. The Startup Repair wizard can be helpful if one or more of the following problems are preventing startup:  A virus infection in the master boot record  A missing or corrupt boot manager  A boot confi guration data store with bad entries  A corrupted system fi le Although Startup Repair typically runs automatically, you can manually initiate this feature using the Windows installation disc. For this reason, part of your recovery plan- ning should include ensuring that a Windows installation disc is available for each hardware architecture used in your server deployments. With a Windows installation disc, you can manually run Startup Repair by completing the following steps: 1. Insert the Windows installation disc for the hardware architecture and then boot from the installation disc by pressing a key when prompted. If the server does not allow you to boot from the installation disc, you may need to change fi rmware options to allow booting from a CD/DVD-ROM drive. Chapter 40 1374 Chapter 40 Disaster Planning Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. 2. If Windows Setup doesn’t start automatically, select Windows Setup (EMS Enabled) on the Windows Boot Manager menu to start Windows Setup. 3. On the Install Windows page, select the language, time, and keyboard layout options that you want to use. Click Next. 4. When prompted, do not click Install Now. Instead, click the Repair Your Computer link in the lower-left corner of the Install Windows page. This starts the System Recovery Options wizard. Keep the following in mind:  If the boot manager is damaged, the wizard will repair it at this point to obtain a list of available operating systems.  If a server has only one operating system, click Next to continue.  If your server has multiple operating systems, you’ll need to select the oper- ating system to use and then click Next.  If a server has multiple operating system and the operating system you want to use is unavailable, click Load Drivers to load the drivers for your server’s hard disks. 5. On the System Recovery Options page, click Command Prompt to access the MINWINPC environment. As discussed in Chapter 3, “Installing Windows Server 2008,” the mini Windows PC environment gives you access to the command-line tools listed in Table 3-5 on page 90. 6. At the command prompt, enter cd recovery to access the X:\Sources\Recovery directory. 7. At the command prompt, enter startrep to run the Startup Repair wizard. Follow the prompts to attempt to repair the server and enable startup. Getting Outside Help As part of your disaster planning you should plan for scenarios where you or another administrator are unable to recover a server and need help. A key part of this planning includes the escalation procedures discussed previously, where you contact more senior administrators when necessary. When escalation fails and you need to get a server back online, you may need to turn to outside help. Windows Server 2008 includes a facility for obtaining diagnostic information during setup and recovery, and then delivering this information to Microsoft Product Support. This diagnostic information comes from the Windows diagnostics and troubleshooting logs and can help diagnose problems that are preventing installation or recovery. To share troubleshooting information about the server with Microsoft Product Support, follow these steps: 1. Insert the Windows installation disc for the hardware architecture and then boot from the installation disc by pressing a key when prompted. If the server does not allow you to boot from the installation disc, you may need to change fi rmware options to allow booting from a CD/DVD-ROM drive. Disaster Preparedness Procedures 1375 Chapter 40 Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. 2. If Windows Setup doesn’t start automatically, select Windows Setup (EMS Enabled) on the Windows Boot Manager menu to start Windows Setup. 3. On the Install Windows page, select the language, time, and keyboard layout options that you want to use. Click Next. 4. When prompted, do not click Install Now. Instead, click the Repair Your Computer link in the lower-left corner of the Install Windows page. This starts the System Recovery Options wizard. Keep the following in mind:  If the boot manager is damaged, the wizard will repair it at this point to obtain a list of available operating systems.  If a server has only one operating system, click Next to continue.  If your server has multiple operating systems, you’ll need to select the oper- ating system to use and then click Next.  If a server has multiple operating system and the operating system you want to use is unavailable, click Load Drivers to load the drivers for your server’s hard disks. 5. On the System Recovery Options page, click Command Prompt to access the MINWINPC environment. As discussed in Chapter 3, “Installing Windows Server 2008,” the mini Windows PC environment gives you access to the command-line tools listed in Table 3-5 on page 90. 6. Insert a fl oppy disk into the server’s fl oppy disk drive or a USB fl ash drive into a USB port. This ensures that the disk or fl ash drive is available when you start the wizard. 7. Change directories to X:\Sources\Recovery by typing cd recovery. 8. Start the Microsoft Product Support Service wizard by typing psswiz at the command prompt. When the wizard starts, write down the contact information provided, including the support phone number. This information is different depending on your locale. 9. Select the drive letter of the fl oppy disk or fl ash device and then click Next to save the data. Remove the fl oppy disk or fl ash device. 10. On another computer that is started and connected to the Internet, insert the fl oppy disk or fl ash device and then contact Microsoft Product Support. Follow the instructions given to you by Microsoft Product Support. Note You don’t necessarily need to deliver this information to Microsoft Product Support. You can just as easily deliver this information to a senior administrator or a skilled technical expert on staff who is not in the offi ce currently or is located at another offi ce. On the fl oppy disk or fl ash device, the diagnostics fi les are created as standard text fi les. You can open these fi les in any text editor or easily add them to an e-mail message. Note You don’t necessarily need to deliver this information to Microsoft Product Support. You can just as easily deliver this information to a senior administrator or a skilled technical expert on staff who is not in the offi ce currently or is located at another offi ce. On the fl oppy disk or fl ash device, the diagnostics fi les are created as standard text fi les. You can open these fi les in any text editor or easily add them to an e-mail message. Chapter 40 1376 Chapter 40 Disaster Planning Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. [...]... available for use with Windows Server 2008 When selecting a backup utility, you’ll need to keep in mind the types of backups you want to perform and the types of data you are backing up Windows Server 2008 includes Windows Server Backup and backup command-line tools Windows Server Backup is a basic and easy-to-use backup and recovery utility When the related feature is installed on a server, you’ll find... a scheduled task that runs Windows Server Backup for you For Windows Server 2008, the task creation and scheduling processes are integrated into Windows Server Backup You can schedule automated backups using Windows Server Backup Click Backup Schedule on the Action menu or in the actions pane to start the Backup Schedule Wizard After scanning the available disks, Windows Server Backup starts the Backup... Features Wizard On the Select Features page, select Windows Recovery Disc and then select Windows Server Backup Features When you select Windows Server Backup Features, the Windows Server Backup and Command-Line Tools options are selected Click Next and then click Install When the wizard finishes installing the selected features, click Close From now on, Windows Server Backup will be available as an option... Procedures 1377 Other Windows Recovery Environment Features As long as the CPU architectures are the same, you can use any Windows installation disc to recover any server running Windows Server 2008 Once you access the Windows Recovery Environment by selecting the Repair Your Computer option, you can access the following tools: Windows Complete PC Restore Allows you to recover a server s operating sys-... storage needs, Windows Server Backup displays the backups that are available and the current disk usage information Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark Chapter 41 You can use Windows Server Backup to perform full, copy, and incremental backups on both local and remote systems You cannot use Windows Server Backup to perform differential backups Windows Server Backup... access The Windows Server backup and recovery tools are available for all editions of Windows Server 2008, including both 32-bit and 64-bit editions Although you cannot install the graphical components of these utilities on core installations, you can use the command line or manage backups remotely from another computer You install the Windows backup and recovery tools using Server Manager In Server Manager,... Review the backup status in Windows Server Backup Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark 1402 Chapter 41 Backup and Recovery Recovering Your Data Windows Server 2008 provides separate processes for system state recovery, full server recovery, and recovery of individual volumes and files and folders You use the Recovery Wizard in Windows Server Backup to recover non-system... fully restore your server using only the Windows backup tools Back up all volumes without application data if you want to be able to restore a server and its applications separately With this technique, you back up the server using the Windows tools and then back up applications using third-party tools or tools built into the applications You can recover a server fully using the Windows backup utilities... recover a server s operating system or perform a full system recovery by using a Windows installation disc and a backup that you created earlier with Windows Server Backup With an operating system recovery, you recover all critical volumes but do not recover non-system volumes If you recover your full system, Windows Server Backup reformats and repartitions all disks that are attached to the server Because... Your Data 1389 Figure 41-1 Getting started with Windows Server Backup When you use Windows Server Backup, the first backup of a server is always a full backup This is because the full backup process clears the archive bits on fi les so that Windows Server Backup can track which files are updated subsequently Whether Windows Server Backup performs subsequent full or incremental backups depends on the default . require more time than using centralized backup servers. Using Startup Repair Like Windows Vista, Windows Server 2008 has several automatic repair features the Windows Server Backup utility, which is discussed in Chapter 41, “Backup and Recovery.” Because this tool is included with Windows Server 2008, there