December 4, 2025 at 10:15 am
Hi all,
Has anyone encountered an issue whereby using a distributed availability group to migrate data from cluster 1 to cluster 2 leaves stale GUIDs in the Veeam postgres database causing the backups to fail with the above error?
Anyone have a fix?
Thanks
December 5, 2025 at 11:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
December 14, 2025 at 5:55 am
First step - I'd read the documentation and make sure you are following the proper configuration as documented by Veeam - https://helpcenter.veeam.com/docs/vbr/userguide/agents_dag_hiw.html?ver=13
Failing that, I'd reach out to Veeam support - you paid for it, might as well use it.
If neither of those solutions are good, I'd recommend reaching out to the Veeam community as the error is being thrown by Veeam, not SQL.
On top of that, this is a MOSTLY SQL Server (Microsoft) forum so posting about a postgresql issue in a SQL Server 2019 section of the forum is not going to get the right people to notice your query.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
December 16, 2025 at 4:58 pm
I'd echo what Brian wrote. Work with VEEM on this
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply