Chat now with support
Chat with Support

NetVault SmartDisk 11.4.5 - Administration Guide

Introducing NetVault SmartDisk Integrating NetVault SmartDisk with your backup product Using the command-line interface (CLI) Configuring NetVault SmartDisk Monitoring performance Troubleshooting

Using resource management

Based on how you configure it, the resourcemanager can check the trace files every minute after NetVault SmartDisk starts. The resourcemanager reads the configured values at the start of every repeat cycle, for example, every minute, which ensures that it reads configuration changes that are made while the process is running.

Using the Modules section in the /foundation/etc/resourcemanager.cfg file and the ResourceManagement:TraceDelete section in each module’s /etc/trace.cfg file, you can specify which modules you want the resourcemanager to monitor and manage.

In the following example, the resourcemanager is set to manage the diskmanager, dedupe, and foundation modules.

NetVault SmartDisk creates several types of trace file, *.trc, *.buffer, *monitorrecent*.txt, and *monitortrace*.txt, but only certain ones are eligible for deletion by the resourcemanager. Understanding the naming convention applied to these files is critical, because it is key to how the resourcemanager determines what to include or exclude from its eligible list. The following table identifies the naming convention used for the different files and the different platforms.

*.trc

<processName>.<processID>.<threadID>.<sequenceNumber>.trc

*.buffer

<processName>.<processID>.<threadID>.buffer

*monitorrecent*.txt

On Linux, UNIX, and Mac OS X:

  monitorrecent.<processID>.<sequenceNumber>.txt

Windows:

  monitorrecent.<sequenceNumber>.txt

*monitortrace*.txt

On Linux, UNIX, and Mac OS X:

  monitortrace.<processID>.<sequenceNumber>.txt

Windows:

  monitortrace.<sequenceNumber>.txt

The resourcemanager only considers trace files as contributing to the totals it compares against the start and stop thresholds if it identifies them as inactive; if the files are inactive, it indicates that they are not associated with a process that is running. It determines this state by comparing the process ID in the trace filename with the list of IDs for processes that are running on the system at the start of each repeat cycle. Because the process ID is not used in the filename on all operating systems, the resourcemanager can delete *.trc, *.buffer, monitorrecent*, and monitortrace* files on Linux, UNIX, and Mac OS X, but it can only delete *.trc and *.buffer files on Windows, as shown in the preceding table.

Specifying which modules to manage

2
Using a text editor, open the resourcemanager.cfg file:
This file is at: …/foundation/etc/resourcemanager.cfg
3
Locate the [Trace:Delete] section.
4
In the Modules = line, enter the applicable modules.

Configuring the Trace-Delete option in specific modules

To limit the overall number or size, or both, of trace files in an installed module's trace directory, you can configure the resourcemanager to delete them between start and stop number and size thresholds. You can set these thresholds through the ResourceManagement:TraceDelete section of a module's etc/trace.cfg file. If that section is not present or is invalid, hard-coded defaults are used.

The ResourceManagement:TraceDelete section in the <moduleName>/etc/trace.cfg file lets the resourcemanager determine which trace-delete parameters to apply in the specified module. The defaults are:

If you change the values and inadvertently render them unacceptable, not present or invalid, the hard-coded defaults are used instead.

In the preceding example, which shows the defaults, the Trace-Delete functionality is enabled, and the resourcemanager starts deleting the trace files, oldest first, that exist in the specified module’s /trace directory when their combined number becomes equal to or greater than 100 or their combined size becomes equal to or greater than 1 GB. The files continue to be deleted until their combined number is reduced to 10 or their combined size reaches or exceeds 1 MB.

To modify the values, perform the following steps.

2
Using a text editor, open the trace.cfg file for the applicable module:
This file is at: …/<moduleName>/etc/trace.cfg
3
Locate the [ResourceManagement:TraceDelete] section.
4
Change the values for the Number Start Threshold, Number Stop Threshold, Size Start Threshold, and Size Stop Threshold values as appropriate.

Number Start Threshold

1

2147483647

Number Stop Threshold

0

2147483647

Size Start Threshold

1

2147483647

Size Stop Threshold

0

2147483647

For both types of threshold, Number and Size, the start threshold must be greater than the stop threshold.
The Size threshold entries must use the form <number>,<byteUnit>. The following byte units are acceptable:

B

Bytes

KB

Kilobytes

MB

Megabytes

GB

Gigabytes

TB

Terabytes

Disabling trace deletion

You can disable trace deletion for all modules or on an individual basis.

2
Using a text editor, open the resourcemanager.cfg file.
This file is at: …/foundation/etc/resourcemanager.cfg
3
In the [Trace:Delete] section, delete the value for the Modules = segment; that is, verify that it is blank:
2
Using a text editor, open the trace.cfg file for the applicable module:
This file is at: …/<moduleName>/etc/trace.cfg
3
In the [ResourceManagement:TraceDelete] section, change the value for the Enabled segment to FALSE:
Related Documents