NetVault 13.0 - Administration Guide

Failed to verify target Windows machine from a Linux-based NetVault Server

When trying to verify a Windows target machine from a Linux-based NetVault server during the creation of a deployment task, the verification fails, even with valid credentials.

While verifying the target machines, the following errors displayed:

This issue occurs when the kerberos on the Linux Server machines is not properly configured. Check /etc/krb5.conf for a valid default_realm.

This issue also occurs when the kerberos ticket is expired for the user. To renew the ticket, run the following command on the Linux NetVault server:

Successful execution of the command should result in successful verification for the specified user.

NetVault is unable to send reports as an email attachment in PDF format on RHEL 5.x platform

The ability to generate a PDF requires components that are not available on RHEL 5.x platforms.

When attempting to send a report as a PDF from a RHEL 5.x platform, the PDF does not generate.

To send the report as an email attachment in HTML format, complete the following steps:

Restore fails on NetVault Database backup

On Windows 2012, the Plug-in for Databases fails to restore a NetVault Database backup that is stored in a NetVault SmartDisk device.

When restoring from a DAV device, the restore fails, but only when NetVault is run as a service.

If the NetVault Database backup is stored in NetVault SmartDisk, stop the NetVault Service and run the service in “user space” (that is, nvpmgr debug) before starting the restore job.

When using RDA for backups, only four streams are used at once

When using RDA to back up 20 or more clients, in device activity, only four streams are used at once. Updating the setting in the configuration file at /config/dellrda config file from 32 streams to 512 streams and restarting NetVault services, yields the same result.

When multiple backup jobs that target the same disk-based storage device are scheduled to start at the same time or within a small window of time, the following issues occur:

These issues occur because the Media Manager uses a “quiesce time” setting to prevent assigning too many simultaneous jobs to a disk-based backup device. By default, the quiesce time is set to 10 seconds. Thus, after a job is assigned to a disk-based storage device, the Media Manager waits for 10 seconds before assigning the next job to the same device. You can change the default setting for quiesce time in the mediamgr.cfg file.

Note the following: