NetBackup™ for Oracle Administrator's Guide
- Introduction
- NetBackup for Oracle QuickStart
- Installing NetBackup for Oracle
- About linking Oracle RMAN with NetBackup for UNIX
- Configuring RBAC for the Oracle administrator
- Managing Oracle instances and databases
- Managing Oracle credentials
- Configuring Oracle policies
- Preparing for NetBackup for Oracle configuration
- About Oracle Intelligent Policies (OIP)
- About script-based Oracle policies
- Managing Oracle RAC
- Performing backups and restores of Oracle
- About NetBackup for Oracle backups
- Managing expired backup images
- About NetBackup for Oracle restores
- Using NetBackup for Oracle in a Windows Server Failover Cluster (WSFC)
- Oracle cloning
- NetBackup Copilot for Oracle
- Configuring an OIP using universal shares (Oracle Copilot)
- Oracle Copilot with instant access
- Prerequisites when you configure an instant access Oracle database
- NetBackup for Oracle with Snapshot Client
- About NetBackup for Oracle with Snapshot Client
- How NetBackup for Oracle with Snapshot Client works
- About configuring Snapshot Client with NetBackup for Oracle
- Restoring NetBackup for Oracle from a snapshot backup
- About configuring NetBackup for Oracle block-level incremental backups on UNIX
- About Snapshot Client effects
- About Oracle support for Replication Director
- NetBackup Dedupe Direct for Oracle
- Using NetBackup Dedupe Direct for Oracle plug-in
- Other Oracle configuration
- Troubleshooting
- Troubleshooting RMAN backup or restore errors
- Appendix A. Deduplication best practices
- Appendix B. Snapshot Client support of SFRAC
- Appendix C. Script-based Block-Level Incremental (BLI) Backups without RMAN on UNIX and Linux systems
- Verifying installation requirements for BLI backups without RMAN
- Creating NetBackup policies for script-based BLI backup
- Creating notify scripts for BLI backups
- Performing backups and restores
- About troubleshooting backup or restore errors
- Appendix D. XML Archiver
- NetBackup for Oracle XML export and XML import
- About XML export shell scripts
- Performing an XML export archive
- Restoring an XML export archive
- Troubleshooting XML export or XML import errors
- Appendix E. Register authorized locations
Clone an Oracle database
The following procedure describes how to clone an Oracle database. The user must have an RBAC role that gives them permissions to perform cloning operations.
See Create a custom RBAC role for Oracle cloning.
To clone an Oracle database
- On the left, click Workloads > Oracle.
- Click the Databases tab.
- Click on the name of the database you want to clone.
- Select the Recovery points tab.
- Locate the recovery point from which you want to create the clone.
- Click Actions > Clone database.
- In Recovery target, enter a host name. Or, click Select host to select a host.
- (Oracle 21 and later) The path for the Oracle base config is required. Otherwise a clone to an Oracle 21 or later database fails.
- Enter all other required information.
- Click Next.
- In Credentials, specify the applicable credential options.
Linux or UNIX: You can select from existing credentials or use OS credentials.
Windows: You can select an existing credential or use OS credentials. If the target Oracle database requires them, also enter the Oracle Home User credentials.
After all required information is entered, click Next.
- In Recovery options, enter the number of channels and the SCN value and then click Next.
- On the Review page, NetBackup runs a pre-recovery check for any errors. You should correct any errors that are highlighted.
During the pre-recovery check, NetBackup looks for:
Credentials
Database name
Oracle base config path
Image access
Existence of Oracle home
SCN Value
- Click Start recovery to begin the cloning operation.
You can start the cloning operation without fixing any of the errors that are shown on the Review page.
- (Optional) You can monitor the progress of the cloning operation in the Activity monitor.
Note the following when you specify the target directory for cloning:
If using an ASM path for any target, the syntax can be as follows:
+ASMDG/path
If the source backup used OMF, selecting an ASM directory for control files or redo files requires a path after the disk group.
If the source backup used OMF and from ASM, selecting an ASM directory for any new location can only contain the disk group. Oracle does not honor any paths after the disk group.
When you clone to a specified target directory, the best effort is made to create the target directories along with the source subdirectories.