CASE07011349 Cant install latest patch Veeam One12 before applying the vunerablity fix: SQL Cluster

[rtheseeker]

I am having issue installing the latest patches on Veeam one 12; I can use the Veeam One settings to access the DB instance and browse the server ; existing Veeam One monitor installation works fine as it collects data and writes to DB; however; when I upgrade I get the error message; also when I click browse next to use existing instance
"failed to connect to SQL server"
also, when I click on browse next to "Use Existing instance of SQL server (?Host\Instance) it bring a empty box.

The DB sits on a always on SQL cluster and DBA team had to create the DB when we initially installed Veeam One; we had upgraded to V12 this year from V11 as well.

Is there a script I can check to ensure DB permissions are right or any logs which can indicate whats going on?

DBA Team has confirmed that the service account has the permissions https://helpcenter.veeam.com/docs/one/d ... ml?ver=120
"
Public role (default permissions)
db_owner role on the Veeam ONE database
db_datareader permissions on the master database
[For Always-On Availability Groups] VIEW SERVER STATE, VIEW ANY DEFINITION permissions
[Optional]* public, db_datareader, SQLAgentUserRole permissions on the msdb database
Public role (default permissions)
db_owner role on the Veeam ONE database
db_datareader permissions on the master database
[For Always-On Availability Groups] VIEW SERVER STATE, VIEW ANY DEFINITION permissions
[Optional]* public, db_datareader, SQLAgentUserRole permissions on the msdb database"

[jorgedlcruz]

Thank you so much for the case number. We have not heard anything related.

Please allow the Support Engineers some time to debug and triage your issue, I will verify internally as well.

Thank you

[rtheseeker]

Is there a way to make sure that the permissions are okay [For Always-On Availability Groups] VIEW SERVER STATE, VIEW ANY DEFINITION permissions; although DBs have confirmed I still want to just make sure these 2 permissions are in place

[rtheseeker]

I have been advised to uninstall Veeam one and reinstall the latest version. This is happening in 2 enviromnets(DR and production) Unfortunetly, I do not think this is the right way forward as support has not advised me yet if they looked into the logs and are there any logs which point to that the issue is. Previously Veeam used to do remote support if they did not understand the issue; however it appears now a days that pracitce is no longer followed; it took multiple days and email just to make the support personal understand the issue and although I raised it a priority 2; my concern is if I uninstall Veeam one and cant reinstall the software due to connection issue; the app wont function any longer. Is there a way to test the always on SQL permissions outside of Veeam?

[rtheseeker]

as suspected, I tried uninstall and reinstall on DR server (Fortunetly); now the reinstall does not work and Veeam one is broken..raised sev to p1

[jorgedlcruz]

Certainly it is very strange, as the security fixes affects mostly webUI components and nothing SQL related.

Let me look internally, you cam always ask for an escalation to the manager from the support portal.

Did you take any backup of the files before applying the patch? Or before reinstalling ?

In the forum usually we do not cover or follow support cases threads like this one. Would you prefer we follow this closely together by email?

[rtheseeker]

Is there a powershell script that I can ask the DBA to run on the SQL server whcih returns the exact permission for the service account that are required for Veeam One. Going through the various fourams it appears to be permission on sQL server however DBA has confirmed that the permissions are fine.

[jorgedlcruz]

Hello,
We have this information documented over here: https://helpcenter.veeam.com/docs/one/d ... o_sql.html

This forum is not intended to discuss or troubleshoot issues that are being handled by support already.

However, if you find that anything is missing in the documentation, please let us know, but it has been verified by our QA and Devs engineers.

Please keep working with support engineers.

[rtheseeker]

We managed to upgrade Veeam one on DR server by giving system admin rights to the service account on the SQL server itself however we cannot do that on the production server as it is on AG which has other production databases as well and the DBA do not want to elevate the permissions; the service account already has the following rights as confirmed by our DBA; does it require any additional rights on the msdb database. What other permission could cause "failed to connect to SQL server"
“Public role (default permissions)
db_owner role on the Veeam ONE database
db_datareader permissions on the master database
[For Always-On Availability Groups] VIEW SERVER STATE, VIEW ANY DEFINITION permissions
[Optional]* public, db_datareader, SQLAgentUserRole permissions on the msdb database

[jorgedlcruz]

As mentioned before, it is difficult for anyone helping you on the forum with a generic error like "failed to connect to the SQL server" nor it is the intention of this forum.

Please keep working with support, where they have access to logs, and even to do webex with you.

Regarding the generic error, generic responses:
1.- AG Listener Support: Veeam ONE should connect to the SQL Server using the AG Listener. This ensures that Veeam ONE connects to the primary replica regardless of any failovers that might occur.Read

2.-Write Access: The database where Veeam ONE stores its data should be accessible with read-write permissions. Since AG typically involves multiple read-only replicas and a single read-write primary replica, it's crucial that Veeam ONE connects to the read-write replica.

3.- Proper AG Configuration: Ensure that the AG is correctly set up and fully operational. This includes having synchronized replicas and a functioning listener.

4.- Permissions: The account used by Veeam ONE to connect to SQL Server should have the necessary permissions on the primary replica of the AG. This typically means db_owner rights on the Veeam ONE database.

5.- SQL Server Version and Edition: Verify that the SQL Server version and edition you are using is supported by Veeam ONE. Some features of AG are only available in specific editions of SQL Server.

6.- Network Configuration: Network connectivity between the Veeam ONE server and all nodes of the AG is essential. This includes ensuring that firewalls are configured to allow traffic on the relevant SQL Server ports.

As said, this is a Support Issue, please read the forum rules veeam-backup-replication-f2/rules-of-po ... -t755.html

Let us know once resolved if you like, and what was the issue.