Hello NetBackup Specialists,

Somebody knows what VG_CHANGE_GLOB and change_globdb_rec means at daemon
log in <<install>>/volmgr/debug/dameon/log.MMDDYY?

01:49:23.275 [1220700] <4> process_request: VG_CHANGE_GLOB requested
01:49:23.482 [1220700] <2> change_globdb_rec: server read:  1 1110097857
LTO2_L700_DR01 sao0115x *NULL* 0 1 8 10 8192
IBM~~~~~ULTRIUM-TD2~~~~~1110097857 -1 IBM~~~~~ULTRIUM-TD2~~~~~4770
*NULL* *NULL* *NULL* -1 -1 -1 -1
01:49:23.483 [1220700] <2> string_to_globrecord: using server version:
45
01:49:23.692 [1220700] <2> change_globdb_rec: server read:
LTO2_L700_DR01
01:49:23.693 [1220700] <4> globdb_open_create_lock: GLOB DB
/usr/openv/volmgr/database/globDB already exists
01:49:23.693 [1220700] <4> globdb_lock: locking globDB
01:49:23.693 [1220700] <4> globdb_auto_upgrade: globDB version is
current
01:49:23.695 [1220700] <2> change_globdb_rec: Comparing: host=
device_type=1 serial_number=1110096498 device_name=
01:49:23.696 [1220700] <2> change_globdb_rec: Comparing: host=sao0115x
device_type=1 serial_number=1110097325 device_name=LTO2_L700_DR17

Everytime that my environment stays down, this syntax "VG_CHANGE_GLOB"
is logged at daemons log (volmgr).

I work with NBU ES MP3 5.1 and 22 SAN Medias (Unix/MS Win) with two SAN
Brocade 24K.

Thanks,

Anderson Henrique Leandrine
Storage Backup Administrator
SBS ORS ITO NOC -  - SIEMENS