Backup of enterprise applications (Microsoft stack, IBM Db2, MongoDB, Oracle, PostgreSQL, SAP)
Post Reply
fsseremba
Enthusiast
Posts: 26
Liked: 5 times
Joined: Oct 20, 2015 5:46 pm
Full Name: Francis Sseremba
Contact:

Oracle DB restore to another server with different SID and database name

Post by fsseremba »

I would like to know if its possible to restore Oracle DB from application-aware backup to a different server with different SID and database name. I tried and I'm getting the following error message.

Failed to obtain information about mounted database. | ExplorerManagementService: Failed to GetRestorePointWithOracle: mountId - ab98b4cb-b4f1-486b-a830-9c832a1dfed6, databaseId - 8db827bc-76e9-47fe-9f47-481fcbcc7253 (sessionId = 'ba3c4274-9243-42ce-b00f-d3f5cb11ee07') | Cannot find database files for BWD on the mounted disks.

Veeam Support Case #07277448
PetrM
Veeam Software
Posts: 3815
Liked: 643 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic
Contact:

Re: Oracle DB restore to another server with different SID and database name

Post by PetrM »

Hi Francis,

Yes, it is possible, we have a wizard step on which you can specify the database name and SID. Looks like there is an issue with the mount process so it would be best to continue working with our support team to find out the root cause of the issue. Additionally, you can request an escalation of your support case if you feel that it's not on the right track.

Thanks!
fsseremba
Enthusiast
Posts: 26
Liked: 5 times
Joined: Oct 20, 2015 5:46 pm
Full Name: Francis Sseremba
Contact:

Re: Oracle DB restore to another server with different SID and database name

Post by fsseremba » 1 person likes this post

Hi Peter,

Thanks for the response. The first error message i got was indeed related to failure to obtain information about mounted database. I was informed by the Veeam Support Engineer that there is Btrfs limitation where the same UUID cannot mounted onto the same system. And the engineer advised that the only solution was to change the file system (to EXT4 or something else other than Btrfs or XFS) and take an active full backup after that or to restore the database somewhere else first. I was not willing to change the filesystem as it will require all the productions to be changed. So i tried to restore database to another location but still i got the same error message. I'm still working with Veeam support to see if this can be resolved.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest