Viewer Provides logs for transactional reactive reviews of system and service events. It is automatically installed with Windows Server 2003. Start > Control Panel > Administrative Tools > Event Viewer Or to open Event Viewer using the command line: >Run. In the Open box, type eventvwr.msc and then click OK. System Monitor (formerly known in Microsoft Windows® 2000 as Performance Monitor) Provides detailed performance information on key metrics used to troubleshoot bottlenecks and degradation. It is automatically installed with Windows Server 2003. Start, > Control Panel > Administrative Tools > Performance Or to open System Monitor using the command line: Start > Run. In the Open box, type perfmon and then click OK. Task Manager Offers an immediate view of system activity and performance. This technology is automatically installed with Windows Server 2003. Right-click an empty space on the taskbar, and then click Task Manager. Service Controller (Sc.exe) Allows for general management of Windows services, including startup, shutdown, and status. \windows\system32\ sc.exe Or to open Service Controller the command line: Start > Run. In the Open box, type sc and then click OK. Netsh (Netsh.exe) Manages network services and configuration objects. Or to open using the command line: Start > Run. In the Open box, type netsh and then click OK. Windows Server 2003 Resource Kit Tools Provides operations tools, scripts, and shortcuts to add and automate administrative functionality for Windows Server 2003. This kit is a separate installable package. , or search for “Windows Server 2003 Resource Kit Tools” at .
Procedure 2: Restoring from backup standard primary zone 1. Build and configure a stand-alone Windows Server 2003 server with hardware configuration as close as possible to that of the production server. 2. Ensure that the server is not connected to the production network. (Many organizations maintain a standing DR lab environment that has been isolated from the networks it supports.) 3. Restore the system state for a stand-alone Windows Server 2003 server or perform the tasks necessary for a normal Active Directory restore if the server is a domain controller. 4. Restore the DNS zone that were backed up in "Task: Create DNS backup and pull backup files to remote storage.” 5. Validate restore by testing DNS functionality. the restored service is in a DR lab environment, the server may not retain full functionality. Where functionality is not testable, check the configuration items—such as the forwarder IP addresses—against production DNS servers. Dependencies Scheduled zone file and system state backups are being performed. Technology Required ● DR lab or similar equipment ● Backup Operating Quadrant Storage Management SMF Operations Role Cluster Weekly Process: Storage resource management Description Storage resource management (SRM) is a key storage management activity focused on ensuring that important storage devices, such as disks, are formatted and installed with appropriate DNS systems. In addition, SRM includes using management technologies to monitor storage resources to ensure that they meet availability, capacity, and performance requirements. Task: Monitor disk space for DNS logs and database Purpose This task ensures that the DNS zone files can grow as appropriate. Because of the relatively small size of zone files, DNS server disk space is normally not an issue. DNS debug logging is disk-resource intensive. Before enabling and configuring DNS debug logging, review disk availability.
2. On the left-tree view, expand the Performance Logs and Alerts branch and Counter Logs. The view in the right pane will display all log settings. 3. Right-click Counter Logs, and select New Log Settings. 4. a name such as “DNS Server Load and Util,” and click OK. 5. the Add Counter button; this will bring up the Add Objects dialog box. 6. Verify that the applicable DNS server is listed in the Select counters from computer: pull-down box. 7. Verify that the Select counters from list: radio button is selected. 8. In the Performance Object pull-down box, select Processor. 9. Click %Processor Time, %Privileged Time, and %User Time from the counters and choose the _Total instance. 10. Click Add. 11. Verify that the new counter was to the logging. (The Add Counters window may be blocking the previous DNS Server Load and Util window.) 12. In the Performance Object pull-down box, select Process. 13. Click %Processor Time, Private Bytes, and Page File Bytes from the counters and choose dns as the instance. 14. Click Add. 15. Verify that the new counter was to the logging. (The Add Counters window may be blocking the previous DNS Server Load and Util window.) 16. In the Performance Object pull-down, select Memory. 17. Click Available Bytes, Pages Input/sec, Pages Output/sec, Page Reads/sec, and Page Writes/sec. There are no instances associated with these counters. 18. Click Add. 19. Verify that the new counter was to the logging. (The Add Counters window may be blocking the previous DNS Server Load and Util window.) 20. In the Performance Object pull-down, select PhysicalDisk. 21. Click Current Disk Queue Length from the counters and choose _Total as the instance. 22. Click Add. 23. Verify that the new counter was added to the logging. (The Add Counters window may be blocking the previous DNS Server Load and Util window.) 24. In the Performance Object pull-down, select Network Interface. 25. Click Bytes Total/sec and choose the appropriate interface instance(s) utilized by the DNS server.