Skip to main content
  • EN

Hello

 

I have configured veeam backup for Oracle rman using veeam plug in. My OS is solaris 11.4 and running oracle database 19.3

Backups are running successfully. Now I am using below script to restore the control file to another solaris server same os and database version but it’s failing.

 

Can anyone please advise what might be wrong?

 

Script used to restore:

RUN {
ALLOCATE CHANNEL ch1 DEVICE TYPE SBT_TAPE PARMS 'SBT_LIBRARY=/opt/veeam/VeeamPluginforOracleRMAN/libOracleRMANPlugin.so';
RESTORE controlfile to '/tmp/stc.ctl' FROM 'c-42xxx701-2xxxx6-00_RMAN_AUTOBACKUP.vab';
}
EXIT;

 

Error encountered:

Starting restore at 26-MAY-25

channel ch1: restoring control file
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 05/26/2025 16:13:21
ORA-19870: error while restoring backup piece c-42xxx701-2xxxx6-00_RMAN_AUTOBACKUP.vab
ORA-19563: control file header validation failed for file /tmp/stc.ctl

RMAN> **end-of-file**

 

Hi! It looks like RMAN is able to access the .vab file but fails during the control file restore due to a header validation issue.

A few suggestions that might help:

  1. Verify that the correct authentication is configured on the target server to allow access to the backup. This step is essential when restoring from backups made on a different server.

  2. Ensure the backup piece is intact and accessible in the Veeam Backup & Replication console — try browsing the restore points there to confirm the backup is healthy.

hi,

did you set original database to destination rman? like:

rman target /
set dbid=<original_dbid>;

i expect that this step you did:

catalog start with '/opt/veeam/veeamPluginOracle/rman/DBNAME';

 

another view: do you restore on the same os kernel? on the same rman version? with same plugin veeam version?

 

try to remount backup:

veeamconfig oracle unmount
veeamconfig oracle mount --recovery-scopes all
 

See if this article from Veeam Help will assist you - Restore to Another Server - Veeam Plug-ins for Enterprise Applications

Hi! It looks like RMAN is able to access the .vab file but fails during the control file restore due to a header validation issue.

A few suggestions that might help:

  1. Verify that the correct authentication is configured on the target server to allow access to the backup. This step is essential when restoring from backups made on a different server.

  2. Ensure the backup piece is intact and accessible in the Veeam Backup & Replication console — try browsing the restore points there to confirm the backup is healthy.

Hello

The authentication is fine and backup piece is intact and accessible.

Note:

  1. Same restore script when used on source server, restore runs fine. Error encountered when running restore on alternate server.
  2. After restore on alternate server, even though error is encountered, the file gets created under /tmp

maybe you can try:

 

duplicate database to NEWDB
  backup location '/opt/veeam/veeamPluginOracle/rman/DBNAME'
  nofilenamecheck;
 

If you are not getting anywhere then support is your best bet.  The community is not technical support and we try to offer best suggestions.

Hi! It looks like RMAN is able to access the .vab file but fails during the control file restore due to a header validation issue.

A few suggestions that might help:

  1. Verify that the correct authentication is configured on the target server to allow access to the backup. This step is essential when restoring from backups made on a different server.

  2. Ensure the backup piece is intact and accessible in the Veeam Backup & Replication console — try browsing the restore points there to confirm the backup is healthy.

Hello

The authentication is fine and backup piece is intact and accessible.

Note:

  1. Same restore script when used on source server, restore runs fine. Error encountered when running restore on alternate server.
  2. After restore on alternate server, even though error is encountered, the file gets created under /tmp

hi ​@STC 

as I wrote in my article dedicated to RMAN plugin, before starting the restore on another server, it is necessary to specify the credentials of a user account under which the backup was created.  

Please check command from the article and verify if it’s what you need to solve. 

 

Comment


Terms & Conditions