Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

SQL Errors on BE2012 backup server.

Created: 09 May 2012 • Updated: 15 May 2012 | 6 comments
This issue has been solved. See solution.

Hi,

I keep getting this error when backing up the BE2012 server. Links referred to either talk about previous versions or have not resolved the issue. Any Suggestions would be helpful??

One suggestion of perfoming seperate backup without AOFO for just SQL just makes an already confusing backup routine (By Server a.k.a BE2012 rather than Backup Job) even worse.

 

Backup
V-79-57344-65268 - Snapshot Technology: Initialization failure on: "servername\BKUPEXEC". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-10896 - SQL Prepare for Freeze failed for snapshot.

 

Backup- PANAUSBCK.pandrol.com.au\BKUPEXEC
V-79-57344-5891 - The object was not found, or could not be accessed (MS SQL backup).
The item ServerName\BKUPEXEC\master in use - skipped.
V-79-57344-5891 - The object was not found, or could not be accessed (MS SQL backup).
The item ServerName\BKUPEXEC\model in use - skipped.
V-79-57344-5891 - The object was not found, or could not be accessed (MS SQL backup).
The item ServerName\BKUPEXEC\msdb in use - skipped.
V-79-57344-5891 - The object was not found, or could not be accessed (MS SQL backup).
The item ServerName\BKUPEXEC\BEDB in use - skipped.

Comments 6 CommentsJump to latest comment

pkh's picture

You don't have to backup the BKUPEXEC instance.  BE will do its daily maintenance and backup its own database daily.  You can deselect the BKUPEXEC instance.

SOLUTION
Backup_Exec's picture

Hi

 

Please check the link below

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

 

Thanks

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

pkh's picture

What has this to do with the user's problem?

Backup_Exec's picture

Hi

The link will be helpful as in his case backup are failing with cannot access or database not found. As SQl agent uses VDI interface to perfrom online backup the solution part given in the link will help to resolve his issue if there is any issue with VDI interface

 

Thanks

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

CraigV's picture

Hi Nick,

 

pkh is right...you can get away with not backing up the BEDB through SQL.

However...you need to check to see if you're getting VSS errors on the target server.

Open a command prompt, type: vssadmin list writers. Any writers NOT stable and running are in error, and you can do 1 of 2 things:

1. Restart the server, rerun the command and check the VSS writers. THis should make them stable again.

2. Reregister the VSS writers as per the TN below:

http://www.symantec.com/business/support/index?page=content&id=TECH70486

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

NickB111's picture

Guys

 

Thanks for all your responses. It has taken a while to work through them all , however none seem to have resolved the intital problem.

 

I have decided to go with the solution from pkh which makes a lot of sense to me.

 

Thanks