Date: 06/07/2006
NV Version: 7.42
OS Version: ALL
Application version:
Plugin version: NDMP 6.304
Description:
NDMP only supports index sizes up to 2GB, if this is exceeded by processing an extremely large number
of files then index generated will be unable to be read and a restore is not possible.
Workaround to prevent the 2.0GB index NDMP limit preventing restores
Symptoms:
The NDMP Backup job is completed successfully without any warning or errors.
When attempting to open and browse the backup data saveset within the netvault restore GUI window under the ndmp plugin
, an error dialog box "Corrupted backup index" is displayed.
Therefore preventing a restore of any data from the backup.
We could open backup data if backup index size is less than 2GB.
To Qualify this issue as the 2.0GB limit infringement
- Identify the associated backup index file by enabling trace on the database browser process
and interrogate the resultant trace file nvbrowsedb.log.
the filename will be listed within a trace statement of the following format:
FILESYS :4438 32 0 113339 TRUE = FileSysOpen(ffbfec94, /usr/netvault/backup/db/MediaDatabase/Files/Backup/0000/00/01,
105)
in this example the index file is named /usr/netvault/backup/db/MediaDatabase/Files/Backup/0000/00/01
- Check the size of the file.
NDMP plugin only supports index sizes up to 2GB, to be able to peform backups of the same volume of
data and avoiding this the following options are available:
1- split the backup volume into seperate 'smaller' jobs that will generate seperate indices that are reduced in size
2 - deselect the ndmp plugin backup option - 'save file information'
This will allow the backup to complete produce a reduced size index and be available for restore
but the user will not be able to browse the content of the backup
and therefore will only be able to restore the complete volume
