RMAN plugin stops working after Repository restarted

[mrholm]

Hi
We have run the RMAN plugin on three servers with success for a while now, this morning our SOBR was down for 5 minutes and the after that all Oracle jobs fails with the fantastic error:
Session failed: One or more errors occurred.

Looking into the logs we see issues on syncronizing the repository and that I understand since the SOBR went down but I have syncronized the SOBR twice and all other backups towards it are fine
Here are the errors in the log:

Code: Select all

[18.03.2021 14:28:26.298] < 14476> plugin_common| ERR |Error has occurred while processing command
[18.03.2021 14:28:26.298] < 14476> plugin_common| >>  |One or more errors occurred.
[18.03.2021 14:28:26.298] < 14476> plugin_common| >>  |--tr:Failed to execute command [repository.checkVbmSynchronized] on backup server [servername.org:10006].
[18.03.2021 14:28:26.298] < 14476> plugin_common| >>  |--tr:Failed to start backup session
[18.03.2021 14:28:26.298] < 14476> plugin_common| >>  |--tr:Failed to build RMAN backup session
[18.03.2021 14:28:26.298] < 14476> plugin_common| >>  |--tr:Failed to create backup session
[18.03.2021 14:28:26.298] < 14476> plugin_common| >>  |--tr:Unable to get or create backup session
[18.03.2021 14:28:26.298] < 14476> plugin_common| >>  |--tr:Unable to prepare non-autobackup backup
[18.03.2021 14:28:26.298] < 14476> plugin_common| >>  |--tr:Unable to perform SbtBackup
[18.03.2021 14:28:26.298] < 14476> plugin_common| >>  |--tr:Unable to execute command sbtBackup
[18.03.2021 14:28:26.298] < 14476> plugin_common| >>  |--tr:Unable to dispatch plugin command [sbtBackup]

Support case is: 04707570
But does anyone else have an idea on how to get the RMAN plugin synced with the repo?
As for now we don't have any backups on our Oracle databases

[PetrM]

Hi Mats,

Please upload all logs requested by our support engineer. I'll keep an eye on it to make sure that the investigation is on right track.

Thanks!

[mrholm]

Hi all
Case is closed the solution as follows:
We did change the IP addresses on the proxy servers holding extents to SOBR, we ran ipcinfig /registerdns on all proxy servers and on the VBR sevrer and all Veeam Agent servers we ran ipconfig /flushdns. All servers cpuld oing eachother and reverese lookup on the name towards new IP and all was fine in Veeam GUI.
But by some reasin that support not really could explain Veeam seemed to hold information about the old name-IP so the jonbs did timeout towards the old iP:6160 port, we then tried to restart the proxy servers and agnet server but still no change, same timeout.
After restarting the VBR server everything started to work immediately using the new IP.

[Andreas Neufert]

Hello Mats, depending on the DNS lifetime and DHCP configuration, the local Windows systems cache the DNS entries longer as they should.
If you want to prefent this, please check with your network specialists how they setup the IP address changes/DNS updates/TTLs as well as the reverse DNS ones.