SQL backup policy and permissions error

[alopez]

We have a project in GCP, which we have added and created the service account like all projects, we generate the service account and assign permissions with the script provided by veeam, we check permissions and everything is validated correctly.

We created a policy to back up the Compute Engine instances, everything is fine and it has been doing the backups for a few days with no errors.

We try to create a backup policy for SQL in this project, we do the initial check of permissions and everything is correct.

We select the region and when trying to list the resources that we want to protect with said policy, we get this permissions error "Unable to rescan SQL instances in the project XX. Insufficient permissions" and we cannot continue creating this policy for this project.

We have created policies for other projects in this way and they are working correctly, we have reviewed the permissions of the service account of this project and we see exactly the same permissions for this one as for another of another project.

To test if it was permissions, we have given owner permissions to the service account and it throws the same message "Unable to rescan SQL instances in the project XX. Insufficient permissions"

What could be happening that makes it not work?

[Mildur]

Hi alopez

If you configured the mandatory permissions and it doesn't work with them, please open a support case. Our Support can analyze the logs and tell you what's missing.

Worker Permission for Cloud SQL
Snapshot Permission for Cloud SQL
Backup Permission for Cloud SQL

Thanks
Fabian

[Vitaliy S.]

Hi alopez,

To make sure we are on the same page: you have two projects, in one of them you're able to back up Cloud SQL instances and in another one you have the permissions issue, right? Can you confirm that both permissions are set: "cloudsql.instances.list" and "cloudsql.instances.get" for the project where you have issues with?

Thanks!

[alopez]

Hi alopez

If you configured the mandatory permissions and it doesn't work with them, please open a support case. Our Support can analyze the logs and tell you what's missing.

Worker Permission for Cloud SQL
Snapshot Permission for Cloud SQL
Backup Permission for Cloud SQL

Thanks
Fabian

I wanted to open a support case, but when I try to add my support id it says "Support ID cannot be found, please check it and try again." and I can't continue creating the case.

Hi alopez,

To make sure we are on the same page: you have two projects, in one of them you're able to back up Cloud SQL instances and in another one you have the permissions issue, right? Can you confirm that both permissions are set: "cloudsql.instances.list" and "cloudsql.instances.get" for the project where you have issues with?

Thanks!

Correct, both projects are the same, with the same permissions and these two specific permissions are in the service account of each of the projects.

In addition to not listing the sql instances creating the backup policy, I get an alert from time to time about this same project that says:

[Vitaliy S.]

Ok, if you have all those permissions set and still see the error, then opening a case is, indeed, required. If your support ID cannot be found, try to use the Talk to Manager option: http://prntscr.com/eCiohjdDw714

Once you open a support case, please let us know your ID. Thanks!

[Lab4CCIE]

When dealing with SQL backup policies and encountering permissions errors, it's essential to ensure that you have the necessary privileges and follow best practices. Here's a general approach to address the issue:

Review User Permissions: Verify that the user attempting the backup has the required permissions. Typically, the user needs the BACKUP DATABASE permission to perform backups.

Grant Permissions: If the user lacks the necessary permissions, grant them using SQL Server Management Studio or SQL commands. For example, you can use the following command to grant backup permissions to a user:

css

GRANT BACKUP DATABASE TO [username];

Verify Backup Device Access: Ensure that the backup device, such as a disk or network location, is accessible to the SQL Server service account or the user performing the backup. The appropriate read and write permissions must be granted for the device.

Check Backup Path: Double-check the path where the backups are being written. Ensure that the specified path exists, and the SQL Server service account or the user has the necessary permissions to write to that location.

Test Backup Policy: Test your backup policy by performing a backup using the SQL Server Management Studio or T-SQL commands. Check for any specific error messages that indicate permission issues or provide further insights into the problem.

Troubleshoot Specific Error Messages: If you encounter specific error messages, search for their exact meaning and possible solutions. SQL Server documentation and online forums are valuable resources for troubleshooting common SQL backup errors.

Remember, the exact steps and permissions required may vary depending on your specific SQL Server version and configuration. It's always recommended to consult the SQL Server documentation and seek assistance from your database administrator or IT department when dealing with backup policies and permissions errors.