KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : How to Check SQL Permissions for arcserve RHA High Availability?

Last Update: 2015-08-31 07:53:47 UTC

XOSOFT Replication: 12.0, 12.5, 15.0

Last Modified Date:    12/06/2010
Document ID:    TEC537191
Tech Document
Title:  How to Check SQL Permissions for CA ARCserve RHA High Availability?

Description:

This article will explain in detail how to check if appropriate permissions are enabled in SQL 2005 to work with an HA scenario.

Solution:

CA ARCserve RHA uses Windows Authentication with MS SQL Server. The account assigned to the CA ARCserve RHA engine service will need to be a member of the SysAdmin role in the MS SQL instance defined in the High Availability scenario. In a CA ARCserve RHA High Availability Scenario for MS SQL, it is strongly recommended that the user account assigned to the CA ARCserve RHA Engine service be a domain user which is a member of the Domain Admins. group. By default the Domain Admins. Group is added to the Local Administrators Group on all Domain Member Servers. In SQL, the built in\Administrators group is a member assigned the SysAmin role. Therefore as a member of the Domain Admins. Group the CA ARCserve RHA Engine is granted the privileges of the SysAdmin. role in SQL.

  • If the Domain Admins Group has been removed from the Local Administrators group, then the CA XOsoft Engine service account will need to be added to the Local Administrators group manually.
  • If the builtin\Administrators are not granted the SysAdmin role, then the CA ARCserve RHA Engine service will need to be added as a SQL Login and granted the SysAdmin role.
  • The same membership to the Local Administrators group and SysAdmin role would apply to the SQL server in a Workgroup.

How to verify permissions in MS SQL Server:

  1. The first step is to open Microsoft SQL Server Management Studio
  2. Next expand the instance(s) you are protecting on the left hand pane
  3. Expand 'Security'
  4. Click on 'Logins'
  5. On the right hand pane right click on 'BUILTIN\Administrators' and go to 'properties'
  6. On the top left hand pane of the box that comes up click on 'Server Roles'.
  7. On the right hand pane that appears make sure there is a check in the 'sysadmin' box, if there isn't a check you can check this to add the appropriate permissions.

See Related Document(s): TEC438292

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments