SQL unavailable

[darkhelmet]

I have installed Veeam on W8.1 64-bit with VEB beta.

I get an error when trying to make a backup (the first):

19-1-2015 11:12:09 :: Microsoft SQL server hosting the configuration database is currently unavailable. Possible reasons are heavy load, networking issue, server reboot, or hot backup. Please wait, and try again later. Error information: Cannot insert duplicate key row in object 'dbo.BObjects' with unique index 'IX_BObjects'. The duplicate key value is (6745a759-2205-4cd2-b172-8ec8f7e60ef8, 4c4c4544-005a-3210-8058-b3c04f463132). The statement has been terminated.

SQL services are running, restarting the laptop has no effect. Pausing anti-virus (Avira) has no possitive effect either.
Laptop is nearly idle, backup destination is a USB drive.

I can try to reinstall Veeam, but i'd like to know what's broken....

[Mike Resseler]

Hi,

This looks like an interesting issue. the fact that it states that he cannot insert a duplicate key doesn't seem nomal. Could you go to the control panel of Veeam Endpoint Backup, support tab and use the technical support to submit a support case? It might be known already, but I haven't seen the issue yet.

Thanks for your help!

Mike

[darkhelmet]

Hi,

This looks like an interesting issue. the fact that it states that he cannot insert a duplicate key doesn't seem nomal. Could you go to the control panel of Veeam Endpoint Backup, support tab and use the technical support to submit a support case? It might be known already, but I haven't seen the issue yet.

Thanks for your help!

Mike

it was just submitted: 00730101

[Mike Resseler]

Thanks a lot!

Cheers

Mike

[darkhelmet]

And i already got a response from support. The described solution worked, although i cant continue on the previous backup.

1. stop EndPoint service
2. execute regedit. go to HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup\ and make a new DWORD value recreatedatabase=1
3.restart service
4.delete previously created value
5. at this point we can`t do any FLR yet, you will need to configure a new backup job, save the previous backup folder to a different destination or rename the current folder, because the old backup chain will not be picked up 6. start the backup job, once it`s complete FLR can be run

[darkhelmet]

backup running flawless now. Takes 10:35 for a full

For comparison Symantec System Recovery 2013 R2 takes only 8:15 for exactly the same backup, so even faster. But still Veeam feels fast

[Dima P.]

darkhelmet,
Glad, you are up and running now.

For comparison Symantec System Recovery 2013 R2 takes only 8:15 for exactly the same backup, so even faster. But still Veeam feels fast

Just to be on the same page these are performance results for full backup run (or it was incremental)?

[JoshHawley]

Thanks for posting this! I had the same problem, and this worked for me too.

[Dima P.]

P.S. Just do not forget to remove the said registry value once you are up and running – otherwise, it recreates database on every service restart. Thanks.

[TroyResources]

Good morning, well this morning my end point reported the very same error.
Thanks for the solution.
After deleting the reg key is it advisable to restart server?
is this fixed in v1.1?

Also to ensure no lose of data I exported disk contents as VDMK for 5 day retention period.

[Dima P.]

Hi,

this morning my end point reported the very same error

Anything changed in regards to your infrastructure? Windows updates or something similar?

After deleting the reg key is it advisable to restart server?

Add the key – Restart the service or restart the machine – Delete the key

is this fixed in v1.1?

We’ve made some improvements for sure.

[TroyResources]

Hi @Dima,

Nothing in environment had changed, sorry very common support comment.
Backup is now working thanks to the post by DH.

Thanks for your input...

[Dima P.]

Good, thanks! As I said before we’ve improved the database handling in the next version, so hopefully is going to cover issues like yours - let’s wait till it released and test it. Meanwhile, if you face this behavior again – please open the support case before recreating the database. Cheers!

[TroyResources]

@ Dima, thank for feed back. If this scenario does present itself again I will certainly pen a support ticket.

Cheers!

[wkmiller]

Thanks for the post - one of the workstations was having this issue and the database recreate worked!

[Dima P.]

Hi Wayne,

Did you see any suspicious activities at the said workstation? Could the Operating System be recently updated? Thanks

[Jan1]

Hi,

I had exactly the same error in VEB 1.5.0.316. Recreate database helped but it looks that this problem still exists.

Jan

[Dima P.]

Hi Jan,

Have you raised a support case? Thanks.

[motoxrdr21]

The RecreateDatabase solution listed in this thread would probably be a good candidate for a KB article to fix a corrupt configuration db. I just had a similar issue with the latest 1.5 where backups failed with a SQL timeout error, tried multiple reinstalls & a couple other solutions before stumbling on this, which worked flawlessly.

[Dima P.]

Steve,

Thank you for the heads up. Can you clarify were you backup files fully operation after you fixed this issue?