Confirming and/or configuring the Backup Exec Service Account(BESA) to the 'db_owner' role using Microsoft SQL Server Management Studio Express.

Article:TECH66396  |  Created: 2008-01-31  |  Updated: 2013-07-10  |  Article URL http://www.symantec.com/docs/TECH66396
Article Type
Technical Solution


Issue



How to confirm and /or configure the Backup Exec Service Account to the 'db_owner' role using Microsoft SQL Server Management Studio Express.


Cause



BESA account is not  part of the db_owners group on the SQL Server.


Solution



When utilizing the SharePoint Agent for Backup Exec for Windows Servers to backup MOSS 2007/2010 Content Databases, it is best practice for the Backup Exec System Account <BESA> to be have the 'db_owner' role.

In some cases, the Database Owner can be the BESA Account but is not required. Confirm the SQL Database Owner using Microsoft SQL Server Management Studio Express.

1. Open the Properties of the SQL Database as shown in Figure 1.
 
Figure 1:
 
 

2. On the General Page of the Database Properties, confirm which account is set to be the Database Owner as shown in Figure 2:
 
Figure 2:
 
 


To add and/or configure the 'db_owner' role for the BESA account for the SQL Content Databases:

1. Click on the Content Database and drill to Security | Users and Click New User as shown in Figure 3.
 
Figure 3:

 

2. Add a User Name and Login name in the appropriate fields (User Name is generic and does not contact Active Directory) as shown in Figure 4:
 
Figure 4:

 

3. Under 'Database role membership' select the db_owner check box as shown in Figure 5:
 
Figure 5:

 

4. The BESA account will show beneath the security folder for the Content Database as shown in Figure 6.
 
Figure 6:

 

Note - If the BESA account being used on Backup/Restore is not set with the 'db_owner' role as shown in SQL Server Studio Management Express then authentication errors and/or limited GRT selections may be exhibited. The BESA account will need to have this role on ALL SQL Content Databases within the Farm.


Alternatively, the current SQL Content Database owner can be replaced. This is not required and should only be done under circumstances necessary and when the role permissions noted above do not work.

If desired and no negative impact on SQL can be confirmed; it is possible to change the SQL Database Owner by issuing the Transact-SQL command <EXEC sp_changedbowner 'accountname'>

The example below makes the BESA login 'Sandman\Administrator' the owner of the current database and maps to 'sandman\Administrator' existing aliases that are assigned to the old database owner.

1. Highlight and right click the Database to run a New Query as shown in Figure 7.
 
Figure 7:

 

2. Execute the command <EXEC sp_changedbowner 'sandman\administrator'> as shown in Figure 8.
 
Figure 8:

 

3. After Executing the command, you should see 'Command(s) completed successfully.' at the Messages field in the Query pane as shown in Figure 9.
 
Figure 9:

 

4. Confirm within the Database Properties the SQL Database Owner has changed as shown in Figure 10.
 
Figure 10:

  





 

Supplemental Materials

Description

 Added cause and the removed duplicate version of Backup exec.



Legacy ID



317055


Article URL http://www.symantec.com/docs/TECH66396


Terms of use for this information are found in Legal Notices