Considerations for centralized Oracle restore and recovery
Ensure that you review the following information before you perform a centralized restore and recovery of Oracle backups by using the
PowerProtect Data Manager.
A centralized restore and recovery of an online Oracle database supports the following features:
Restore and recovery to the original Oracle host.
Restore and recovery to an alternate Oracle host.
Point-in-time restore and recovery, based on time, SCN, or log sequence.
Dry run of the database restore and recovery.
NOTE A centralized restore and recovery of an Oracle database is allowed only when the backup copies location is listed as LOCAL or Local_Recalled in the
Location column in the
PowerProtect Data Manager UI. (To see the
Location column, go to
Infrastructure > Assets, select the asset on the
Oracle tab, click
View Copies, and then click the storage icon on the left.) To recall a cloud tier backup before you perform a centralized restore, follow the procedure in
Restore the cloud tier backups to DD.
For any centralized restore to an alternate host, ensure that the alternate host is an Oracle Server host that is a discovered asset of
PowerProtect Data Manager.
NOTE If the alternate host is not included in the list of available hosts, follow the instructions to install and configure the Oracle RMAN agent on the alternate host. Ensure that the Oracle Server host is registered to the same
PowerProtect Data Manager server.
A centralized restore of only Oracle archive logs supports the following features:
Restore to the original Oracle host.
Restore to an alternate Oracle host.
Restore of a specific range of archive logs, based on time, SCN, or log sequence.
Dry run of the archive log restore.
A centralized Oracle disaster recovery supports the following features:
Restore to the original Oracle host.
Restore to an alternate Oracle host.
NOTE You can use the disaster recovery for Oracle testing and development purposes, for example, to validate the Oracle backups on an alternate host.
Change of the database ID (DBID) of the restored database after disaster recovery.
Relocation of the Oracle data files.
Customization of Oracle startup parameter settings in the spfile of the Oracle database.
Point-in-time restore and recovery, based on time, SCN, or log sequence.
Dry run of the disaster recovery.
PowerProtect Data Manager applies the following concurrency rules for jobs associated with a centralized restore, including any backup, restore, and manual agent installation jobs that you run on the same host:
If an asset backup is in progress, the Oracle Server restore against the same asset is queued.
If an Oracle Server restore against an asset is in progress, the backup against the same asset is queued.
If an archive log restore is in progress, a backup request is not queued.
If a restore is in progress for 48 hours or less, a manual or scheduled delete job is not started.
NOTE If a restore runs for more than 48 hours, a scheduled delete job is started.
Application agent manual installation and configuration
When you want to restore to a host that is not part of a protection policy, you must manually install and configure the Oracle RMAN agent on the target host of the restore.
Ensure that the target host meets the following prerequisites:
An AIX or Linux OS is running.
The Oracle Server is installed and running.
The Oracle DBA account has the same security configuration as required for backup.
The network ports are configured as required for backup.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\