Backup and DR fails to onboard Microsoft SQL Server

[matinlotfali]

Hi. I am trying to add the Microsoft SQL Server application to my Google Backup and DR Management Console. The SQL instance is discovered on my Host and databases are listed correctly. I also include the super admin credentials in the settings. But in the end, when I try to finish the wizard, it shows me the error below:

Onboarding failed: Unable to find the application undefined.

Can anyone help me to find the issue?

[Willbin]

Hello @matinlotfali,

Welcome to Google Cloud Community!

You need to resolve the conflict on the appliance that is experiencing the issue. Based on the identified conflict you can do the following:

---

• Rename conflicting backup templates on the appliance.
• Modify a conflicting backup template on the appliance to add the missing policies or remove the extra policies.
• Modify the attributes in the differing policy (or policies) in the conflicting backup template on the appliance to make the attributes the same.
• Modify the services or rights associated with the conflicting role identified on the appliance to make the services or rights the same.

Imported backup templates, organizations, users, and roles that already exist in the management console–that have the same name—are addressed as follows:

• Backup templates: Templates go through a conflict-resolution process by management console as described below.
• Organizations: Imported Backup and DR management console-level organizations with the same name are merged with the management console-level organizations, and their management console-level objects—users and backup templates—are associated with their respective management console objects
• Users: Users that already exist in management console are ignored and are not imported from the appliance.
• Roles: Roles go through a conflict-resolution process by the management console as described below.

---

See also Backup and DR Faq

[matinlotfali]

I can't find any name conflicts

[Mike-GCBDR]

Sorry to hear you've encountered an error when trying to setup protection for a SQL Server.

One question for you - when you say you provided the super admin credentials in the settings, I am wondering if you updated the Actifio agent service account to run as a user with these permissions, or if you entered them into the UI?  Either approach should work, but generally speaking it is easier to make the service run as an account that has the required permissions, so you do not need to re-enter the credentials every time you want to perform a recovery.

This video has a nice walk-through of the setup process. At about the 5 minute mark the video talks about security and how to ensure all required permissions are available without entering them into the UI. Note: the video talks about granting permissions to the default service account, but you also can change the account for the service to a local or domain account with the appropriate permissions, and then restart the service.

If the error is not resolved with the above update to the method of granting access, then we also see this error when the SQL Server has an out-dated version of SQLPS. You can update it using the information on this page: SqlServer module in the PowerShell Gallery

I hope this helps you get past the error.

[matinlotfali · Accepted solution]

I learned that the error is shown for the Microsoft SQL Server Express Edition.
Sadly the Google Backup and DR does not support the Express Edition.

[Mike-GCBDR]

Thanks for replying with the resolution!

[Eddie_NC]

I have faced an error while connecting the Backup and DR Appliance host, the Error, message is: Partial Success Host update operation successful. Connection to 192.*** failed. This is within the 2hour period of generating the secret, any solution or guide on the same would be highly appreciated