Data Protector could not store a part of the detail catalog during the backup or import. All files that are backed up on the same device after this message are not marked as backed up in the Data Protector Internal Database. Backup is still valid and restore of complete objects is possible.
------------
* Check the additional error message for the cause of the problem and fix the problem. Most often the problem will occur when the disk runs out of space or when the maximum size limit of the DC directories is reached. * If you want to browse files in that particular backup import the catalog for the medium that was in use when the error occurred and all media that were written after the error in the same device
----------------------------
Check for possible reasons why those files can be missing and try to fix the issue. For example if the file is on the filesystem that is for some reason not mounted, mount it ... * If file is really missing, you can get the contents of the file back by executing the following procedure: 1) Stop all sessions and close all GUIs 2) Run: omnidbutil -fixmpos 3) Find the correct medium and run "Import catalog" for that medium. Note that the debug.log contains the medium ID of the file and that you can use: omnimm -media_info
The above messages contains the problem and it solution. we found when some of dcbf files moved related bakup is firing at that time it is fired. if dcbf directory getting more space simply map additional directory to IDB but don't move to some other place
