in Visual C#.NET

Generate Code39 in Visual C#.NET

17

Managing and Maintaining a Server Environment (4.0)

B. Correct: Moving the problematic Web site to its own application pool will insulate the other Web sites from crashes. Each application pool functions independently of the others, and the health of one does not directly affect the health of others. C. Incorrect: Creating a new host header will not solve the problem. Moving the problematic Web site to its own application pool is the best solution D. Incorrect: Limiting the kernel request queue will not solve this problem. Moving the problematic Web site to its own application pool is the best solution.

Correct Answers: A, B, D A. Correct: Backing up the system state data backs up the IIS metabase. This backs up all Web site configurations. B. Correct: Running iisback /backup from the command prompt will back up all Web site configurations. C. Incorrect: This might back up some Web site data, but not configuration information. D. Correct: Using the Backup/Restore IIS configuration context option of the IIS node of the Computer Management Console will back up the IIS metabase and hence all Web site configurations.

18 Managing and Implementing Disaster Recovery (5.0)

Disasters will occur. Disks will fail, files will be lost, and power supplies will fuse with a puff of smoke, a few sparks, and an acrid smell. Systems administrators should not wait for a disaster to occur before deciding on a course of action. Before disaster strikes, administrators should have planned and put in place the procedures that will restore system functionality as soon as possible. The first step in protecting data stored on Windows Server 2003 systems is to ensure that it is backed up correctly. Windows Server 2003 has a built-in backup application that enables the administrator to perform the vast majority of backup tasks. Critical systems should be backed up every 24 hours, or more often in some cases. Backups can be written to several forms of media. Windows Server 2003 also has a feature called Automated System Recovery (ASR) that is new to the server line of products. ASR can be used to restore a completely nonfunctional system to working order. ASR stores some configuration information on a special disk and other configuration information within the ASR backup set. ASR only restores a system; it will not restore data that is stored on the system. Stored data must still be backed up in the normal manner. Emergency Management Services (EMS) is another new tool that administrators can use to manage a server or recover from hardware failure. EMS allows you to manage a server through a null-modem cable connected to a computer s COM port. The EMS interface is text-based but will allow management of the server when the server s Transmission Control Protocol/Internet Protocol (TCP/IP) stack has failed or the server has encountered a STOP error. Depending on the severity of the failure, it might be possible to use EMS to shut down a problematic process, reconfigure an IP address, or even run command-line utilities such as NTBACKUP. It is also important for an administrator to understand how to repair a fault-tolerant volume set up within the Disk Management console if a disk happens to fail. The process for restoring a mirrored volume is different from that of restoring a RAID-5 volume. Administrators should test their fault-tolerant configurations, disabling disks to check that the server remains operational if a disk fails. Finally, the ability to restore files and folders correctly from backup sets is also important. In general, if incremental or differential backups are used, restore first from the older backup set and then overwrite with data from the newer backup set.

18-1

18-2