problem deleting job history 11d 7170

[Ryan_Rupert]

can someone help
when I delete old Job History items (274 total) in BackupExec 11d 7170 I get the following:

1.) slow response from admin console
2.) sometimes it will delete an item
3.) most of the time the following event viewer entries

a.)
Event Type:    Information
Event Source:    Backup Exec
Event Category:    (65535)
Event ID:    57345
Date:        11/2/2007
Time:        3:55:59 PM
User:        N/A
Computer:    CEADMINSERVER
Description:
Database Exception Context:m_QueryTimeoutInSeconds=30
sql={CALL DBO.DELETEJOBHISTORY(?,?)} Error:-536837662:
:: -2147217871:Timeout expired :: DB Error Set 0:
native=0xffffffff source=Microsoft OLE DB Provider for
SQL Server hr=0x80040e31 Timeout expired


b.)
Event Type:    Information
Event Source:    Backup Exec
Event Category:    (65535)
Event ID:    57345
Date:        11/2/2007
Time:        3:55:59 PM
User:        N/A
Computer:    CEADMINSERVER
Description:
Current DbTimeoutValue=30

[Michael_Holt]

I've been having the same problem since migrating to 11d; so I'll be interested to see what comes of the thread started here.

[Ryan_Rupert]

I am in a support case now with Symantec, not resolved yet, but I will share what happens and please provide any info you may discover (this includes lurkers)

[Michael_Holt]

This lurker also has a case open (as of 20 mins ago).  Perhaps we can compare answers afterward...

[Exchange_Sys]

We had the same Problem with Legacy Mailbox Backupjobs wich created in the old Version. After upgrade to 11d we cant delete the Jobhistory and this error reported.Also the express Database grow very fast. So we change to GRT-Backup but there are also different issues. We open a symanteccall (Terrible responsetime from symantecsupport, the need a few days to response) and the result was that the GRT-Backups in 11d dont work probaly in some envirements, they work on a hotfix... We should go back to legacy Backup....

Now i can say symantec backup exec is a very buggy terrible product and you cant use it in middle or big Enterpriseenvirements.

I must look after backupsolutions from other manufactorer.

I am very angry about this....

[Ryan_Rupert]

resolved with all these steps:

1.) chkdsk and defrag
2.) re-insatll MS XML from BackupExec source
3.) repair install BackupExec
4.) config retention of job history and job logs to say 5 days
5.) multiple manual db maintenance operations using beutility.exe (check, age, compact, repair, etc.)
6.) manual delete of job history items as allowed between all the above ops
7.) final fix was the following from SQL commands from command line (use at your own risk)

osql -E -S localhost\bkupexec

1.)
use BEDB
truncate TABLE JobHistoryDetailInfo
go
select Count(*) from JobHistoryDetailInfo
go


2.)
use BEDB
truncate TABLE JobHistorySummary
go
select Count(*) from JobHistorySummary
go


3.) (rarely needed to truncate 'JobHistoryDetail')
use BEDB
truncate TABLE JobHistoryDetail
go
select Count(*) from JobHistoryDetail
go


4.)
use BEDB
DBCC SHRINKDATABASE (BEDB,5)
go

[Michael_Holt]

Ryan,

I just ran Step 7 (sql commands) and all is fixed!  Wow, thanks so much for all your help and thanks for posting the fix.

I'm a happy camper now, since this was bugging me to the point of wanting to uninstall/reinstall the entire application.

thanks

[Michael_Holt]

Additionally, the sql commands has sped up the opening of job histories, making this an uneventful process.  In the past, it took about 30 secs to open a Job History.