Performing centralized Oracle restore of archive logs
You can use the
PowerProtect Data Manager UI to perform a centralized restore of an Oracle archive logs backup without the control file. The archive logs restore is performed for an asset, based on the Application Direct or Oracle Incremental Merge backup technology used for the last backup.
Steps
In the
PowerProtect Data Manager UI, select
Restore > Assets and select the
Oracle tab.
The
Restore window displays all the databases that are available for restore.
To filter the displayed list of assets if needed, you can click
in the column heading
Name,
Status,
Protection Policy,
Host/Cluster/Group Name,
Host Type,
Data Guard Name,
Data Guard Role,
Application Name,
Last Copy,
Network,
Protocol, or
Backup Technology:
The
Name and
Application Name columns list the Oracle database asset names.
The
Status column lists the status as Available, Deleted, or Not Detected.
The
Protection Policy column lists the names of the protection policies for the assets.
The
Host/Cluster/Group Name column lists the hostnames.
The
Host Type column lists the host types as RAC or Standalone.
The
Data Guard Name column lists the names of associated Data Guard groups.
The
Data Guard Role column lists the Data Guard roles as Logical Standby, Physical Standby, Primary, Snapshot Standby, or Generic.
The
Last Copy column lists the dates and times of the backup copies within the specified date and time range.
The
Network column lists the networks that are available under the selected host or cluster.
The
Protocol column lists the protocol as BOOSTFS or NFS when a protocol has been set.
The
Backup Technology column lists the backup technology as Application Direct or Oracle Incremental Merge.
NOTE: The listed assets are the assets that have at least one copy discovered by
PowerProtect Data Manager. You can select only one asset for one Oracle host.
Select the check box next to the Oracle Server database asset for restore, and click
Restore.
The restore wizard opens the
Oracle Restore and Recovery window.
On the
Scope page, select
Online database recovery, then select
Archive log only restore, and then click
Next.
This option restores only the archive logs without the control file. The database can be in either the mount state or open state.
On the
Storage Unit Selection page, type the name of the storage unit that contains the backup in the
Storage unit field, or select the storage unit from the menu, and then click
Next.
On the
Location page, select the preferred type of restore, and then click
Next:
Restore to original host—Specifies to restore to the original host with the displayed hostname.
If the original host is part of a RAC cluster, select the available node hostname from the list.
Restore to alternate host—Specifies to restore to an alternate host.
Select the alternate hostname from the list, and then select the required instance name.
NOTE: For an Application Direct restore, Oracle RMAN agent version 19.12 or later is required on the alternate host. For an Oracle Incremental Merge restore, Oracle RMAN agent version 19.13 or later is required on the alternate host.
On the
Credentials page, select one of the following options, and then click
Next:
Use the credentials set at asset level or policy level for restore
NOTE: Credentials at the asset level take precedence over credentials at the protection policy level.
Select existing credentials or create new credentials for restore
Click
Set Credentials, complete the fields in the
Set Credential dialog, and then click
Save.
On the
Archive Log Options page, select the required options, and then click
Next:
Restore To—Select one of the following options:
All—Specifies to restore all the archive logs of the database asset.
System Change Number—Specifies to restore the archive logs for the SCN range. Type the SCN start and end values in the text boxes.
Timestamp—Specifies to restore the archive logs for the timestamp range. Type or select the timestamp start and end values in the text boxes.
Log Sequence—Specifies to restore the archive logs for the log sequence range. Type the log sequence start and end values in the text boxes.
Database Options—Select either or both of the following options:
Crosscheck backups—Specifies to crosscheck the backup before performing the restore. This option applies only when the application agent version 19.13 or later is installed on the target host. Selecting this option causes a delay in the display of progress updates for the restore job. Additional time is needed to crosscheck the backups from the Oracle RMAN catalog.
Dry run—Select this option if you do not want to run an actual restore and recovery. This option enables a job that creates the required RMAN restore scripts in the
$RMAN_AGENT_HOME/tmp directory on the selected target host. The dry run procedure does not perform a restore or recovery. You can use the scripts that the dry run creates to perform a self-service restore as required.
On the
More Options page, specify the required options, and then click
Next:
Set Stream Count—Type an integer stream count in the text box, if required. The default stream count is 4. The maximum stream count is 255.
Compressed Restore—To enable restore compression and reduce the impact on the network bandwidth, select
Use PowerProtect DD Boost compressed restore.
Troubleshooting—To enable troubleshooting, select
Enable debug logs for troubleshooting purposes.
On the
Summary page:
To ensure that the restore settings are correct, review the information about the
Scope,
Storage unit,
Location,
Credentials,
Archive Log Options, and
More Options.
To change any settings, you can click
Edit beside an information section. As an alternative, you can click
Back to access a specific page and change the settings as needed.
To start the centralized restore operation for the Oracle database, click
Restore.
A status message appears with a link to the
Protection Jobs page where you can monitor the restore job.
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: <>()\