Skip to main content
Answer

The storage system is in the SynchronizationFailed state

  • July 30, 2025
  • 4 comments
  • 42 views

Forum|alt.badge.img+1

The storage system is in the SynchronizationFailed state

 

Failed to synchronize storage data: An item with the same key has already been added. Key: 4422-afbb-aass-xdxd…..

 

I would like to try removing and adding the affected storage but not really sure to what extent this would affect the Orchestration Plans. Or could this just be a DB issue?

Best answer by spider32

I opened a support case with Veeam, thinking that there was a conflict in the DB. Gave them a copy of the VRO DB and found where the conflict is. They provided this SQL command:

delete from [VRO_DB].[VeeamAA].[StorageProtectionGroupSnapshot]

If anybody is encountering the same issue, I would recommend opening a case so Veeam Support can send you the exact SQL line to execute to avoid and DB inconsistency or issue. I will also check possible causes why the conflict occurred with Veeam. 

 

4 comments

Chris.Childerhose
Forum|alt.badge.img+21

@Madi.Cristil ​@safiya - please move this to VRO Den for better assistance.


Marcel.K
Forum|alt.badge.img+9
  • Veeam Legend
  • July 31, 2025

Could you please desribe closer, what kind of storwge you meant and how was added and in which process do you see this error?

Thanks 


Forum|alt.badge.img+1
  • Author
  • Influencer
  • Answer
  • July 31, 2025

I opened a support case with Veeam, thinking that there was a conflict in the DB. Gave them a copy of the VRO DB and found where the conflict is. They provided this SQL command:

delete from [VRO_DB].[VeeamAA].[StorageProtectionGroupSnapshot]

If anybody is encountering the same issue, I would recommend opening a case so Veeam Support can send you the exact SQL line to execute to avoid and DB inconsistency or issue. I will also check possible causes why the conflict occurred with Veeam. 

 


Chris.Childerhose
Forum|alt.badge.img+21

I opened a support case with Veeam, thinking that there was a conflict in the DB. Gave them a copy of the VRO DB and found where the conflict is. They provided this SQL command:

delete from [VRO_DB].[VeeamAA].[StorageProtectionGroupSnapshot]

If anybody is encountering the same issue, I would recommend opening a case so Veeam Support can send you the exact SQL line to execute to avoid and DB inconsistency or issue. I will also check possible causes why the conflict occurred with Veeam. 

 

Glad to hear you resolved it and Support helped out. 👍🏼