Netherlands: Software

Introductie Windows Server 2016

Issue link: http://hub-nl.insight.com/i/692748

Contents of this Issue

Navigation

Page 29 of 173

22 C H A P T E R 2 | Compute [=== Microsoft-Windows-ClusterAwareUpdating/Admin logs ===] All events from the Microsoft-Windows-ClusterAwareUpdating/Admin channel that gives you information about Cluster Aware Updating [=== Microsoft-Windows-FailoverClustering/DiagnosticVerbose ===] This is actually a new event channel that gives you the similar output as Debug Level 5 for a Cluster Log without having to set it. You can use this information to get deeper into the calls and goings on with the cluster and gives it in a more verbose output. [=== Cluster Logs ===] This is the output that you normally see in a cluster log. Clearly, there is a lot to this log now. Using this one log can reduce the time you spend looking for information or trying to resolve an issue. Instead of having to review three or more files that might be loaded in three different applications with their own formats, you now need only review one file. The other useful thing about the log is that if you generate it with no switches, everything in an event channel (for example, the System Event) is shown. So you can actually get any history pertaining to a particular problem. In cases for which you can reproduce an error condition and do not need all of the history, you can generate a log for the past five minutes (TimeSpan=5). Helpfully, the new cluster log uses this same five-minute time span for all of the event channels and gives you only those, so you don't need to deal with an unnecessarily large file. Active memory dump Another new feature as it relates to diagnostics is the ability to capture memory dumps. Imagine that you have a big Hyper-V cluster and each of the nodes has 512 GB of memory. If the node is having an issue and you create a memory dump that contains both user and kernel mode memory, that memory dump is going to be over 512 GB. Trying to work with a file that size can be a nightmare. First, you need to ensure that you have a drive with enough free space to hold a file of that size. You then need to spend hours zipping, uploading, and unzipping before you can even begin to open it. If the problem is with the host server itself and you are running VMs that use 500 GB of that memory, this is information that you don't need, because it does not pertain to the host. Because of this, there is a new dump setting called Active Memory Dump. This setting captures only the memory that the host is actually using. If the host is actively using only 5 GB of memory, a 5-GB memory dump is what will be created. This smaller dump is much easier to parse than the 512-GB file in the previous scenario. The Active Memory Dump option is in the same location as the normal dump settings, in the Startup And Recovery dialog box of the System Properties, as shown in Figure 2-11.

Articles in this issue

Archives of this issue

view archives of Netherlands: Software - Introductie Windows Server 2016