Chat now with support
Chat with Support

NetVault 11.4 - Administration Guide

Introduction Getting started Configuring clients Configuring storage devices Backing up data Managing policies Restoring data Managing jobs Monitoring logs Managing storage devices
Monitoring device activity Managing disk-based storage devices in table view Managing disk-based storage devices in tree view Managing tape libraries in table view Managing tape libraries in tree view Managing tape drives in table view Managing tape drives in tree view Adding shared devices
Managing storage media Managing user accounts Monitoring events and configuring notifications Reporting in NetVault Backup Working with client clusters Configuring default settings for NetVault Backup
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 Backup to use a specific VSS provider Configuring default settings using Txtconfig
Diagnostic tracing Managing diagnostic data Using the deviceconfig utility NetVault Backup processes Environment variables Network ports used by NetVault Backup Troubleshooting

VSS-based backup fails

When performing a VSS-based backup, if the VSS writer fails to generate a snapshot, the job fails.

The log messages show the following errors:

These messages indicate a problem in the VSS subsystem. NetVault Backup cannot complete the backup job if the VSS subsystem is not functioning properly. Before you run the job again, we recommend that you do the following:

Delete the existing shadow copies. (You can use the Vssadmin or DiskShadow utilities to delete the shadow copies.)

Modifying TCP/IP socket buffer size on Windows

Cannot modify TCP/IP socket buffer size on Windows.

Slow performance occurs on Windows when data is transferred over a LAN. Changing the window size using any network tool (for example, IPerf) does not change the buffer size.

On Windows, the registry settings must be modified to increase the TCP/IP buffer size. For more information about these settings, see the KB article from Microsoft.

Restores using Data Copy savesets fail on clients running NetVault Backup 10.0.1

When restoring a Data Copy saveset on a client running NetVault Backup 10.0.1 or an earlier version, the job fails.

The restore job reports the following error:

Failed to get index.

The trace logs contain the following messages:

New style index.

Corrupt index file, version number invalid.

On NetVault Backup Server 10.0.5 and later, the Plug-in for Data Copy creates index version 4, which is incompatible with earlier versions of NetVault Backup. A client running NetVault Backup 10.0.1 or an earlier version cannot read these index files, causing the restore job to fail.

To restore Data Copy savesets generated from NetVault Backup Server 10.0.5 or later, the client must be upgraded.

Restore fails on Itanium platforms if the index is larger than 2GB

On Itanium platforms, restore fails for backups with indexes larger than 2GB in size.

On Itanium platforms, when you try to restore a backup with an index larger than 2GB in size, the job fails with the error message “Failed when sorting items to restore.”

To correct this issue, increase the stack size:

On the standard UNIX platforms, edit the ulimit setting from the CLI to increase the stack size.
After changing the value, run the ulimit -a command to ensure that the setting has been changed.
On HP-UX Itanium platforms, use the bash command kmtune or kctune (depending on the operating system) to access to the kernel stack size information. The stack variables are maxssiz for 32-bit applications and maxssiz_64bit for 64-bit applications.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating