Sharepoint 2010 with SQL 2010 backup failed

[demo4119]

system configuration

Server 1

Windows 2008 with Sharepoint 2010 (Front End)

BE 2010 R3 with latest hotfixes

Server 2

Windows 2008 with SQL 2010 ( backend)

I have tested the credential for the full admin of Sharepoint and SQL successful. But when the backup policy for the Sharepoint farm started it will always prompt the error message below. But Front End configuration can be backup successful but no the backend SQL database,

error message from backup job

0x0009b61 - the logon account that was provided does not have valid credentials. ensure that the user name and password are correct, then try again

additional info v-79-57344-39777

Pls advise.

[ZeRoC00L]

Are you sure the account you specify for the backup has the right (SQL) permissions ?

Rights to SharePoint databases

• Must be a logon account
• Must have backup operators role on each SharePoint database
• SSO (Single Sign-On) databases:  must be either the account name or a member of the group that is specified in the "Account name" field on SharePoint Portal Server Manage Settings for Single Sign-on administration page in the Single Sign-on Settings section

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

[pkh]

Try adding the BESA as a db_owner on each of the back-end SQL databases,

[V4]

Hi 

Can u please verify SQL version. it would be 2008  not 2010...also verify that your account is not locked.. sometimes this also causes issue.. and make sure if due to compliance policy password is changed you also change it into services as NBU doesn't syncs with AD for updated password.

[DoubleEM]

Hi all,

Thanks for the responses.

First, SQL is 2008 and BE is R3.

Second, the same account is granted as local admin as well as able to login and browse the databases in SQL studio management. DB_OWNER is certainly granted to this account and status is OK (not locked and grant to login)

Third, try to follow this link but the excludes list is empty.

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

Fourth, the front end server, where the BE media is installed doesnt have credential issue. Use the same account, I successfully tested the credential.

Fifth, flat file backup on the back end server completed with no issues. Eliminate the potential of BE remote agent problem.

Rechecking the rights as suggested by the ZeroCOOL.

Any other things to try? Many thanks

[ZeRoC00L]

Do you also have this problem if you run a 'normal' backup job (not a policy).

[DoubleEM]

Hi ZeroCOOL,

All the jobs tried/created are not under policy.

Thanks

[ZeRoC00L]

Ah, because in you startpost you mention: "But when the backup policy ...."

So I thought you were using a policy to backup the sharepoint environment.

[DoubleEM]

No worries... We all Netbackup trained and so use to the NBU term  

Btw, hardly use policy in BE.

[DoubleEM]

Was on a webex with support. He told me that domain admin rights is MANDATORY?

According to doc (http://www.symantec.com/business/support/index?page=content&id=TECH130255#SharePoint_Agent), it is best practice. Any comments?

Thanks in advance

[ZeRoC00L]

Is the backup working fine when the service account is added to the domain admin group ?
(restart BE services after adding to the group to be sure to get the 'new' access).

[demo4119]

The test run for credential and Policy is successful. monitoring the weekend backup status.

[ZeRoC00L]

Oke, good, what have you changed ?

[DoubleEM]

Hi ZeRoC00L,

We changed the BE logon acct to domain admin acct. Problem is while the test backup running fine, we still hit error when the actual backup runs. See the link below for details:

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

It seems that Lady Luck is not on our side. The log has been turned on and now waiting for Support to collect it and analyze. Hope we can resolve this soon cause the Sharepoint is already in production...

[DoubleEM]

We managed to isolate that the Global settings and Shared Services components are causing problem. The other components can be backup fine.

Still waiting for support to feed back and meanwhile we are turning to Sharepoint internal backup as a workaround.

Will keep the post updated...