Chat now with support
Chat with Support

NetVault 13.0.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 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
Safe Mode in NetVault

Restarting a job

The Restart method lets you resume a backup from the point the job was stopped. To have this ability, you must configure the job as restartable.

The following plug-ins support this feature:

•
Plug-in for FileSystem: The Plug-in for FileSystem allows you to stop a backup job at any point and resume it later from the same point. To have this ability, you must configure the backup option Enable Restartable Backup for the job. For more information about this option, see the Quest NetVault Plug-in for FileSystem User’s Guide. When you stop the job, the plug-in generates an index for all items that have been processed up to that point and sets the job status to Job Stopped. When you restart the job later, the plug-in runs an Incremental Backup job to back up the remaining files and folders.
•
Plug-in for VMware: The Plug-in for VMware allows you to restart a job to back up only those virtual machines that failed previously. To have this ability, you must configure the backup option Enable Restartable backups for the job. For more information about this option, see the Quest NetVault Plug-in for VMware User’s Guide. When a restartable backup completes with some failed virtual machines, the plug-in generates an index for the completed virtual machines and sets the job status to Job Stopped. When you restart a job, the plug-in runs an Incremental Backup job to back up the failed virtual machines.
 
* 
NOTE: The Restart method does not work if you select multiple jobs simultaneously.
To restart a job:
1
In the Navigation pane, click Job Status.
2
In the list of jobs, select the stopped job, and click Restart.

Placing a job on hold

To prevent a scheduled job from running, you can place the job on hold. When you place a job on hold, its schedule is disabled until you resume the job.

To place a job on hold:
1
In the Navigation pane, click Job Status.
2
In the list of jobs, select the job, and click Hold Schedule.
3
In the confirmation dialog box, click OK.
When the schedule is suspended, the job shows a status of On hold in the Next runtime column.
 
* 
NOTE: If you restart NetVault, a job on hold remains in the same state, but it is rescheduled to run at its next scheduled time. If the job cannot be rescheduled because it was scheduled to run once and this time has now elapsed, the job status is set to Did not Run. Warning messages are generated in the NetVault Logs that describe why the job did not run.

Resuming a job

When you place a job on hold, its schedule is disabled until you resume the job. You can resume the scheduling of the job from the Job Status page.

To resume a job that was placed on hold:
1
In the Navigation pane, click Job Status.
2
In the list of jobs, select the job, and click Resume Schedule.
3
In the confirmation dialog box, click OK.
When the schedule is resumed, the Next runtime column is updated to display the date and time when the next instance is scheduled to run.

Determining the reason for "waiting for media" status

Determining the reason for “waiting for media” status

When a job is in Waiting for Media state, it implies that the job is unable to initiate data transfer as the target drive or media item is unavailable. The Diagnose Job method allows you to determine the exact reason for this state.

A job may be in the Waiting for Media state due to the following reasons:

•
The target media or device is in use by a different job.
•
The target device is offline.
•
The target media item is not loaded.
•
The Reuse Media option is not selected for the job. So, the job is waiting for new media.
•
No blank or reusable media item is available for the job.
To determine the exact reason for the “Waiting for Media” status:
1
In the Navigation pane, click Job Status.
2
In the list of jobs, select the job, and click Diagnose Job.
3
On the Diagnose Media Request page, you can view the following information:
•
Media Request ID: Media request ID.
•
Request Type: Backup or restore.
•
Status: Status of the media request.
•
Priority: Media request priority.
•
Client: NetVault Client on which the job is running.
•
Media: Target media and group label (if specified).
•
Reuse Media: The “Reuse Media” option is selected or not.
•
Required Space: Amount of space required on the media to complete the current request.
•
Ensure backup is the first on the target media: The “Ensure This Backup is First on the Media” option is selected or not.
•
Auto-Label: The “Label Blank Media Automatically” option is selected or not.
•
Mark Read-Only After: The “Mark Media Read-Only” option is selected or not.
•
Media Format: Media format.
•
Unload on Completion: Media to be unloaded after job completion or not.
•
Drives: Drive on which the tape resides.
•
Force Local: The “Local Drives Only” option is selected or not.
•
Network Compression: The “Network Compression” option is selected or not.
The Reasons table lists the reasons why the specified device or media cannot be used for the job. The following list provides some examples:
•
Not enough space.
•
Currently unavailable.
•
The 'force local drives' option is set. This type of device is considered network attached.
 
* 
NOTE: We recommend that you perform the steps described in this section and generate a log dump file when logging a case with Quest Technical Support.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating