Highlighted

Error: e000848c when backing up SQL Server Instance

I have four servers that I am backing up. 3 of them have the option to select "SQL Server Instance" when setting up a backup. One of the servers backs up just fine with it selected however, the other two servers fail with the error noted below...I de-selected the SQL portion and the two servers backup just fine.

Error: e000848c, The job failed with the following error:
Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.

 

The wierd part is that when "SQL Server Instance" IS selected, the actual job and test runs show that every selected drive is unable to access the resource. How is having this selected preventing everything from seeing the resource I am trying to backup to. Makes no bloody sense. Moreover, how do I fix this so that I can do a backup of "SQL Server Instance". Thanks.

 

1 Solution

Accepted Solutions
Accepted Solution!

Check if the BE Service

Check if the BE Service account has been granted the System Administrator role on the SQL instance:

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

4 Replies

Does the BE service account

Does the BE service account has access to the SQL instances and databases ?

Edit:

Also check this technote:

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

Im supposing it does. Like I

Im supposing it does. Like I said I was able to backup the SQL Instance on one server but not the other two. Also I am not trying to restore, just backup right now.

Accepted Solution!

Check if the BE Service

Check if the BE Service account has been granted the System Administrator role on the SQL instance:

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

Re: Error: e000848c when backing up SQL Server Instance

I had this issue, in our case we had a disaster where an entire RAID array went on us.

Unfortunately we hadn't backed up the SQL install part of the instance so in effect we were trying to restore SQLINSTANCE to nothing which is why we kept getting the error.

I went into SQLExpress 2008 and created another instance, this time I called it SQLINSTANCENEW, once it was setup and ready, I pointed Backup Exec to our backup and found the database files we needed but made sure to select "restore to a different instance"

I ran it and it was successful.

 

Tags (2)