Behaviour Of Media Server

[Possible]

Hi All,

I am having ockward scenario :

I am having a media server (B : Not a robot control host) which is showing all the drives MISSING PATH in tpconfig o/p.

Now I go to device configuration wizard and I can see the drives (shred) in the screen. Here, A (consider) is robot control host which can see all drives wih proper path.

Now i go to server B and use tpconfig -multiple_delete -drive to delete all the drives which are having MISSING PATH and having success (The drives are deleted from the media server only and not from whole drive databse as they are seen by robot control host A).

I go backup to device configuration wizard to scan the drives in order to reconfig them but i am not able to see any drive over there now (Server A can see them in wizard ).

My question is where those drive gone ?? I am not having a single drive for that particular robot now? How could I bring them back?

I looks abnormal to me....please help

[V4]

If OS is able to scan the devices you have but is failing during configuration

Try to remove all the orphaned entries of Devices from EMM DB

from admincmd execute below syntax

nbemmcmd -deletealldevices -machinename serverB -machinetype master/media

once it confirms Successful removal. do a Scan and try to configure devices through wizard or CLI again. What does it says

please post verbose output for better troubleshooting

let us know if above helps

[mph999]

OP doesn't want to delete all devices if possible.

Good idea though, sometimes this will fix odd issues, but lets wait for scan output first.

martin

[Marianne]

Giri, any reason why you are NOT posting full scan output? we have been asking for this for two days now...

Our only motivation is to help YOU...

[Possible]

Maria..u have been always inspiration for us..

amazingly i can see tht drive in scan o/p and vmoprcmd ...

whats going on ???

[root@AAA ~]# vmoprcmd -h AAA-autoconfig -t |grep 1304927336
TPAC60 IBM     ULT3580-TD4     4C17 1304927336 -1 -1 -1 -1  /dev/nst57 - - -
 

I am not putting scan o/p as its too huge...

Thanks ,

Giri

[Marianne]

3 days later you tell us that scan output is 'too huge...'

At last SOMETHING to work with....

Probably lots of virtual drives in VTL as well as physical drives?

This could mean that the GUI is timing out.

When that happens, I use the cmd equivalent:

vmoprcmd -h <media-server-name> -timeout 3600 -autoconfig  -a

I see you already know the cmd equivalent!

[Possible]

vmoprcmd -h <media-server-name> -timeout 3600 -autoconfig  -a

will keep the exixiting configuration (will referesh only exisiting drives)

But what should be done if i want to alter the config...

You are correct that we are having large vtl drives as a part of big infra.

Thx.

[Yogesh9881]

Can you post that HUGE o/p here in attached file (txt or doc frormat).

dont mind but .......i am really curious to know how HUGE it is

[Marianne]

That command does EXACTLY what the GUI wizard does. Only difference is that you specify timeout with cmd.

Always best to delete old devices first, restart NBU on media server, then re-add via GUI wizard or cmd.