Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and usage reporting
- How capacity licensing works
- Creating and viewing the licensing report
- Reviewing a capacity licensing report
- Reconciling the capacity licensing report results
- Reviewing a traditional licensing report
- Reviewing an NEVC licensing report
- Additional configuration
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About the Shared Storage Option
- DELETE About configuring the Shared Storage Option in NetBackup
- Viewing SSO summary reports
- About the vm.conf configuration file
- Holds Management
- Menu user interfaces on UNIX
- About the tpconfig device configuration utility
- About the NetBackup Disk Configuration Utility
- Reference topics
- Host name rules
- About reading backup images with nbtar or tar32.exe
- Factors that affect backup time
- NetBackup notify scripts
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About checking for data loss
- About checking for tape and driver configuration errors
- How NetBackup selects media
- About Tape I/O commands on UNIX
NetBackup for Oracle server agent
Accurate licensing for Oracle is specific to an Instances and Database tab. The backup selection for Oracle Template or Script policies is defined based on what the template or 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;