16:06:41 Job BackupJob started at 2018-10-27 16:06:41 CEST
16:06:41 Preparing to backup
16:06:41 Creating volume snapshot 00:00:02
16:06:47 [error] Failed to perform backup
16:06:47 [error] SQL logic error or missing database
16:06:47 [error] Unable to run query
16:06:47 [error] OibSensitiveInfoScope: Unable to create OIB Info
16:06:47 [error] OibScope: Unable to create OIB
16:06:47 [error] Processing finished with errors at 2018-10-27 16:06:47 CEST
veeamconfig repository delete --name Repository_1
Backup [homeserver.server.home DebianBackup] depends on repository and will be removed from database. Proceed? (y/n)
y
Error: SQL logic error or missing database
Unable to run query.
OibSensitiveInfoScope: Unable to find oib sensitive info by id.
OibScope: Unable to get OIBs by Point id [{4919c998-ddc5-4203-b860-eb9fca1b56b6}].
Have you recently updated your kernel? if so try running Veeam again with the old kernel. I had a similar issue that I opened a support case for and was told by Veeam support that VeeamSnap kernel module is not supported by the latest Linux kernel.
I don't think that OP's problem is related to his kernel version since his error messages clearly show that the problem is with the database. Since you've mentioned the KB in the other thread that is related to RHEL and its derivatives, I assume that you run RHEL/CentOS and those are affected by the particular update mentioned in the KB. Would you also share your case ID, please?
It's a Cluster, and the node on which it doesn't work now is the passive one, so for the moment not so urgent.
In the past it worked.
Now I've done a "veeamconfig vbrserver resync" as well as a "veeamconfig vbrserver edit --name NAME_SERVER --address IP_SERVER --port 10006 --login USERNAME --domain OUR_DOMAIN --password PASSWORD_USER" , and in both cases I get the error:
"SQL logic error or missing database
Unable to run query."
On the active node, server identical to this one, as well as the version of the Veeam Agent (v.2.0.0.256), its configuration, and the backup job.
Your difficulty may have a different nature, so opening a support case is a way to go.
In general, all technical issues should be addressed to our technical support team because troubleshooting through the forums is not possible and the forum is not a replacement for the technical support service. Additionally, you should specify a case ID when posting about a technical issue, as requested when you click "New Topic".
I've reviewed the previous poster's case and found out he had an issue with the configuration database that has been fixed with the help of our support engineers.