Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- Creating and viewing the licensing report
- Reviewing a capacity licensing report
- Reconciling the capacity licensing report results
- Reviewing a traditional licensing report
- Additional configuration
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About the Shared Storage Option
- 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
Note:
The following section is applicable for NetBackup master server 8.1 or later and NetBackup client 8.1 or later.
Accurate licensing for Oracle is specific to an
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. The backup selection is defined in the Oracle Instances and Databases tabs in the policy (OIP, templates, and scripts). The data size collection may not work properly if OS authentication is disabled.The following Oracle queries are used to gather file size information.
Get size of database files being backed up
Given the database file names that are backed up, these queries retrieve the file size (in MB) for every database in an instance. These queries do not include the transaction log:
select name, BYTES/1024/1024 from v$datafile; (where name is the name of the database file being protected in the backup policy)
Or to collect the entire sum of the database files in the instance, use the following query:
select sum(BYTES/1024/1024) from v$datafile;
Get the size of the control file
Given the database name, this query gets the control file size (size is only collected for one) in MB, not including transaction log:
select name, BLOCK_SIZE*FILE_SIZE_BLKS/1024/1024 controlfile_size from v$controlfile;