Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

PowerProtect Data Manager 19.17 Oracle RMAN User Guide

PDF

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:

Before you perform a centralized restore or disaster recovery on Windows, ensure that the Windows services for Oracle are running on the destination host with the target system identifier (target Oracle SID) to be used for the restore.

Before you perform a centralized restore and recovery, ensure that the Oracle database parameter CONTROL_FILE_RECORD_KEEP_TIME is set for the Oracle database, for example, by using sql commands. The parameter setting specifies the minimum number of days that Oracle keeps the database backup and restore history in the control file. Set the parameter to the length of time that covers the next full backup and its control file backup plus 3 days as an extra buffer.

A centralized restore and recovery is supported only when the backup copy 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 Backup copies 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 protection storage.

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 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 and instant access recovery support the following features:

  • Restore to the original Oracle host.

  • Restore to an alternate Oracle host.

    NOTE:You can use the disaster recovery or instant access recovery for Oracle testing and development purposes, for example, to validate the Oracle backups on an alternate host. The instant access recovery is applicable to Oracle Incremental Merge backups only.
  • Change of the database ID (DBID) of the restored database after disaster recovery.
  • Relocation of the Oracle datafiles.
  • 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. A dry run is not applicable to an instant access recovery.

PowerProtect Data Manager applies the following concurrency rules for jobs that are associated with a centralized restore. The jobs can include 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

To restore to a host that is not part of a protection policy, manually install and configure the Oracle RMAN agent on the target host.

Ensure that the target host meets the following prerequisites:

  • A supported AIX, Linux, or Windows operating system is run.
  • 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.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  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: <>()\