tailieunhanh - Khám phá windowns server 2008 - p 44

Tránh sử dụng quá nhiều quầy. Một số quầy rất tốn kém trong việc đánh thuế một máy chủ cho tài nguyên hệ thống và có thể làm tăng chi phí của hệ thống. Giám sát một số hoạt động tại một thời gian cũng trở nên khó khăn. . Sử dụng các bản ghi thay vì đồ thị hiển thị. Các bản ghi sau đó có thể được nhập khẩu vào một cơ sở dữ liệu hoặc báo cáo. Các bản ghi có thể được lưu trên đĩa cứng không được giám sát hoặc phân tích. . | 410 13 Debugging and Problem Solving the Hyper-V Host and Guest Operating System Avoid using too many counters. Some counters are costly in terms of taxing a server for system resources and can increase system overhead. Monitoring several activities at one time also becomes difficult. Use logs instead of displaying graphs. The logs can then be imported into a database or report. Logs can be saved on hard disks not being monitored or analyzed. Important Objects to Monitor The numbers of system and application components services and threads to measure in Windows 2008 are so extensive that it is impossible to monitor thousands of processor print queue network or storage usage statistics. Defining the roles a server plays in a network environment helps to narrow down what needs to be measured. Servers could be defined and categorized based on the function of the server such as application server file and print server or services server such as DNS domain controller and so on. Because servers perform different roles and hence have different functions it makes sense to monitor the essential performance objects. This helps prevent the server from being overwhelmed from the monitoring of unnecessary objects for measurement or analysis. Overall four major areas demand the most concern memory processor disk subsystem and network subsystem. They all tie into any role the server plays. The following list describes objects to monitor based on the roles played by the server Domain controller Because the DC provides authentication stores the Active Directory database holds schema objects and so on it receives many requests. To be able to process all these requests it uses up a lot of CPU resources disks memory and network bandwidth. Consider monitoring memory CPU system network segment network interface and protocol objects such as TCP UDP NBT NetBIOS and NetBEUI. Also worth monitoring are the Active Directory NTDS service and site server LDAP service objects. DNS and WINS also