Restoring RMAN Backups using VeeamExplorers.

[cleberzorzi]

Hello,

I'm backing up Oracle RAC (ASM disks) using RMAN scripts. Backup is working fine.

I tested the restore on another server using RMAN scripts and it worked.

I would like to know if it is possible to use Veeam Explorer to restore a backup made with RMAN scripts to another Oracle server with ASM disks. The target server is standalone (not RAC).

In tests it is not possible to select /change for ASM disks. Restore points to the directory where the Oracle binary is installed.

Thanks!

[PetrM]

Hi Cleber,

Could you please clarify whether you select "Restore with different name and settings" or "Restore with the original name and settings" option on this wizard step?

Thanks!

[cleberzorzi]

Hi PetrM,

I'm "restoring with the original name and settings".
When I perform the restore, the option is the Oracle Home directory.
I cannot, for example, switch to ASM volume (+DiskGrp...) (the source uses ASM disks).
When I switch to ASM disk, it looks like a message:"ASM invalid path".

Thanks!

[PetrM]

Thanks. May I ask you to raise a support case and to upload logs as per the instruction of this KB and to attach the screenshot with the error message which pops-up when you switch to ASM disk. Please don't forget to share a support case ID with us so that we can make sure that it moves in right away.

Thanks!

[tgjerdahl]

Has this issue been resolved yet? I'm encountering the exact same problem. Running

Backup of Oracle database using ASM works just fine. However, when trying to restore the database (using original name and settings), all of the paths are using the Oracle Home directory. If I try updating the paths to the ASM disk groups, the restore wizard states:

"ASM path is invalid. Please select ASM path from the drop-down list."

I don't see any dropdown list anywhere! Am I missing something?

[PetrM]

Hi Tony,

Do you see the same behavior if you try "Restore with different name and settings"? Also, could you please open a support case and share a support case ID. The described behavior looks like a technical issue.

Thanks!

[tgjerdahl]

Figured out how to get this to work (for my scenario at least):

After enabling extended logging in Veeam Explorer for Oracle (VEOR), I was able to see that VEOR was actually trying to get the ASM disk info via:

sqlplus -l / as sysasm

By default the "oracle" O/S account only has sysdba privileges and not sysasm. I was able to get everything to work by adding an O/S account for veeam with all of the appropriate privileges. I then entered those credentials in the VEOR wizard (did not have to select the "Elevate specified account to root" either):

useradd veeam -g veeam
passwd veeam
usermod -a -G asmadmin veeam
usermod -a -G dba veeam
usermod -a -G oinstall veeam

I haven't actually performed a restore yet, but at least the wizard got through all of the steps and had the correct ASM disk group paths for all of the datafiles/etc.

Hope this helps others.

[PetrM]

Hi Tony,

Awesome news! I will share this topic with my colleagues, maybe we should mention this behavior in the documentation.

Thanks!