06-16-2015 03:15 AM
hi all we are having an issue with a netbackup master server and a media server, this is the environement discription :
Solved! Go to Solution.
06-16-2015 04:46 AM
<install_path>\veritas\volmgr\vm.conf is there but <install_path>\veritas\volmgr\debug\ltid\ and <install_path>\veritas\volmgr\debug\ltid\robots\ are not, how do i create those files ?
Use mkdir or in file explorer, just create them as directories
> When clicking on Properties - Additional Information, you see the message "No shared storage option license installed".
Lets see the output of: bpminlicense -verbose
If you are sharing drives, but do not have SSO license on all the servers, then you will have problems with drives, and hence no wonder the ltid won't start.
06-16-2015 03:31 AM
> of all the servers can correctly see the robot
Only the RCH needs to have the robot zoned
> and bck02 is working fine, but after the installation of bck03(media) and the restarting of bck01(master) the device manager service on both servers fails to start, with no errors on windows event viewer, on bck01 also the key management service fails too.
NetBackup Device Manager? Do you have these log directories created? If not, create them, add VERBOSE to <install_path>\veritas\volmgr\vm.conf and restart the media server NetBackup daemons
<install_path>\veritas\volmgr\debug\ltid\
<install_path>\veritas\volmgr\debug\ltid\robots\
> bck02 is using only two drives from the robot and fails to connect to emm database, i believe that is because of failing device manager services on the master.
06-16-2015 04:30 AM
>NetBackup Device Manager? Do you have these log directories created?
<install_path>\veritas\volmgr\vm.conf is there but <install_path>\veritas\volmgr\debug\ltid\ and <install_path>\veritas\volmgr\debug\ltid\robots\ are not, how do i create those files ?
>more likely that the device manager is failing to start because it cannot connect to the EMM
on bck02 the device manager is starting and somtimes it shoes a popup saying that it can not connect to emm database on the bck01 where device manager is down, but it's not starting on bck01(master) and bck02 (media)
when i execute the commands the media servers detects bck01 as emm server
>Different in what way?
the content is not the same.
Now i'm suspecting a license issue, because when using NetBackup Configuration Wizard to Configure Storage Devices for a second media server, the drives are detected with a limitation.
When clicking on Properties - Additional Information, you see the message "No shared storage option license installed".
but when i execute bpminlicense -verbose it shows shared storage license with license type = 1 Permanent
06-16-2015 04:46 AM
<install_path>\veritas\volmgr\vm.conf is there but <install_path>\veritas\volmgr\debug\ltid\ and <install_path>\veritas\volmgr\debug\ltid\robots\ are not, how do i create those files ?
Use mkdir or in file explorer, just create them as directories
> When clicking on Properties - Additional Information, you see the message "No shared storage option license installed".
Lets see the output of: bpminlicense -verbose
If you are sharing drives, but do not have SSO license on all the servers, then you will have problems with drives, and hence no wonder the ltid won't start.
06-16-2015 06:42 AM
hi,
the problem was in the licenses, in the help section on the admin consol we can see that the SSO license, even when i execute bpminlicense -verbose it shows shared storage license with license type = 1 Permanent (seems that does not mean that the lisences are there on the media server)
but when using the command below on the media servers :
...veritas\netbackup\bin\admincmd>bpminlicense.exe -list_keys -verbose
we discovered that there are no SSO license and no Library Based Tape Drive license so we added them manually
...veritas\netbackup\bin\admincmd>bpminlicense.exe -add_keys XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
we removed drives and robots then added them and everything is working great.
06-16-2015 06:56 AM
Good job. That error was a big give away :)