Chat now with support
Chat with Support

NetVault 13.0.1 - Administration Guide for Managed Service Providers

Introduction Getting started Configuring clients Managing catalog search Configuring storage devices
About storage devices SAN considerations Quest DR Series systems Quest QoreStor 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
Role-based access to manage 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 Managing Tenant 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 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 Safe Mode in NetVault

Adding a non-policy job to a policy

You can add a non-policy job to an existing policy.

To add a non-policy job to an existing policy:
1
In the Navigation pane, click Manage Job Definitions.
2
In the list of available job definitions, select the non-policy job, and click Add to Policy.
3
Select a policy on the Select Policies dialog box. Click OK.
 
* 
NOTE: Adding a non- policy job configured on a client which is associated to a selected policy adds the same job ID in the policy. However, adding a non-policy job configured on a client which is not associated to a selected policy adds a new job with same job name, job definition, and different job ID in the policy.
The following example describes adding a non-policy job (BackupJob) with Job ID (69) configured on a client (Client-D) which is not associated to a selected policy (Policy1) and includes two backup jobs on three clients (Client-A, Client-B, and Client-C):
a
In the list of available job definitions, select the non-policy job ‘BackupJob’ and click Add to Policy.
b
In the Select Policies dialog box, select the policy name ‘Policy1’.
c
Click OK.
d
New backup jobs with the name ‘BackupJob’ and Job ID as 70, 71, and 72 for each client in the selected policy ‘Policy1’ will be added as shown below:
 
Job Name
Job ID
Client Name
Policy Name

BackupJob

69

Client-D

 

BackupJob

70

Client-A

Policy1

BackupJob

71

Client-B

Policy1

BackupJob

72

Client-C

Policy1

Viewing job history

You can view the completed jobs from the Job History page. The page shows all the instances that have run for the jobs. When viewing job history, you can use one or more filters to display jobs that match the specified criteria. Respective users can view job history for their created jobs.

To view job history:
1
In the Navigation pane, click Job History.
2
On the Job History page, you can view the job history records that are available in the NetVault Database.
 
* 
NOTE: You can also access this page from the Job Status page. You can select a job on the Job Status page, and click View history to view all past instances for that job.
The table displays the following default information:
•
Job Title: Name or title of the job.
•
End Time: Job completion time.
•
Job ID: Job ID number (also shows the instance ID number and phase ID number).
•
Job Type: Backup or restore.
•
Plugin: Name of the plug-in used to perform the job.
•
Selection Set: Backup or Restore Selection Set.
•
Client: Name of the NetVault Client for which the job was performed.
•
Status: Status (Succeeded, Failed, Aborted, and others).
You can add or remove the following columns in the list using the column menu:
•
Duration: Displays the time (hours: minutes: seconds) to complete the operation (back up, restore, and reporting)
•
Policy Name: Displays the name of the backup policy.
The row background color in the table is displayed for a job based on run status. For more information, see Job activity table.
3
By default, the table is sorted by End Time (descending order).
You can sort the table by one or more columns, as required. For more information, see Sorting records in NetVault WebUI.
To set the filter options (For more information on table filter options for Job History page, see Table 12), view the page size setting, column sort order, applied filters in the table, export the records, or edit table settings, click the icons at the lower- right corner of the table.
For more information, see Customizing tables in NetVault WebUI.
4
You can use the Search option to filter the table data and quickly find entries that contain the specified string in any column values. You can also include wildcards (“?” or “*”) in the search filter string.
5
The Job History page loads a maximum of 10,000 records initially. The total number of records fetched is displayed at the lower-right corner of the table.
You can click Load more to load the next set of records, if available. Each load action fetches a maximum of 10,000 records. This button is disabled if there are no more records to load.
6
To perform a job-related task, click the corresponding button in the Operations pane. Alternatively, click a link in the Navigation pane to open a different page. If the job is associated with a policy, clickManage Job to open the Manage Jobs page and make changes to the policy.

Monitoring logs

•
About NetVault logs
•
Viewing log messages
•
Downloading logs
•
Exporting logs
•
Manually purging the log messages
•
Setting up a user-defined log event
•
Searching the knowledge base

About NetVault logs

About NetVault logs

All NetVault processes generate log messages to provide information about the status of various operations and report error conditions. These messages are stored in the NetVault Database. You can view the log messages from the View Logs page.

NetVault uses the Logging Daemon to manage and write the log messages to the database. The Logging Daemon runs on the NetVault Server.

Log messages contain information that can be used for diagnosing and troubleshooting problems. When you report a problem, Quest Technical Support might request you to provide the log dump file. You can use the Download or Export method available on the View Logs page to generate the log dump file. For more information, see Downloading logs or Exporting logs.

 
* 
NOTE: NetVault also provides diagnostic tracing capabilities to collect detailed information about error conditions. This information is used for debugging and troubleshooting purposes.

Unlike logging, tracing is disabled by default. When investigating a problem, Quest Technical Support may request you to enable tracing on the server or client machines.

Diagnostic information is written to trace files. Each process generates its own trace file. By default, trace files are stored in the trace-container directory under the NetVault installation directory. For more information, see Diagnostic tracing.

Log messages that are older than 30 days are automatically purged from the database. You can use the configuration settings for Logging Daemon to change the maximum age for log messages. You can also manually delete the log messages by using the Purge Logs method available on the View Logs page.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating