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 a pluggable database
The following procedure describes how to clone a pluggable 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 a pluggable database
- On the left, click Workloads > Oracle.
- Click the Pluggable databases tab.
- Click on the name of the pluggable 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 pluggable database.
- In Recovery target, enter a host. Or, click Select destination. That option automatically fills in both the Host and the Target instance.
A container must exist and must be open (read-write mode) for the pluggable database to be plugged into. None of the existing PDBs in the container can have the same name as the new PDB.
- (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.
- In Credentials, specify the applicable credential options.
Linux or UNIX: You can select an existing credential 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.