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
About accurate licensing for Oracle
Accurate licensing for Oracle is specific to an Instances and Databases tab. The backup selection for script-based Oracle policies is defined based on what the script protects.
policy. The size of the data that is reported does not include the NetBackup for Oracle XML Archiver. This type of licensing collects the front-end data size (FEDS) for any Oracle backup that can be restored, not including transaction logs. Oracle Intelligent Policies define the backup selection on theNote:
The data size collection does not work properly if OS authentication is disabled.
Licensing data is collected for each database that is protected even if there are multiple databases on a single host or cluster. Licensing uses physical data file characteristics the Oracle database reports, not logical or segment sizes. The reason NetBackup collects data this way is that during a disaster recovery, RMAN needs to restore the full physical data file and not just its logical pieces.
Oracle Data Guard configurations are licensed on a per database basis. Each of the primary or the standby databases needs to be restored individually and FEDS licensing is used for any Oracle backup that can be restored. Each of the primary or the standby databases reports their FEDS data whenever NetBackup protects it during a backup operation.
The following Oracle queries are used to gather file size information:
Get size of database files being backed up
This query retrieves the list of database files and their file sizes (in MB) for an instance:
select NAME, BYTES/1024/1024 from v$datafile;
This query shows the sum of the database file sizes for an instance:
select sum(BYTES/1024/1024) from v$datafile;
Note:
The preceding queries do not have information about the transaction log.
Get the size of the control file
This query retrieves the list of control files and their sizes (in MB), not including the transaction log:
select NAME, BLOCK_SIZE*FILE_SIZE_BLKS/1024/1024 controlfile_size from v$controlfile;