Backup Exec Errors and SQL Server Errors

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Has the SQL backup ever worked? If so, can you pinpoint any change that was made around the time it stopped working?

SOLUTION

David Todd

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

VSS is not disabled. I have already checked that. It does backup without errors every now and then on the same jobs but most of the time there are errors.

how did you set BE connection to sql server? make sure that BE login has sql server login rights.

Not sure what you mean by how I set the connection. The BESA account has domain admin permissions.

How are this server resources doing during this connection attempt? is the server busy (memory/cpu?)?

I am going to setup a monitor to monitor the resources at the time of backup as I have not done that yet.

What is your BE version? sql server 2005 edition sp? What is your Windows editon ; version, sp?

BE version is 12.5 rev. 2213, SQL Server 2005 SP2, both servers are Windows Server 2003 SP2.

ASKER

There are 10 GB available on C drive and 70 GB available on D drive (where data dbs are stored) of the SQL Server. The Backup Exec server has even more space allocated to both C and D.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

ID: 38876957 states the version of SQL server and OS for both servers. One thing to keep in mind is that the same jobs sometimes do finish without errors. Could a service, process, or an sql job be causing this?

If so, how could I narrow down my search?

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

It is directly associated with the System State and Shadow Copy Components.I had removed the system state from being backed up and it backs up just fine.

Sorry for not mentioning that but yes, you are correct in your assumption.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Are there any errors in the event logs? I'm looking at this article, which is similar to your issue except for the Windows server OS version:

http://www.symantec.com/business/support/index?page=content&id=TECH187366&actp=search&viewlocale=en_US&searchid=1360679439718

ASKER

Good day everyone. My apologies for the late reply but I was away at a conference all last week.

Getting back to the issue.

EugeneZ, yes the BESA account used for the Backup Exec backups does have access to the SQL server. It does not have an account listed under the Security/Logins section of SQL server where all the accounts are listed. Should it?

How and where do I check if the BE installed a named instance?

hypercat, the only error I see in the System logs of the event viewer in the last 24 hours is the following which does relate to when one of the backup jobs shows as failed but there was also other backup jobs for sql that showed as failed but no reported errors for these:

Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7031
Date:            2/19/2013
Time:            6:07:59 PM
User:            N/A
Computer:      MS7
Description:
The SQL Server Reporting Services (MSSQLSERVER) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

ASKER CERTIFIED SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

I haven't rebooted the server in a long time. I will attempt that this Saturday adn will monitor. If it continues, I will reregister the VSS writers.

The link you posted does not have a working link as to how to reregister the writers. Could you point me to a good how-to guide?

Here's a good one:

http://support.microsoft.com/kb/940184

Here's the Symantec one that corresponds with the error messages you're getting in BE:

http://www.symantec.com/business/support/index?page=content&id=TECH64330&actp=search&viewlocale=en_US&searchid=1361393228470

ASKER

Great. Thank you. I will give it a try this Saturday and report back.

<It does not have an account listed under the Security/Logins section of SQL server where all the accounts are listed. Should it?>
it should

<How and where do I check if the BE installed a named instance?>

several ways - > in windows services

if you see SQL Server (BKUPEXEC) - -> it is sql server yourboxname\BKupexec named sql server instance

if just SQL Server (MSSQLSERVER) -- it is your default ==> sql server "yourboxname"

ASKER

And where do I check this...on the SQL Server or on the Backup Server?

Also, if I created an account on SQL Server for the BESA account, what permissions would it need?

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.