Video Screencast Help

I am having the same issue on

Created: 09 Nov 2012 | 8 comments

I am having the same issue on a fresh install of BE2012 14.0. When I test credentials it passes the "Microsoft SQL Server Instances" logon, but fails the MICROSOFT ##SSEE and MSSQLSERVER logons. All other backup jobs finish successfully including Exchange GRT backup.

I have tried checking the permissions, but every thing looks fine. I am a newbie to SQL, but did add an account in security (The one I created for this install of BE) and gave it admin rights to every checkbox and still the permission checks failed. I believe the default user for access was set to System Logon Account, but I changed it to the Domain Admin Account I used to set everything else up with and those credentials fail as well.

The job fails with the following error:

Unable to attach to <MYSERVER>\MSSQLSERVER.

V-79-57344-33932 - 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.

Unable to attach to <MYSERVER>\MICROSOFT##SSEE.

V-79-57344-33932 - 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.
 

Comments 8 CommentsJump to latest comment

CraigV's picture

...moved to a new discussion as per Donald's request.

Alternative ways to access Backup Exec Technical Support:

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

VJware's picture

Pls ensure named pipes & TCP/IP protocols are enabled & the Backup Exec account has enough privileges ...verbatim from KB ~

1) Open SQL Management Studio

Connect to the Instance>Security>Logins

2) Find the Backup Exec account or the account used for the SQL backup in the List

If it is not found, add it and give it Sysadmin role

If it is already present, make sure it has Sysadmin Role assigned

3) On the same "Select a page" option  select "User Mapping

4) Under "Users mapped to this login" select "master" database

5) Under "Database role membership for: master" select "db_datareader" and "db_datawriter"

 

SD33's picture

Well, after doing some more research there is probably no point in trying to fix this. I am trying to back up a SCCM 2012 server. Further reading says that the only way to recover a site is to use the SCCM backup service,which I ran last night, and restore using the SCCM restore tool.

With that in mind I am more confused than ever as most SCCM 2012 Restore guides talk about rebuilding the machine from scratch and then using the SCCM 2012 recovery tool. It would seem to me that I could use BE to backup everything except the SQL Database, use that to restore the server and then run the SCCM recovery tools.

If there is a simpler backup and restore procedure for SCCM 2012 I'm all ears :)

In case anyone is curious as to some of my reading on the subject http://anoopcnair.com/2012/07/01/sccm-configmgr-20...

 

Also, while I appreciate the thread creating, doesn't seem like the title is going to attact a lot of attention :)

 

- Shawn

SD33's picture

Also, the above mentioned solutions did not fix the access issues when testing credentials of the job.

Donald Eady's picture

 

SD33,
 
what version of SQL are you running and what OS is it running on ? Is the service account D.B. admin on that server and are you able to backup anything else on that box

I hope this posting was helpful

  

SD33's picture

SQL Server 2008

 

Microsoft SQL Server Management Studio                        10.0.5512.0
Microsoft Analysis Services Client Tools                        10.0.5500.0
Microsoft Data Access Components (MDAC)                        6.1.7601.17514
Microsoft MSXML                        3.0 6.0
Microsoft Internet Explorer                        9.0.8112.16421
Microsoft .NET Framework                        2.0.50727.5456
Operating System                        6.1.7601

Windows Server 2008 R2 Standard 64-Bit

 

Not sure what you mean by service account D.B admin.

I just ran the job without SQL selected and these were the results:

Click an exception below to locate it in the job log
Resource<MYSERVER>\MICROSOFT##SSEE was found in the previous instance of this job, but it is not present in this job.

Resource <MYSERVER>\MSSQLSERVER was found in the previous instance of this job, but it is not present in this job.

The backup options or selections for this job have changed since the last time it ran.

Backup- \\<MYSERVER>\System?StateVSS Snapshot warning. File c:\windows\\systemroot\system32\drivers\lsi_sas.sys is not present on the snapshot.
 

You have successfully completed a backup job that includes all critical system components. The computer is now fully backed up.

Backup Exec stores the important disaster recovery information file in the default disaster recovery path of the Backup Exec server, and at an alternate location of your choosing. However, Symantec recommends that you make an additional copy of the file and store it in a safe place. Without a disaster recovery information file, you cannot recover a Backup Exec server from a tape drive or an autoloader with Simplified Disaster Recovery. Having multiple copies of a disaster recovery information file ensures that you have at least one copy if a recovery from a disaster is required.
Click the Backup Exec button and go to Configuration and Settings > Backup Exec Settings > Simplified Disaster Recovery to determine the Backup Exec server's default disaster recovery path, which is where the disaster recovery information file resides.

 

 

SD33's picture

Is this issue considered closed? Is there no single solution using BE 2012 to back up a SCCM 2012 server and the actions above are considered the correct way to back up an SCCM Server?

 

Thanks,

Shawn