HP Data Protector : There is no more space in the internal database for filenames

There is no more space in the internal database for filenames

This error occured due to filename.dat (The max size 2gb) so we are getting above error.

due to this while taking backup or intiated it is giving a critical error like backup is taken with logging.

Ther Resuloutaion.

In Catalog database we added another table name for more space.

now there is no error

Internal Database network communication error

The above screen describes the cell manger unable to connect the velocis database .
inthis case the user may not have the enough privilages .
hope while troubleshooting this may usefull.

Bocada plugin

Some good reference

(pls refere for more inforamtion on DP errors and reporting BOCADA site)

All this information you can find in BOCADA plugin for HP DP Guide.

pls gothrough it copied some of the error messages here for reference.

❒[84:600] Cannot establish connection with Library Manager host. VBFS API error code ([num]).
❒[84:2399] param1 Disk quota information was restored as plain text file: param2
❒[90:11] Unrecognized option “p” => ignored
❒[90:12] param1 Cannot open option file: (param2)
❒[90:17] Cannot param1 NETIO process (param2) => aborting
❒[90:41] Invalid device type specified (param1) => abort­ing
❒[90:43] param1 Invalid physical device type => aborting
❒[90:44] No physical device(s) specified => abort­ing
❒[90:45] No exchanger con­trol device specified => aborting
❒[90:71] param1 Cannot open() script: (param2)
❒[90:73] param1 Error read­ing script output (param2)
❒[90:120] param1 Cannot get device file status (param2) => aborting
❒[90:121] param1 Not a char­acter device nor regular file => aborting
❒[90:123] param1 Unknown device, please check device support matrix
❒[90:124] Not a BSD device => aborting
❒[90:125] Limited block size of 64K => aborting
❒[90:126] Not a variable block size => aborting
❒[90:157] param1 Rewindable device.
❒[81:53] [param1] Not in hard link catalog => backed up regularly.
❒[81:54] [param1] Object does not reside in current filesystem => not backed up.
❒[81:76] [param1] Can not perform stat(): [param2] => not backed up.
❒[81:141] [param1] Can not export configuration object: [param2] => backup incom­plete.
❒[81:180] [param1] Can not clear archive flag: [param2].
❒[81:181] [param1] Dupli­cate filename => not backed up.
❒[81:202] [param1] Not a valid VBFS mount point => aborting.
❒[81:302] [param1] Object is not a character device => not backed up.
❒[81:304] [param1] Object is a mounted filesystem.
❒[81:305] [param1] Can not compute disk capacity [param2] => not backed up.
❒[84:5] Filesystem too deep: (param1) levels .
❒[84:6] Cannot open mount table: (param1).
❒[84:109] Incorrect type of backup must be done with: p.
❒[84:114] Unknown type of compression: [num].
❒[84:119] Unknown type of encoding !
❒[84:208] param1 Configura­tion object not recognized by the system => not restored.
❒[84:210] param1 Object is not restorable.
❒[84:500] Cannot migrate file (p) to the nearline storage. VBFS API error code ([num]).

[12:1051] Client security violation. Access denied. in DP 6.1

Critical] [110:1043] Hostname reported by client ([Critical] From: INET@hifalwps2 "hiaflwps2" Time: 01/18/10 09:45:00
[12:1051] Client security violation. Access denied.

When i got this error i found 2 problems.

1. cell manager system host entry (ie c:\windows\system32\driver\etc\hosts) and one more client side host entries problem. even if u are update boath side pls check with installation server same.

2. After this also if u are facing same problem pls add cell manger host name in

client side . ex: if os is hp-ux pls add cell manager host entry in etc\opt\omni\client\allow_host