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
Prerequisites when you configure an instant access Oracle database
The following prerequisites apply when you configure Oracle instant access databases:
Instant access is only supported for Oracle backup images when the following conditions are met:
The backup image is created using an Oracle Copilot Universal Share policy. The policy has two options, that you can select:
is supported by the web UI.
is only supported from the REST API.
For more information, see the following topic:
The backup is a full database backup.
Supported platforms for Oracle Copilot Backup with Instant Access:
Primary
Platform
Version
Backup From Single NFS Server
BYO,Flex Appliance, Flex WORM, Flex Scale, MSDP AKS (Azure Kubernetes Services), EKS (Amazon Elastic Kubernetes Service)
NetBackup 10.0 and later
Backup From Single NFS Server
NetBackup Appliance
NetBackup Appliance 4.0 and later
Backup From Single NFS Server
Cloud LSU (logical storage unit)
NetBackup 10.0.1 and later
Backup From Multiple NFS Server
Flex Scale
NetBackup Flex Scale 3.1 and later
Backup From Multiple NFS Server
BYO
NetBackup 10.2 and later
Backup From Multiple NFS Server
Flex Appliance
NetBackup Flex Appliance 3.0 and later
For Build Your Own (BYO) server, the operating system version must be same as the latest appliance operating system version that is RHEL 7.6 and later.
For BYO server, NGINX is installed on the storage server.
The NGINX version must be same as the one in the corresponding official RHEL version release. You need to install it from the corresponding RHEL yum source (EPEL).
Ensure that the policycoreutils and policycoreutils-python packages are installed from the same RHEL yum source (RHEL server). Then run the following commands:
semanage port -a -t http_port_t -p tcp 10087
setsebool -P httpd_can_network_connect 1
For BYO server, the /mnt folder on the storage server cannot be mounted by any mount points directly. User mount points must be mounted to its subfolders.
For BYO server, enable the logrotate permission in SELinux using the following command:
semanage permissive -a logrotate_t