Backup exec application hang

[isdd2000]

Hi Experts,

Lately we have been running into issues with backup exec and have been failing
No changes have been made to either of the servers recently, to cause the issues we are having. I came across and error message whilst monitoring the backup, stating it was unable to connect to the database.

The database is located on another server. At the time of the occurrence the database server is operational and network connectivity is fine. I checked in the event logs and found multiple events.

The exact error that backup exec reports is as follows:

The connection to the backup exec database has been lost. Make sure network cables are properly attached and that services are running for SQL server instance on which the backup exec database is installed.

After backup exec hangs a restart on the server is required. 
_________________________________________________________________________

Event ID:846
Source: MSSQL$BACKUPEXEC_12

A time-out occurred while waiting for buffer latch -- type 3, bp 02C401E4, page 1:6, stat 0x1c0010b, database id: 5, allocation unit Id: 6488064, task 0x00959C48 : 0, waittime 300, flags 0x40039, owning task 0x008CAF28. Not continuing to wait.

_________________________________________________________________________


There are others but they mostly just state current db TimeOutValue. On the SQL server there are no event logs outline issues.


Nothing has changed in the environment; however I have been performing multiple disk cleanup's on the server.

Look forward to hearing from you!

[newsolutionBE]

Hi

DBCC UPDATEUSAGE is executed against the database to scan all data pages and to update all space allocation information. This command can be run against a specific database table or against an entire database. For more information on how to run DBCC UPDATEUSAGE 

  http://msdn.microsoft.com/en-us/library/ms188414.aspx

Also please check the link to which refer event id given by you

http://www.symantec.com/docs/TECH62275

Thanks

[pkh]

@isdd2000 - You should not be backing up the BEDB.  BE does its own database maintenance and backup.  By default, this is done at 4 a.m. daily.

If you want you should backup the Data directory under the BE installation directory.  This is where BE stores the bedb.bak file.

[pkh]

How is DBCC UPDATEUSAGE going to solve the OP's problem?

[isdd2000]

Hi nesolutionBE,

I am trying to perform a backup not an upgrade.

Thanks.

[isdd2000]

Hi All,

Thank you for the help.

I am trying to backup the entire system but it will not perform due to the issues outline. I have not been able to faultfind the issue any further.

Thanks.

[pkh]

Exclude the BEDB from your backup.

[isdd2000]

The BEDB has not been an issue before. Why would it be now? How does backing up the BEDB fault backup exec part way through the backup procedure?

[CraigV]

...might be worth your while to repair that BEDB in any case in order to rule out corruption. You can use BEutility for this and it is non-intrusive. If you don't know how too, follow the TN below for a comprehensive repair of the BEDB... http://www.symantec.com/business/support/index?page=content&id=TECH67239

[Vinothkumar]

Hi isdd2000,

The only resolution you can get it through linear and logical troubleshooting steps

You have mentioned all was working, y suddenly you have an issue.

You have mentioned that the DB is in different server too !!

Please let me know the answes for the below mentioned questions:

1. Is there any major/minor updates on both systems

2. Is there any upgrades on both system either software/HW

3. Any one of the server got restarted recently ?

4. Check the server security applications, anything got out dated or any updates on the same on both servers

5. Let us know the backup exec version

6. Your server architecture  

7. Open the logs and check for the errors before the Application goes to hang

8. Lets us know how you are performing backup, source destinations in breif

Regards

Vinoooo :)

An !! Idea !! can Change your Life to :)

[isdd2000]

1. No windows updates have been recently applied, but there are updates waiting to be applied.

2. No upgrades have been recently done.

3. servers get restarted regularly to get backup exec running.

4. Network security needs updating.

5. Backup exec is 12.5

6. 2 servers

backup exec server: Domain controller, dns, dhcp etc.

Database server: database and application server.

7. There are no errors just information logs.

              Event ID: 57345

8. Nightly full backups are performed to tape.

Look forward to hearing from you.

[isdd2000]

Hi Symantec Users,

Backups are working if a restart is performed prior to the backup taking place.

[isdd2000]

Please See the information posted.

[isdd2000]

Please read bellow comments. Could backup exec hanging be a product of trying to connect to the media server?

[Nicenavin]

Check the Domain controller time synchronization, some time difference may cause this issue.

Also check the DNS records are available with latest updates.