unable to read the EMM database:server connection failed

[Srikanth_Gubbal]

Hi,

Recently i upgraded from 5.1 mp6 to 6.5 on WIN 2000 service pack 4. upgradation went smooth, but after upgrading when trying to refresh the robot after mounting the tapes,i get an error

unable to read the Enterprise Media Manager Database:Server connection failed. Verify services or daemons are up and running.(195). after resolving this issue, a 'Refresh All' is required to display updated information.

this error is disappearing when i restart the services but, when i schedule the backup and check in the next morning i get the same message and jobs fail with 96 error

i have raised an call with veritas support they said that it was problem with drive, but all my earlier backups are 100% successful.

so i got in touch with my IBM engineer, verified the drives and upgraded the firmware.

next day it is fine but again, i got the same problem and the one drive was down with missing path error.

this is happening for the past 7 days and even the call was escalated to second level support.

i clearly told the support, that it is not the problem with drive because when i restart  the services everything is fine but after some time suddenly some services are being stopped .

even i got same problem with my offsite netbackup server which is WIN server 2003

when commuicated the same thing to support they suggested me to raise an seperate request.

my request is does any one of you face the same problem, if yes, please share me how to resolve this.

regards,

srikanth

[Stumpr2]

It sounds to me that the drive problems are just a symptom of a bad EMM database. Ask support to verify a complete and accurate EMM database content and configuration.

[Nicolai]

I had a similar problem on my NBU 6.5 test system. The EMM database stopped responding every 24 to 30 hours. Once I configured the Netbackup catalog backup to run every day that problem disappeared. I didn't had drive down issue however.

Regards
Nicolai

[Srikanth_Gubbal]

hi,

did you see any netbackup tld daemon information event logs, i could an event log id 5122

11/25/2007 8:22:22 AM NetBackup Tape Manager Information None 5122 N/A PLUTO DeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/25/2007 3:29:27 AM NetBackup Tape Manager Information None 5122 N/A  PLUTO DeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/25/2007 12:37:51 AM NetBackup Tape Manager Information None 5122 N/A  PLUTO DeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/24/2007 10:52:22 PM NetBackup Tape Manager Information None 5122 N/A  PLUTO DeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/24/2007 9:01:19 PM NetBackup Tape Manager Information None 5122 N/A  PLUTO DeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/24/2007 9:00:47 PM NetBackup Tape Manager Information None 5122 N/A  PLUTO DeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/24/2007 12:53:03 AM NetBackup Tape Manager Information None 5122 N/A  PLUTO DeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/23/2007 9:01:26 PM NetBackup Tape Manager Information None 5122 N/A  PLUTO DeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/23/2007 9:01:01 PM NetBackup Tape Manager Information None 5122 N/A  PLUTO DeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/23/2007 7:43:04 PM NetBackup Tape Manager Information None 5122 N/A  PLUTODeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/23/2007 6:01:04 PM NetBackup Tape Manager Information None 5122 N/A  PLUTODeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/22/2007 8:37:37 PM NetBackup Tape Manager Information None 5122 N/A  PLUTO DeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/22/2007 6:43:52 PM NetBackup Tape Manager Information None 5122 N/A  PLUTODeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )
11/22/2007 6:43:25 PM NetBackup Tape Manager Information None 5122 N/A  PLUTO DeviceIoControl() error on bus 0, target 0, lun 0 (1117:The request could not be performed because of an I/O device error. )

can you provide any solution for this

[ReneeC]

I am starting to see the same issue of a Windows server who's drive path just suddenly keeps going out to lunch after a 6.5.1 upgrade.  It is using the latest IBM drivers and the drives have persistent binding enabled.  I know that it is not the drives themselves because we are using SSO, and the other server, which is a Solaris box is still writing to the drives fine.  Just wondering if you ever got a resolution that fixed your issue and what it was?  Thanks

[zippy]

hahha  I like the first line and the paper clip pic!

http://www.columbia.edu/~ip71/ltohell/ltohell.html

JD

[Stumpr2]

LOL

Welcome back James!