Failed to create SQL shadow for database

You should check the status of your writers.

Ignore the fact that this is a veritas article the steps should be the same. 

https://www.veritas.com/support/en_US/article.100020300

Hi @chrisknows ,

I have already checked the below  given command but there is no error,

"vssadmin list writers"

Could you please share any other solution for this issue

This may sound obvious but is the SQL writer there? 

I have in the past listed the writers and they all show no errors, but what I didn’t realize is that the writers are missing.

Can you post the contents of the backup log for SQL?

Thanks.

Chris.

@Adarsh.op  This is a SQL AG?

Its best to leverage the SQL AG client itself 

https://documentation.commvault.com/2022e/expert/18295_always_on_mssql_availability_groups.html

Also make sure you unchecked use vss option on the properties of the SQL agent under each client machine.

Hi @Scott Reynolds ,

 This is a SQL AG? Yes

Its best to leverage the SQL AG client itself https://documentation.commvault.com/2022e/expert/18295_always_on_mssql_availability_groups.htmlAlso make sure you unchecked use vss option on the properties of the SQL agent under each client machine. -We have already unchecked this VSS option in the each client.

Okay so do you know if you are running appaware backups or intellinsnap? This would be the only other option it would leverage VSS for the backups.

As a test you could disable the appaware option and run a backup to test backups leveraging VDI and confirm those are working. Besides that checking Windows app/sys log can also help troubleshoot the issue as vss usually logs some info in there like space issues, shadow storage limitations, etc

Hi @Scott Reynolds , 

I will try all the steps you shared, But still i hva egetting same error

failed to create SQL shadow for databse