Failed to copy existing index entry to new backup index (4045547)

Title: Failed to copy existing index entry to new backup index
Date: June 2006
NV Version: 7.x
OS Version: all
Application version:N/A
Plugin version:N/A


Symptoms:
Although the index is present in the nvdb, the Incremental backup fails to copy it to the client’s.
The backup fails with the following log message:

Log message " Failed to copy exisiting index entry to new backup index"
Example:
Error 2006/06/05 22:33:29 7611 Data Plugin PRIMARY Failed to copy existing index entry to new backup index

Description/Context:
A Full successful backup has previously been done, backing up the FS on a client across a network.
In details, when a Full backup occurs on a client, an index entry is created into the client’s /NetVault/tmp (_NV_TMP) directory. It is then copied into the NetVault server’s MediaDatabase directory and appended at the end of the media on which the full is written. This same index is finally discarded from the client’s tmp directory, meaning there are only 2 places where it resides: server’s MediaDatabse and tape/media.
Later on an Incremental backup is performed and immediately fails with the log error message:
“ Failed to copy exisiting index entry to new backup index”
It appears that NetVault does locate the index in the MediaDatabase but fails to copy it into the clients tmp directory in order to proceed in performing an incremental.

Procedure/Troubleshooting:
We need to test the integrity of this index and the space on the client’s tmp dir:

#1 Testing the index integrity and ability to be read and processed:
- The full FS backup can be browsed successfully
- A restore from this backup to the original client with the rename option and using the VDL media restore was successful

#2 Checking the contents of the netvault/tmp directory on the target client
to verify that there were no 'old' index files that cannot be ov

Please refer to the text above