SQL Server Restore : Source list is longer than target list

[sommerso]

Hi,

I'm getting an issue when doing a SQL server restore from this mornings backup. At the moment the DB is down. When I do the restore, it goes through all steps.
Mounting Restore Point
Calculating Required space

and then I get an error
Source list is longer than target list.

Windows 2012
SQL Server 2016


Case #05059154


What am I possibly missing?

[HannesK]

Hello,
if I understood support correctly, then the restore was done using a workaround.

For the root cause: please continue investigating with support. I makes no sense to speculate about that kind of error on a forum.

Best regards,
Hannes

[sommerso]

Hi Hannes,

I understand. If you had a look at the time stamp of this post, it was posted before there was a "workaround" provided by support. It was out of desperation as there were no answers and the supposed work around would have taken 2 days to restore the production DB.

[edk3r]

I have the Same error, Do you have a Workarroun?

[PetrM]

Hi Eduardo,

As a workaround, you can try to restore the entire VM or to perform VM Instant Recovery and extract DB from the restored VM. But if there is no urgency, I'd propose to wait for the result of technical analysis from our support engineers. Also, please share a support case ID over here for our reference.

Thanks!

[edk3r]

Hi Peter, It was a bad configuration in the job with the truncate logs option. Thanks

[PetrM]

Hi Eduardo,

May I ask you to elaborate more on it? What do you mean by "bad" configuration?

Thanks!

[leeuwena5]

Hi,

I have the same issue.
Trying to restore a SQL-database fails with this error.
I have changed backupjob from Backup Logs every 15 minutes to Truncate Logs, but no difference in restore.

Can you or anybody elloborate what I should do differently, or how I should setup my backupjob of SQL-databases on a physical server with an Availability Group?

Thank you!

[PetrM]

Hello and Welcome to Veeam R&D Forums!

Please contact our support team and provide a support case ID as requested when you make a post about a technical issue. We cannot troubleshoot technical issues effectively over the forum posts. All posts about technical issues without case ID will be eventually deleted by the forum moderator. You can also upload debug logs for our support as per the instructions of this KB.

Thanks!

[kacperxxx]

In 2024 this problem still exists, do you know how to solve it?

[PetrM]

Hello and Welcome to Veeam R&D Forums!

This error is generic and can occur due to various reasons. Please open a support case to determine the root cause of the issue and provide a support case ID. As mentioned earlier, any posts regarding technical issues without a support case ID will eventually be deleted by the forum moderator.

Thanks!