10-10-2014 02:19 AM
Good day
We have a Netbackup Master/Media server on version 7.1.0.4 on Windows. We have client on Solaris 10 also with Netbackup client 7.1.0.4.
When setting the policy to force deduplication on client side, we get the following errors and the backup fails:
2014/10/09 05:25:35 PM - started process bpbrm (4336)
2014/10/09 05:26:38 PM - Error bpbrm(pid=4336) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1
2014/10/09 05:26:38 PM - Error bpbrm(pid=4336) sts_get_server_prop_byname failed: error 2060057 - retrying
2014/10/09 05:27:40 PM - Error bpbrm(pid=4336) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1
2014/10/09 05:27:41 PM - Error bpbrm(pid=4336) sts_get_server_prop_byname failed: error 2060057 - retrying
2014/10/09 05:28:43 PM - Error bpbrm(pid=4336) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1
2014/10/09 05:28:43 PM - Error bpbrm(pid=4336) sts_get_server_prop_byname failed: error 2060057 - retrying
2014/10/09 05:29:45 PM - Error bpbrm(pid=4336) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1
2014/10/09 05:29:46 PM - Error bpbrm(pid=4336) sts_get_server_prop_byname failed: error 2060057 - retrying
2014/10/09 05:30:48 PM - Error bpbrm(pid=4336) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1
2014/10/09 05:30:49 PM - Error bpbrm(pid=4336) sts_get_server_prop_byname failed: error 2060057
2014/10/09 05:30:49 PM - Critical bpbrm(pid=4336) Client Direct plugin not available (2060057)
2014/10/09 05:30:49 PM - end writing
media open error(83)
Please assist
Thanks
Wilhelm
Solved! Go to Solution.
10-30-2014 06:02 AM
Hi Wilhelm,
from the errors in the bpbrm log, this looks like a name resolution issue.
please have a look at this technote:
http://www.symantec.com/docs/TECH137755
let me know if that helped
Kind regards,
Konstantinos
10-30-2014 06:02 AM
Hi Wilhelm,
from the errors in the bpbrm log, this looks like a name resolution issue.
please have a look at this technote:
http://www.symantec.com/docs/TECH137755
let me know if that helped
Kind regards,
Konstantinos
10-30-2014 09:58 AM
Some commands to help verify hostname resolution per Wilhelm's response:
From the client: usr/openv/netbackup/bin > bpclntcmd -self (note upper/lower case, FQDN vs short name etc.)
From the Master Server: Program Files/Veritas/Netbackup/bin >bpclntcmd -host <client name>
Verify that the master server resolves the same host name as the client -self command
From the client: usr/openv/netbackup/bin > bpclntcmd -pn (this will query the master server and ask "who am I") verify that the correct master server is returned and that the client hostname is correct.
I strongly recommended adding the master and media server hostnames to the client /etc/host name file and visa versa. Even when using DNS there can be hostname resolution errors and the /etc/host file by-passes any DNS errors.