Skip to main content
Question

SQL Database Backup is failed with Error

  • January 29, 2023
  • 7 replies
  • 4336 views

Forum|alt.badge.img+7

Hi Team,

I Have facing one issue in our commvault ,

While running the SQL database backup we have getting below error ,please provide any solution for the below issue.

Error Code: [30:324]

Description: "Error encountered when closing the virtual device, Please see SQL server vdi.log for more details"

 

7 replies

Forum|alt.badge.img+14

@Adarsh.op  Unfortunately that message is somewhat generic. It could be there was a backup outside of Commvault running at the same time, there was an issue writing the data to media, etc

We would need to see the SQLbackup.log on the client machine to get a better idea of the failure.


Forum|alt.badge.img

Check if the Log files drive is full. extend the drive size.


Forum|alt.badge.img
  • Novice
  • November 10, 2023

Check if the Log files drive is full. extend the drive size.

I got this error today and the drive is less than ½ full


Forum|alt.badge.img+14

Yes, the error is generic

Sometimes there is another underlying issue with the SQL server, database issue which prevented one DB from backing up, etc

@Adarsh.op / @AricA were you able to resolve your issues?


SivaShankarBehera
Novice
Forum|alt.badge.img+2

Hi,

I too received the same error message for one of my SQL DB server.

Error code: [30:324]

Description: Error encountered when closing the virtual device. Please see SQL Server vdi.log for more details.

Are there any specific solution/ troubleshoot steps for this? 

 

 


Forum|alt.badge.img+14

@SivaShankarBehera 

You can test native backup and confirm that works and SQL is functioning.

Also review the if there are any errors on the media agent sometimes this error occurs because the media agent fails to write data to media.

If unable to determine open case support and review logs and pinpoint the issue.

 


Forum|alt.badge.img
  • Novice
  • December 9, 2024

If everything looking good still backup failing with similar error reboot will fix the issue