Feature Request - Edit database settings during restore of Oracle database

[krivaneka]

Hello,

I have a feature request/suggestion regarding the ability of Veeam to backup and restore an Oracle database instance. First I would like to describe the setting we have set up:

1) One database server with Windows Server 2012 R2.
2) Two Oracle instances on that server – PROD and TEST.
3) PROD is being used in production, while TEST serves for purposes of user trial testing.
4) TEST is being duplicated each week from backups of PROD, which basically tests, whether we can successfully restore PROD in case of a disaster.
5) Each instance is using different PFILE with different parameters (TEST is using much less SGA memory for example).

So far we have been using RMAN scripts and scheduled Windows tasks to take care of this process and now we tried to replicate it using Veeam. We found out that we can duplicate PROD to TEST on the same machine without much of an issue, but there are some minor problems, which we would like to solve:

1) TEST is restored with SPFILE created from parameters of PROD instance.
2) Destination for archived REDO logs on TEST after restore is the same as the destination on PROD.


Could you add a possibility to either configure initialization parameters of the restored instance (TEST instance in our case) before the actual restore operation or to point Veeam to a custom created PFILE, which would be used by restored instance for startup?

Thank you for your time.

[foggy]

Thanks for your request. You can change the path to the logs even now though. As for spfile, it can be changed manually after restore. Thanks!

[chendrix]

There are times you need to edit the init before the retore can be completed.
Consider this scenario:
VEEAM has backed up a db. This backup contains inconsistent controlfiles in it. Try to restore:
VEEAM restores init file.
VEEAM cannot complete the db restore because controlfiles are out of sync.

This error could be bypassed by using an init file which only points to one control file
You must edit the init being used by the running instance before moving forward with the rest of the restore- but VEEAM overwrites this edit when you run the restore process.

Does VEEAM currently have a work around for this scenario? Maybe a feature/setting within VEEAM or some way to work around it?
The need is for VEEAM to not overwrite the init file during the restore process.

[PetrM]

Hello and Welcome to Veeam R&D Forums!

May I ask you to elaborate a bit more on the reason of the control files inconsistency in the backup? Probably, we should keep focus on the root cause instead of looking for workarounds to fix the symptoms?

Thanks!