Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- About NetBackup licensing models
- About the capacity licensing model
- nbdeployutil utility options
- Creating and viewing the licensing report
- After creating a traditional licensing report
- After creating a capacity licensing report
- Reconciling the capacity licensing report results
- 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 selecting media in robots
- About selecting media in standalone drives
- About Tape I/O commands on UNIX
NetBackup for Exchange Agent
The NetBackup for Exchange Agent reports data using the accurate licensing method when capacity licensing is used. After a backup is complete using the MS-Exchange-Server policy type, the agent captures the size of data that the policy protects. The data is reported to the master server.
Using the MS-Exchange-Server policy, as the Exchange database is backed up; the definition of protected data for the policy is the size of Exchange database (.edb file). Licensing for Exchange is specific to an MS-Exchange-Server policy and does not support an Exchange server that is backed up using any virtualization policy, such as VMware.
Exchange 2007 snapshot based backups are supported similar to Exchange 2010, 2013, and 2016.
Licensing for Exchange does not support Exchange 2007 streaming backup policies. For these policies, the report is generated using the existing method of capacity licensing (backup image headers).
Administrators can use any of the following ways to verify if the Exchange database size that is reported by the accurate licensing method is correct.
Use the Microsoft Exchange Management shell command that is available by default on the Exchange server.
Get-MailboxDatabase -Status | select Name,DatabaseSize
Use the help Get-MailboxDatabase command to see more information about this command.
Check the properties of Exchange database file (.edb) that was backed up on the Exchange server to view the size of the file.
Table: Reporting for Exchange backup environments
Database Availability Group (DAG)/Cluster backups
Standalone exchange backups
In an Exchange DAG/Cluster environment, a user can choose a DAG directive to back up all Exchange databases or back up an individual database of DAG as a standalone database backup.
Overlap is reported for DAG. You can back up an Exchange DAG database from any node based on the server preference list that is configured in the backup policy. No matter which node is used to back up the Exchange DAG database, the capacity licensing report identifies the database uniquely across DAG nodes, and identifies overlap. The protected data size is calculated from the node that is used to backup the Exchange DAG database.
For a standalone Exchange environment, protected data is reported. For multiple policies with some common databases, overlap is identified.