Understanding Resource Monitoring Tool (RMT) and its data collection capabilities
Summary: RMT assists with NetWorker performance problem troubleshooting by capturing requested environment details about the machine on which it is running. The tool captures details about machine resource utilization such as CPU, Memory, I/O, and network operation. RMT captures the NetWorker process memory and CPU utilization, as well as NetWorker daemon response time. ...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Instructions
RMT
The Resource Monitoring Tool (RMT) collects utilization statistics of system and NetWorker related modules.
Description
RMT assists with NetWorker performance problem troubleshooting by capturing requested environment details about the machine on which it is running. The tool captures details about machine resource utilization such as CPU, Memory, I/O, and network operation. RMT captures the NetWorker process memory and CPU utilization, as well as NetWorker daemon response time.
Prerequisites
Required commands/utilities
The following utilities/commands are used to collect some of the data. If any of these are missing from the system, then RMT will not be able to collect the information provided by these commands.
On a Linux machine, "iostat" and "sar" utilities for capturing the I/O information.
The script captures the "pstack" output for NetWorker critical daemons for the Linux machine.
Required space
Ensure that you have enough disk space to run the script. The disk space requirement depends on how many days the script is continuously running, and on the interval time that is specified to capture the resource details. To conserve disk space, you may set larger interval in the NTT RMT GUI.
Windows Debugging Tool
Make sure that Windows Debugging Tool is installed on the machine where NetWorker Troubleshooting Toll is installed. Also make sure the path for Windows Debugging Tool is added to the Windows Environment variable PATH.
To make it permanent, add the path into the System's environment variables, and reboot.
1. Browse to Control Panel > System and Security > System > Advanced System Settings.
2. In the General tab click Environment Variables...
3. In System variables scroll to the Path variable
4. Click to select Path
5. Click edit
6. Append to the end of the "Variable value:" ;<path_to_cdb.exe>
7. Reboot the host
NetWorker .PDB files
Please contact NetWorker support and get NetWorker nonstripped binaries for your version. Copy these files to a local drive. These contain .pdb files and you will need to provide this path to the RMT tool when running 'daemon response' action.
Detailed Overview
You can use the RMT tool to capture information about any process and it will parse the collected details for these processes into a ".tsv" file for analysis using Excel.
Note: The RMT tool captures overall system CPU and memory as well as per-process CPU and memory for all processes.
The RMT tool captures following useful information:
Environment details on the machine where it is running, including CPU speed, number of CPUs, CPU arch, OS details, ulimit details, memory information, and system bus info.
The memory and CPU utilization details reported are for the processes that are selected from the UI.
Overall system CPU and memory utilization
Disk I/O statistics using the iostat command
IOPS details for all the configured disks
TCP LISTEN, WAIT, ESTABLISHED etc. for all TCP connections
Summary statistics for each network protocol such as TCP, IP for inte4 and inte6.
Overall number of "NetWorker" sessions running on NW server.
On a NetWorker server, the RMT tool captures the daemon response time for networker key daemons such as nsrexecd, nsrd, nsrjobd, nsrindex and nsrmmdbd.
If the response time for any of the critical daemon is >60 seconds, the tool captures the "pstack" details for that daemon during that time.
All *.tsv files provide resource utilization details that you can export directly to MS Excel file for plotting graphs.
Current Limitations
If "pstack" command is not installed, then script will not capture the pstack output for daemons.
Network utilization is currently captured only for Linux.
The tool runs on Windows 2008 and newer versions,
The Resource Monitoring Tool (RMT) collects utilization statistics of system and NetWorker related modules.
Description
RMT assists with NetWorker performance problem troubleshooting by capturing requested environment details about the machine on which it is running. The tool captures details about machine resource utilization such as CPU, Memory, I/O, and network operation. RMT captures the NetWorker process memory and CPU utilization, as well as NetWorker daemon response time.
Prerequisites
Required commands/utilities
The following utilities/commands are used to collect some of the data. If any of these are missing from the system, then RMT will not be able to collect the information provided by these commands.
On a Linux machine, "iostat" and "sar" utilities for capturing the I/O information.
The script captures the "pstack" output for NetWorker critical daemons for the Linux machine.
Required space
Ensure that you have enough disk space to run the script. The disk space requirement depends on how many days the script is continuously running, and on the interval time that is specified to capture the resource details. To conserve disk space, you may set larger interval in the NTT RMT GUI.
Windows Debugging Tool
Make sure that Windows Debugging Tool is installed on the machine where NetWorker Troubleshooting Toll is installed. Also make sure the path for Windows Debugging Tool is added to the Windows Environment variable PATH.
To make it permanent, add the path into the System's environment variables, and reboot.
1. Browse to Control Panel > System and Security > System > Advanced System Settings.
2. In the General tab click Environment Variables...
3. In System variables scroll to the Path variable
4. Click to select Path
5. Click edit
6. Append to the end of the "Variable value:" ;<path_to_cdb.exe>
7. Reboot the host
NetWorker .PDB files
Please contact NetWorker support and get NetWorker nonstripped binaries for your version. Copy these files to a local drive. These contain .pdb files and you will need to provide this path to the RMT tool when running 'daemon response' action.
Detailed Overview
You can use the RMT tool to capture information about any process and it will parse the collected details for these processes into a ".tsv" file for analysis using Excel.
Note: The RMT tool captures overall system CPU and memory as well as per-process CPU and memory for all processes.
The RMT tool captures following useful information:
Environment details on the machine where it is running, including CPU speed, number of CPUs, CPU arch, OS details, ulimit details, memory information, and system bus info.
The memory and CPU utilization details reported are for the processes that are selected from the UI.
Overall system CPU and memory utilization
Disk I/O statistics using the iostat command
IOPS details for all the configured disks
TCP LISTEN, WAIT, ESTABLISHED etc. for all TCP connections
Summary statistics for each network protocol such as TCP, IP for inte4 and inte6.
Overall number of "NetWorker" sessions running on NW server.
On a NetWorker server, the RMT tool captures the daemon response time for networker key daemons such as nsrexecd, nsrd, nsrjobd, nsrindex and nsrmmdbd.
If the response time for any of the critical daemon is >60 seconds, the tool captures the "pstack" details for that daemon during that time.
All *.tsv files provide resource utilization details that you can export directly to MS Excel file for plotting graphs.
Current Limitations
If "pstack" command is not installed, then script will not capture the pstack output for daemons.
Network utilization is currently captured only for Linux.
The tool runs on Windows 2008 and newer versions,
Additional Information
- For Windows, the RMT tool creates a Perf counter automatically and captures CPU and memory utilization details for the processes listed in NTT RMT GUI and for the overall system.
- IOPS are captured based on the interval specified in the NTT RMT GUI
Article Properties
Article Number: 000158481
Article Type: How To
Last Modified: 13 Apr 2021
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.