Quantum| Information Required for Troubleshooting (DRAFT) |
This topic identifies the logs required to troubleshoot PTT/NDMP issues. Some PTT/NDMP issues require increased logging to capture additional details in the NBU or DXi logs To increase the logging, you must enable debug in NBU and/or the DXi.
If DXi Advanced Reporting (DAR) is configured for auto upload on the Customer DXi, the link to DXi Advanced Reporting will take you to DXi Advanced Reporting Repository. Once in the repository locate the serial number of the Customer's DXi to display DAR data.
When enabling Debug for NDMP, make sure that you enable Debug for the duration of the duplication. Then disable it once the duplication has completed. Refer to Enable Debug and Gather DXi logs for details on enabling Debug for NDMP on DXi. Most of the messaging logged in the NDMP logs is keep-alive operations. However, when Debug is enabled, the message logging is increased, typically one hour's worth of NDMP operations will be captured with the default roll over settings for tsunami.log. To modify the default roll over settings refer to Enable Debug and Gather DXi logs.
All NDMP activity is captured in tsunami.log, most of the logging is for keep-alive operations. To quickly navigate the tsunami log it is important to define a time frame by using the stop and start time for a specific duplication job. The easiest way to get the stop and start time for a duplication job is to ask the customer to look at the job in the GUI.
NBU logging is more complex than with other products and can take some time to understand. For details about gather NBU logs, refer to Increase Log Level and Gather NBU Logs.
For NDMP issues, review the NBU logs listed below in the order shown:
Add content here.
This page was generated by the BrainKeeper Enterprise Wiki, © 2018 |