v9.5 Update 3 Agent backup complaining about Oracle

[dsegel]

I want to switch the backup of some physical servers via Veeam B&R Agent from locally managed to managed by the VBR server, and it works but the backup process complains that it can't connect to Oracle. There is no Oracle software installed on any of these servers, and the backup process via the local agent never complained about it.

Is this a bug in the new version, or is there some new option I'm not doing right?

ETA: I tried the DisableOracleProcessing reg key, but it's not helping. I have it set to 1; should it be 0 instead?

[Dima P.]

Hello Daniel,

Did you get this error during rescan? Can you please provide the text of the error you get (screenshot is the best)? Thanks in advance.

[Gostev]

Perhaps some remains of Oracle are there that makes the agent think it is installed?

[dsegel]

No errors during rescan.

How do I attach an image? I don't see any options.

The error is: "12/20/2017 8:25:42 AM :: Failed to connect to Oracle Details: Failed to logon user [shs\veeam-server-backup]
Win32 error:The user name or password is incorrect. Code: 1326 "

These servers have never had any Oracle components installed.

Image here:
https://imgur.com/a/F7IPg

[Vitaliy S.]

If there are no Oracle software packages on these servers, then I would suggest to contact our support team and take a look at the debug logs (to detect what's causing it).

[Dima P.]

Generally, this behavior is expected when application-aware processing is enabled in job settings but no credentials were provided for Oracle processing. Since you do not have Oracle installed on this computer this might be a bug. As Vitaliy suggested, please open a case and do not forget to share the case ID in this thread. Thanks in advance.

[dsegel]

Done, case ID 02433584

[Dima P.]

Passed to QA. Thanks!

[skomjath]

Hi! Are there any updates regarding this issue? I'm getting the same error message during an SQL cluster backup. There is no Oracle software installed on any of these nodes. Thanks.

[aschalk]

Same for me. Should I open a case for this, too?

[Dima P.]

Hi guys,

Yes, if you are facing this issue - please open a support case and share the case ID in this thread. Thank you in advance.

[aschalk]

Hey Dima,

02464796 is the ID.

[Ron_Jon]

I am seeing the same issue. Case 02470005 has been opened.

[Dima P.]

Thank you for sharing your case IDs. Checking with QA team.

[torstende]

Hello,

First of all: Thank you very much for supporting Microsoft Failover Clusters with update 3 and Agent 2.1
This is the most needed feature for me to replace some other backup products

Is there already a solution for this behaviour?
I am rolling out agents as proof of concept on some clusters an so far every failovercluster is having this warning.
There is no Oracle Software installed on these VMs. Thats why I see this problem as a low priority issue, but for go live it would be nice to avoid discussions with the customer.
The warning occurs while the job is running.

Thanks in advance.

[Dima P.]

Hello torstende.

Thank you for the kind words! Please make sure that account specified in Protection Group settings has local admin privilege on the affected computer.

[dib]

Are there any solutions for this because we have the same error.

Can someone tell me why we should submit a case number?

/Dennis

[Dima P.]

Dennis,

To submit a case please use Veeam Customer Support Portal. Thanks!

[Unreliably-Recurring]

Case 03038658.
Am trying to move from Backup Exec to Veeam, and am seriously considering switching back at the end of our license term because of this and other Veeam-specific problems that aren't because PICNIC...

[Unreliably-Recurring]

I just got off my call with Support for my Case on this.

The solution was to:

1. Edit the job
2. Select the Guest Processing step
3. Click the Applications button
4. Edit the server(s) that is/are failing
5. Select the Oracle tab, and specify a Credential account

The Oracle step was completely skipped the next time the job ran, even though the desired Credential that I had explicitly selected was the same one that it had been locking out.