Oracle backup with Veeam rman plugin

[isaez]

Hi,

We use the Veeam rman plugin to backup our Oracle databases and today I see these kind of warnings (?) in the Veeam console:
Some backup files do not have metadata. Backup cannot be imported before metadata is automatically recreated

From the Oracle rman side everything looks fine. What does the warning means?

regards,

Ivan

[mohammed.junaid]

Hi Ivan,
What version of Veeam RMAN Plugin are you using?
Since v11, we created a separate Metadata file for each database backup file (.vab)

Try to Re-Scan the repository. It will align the Metadata for the database backup files.

I hope it will resolve your issue.

Regards,
MJ

[Andreas Neufert]

You used the Oracle Plug-in before v11 came out and therefore use an old metadata format.
To increase performance and to support new features the new metadata format is mandatory in the upcoming v12.
Therefore v11 will warn you at first processing to update the metadata.
v11a will permanently warn you to update the metadata.
v12 can not work with the old metadata and you have to update before additional backups can be created.

Please find instructions for the update planning here: https://helpcenter.veeam.com/docs/backu ... adata.html

[isaez]

Mohammed, Andreas,

Thank you for the information. @Mohammed, who does normally re-scan the repository? I'm a DBA. Should our Veeam engineer do the rescan?
And we have version 11 of the Veeam Rman Plugin (VeeamPluginforOracleRMAN-11.0.0.837-1.x86_64). And it's running since a few months (6 months +/-). Why do we have these warning since today? and just for a few database servers?
@Andres, thanks for thw link. I'll read it.

regards,

Ivan

[Andreas Neufert]

Ah wait...
If it is not old backups and you did not upgraded to v11a lately.
Then there is a 15min background process that heals the metadata situation.
If the situation continues and you get more issues tomorrow, then please open a support ticket.

Rescan can be manually triggered on the backup server. Backup Infrastructure and go there to the Repository or Scale-out Backup Repository that you use for the backups and right click rescan it there.

[isaez]

Hi,

We did a rescan but it did no solve the issue. We are still getting these errors:
"25-10-2021 02:00:42 :: Some backup files do not have metadata. Backup cannot be imported before metadata is automatically recreated "
and today I see also this one "25-10-2021 02:00:42 :: Session failed: Failed to create metadata for the storage: c-1063518378-20211025-01 "

regards,

Ivan

[Andreas Neufert]

Thanks for comming back here.
Can you please create a support ticket, to check why we can not create the metadata file on disk?