Error performing client side deduplication: error 83
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
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