cancel
Showing results for 
Search instead for 
Did you mean: 

SQL Disaster Recovery configuration wizard fails

shahfar
Level 5
Accredited Certified

Hi Everyone,

I am facing an issue when running the DR config wizard for SQL (SFWHA 5.1 SP2) on a current node of a cluster. I get the error:

'Exception occured while discovering sql. Failed to discover 'Microsoft SQL Server' on Node 'S****4'.'

The SQL instance is up and running on this node and is in production. I have also checked the solutions configuration log and the last entry that I saw there is:

========================================

0,52410,208,208,303,1302589110737,8088,3964,7:S*****4,32: [4/12/2011 10:18:30 AM] Entered,35:CDRProxy::GetResourceAttributeValue,0

0,52410,208,208,304,1302589110737,8088,3964,7:S*****4,131: [4/12/2011 10:18:30 AM] Getting value Instance of resource SQLServer2008-MSSQLSERVER in Group 'SQL_SG' in cluster 'SQLPRODCLUS2_A',35:CDRProxy::GetResourceAttributeValue,0

0,52410,208,208,305,1302589110737,8088,3964,7:S*****4,131: [4/12/2011 10:18:30 AM] Getting value Instance of resource SQLServer2008-MSSQLSERVER in Group 'SQL_SG' in cluster 'SQLPRODCLUS2_A',35:CDRProxy::GetResourceAttributeValue,0

0,52410,208,208,306,1302589112389,8088,3964,7:S*****4,130: [4/12/2011 10:18:32 AM] Exception occured while discovering sql.

Failed to discover 'Microsoft SQL Server' on node 'S*****4'.

==========================================

This node has the default MSSQLSERVER instance installed and running. I am suspecting that the wizard is refering to some registry entry which might be blank. I have also verified that the sql instance entry in the registry is also MSSQLSERVER. Any help would be appreciated. Thank you.

-Shahbaz

1 ACCEPTED SOLUTION

Accepted Solutions

jlockley
Level 3
Employee Accredited Certified

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

Extract from this article for reference:

Verify that the account used to run the DR Wizard has the appropriate SQL permissions to execute SQL commands that are required to complete SQL discovery.

1. Bring SQL services online in VCS.
2. Open SQL Server Management Studio and connect to the instance in question.
3. Open Security --> Logins
4. Right click on the user and choose properties.  (If the user's account is not listed check the permissions for BUILTIN\Administrators.)
5. Choose Server Roles on the Login Properties window.
6. Make sure "sysadmin" is checked.  The wizard will not be able to discover SQL databases if this permission is not granted.
 

 

View solution in original post

4 REPLIES 4

Wally_Heim
Level 6
Employee

Hi Shahbaz,

I don't really have any suggestions based on what you have presented.  I would recommend that you open a case with Symantec Technical Support and provide a full set of VxExplorer logs from all nodes involved for us to review.

Thank you,

Wally

shahfar
Level 5
Accredited Certified

Interestingly, I moved the SQL service group to the other node in the cluster and the wizard went through sucessfully.

Wally_Heim
Level 6
Employee

Hi Shahfar,

That is interesting. Are you going to leave it the way it is or can you open a case with Symantec Technical Support so that we can investigate?

If you decide to open a case we will need to a set of VxExplorer logs from all nodes in the cluster.

Thanks,

Wally

jlockley
Level 3
Employee Accredited Certified

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

Extract from this article for reference:

Verify that the account used to run the DR Wizard has the appropriate SQL permissions to execute SQL commands that are required to complete SQL discovery.

1. Bring SQL services online in VCS.
2. Open SQL Server Management Studio and connect to the instance in question.
3. Open Security --> Logins
4. Right click on the user and choose properties.  (If the user's account is not listed check the permissions for BUILTIN\Administrators.)
5. Choose Server Roles on the Login Properties window.
6. Make sure "sysadmin" is checked.  The wizard will not be able to discover SQL databases if this permission is not granted.