• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 27 subscribers
  • Views 6082 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

    Hurray!

    Yep, running the MofComp command with the correct version of SQL Server in the path (as outlined here) means RapidRecovery can see the SQL instance.  I wonder what causes this WMI corruption in the first place? 

    Cheers,

Reply
  • 0 over 7 years ago

    Hurray!

    Yep, running the MofComp command with the correct version of SQL Server in the path (as outlined here) means RapidRecovery can see the SQL instance.  I wonder what causes this WMI corruption in the first place? 

    Cheers,

Children
No Data