redmanjb
asked on
BackupExec 11d problem - ODBC Access Error
I'm having this issue on 5 of our 15 BE servers. I have tried stopping the BE services, renaming the Catalog folder, and restarting the BE services (which creates a new Catalog folder). I've confirmed the catalog path is correct in the registry as well. Also, the media labels that BE is using is nothing strange, we're using the following naming scheme: DLT000001.
Here are the two messages in the event logs:
Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 34338
Date: 1/24/2007
Time: 7:52:09 AM
User: N/A
Computer: NTPA
Description:
Backup Exec Alert: Catalog Error
(Server: "NTPA") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
and this:
Event Type: Error
Event Source: Backup Exec CatErrorHandler Server
Event Category: None
Event ID: 34326
Date: 1/24/2007
Time: 7:52:09 AM
User: N/A
Computer: NTPA
Description:
Access to catalog index (Catalog index database) failed.
Reason: Data type mismatch cat_RecordSet::GetField()
e:\crete\6235r\becat\segod
SELECT DISTINCT MediaGuid, MediaSide, MediaFamilyGuid From ImageObjectView WHERE ImageObjectView.BackupDate
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
Here are the two messages in the event logs:
Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 34338
Date: 1/24/2007
Time: 7:52:09 AM
User: N/A
Computer: NTPA
Description:
Backup Exec Alert: Catalog Error
(Server: "NTPA") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
and this:
Event Type: Error
Event Source: Backup Exec CatErrorHandler Server
Event Category: None
Event ID: 34326
Date: 1/24/2007
Time: 7:52:09 AM
User: N/A
Computer: NTPA
Description:
Access to catalog index (Catalog index database) failed.
Reason: Data type mismatch cat_RecordSet::GetField()
e:\crete\6235r\becat\segod
SELECT DISTINCT MediaGuid, MediaSide, MediaFamilyGuid From ImageObjectView WHERE ImageObjectView.BackupDate
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
rindi
Did you install BE for SQL cataloging, as opposed to the builtin version? IF so you need to have setup a SQL server so that BE can store it's data there. If you don't use an SQL server to store the BE catalogs, Reinstall BE without that option.
ASKER
Thank you very much for the reply rindi! :)
How do I find out which way it was installed, using either SQL or the builtin?
How do I find out which way it was installed, using either SQL or the builtin?
As I've never used SQL I don't know what it looks like then, but yours seems to be wanting to write the catalog to an SQL server because of the ODBC (ODBC access error) error you get. ODBC is an interface used to connect to databases, and if it can't connect it won't know where to save the catalogs. I'd reinstall BE and then you should be able to choose between SQL or native.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks CGretski. This may possibly work on one or more of the servers, but one server it will definitely not work on. We had purchased a brand new Quantum SuperLoader 3 and brand new tapes for one of our offices. That server still receives the ODBC access errors, even though the tapes are brand new.
It was because my tapes were new I was getting the error -- BE wasn't able to distinguish between the tapes to label/inventory them until they had been long erased
ASKER
Thanks CGretski. I will do a long erase today on the tape that our weekly backup job will be performing on tonight. It may be Monday until I post back with the results. In the mean time, would you happen to have any other ideas?
not off the top of my head....
when is it that you're getting the error mesages? - are they related to a specific task?
Re: rindi's comments, if BE11 is anything like BE10, the "built-in" backend is actually MSDE (Microsoft Sql Desktop Engine- now called Microsoft SQL express), which is just a basic version of M$ SQL server without any of the tools. You should be able to see either MSDE or M$SQLexpress in the add/remove programs list if it is installed.
when is it that you're getting the error mesages? - are they related to a specific task?
Re: rindi's comments, if BE11 is anything like BE10, the "built-in" backend is actually MSDE (Microsoft Sql Desktop Engine- now called Microsoft SQL express), which is just a basic version of M$ SQL server without any of the tools. You should be able to see either MSDE or M$SQLexpress in the add/remove programs list if it is installed.
ASKER
I did a long erase on the tape in one of the servers, then did a full backup Friday night. I still receive the error messages.
Each day, I receive an alter (informational and error) similar to the ones below:
1 - 4:00am - Maintenance of application databases on server CLW-NAS\BkupExec has started.
2 - 4:00am - Summary of database maintenance activity:
* Saved contents of BEDB database
* Optimized BEDB database size from 13.88 MB to 13.88 MB
* Deleted expired data for BEDB database:
1 expired audit logs were deleted
0 expired reports were deleted
0 expired job histories were deleted
14 expired alert histories were deleted
0 expired job logs were deleted
Total elapsed time: 00:00:05
Originally received: Sunday, January 28, 2007 4:00:05 AM
3 - ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.
Originally received: Sunday, January 28, 2007 9:00:14 AM
4 - ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.
Originally received: Sunday, January 28, 2007 3:00:14 PM
5 - ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.
Originally received: Sunday, January 28, 2007 3:00:14 PM
Then the same ones as in 1 & 2 above, occurring at 4am the next day.
So at 4am, I get the database maintenance informational alerts, then at the following times I get the ODBC errors: 9am, 3pm, 9pm, 3am.
I hope this maybe sheds some light on things.
BTW, all of the servers are running MS SQL Express...
Each day, I receive an alter (informational and error) similar to the ones below:
1 - 4:00am - Maintenance of application databases on server CLW-NAS\BkupExec has started.
2 - 4:00am - Summary of database maintenance activity:
* Saved contents of BEDB database
* Optimized BEDB database size from 13.88 MB to 13.88 MB
* Deleted expired data for BEDB database:
1 expired audit logs were deleted
0 expired reports were deleted
0 expired job histories were deleted
14 expired alert histories were deleted
0 expired job logs were deleted
Total elapsed time: 00:00:05
Originally received: Sunday, January 28, 2007 4:00:05 AM
3 - ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.
Originally received: Sunday, January 28, 2007 9:00:14 AM
4 - ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.
Originally received: Sunday, January 28, 2007 3:00:14 PM
5 - ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.
Originally received: Sunday, January 28, 2007 3:00:14 PM
Then the same ones as in 1 & 2 above, occurring at 4am the next day.
So at 4am, I get the database maintenance informational alerts, then at the following times I get the ODBC errors: 9am, 3pm, 9pm, 3am.
I hope this maybe sheds some light on things.
BTW, all of the servers are running MS SQL Express...
ASKER
This is still an ongoing problem. Does anyone have any other ideas?
ASKER
anyone?
ASKER
anyone?
This is occurring with our sbs 2003 server as well. Going to Tools, Options, I noticed that the errors occur every 40 minutes into the scheduled data base maintenance. For now I've disabled the database maintance to see if I can narrow the problem down and will post the results.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I found that the other way of working around this error is to do a long-erase on both new and recycled tapes before the next backup. Since I started doing this, especially with our daily incremental backups, the error messages have disappeared.