• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 27 subscribers
  • Views 6099 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

See SQL instance when SQL alias in use

SEVAUGHN
over 7 years ago

Hi there,

Switching our SharePoint backups from AvePoint over to AppAssure, which has been doing a great job of -well, everything other than SharePoint in our environment! But it means I'm a newby to AppAssure, and the experienced staff member is away crook.  

Issue is the AppAssure console can't see the SQL instance on my SharePoint database server.  I'm suspecting the issue might be the alias on the database instance (so the DB is accessed remotely referenced by something other than the server name). I am also suspecting the 'non standard' ports used for the SharePoint SQL.  Both of these thing are MS best practice, but have cause hiccups in the past.

Any assistance appreciated!  Hoping to get DocRetriever working soon, but obviously won't be able to progress until DB is visible to backups.

Parents
  • 0 over 7 years ago

    Hi Tudor.Popescu,

    Thank you for such a considerate reply.  

    Yes, foolish me, the name AppAssure was long ago.  We are on version 6.0.1.609 of 'Data Protection | Rapid Recovery'.  I checked the registry key you show in your screen shot, and it is correct. Also, I take it from the existence of the 'DisableSQLMetadata' Dword that the Agent version can't be too far off. With those (roughly) ruled out the next best target is WMI.  I took the actions listed here:

    https://support.software.dell.com/appassure/kb/123254

    -no improvement.  Then, happily, I tried to open SQL Server Configuration Manager and it failed, blaming WMI.  I took the actions listed here:

    https://support.microsoft.com/en-au/kb/956013

    and now SQL Server Configuration Manager is able to open on our SharePoint DB server.  Seems possible that this will resolve the issue with Data Protection, but I will be unable to test until tomorrow.  Will update then.

    Thanks again.

Reply
  • 0 over 7 years ago

    Hi Tudor.Popescu,

    Thank you for such a considerate reply.  

    Yes, foolish me, the name AppAssure was long ago.  We are on version 6.0.1.609 of 'Data Protection | Rapid Recovery'.  I checked the registry key you show in your screen shot, and it is correct. Also, I take it from the existence of the 'DisableSQLMetadata' Dword that the Agent version can't be too far off. With those (roughly) ruled out the next best target is WMI.  I took the actions listed here:

    https://support.software.dell.com/appassure/kb/123254

    -no improvement.  Then, happily, I tried to open SQL Server Configuration Manager and it failed, blaming WMI.  I took the actions listed here:

    https://support.microsoft.com/en-au/kb/956013

    and now SQL Server Configuration Manager is able to open on our SharePoint DB server.  Seems possible that this will resolve the issue with Data Protection, but I will be unable to test until tomorrow.  Will update then.

    Thanks again.

Children
No Data