Backups fail with status 2063 "Server is not licensed for remote option"

Article:TECH201869  |  Created: 2013-01-21  |  Updated: 2013-01-28  |  Article URL http://www.symantec.com/docs/TECH201869
Article Type
Technical Solution



Issue



Backups fail with status 2063 "Server is not licensed for remote option".


Error



In the job log:

28/07/2012 02:56:11 - Error nbjm(pid=5024) NBU status: 2063, EMM status: Server is not licensed for Remote Client Option
Server is not licensed for Remote Client Option(2063)

In the nbemm log, from MDS:

28/07/2012 02:56:09.574 [Debug] NB 51216 mds 143 PID:2608 TID:1576 File ID:111 [jobid=174624] 1 [allocateTwin] EXIT STATUS = 2005063 (EMM_ERROR_MDS_HostNotLicensedForRemoteClient, Server is not licensed for Remote Client Option)
 


Cause



This problem can occur if a media server in the NetBackup configuration has MM_SERVER_NAME set incorrectly in the vm.conf file.

UNIX/Linux media server:  /usr/openv/volmgr/vm.conf

Windows media server:  \Veritas\Volmgr\vm.conf

If MM_SERVER_NAME is defined in vm.conf on a separate media server, and it is incorrectly set to the name of the master/EMM server, this can cause the problem of jobs failing with status 2063.

If MM_SERVER_NAME is used in vm.conf, it should be set to the host name of the network interface on the media server, which is used for communication with other NetBackup servers.  This value is only necessary if a media server has more than one network interface.  If the media server has only one network interface, it is not necessary to define MM_SERVER_NAME in vm.conf.

 


Solution



Change the value of MM_SERVER_NAME to be the host name of the network interface on the media server, which is used for communication by NetBackup.

All media servers should be checked to make sure that, if the vm.conf file exists on a media server, and MM_SERVER_NAME is defined in vm.conf, it is not set to the host name of the master/EMM server.

Note: If the vm.conf file does not exist on a media server, or MM_SERVER_NAME is not set in vm.conf, then this document does not describe the cause of the status 2063 error.  Creating the vm.conf file and/or adding MM_SERVER_NAME to it will not make the error go away.

 





Article URL http://www.symantec.com/docs/TECH201869


Terms of use for this information are found in Legal Notices