RMAN backup failed even when trying to run full backup

[kchtang]

Case ID# 07307526

We have restarted our HPE StoreOnce and Veeam server, now the RMAN backup failed with the following error:
11:16:57 AM RMAN error: RMAN-03002: failure of backup plus archivelog command at 06/19/2024 11:16:50 ORA-19506: failed to create sequential file, name="af74e397-48c8-467c-b5cb-174bb212a6b4/RMAN_2168013810_ISFASTP__20240619_6k2toagj_21716_1_1.vab", parms="" ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: non RMAN, but media manager or vendor specific failure, error text: Previous session failed --tr:Failed to create backup session --tr:Unable to get or create backup session --tr:Unable to prepare non-a

Looking at the log file in the Veeam plugin, it seems that the plugin cannot find the existing vab file in the repository so the backup failed.
--- edited by moderator ---

So I thought, ok the differential backup is some how not working, I will take a new full backup instead, but the full backup failed with the same situation. Is there a way to reset the plugin so that it will not try to look for the existing backup file and start a new full backup instead? Thanks.

[Andreas Neufert]

In most of the cases this is a communication or timeout issue with the backup target. Can you check pinging the Repository Gateway Server that is defined for handling the StoreOnce backups?

[kchtang]

The gateway server is the VBR server itself, other backup (VM backup) which target this StoreOnce is running fine, just this RMAN backup is failing.

[PetrM]

Hi Kevin,

I edited the first post because as explained here we try to avoid pasting log snippets in the forum posts.

Based on my observation, I believe the issue persists because our scheduler is unable to prepare the backup infrastructure resources, possibly due to a problem with the repository that is relevant to plug-in jobs only. Unfortunately, the important part of the error stack trace is cut off: "Unable to prepare non-a...".

Anyway, we cannot troubleshoot technical issues effectively over the forum posts so please continue working with our engineers. If you feel that your support case is not progressing towards a resolution quickly enough, please feel free to request escalation.

Thanks!

[mpm@aramark]

Kevin, did support ever provide a solution to your issue?

[PetrM]

Hi Martin,

Please open a support case and let our engineers analyze the issue. The error above is quite generic and may persist due to various reasons. There are no guarantees that the solution which worked in one case will be efficient in another one.

Thanks!