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 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:
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 https://support.microsoft.com/en-us/kb/823764 from Microsoft.
Restores using Data Copy savesets fail on clients running NetVault 10.0.1
When restoring a Data Copy saveset on a client running NetVault 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 Server 10.0.5 and later, the Plug-in for Data Copy creates index version 4, which is incompatible with earlier versions of NetVault. A client running NetVault 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 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 HP-UX Itanium platforms, use the bash command kmtune
(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.