Highlighted

BMR of oracle windows server

Hello

I am taking a BMR backup of a windows 2008R2 server hosting an Oracle DB. The Oracle services are shut down while the backup is performed.

When restoring this backup to a different hardware, the OS is running fine (after updating the missing drivers ofr new hardware), but the Oracle DB is not able to start : Oracle processes are "eating" the whole memory but database is not mounting nor opening....

Any advice would be appreciated

Best regards

5 Replies
Highlighted

Re: BMR of oracle windows server

Sounds like a question for Oracle admins - as the NetBackup part seems to have gone ok.

.

Just out of curiosity:

1) Did the hostname change?

2) Did the IP address change?

3) Does this folder still exist?   C:\BMR

...BTW - if it still exists do NOT attempt to delete it yet, as it is an indicator of an incomplete BMR client recovery, and we may need to run some additional steps manually.

Highlighted

Re: BMR of oracle windows server

Hello

There is no change (nor IP nor hostname) and the \BMR folder is deleted correctly at the end of BMR finalization process ...

The bahviour is the same when trying to create a new DB on this restored server : the oracle.exe process is consuming more and more memory without being able to start the service ...

Best regards

Highlighted

Re: BMR of oracle windows server

Certainly sounds like an issue for Oracle Support. 

Re: BMR of oracle windows server

The recommendations from Veritas employees that I have seen in the past on this forum, was to use BMR for boot/system disks only and then use application/db agent backup and restore for the rest. Curious to know if the restored Oracle server have identical physical resources?
Highlighted

Re: BMR of oracle windows server

Marianne raises a good point there...

...if the instance of Oracle was not fully down at the time the BMR backup of the whole server instance was taken, then, the captured instance of Oracle within the BMR based backup image will very likely be incomplete and incocnsistent, and therefore not guaranteed to start correctly upon server based recovery using BMR.