First published on TechNet on Aug 01, 2016
This blog post brought to you by eighteen year veteran Microsoft Premier Field Engineer David Morgan.
Goal of this Post
Over the years my customers have asked about what they should do first when they get a trouble ticket for a misbehaving Windows failover cluster. There are some fairly simple steps one can take first that can provide a host of benefits during the troubleshooting process like:
This particular post isn't about doing actual troubleshooting. Here I'm only going to go into the primary steps one should take before undertaking in-depth troubleshooting activities. Actual troubleshooting scenarios and details will follow in future posts where you'll see why having captured these resources in the beginning can make your IT life a bit better. Summary
If this is not done within ~72 hours (varies) the data logged about your problem event will be overwritten when the log wraps. In almost all cases if the cluster log is not available for the time of the event a reliable root cause cannot be provided.
Finally , store all these files in case you later work with a Microsoft support engineer. You'll be amazed at how much faster your support call can go if you already have this data collected and ready to upload to your support vendor.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.