cancel
Showing results for 
Search instead for 
Did you mean: 

media manager device daemon error on HPUX

toichubek
Level 3
Partner Accredited

Hi,

 

I have problem with media server on HP-UX

master server on red-hat, NB 7.1

 

i have SSO licence,

here is some commands:

 /usr/openv/volmgr/bin/tpconfig -l
Device Robot Drive       Robot                    Drive  Device
Type     Num Index  Type DrNum Status  Comment    Name  Path
robot      0    -    TLD    -       -  -          -  nbumedia
robot      1    -    TLD    -       -  -          -  nbumedia
# /usr/openv/volmgr/bin/vmoprcmd -d
The Media Manager device daemon (ltid) is not active on host geodwhdb.intra

/usr/openv/volmgr/bin/tpautoconfig -t sees the drives

 

but when i creating with storage device wizard, it cannot restart media manager device daemon

on media server when i try to run manually ltid:

No Entries in the Drive Database
TLDCD: No robots are configured

 

thanks in advance,

 

6 REPLIES 6

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

"when i creating with storage device wizard, it cannot restart media manager device daemon"

Are you getting an error message at this point?

Can you confirm that Library Based tape drive license as well as SSO license have been added on the media server?

Please run the following on the master server and post output:

nbemmcmd -listhosts -verbose

nbemmcmd -getemmserver

toichubek
Level 3
Partner Accredited

exclamation mark appears... but it saw robot and drives

 

Yes licenses've been added on both servers...

 

 

# ./nbemmcmd -listhosts -verbose
NBEMMCMD, Version:7.1
The following hosts were found:
nbumedia
        MachineName = "nbumedia"
        FQName = "nbumedia.geocell.com.ge"
        MachineDescription = ""
        MachineNbuType = server (6)
nbumedia
        ClusterName = ""
        MachineName = "nbumedia"
        FQName = "nbumedia.geocell.com.ge"
        GlobalDriveSeed = "VEND:#.:PROD:#.:IDX"
        LocalDriveSeed = "DT"
        MachineDescription = ""
        MachineFlags = 0x77
        MachineNbuType = master (3)
        MachineState = active for tape and disk jobs (14)
        NetBackupVersion = 7.1.0.0 (710000)
        OperatingSystem = linux (16)
        ScanAbility = 5

geodwhdb.intra
        ClusterName = ""
        MachineName = "geodwhdb.intra"
        FQName = "geodwhdb.intra"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x17
        MachineNbuType = media (1)
        MachineState = active for disk jobs (12)
        MasterServerName = "nbumedia"
        NetBackupVersion = 7.1.0.0 (710000)
        OperatingSystem = hpux (4)
        ScanAbility = 5

 

# ./nbemmcmd -getemmserver

 

MEDIA          7.1                 geodwhdb.intra                nbumedia

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Master server believes that media server is active for disk only:

MachineState = active for disk jobs (12)

Try the following on the master server:

nbemmcmd -updatehost -machinename <media-server> -machinestateop set_tape_active -machinetype media -masterserver <master>

toichubek
Level 3
Partner Accredited

i've already tried, unfortunatelly...:)

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

The only times where i have seen this is when license keys on media server were not correct and once when media server had 2 NICs and was responding on second interface.

Media server's incoming IP address will be logged in master's admin log and/or PBX logs.

Yasuhisa_Ishika
Level 6
Partner Accredited Certified

Observing output of "vmoprcmd -d",  you run "tpconfig -l", "vmoprcmd -d", "tpautoconf -t" on geodwhdb.intra(HP-UX media server). Right?

By "tpconfig -l", two remote robots controled by nbumedia(linux master server) is configured on your master server. And there are no drives.
If no drives configured, Media Manager device daemon(ltid) can not run on the host. This is cause of "vmoprcmd -d" error.

If drives are really visible, drives are configured thru Device Configuration Wizard. Check following points.

  • Run /usr/openv/volmgr/bin/scan on geodwhdb.intra, and check whether drives are listed.
  • Run wizard again, and check drives are really detected on geodwhdb.intra.