synchronize the global device database

[Manfred_Ratzke]

Hi,

I get error message:

bash host01# tpautoconf -get_gdbhost
The global device database version is incompatible

any ideas how to synchronize the global device database without the GUI as this isnt working either

[Andy_Welburn]

Is the volume management daemon (vmd) running?

[Amit_Karia]

Agree with Any you must start VMD either manually or recycling netbackup daemons , even after starting if it is giving same error them use the following command

vmglob -get_gdbhost

it should result in global device databasehost name

if it doesnt do so

vmglob -set_gdbhost <global device database host>

[Manfred_Ratzke]

Ok, I did

   bash #   vmd

that came back with infos in /usr/openv/volmgr/debug/daemon

15:16:34.191 [1496] <16> vm_getservbyname: getservbyname() failed after 3 attempts for vmd/tcp
15:16:34.191 [1496] <16> getsockbound: cannot find Internet service vmd/tcp
15:16:34.191 [1496] <2> mm_bind_and_listen: netconf.c.913: getsockbound(vmd) failed: 0
15:16:34.192 [1496] <16> vmd: unable to obtain bound socket, no port number available for vmd (0)
15:16:34.192 [1496] <16> vmd: terminating - daemon cannot obtain socket (58)

dont now if but just made a reboot

[Amit_Karia]

Hi

See if vmd is having entry in services file

more /etc/services | grep vmd

vmd     13701/tcp       vmd

[Manfred_Ratzke]

ok, I checked /etc/services and addes the port from old services file I had, now after reboot vmd is running and now tpconfig -d just shows the robot so I need to config all drives

any docu online available ? what I have is:

1. Determine if an sg driver is loaded by using the following command:

     /usr/sbin/modinfo | grep sg

2. Remove the existing driver:

     /usr/sbin/rem_drv sg

  3. Install or reconfigure the sg driver.

       a. If reconfiguration is desired, run the following command first:

          /usr/bin/rm -f /kernel/drv/sg.conf
         
b. To install the driver run the following command:

          /usr/openv/volmgr/bin/driver/sg.install

cd /usr/openv/volmgr/bin/driver

/usr/openv/volmgr/bin/sg.build all -mt 11 -ml 1

Make a copy of the /kernel/drv/st.conf file.
Edit the /kernel/drv/st.conf file.
The temporary file ./st.conf contains the entries that you need
to insert into /kernel/drv/st.conf.

 c. Reboot the system with the reconfigure option (boot -r or reboot
          -- -r).

  d. Verify that the system created device nodes for all the tape
          devices using the following command: ls -l /dev/rmt/*cbn

 5. Install the new sg driver configuration.

     /usr/bin/rm -f /kernel/drv/sg.conf

   /usr/openv/volmgr/bin/driver/sg.install

is that the right way ??? thanks

[Amit_Karia]

Which driver you are using , In case if you are using qlogic drivers.. you need to perform persistent binding

rest seems ok

[Manfred_Ratzke]

how can i find out about the qlogic driver or not ?

I just made those steps and only the robot is listed no drives

Thanks

Manfred

[Manfred_Ratzke]

starting the gui I get a Java error :

unable to login status 505

cannot connect to NB-JAVA service on host on configured port - 13722

java connection error

connection refused

[Amit_Karia]

can you run luxadm -e port command?

[Amit_Karia]

http://seer.support.veritas.com/docs/233992.htm

[Manfred_Ratzke]

Hi sorry for late response:

I configured the complete sytem new

on boot the robot will be initialized

all drives then up and CONTROL by TLD

when i then start a backup the first 2 tape are mounted and placed into a drive all others will then be switched to Control: AVR  an dit shows the message : unable to initialize robot, which was the root cause when investigating it.

Any idea why drives will be set to AVR and robot cannot be initialized anymore???

[Andy_Welburn]

Sounds like there may be some discrepancies in the configuration of your robot/tape drives. Incorrect paths, serial numbers or other mis-matches etc.

Try the commands:

/usr/openv/volmgr/bin/tpautoconf -report_disc

/usr/openv/volmgr/bin/tpconfig -d

/usr/openv/volmgr/bin/scan

& double- or triple-check the output.

Failing that you could always try deleting all your tape drives & robot & reconfiguring them.

Could always search in the knowledge base or this forum for AVR - there may be other possible resolutions.

[Manfred_Ratzke]

Hi, thanks,

I checked all path names and configs and that is ok, just after a reboot the robot is initialized but as soon as I start more then 3 backups the first 2 to4 drives are loaded and workingbut all others going inot AVR mode and system tells me cannot initialize robot....