Tchater maintenant avec le support
Tchattez avec un ingénieur du support

NetVault 13.2 - Administration Guide

Introduction Getting started Configuring clients Managing catalog search Configuring storage devices
About storage devices SAN considerations Quest DR Series systems Quest QoreStor Object storage NetVault SmartDisk EMC Data Domain Systems Snapshot Array Manager Virtual Tape Libraries Virtual standalone drives Shared Virtual Tape Libraries Physical tape devices Storage tiers
Backing up data Managing policies Restoring data Managing NetVault dashboard Managing jobs Monitoring logs Managing storage devices
Monitoring device activity Managing disk-based storage devices in list view Managing disk-based storage devices in tree view Managing the Snapshot Array Manager Managing tape libraries in list view Managing tape libraries in tree view Managing tape drives in list view Managing tape drives in tree view Adding shared devices
Managing storage media Managing user and group accounts Monitoring events and configuring notifications Reporting in NetVault Working with client clusters Configuring default settings for NetVault
About configuring default settings Configuring encryption settings Configuring plug-in options Configuring default settings for post-scripts Configuring default settings for Verify Plug-in Configuring Deployment Manager Settings Configuring Job Manager settings Configuring Logging Daemon settings Configuring Media Manager settings Configuring Network Manager settings Configuring Process Manager settings Configuring RAS device settings Configuring Schedule Manager settings Configuring Web Service settings Configuring Auditor Daemon settings Configuring firewall settings Configuring general settings Configuring security settings Synchronizing NetVault Time Configuring default settings for global notification methods Configuring the reporting utility Configuring NetVault WebUI default settings Configuring NetVault to use a specific VSS provider Configuring default settings using Txtconfig
Diagnostic tracing Managing diagnostic data Using the deviceconfig utility NetVault processes Environment variables Network ports used by NetVault Troubleshooting
Common errors
NetVault Service fails to start on Windows NetVault Service fails to start after the machine is restarted NetVault Service starts, but stops immediately on Linux Login fails after any change in the server IP address Unexpected behavior of NetVault WebUI WebUI does not run in Compatibility View in Internet Explorer NetVault installer fails during push installation VSS-based backup fails Modifying TCP/IP socket buffer size on Windows Restores using Data Copy savesets fail on clients running NetVault 10.0.1 Restore fails on Itanium platforms if the index is larger than 2GB After upgrade, Data Copy and Consolidated backup job on Linux fails After upgrade, console error is displayed on WebUI pages Deployment task hangs on target Linux machine during push installation. Unable to add package store with hostname. Deployment task fails due to network configuration issues. Domain user is unable to login NetVault Server if the workstation attribute is set. Domain user is unable to login NetVault Server on Debian 9. Adding the target machine as a client fails, after successful push installation. Unable to install, uninstall or navigate catalog search page after manually uninstalling NetVault Client Host. Unable to install, uninstall catalog search on client after NetVault Server migration with the same or different server name External Azure AD user cannot add an external Azure AD user to NetVault Server Failed to verify target Windows machine from a Linux-based NetVault Server NetVault is unable to send reports as an email attachment in PDF format on RHEL 5.x platform Restore fails on NetVault Database backup When using RDA for backups, only four streams are used at once Unable to create large VTL on Linux Browsing a folder with a large number of files times out Push installation failed on Linux
Safe Mode in NetVault

About diagnostic tracing

Diagnostic tracing is used to capture detailed information about error conditions. Quest Technical Support personnel use this information for debugging and troubleshooting purposes.

Tracing is disabled by default. To capture diagnostic information, you must enable tracing on the relevant NetVault machines. You can configure NetVault to start tracing immediately or when the service restarts. You can also specify a time window to automatically start and stop tracing at the specified time.

Diagnostic information is written to trace files. You can generate trace files for all processes or a subset of processes. These files are generated on the machine where the selected processes are running. NetVault uses a Trace Container directory to store all trace files generated during various sessions. By default, the trace container directory is created under the NetVault installation directory. You can modify the default settings to specify a new location for the container directory. When tracing is enabled, a session directory is created under the container directory; all trace files generated during the session reside in this directory. You can use the WebUI to download trace files from various machines to the local machine where the WebUI is running.

Managing trace filters

NetVault 11.2 or later allows you to manage trace filters to NetVault processes (core and plug-in) from the NetVault WebUI. You can change/ assign trace settings for these processes using the option Manage Trace Filters.

For the NetVault Server: On the NetVault Server Settings page, under System and Security, click Diagnostic Tracing.
For the NetVault Client: On the NetVault Server Settings page, click Clients. In the NetVault Clients table, select the client, and click Next. Under System and Security, click Diagnostic Tracing.
3
In the Diagnostic Trace Settings page, click Manage Trace Filters.
5
In the Edit Trace Filter Mapping dialog box, configure the following settings:

Selected Process

Selected NetVault process (core and plug-in) is displayed.

Filter

Click the down arrow and select any of the following filter options:

KillAll: When this filter is assigned to a process, the process will not generate any traces.
MessageOnly: If this filter is assigned to a process that process will only produce trace messages from MESSAGE module. All other trace messages will be filtered out.

Specify the following trace filter mapping options for the selected process:

Enable Filter: Select this option to enable the selected filter option for the selected process.
Force Disk Tracing: Select this option to allow the selected process to trace the disk (even when disk tracing is disabled).
Circular: Select this option to enable circular tracing and type or select the values in the following fields:
Lines per trace file: Number of lines per trace file when circular is enabled. When lines in a trace file exceed this threshold, traces are written to next trace file.
Number of trace files to keep: Number of trace files to keep when circular is enabled. When number of trace files exceed this threshold, oldest trace file will be overwritten.
6
Click Update to apply the new settings and close the dialog box.

Enabling tracing

Diagnostic tracing is disabled by default. When investigating a problem, Quest Technical Support might ask you to enable tracing on the relevant NetVault machines to capture diagnostic information about the error condition. This information helps in determining the source of error condition. Once the traces are enabled for the server, warning is displayed as Diagnostics in the Header Pane of NetVault.

fFor the NetVault Server from Change Settings: On the NetVault Server Settings page, under System and Security, click Diagnostic Tracing. On the Diagnostic Trace Settings page, click Enable Tracing.
For the NetVault Client from Change Settings: On the NetVault Server Settings page, click Clients. In the NetVault Clients table, select the client, and click Next. Under System and Security, click Diagnostic Tracing. On the Diagnostic Trace Settings page, click Enable Tracing.
On the Manage Clients page, select the Trace Status check box or click Enable Tracing
On the Manage Clients page, select the client, and click Enable Tracing.
3
In the Trace Enable Options drawer, configure the following settings.
IMPORTANT: When you select multiple clients, the Trace Enable Options drawer does not show the list of process names. You can either use the All current and future processes option, or provide the process ID list in the associated box.

Enable Tracing

Select one of the following options:

Immediately: This option is selected by default. To start tracing immediately, use this option.
At service startup: To enable tracing at service startup, select this option.
NOTE: You can also enable tracing at service startup by clicking Trace Configuration on the Diagnostic Trace Settings page, and selecting the Enable trace on service startup check box in the Trace Configuration Options dialog box.
At a certain time: To automatically start and stop tracing at specified times, select this option, and specify the time window:
- Starting at: Select this check box, and type or select the date and time when tracing should be started on the machine.
- Stopping at: Select this check box, and type or select the date and time when tracing should be stopped on the machine.

Create Trace for

Specify the processes for which trace files are required:

All current and future processes: This option is selected by default. To generate trace files for all current and new processes, use this option.
Specific processes: To generate trace files for specific processes, select this option.
IMPORTANT: Trace settings do not persist across restarts of NetVault Service unless you have selected the At service startup or Enable trace on service startup options. In such cases, tracing is enabled on all processes.
4
Click Apply to apply the settings and close the drawer.

Downloading trace files

Trace files are generated on the machines where the selected processes are running. You can use the WebUI to download trace files from various machines to the local machine where the WebUI is running.

From the NetVault Server: On the NetVault Server Settings page, under System and Security, click Diagnostic Tracing.
From the NetVault Client: On the NetVault Server Settings page, click Clients. In the NetVault Clients table, select the client, and click Next. Under System and Security, click Diagnostic Tracing.
4
Click Download, and in the confirmation dialog box, click OK.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation