Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- About NetBackup licensing models
- Tools for creating licensing reports
- How capacity licensing works
- How capacity licensing detects overlap when multiple policies protect data
- Backup policies and agents that support accurate licensing
- Requirements before gathering data for multiple master servers
- Scheduling capacity licensing reports
- Manually generating licensing reports
- Creating and viewing the licensing report
- Reviewing a capacity licensing report
- Summary tab
- Client aliases and multiple IP addresses
- Itemization tab
- Clients backed up with multiple streams
- NetBackup CloudCatalyst (NetBackup 8.1 and later clients)
- Data backed up by multiple policies
- BigData plug-ins for NetBackup
- NetBackup for Exchange agent
- NetBackup for NDMP agent
- NetBackup for Oracle server agent
- NetBackup for SQL Server agent
- NetBackup for VMware agent
- Windows file system backups
- UNIX file system backups
- Reconciling the capacity licensing report results
- Reviewing a traditional licensing report
- Using the NetBackup Storage API to get the total backup size information
- Additional configuration
- About multiple NetBackup master servers
- About multiple media servers with one master server
- About direct I/O for backups on Windows
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About specifying the locale of the NetBackup installation
- About the Shared Storage Option
- About Shared Storage Option components
- About reserving or releasing shared devices
- How to share robotic libraries without using the Shared Storage Option
- Shared Storage Option terms and concepts
- About the Shared Storage Option license
- About Shared Storage Option prerequisites
- About hardware configuration guidelines
- About installing and configuring drivers
- Verifying the connectivity
- About configuring the Shared Storage Option in NetBackup
- Verifying your Shared Storage Option configuration
- Device Monitor and Shared Storage Option
- Viewing SSO summary reports
- Operating system assistance
- Common configuration issues with Shared Storage Option
- Frequently asked questions about Shared Storage Option
- About the vm.conf configuration file
- ACS_mediatype entry in vm.conf
- ACS_SEL_SOCKET entry in vm.conf
- ACS_CSI_HOSTPORT entry in vm.conf (on UNIX)
- ACS_SSI_HOSTNAME entry in vm.conf
- ACS_SSI_INET_PORT entry in vm.conf (on UNIX)
- ACS_SSI_SOCKET entry in vm.conf
- ACS_TCP_RPCSERVICE / ACS_UDP_RPCSERVICE entry in vm.conf (on UNIX)
- ADJ_LSM entry in vm.conf
- API_BARCODE_RULES entry in vm.conf
- AUTHORIZATION_REQUIRED entry in vm.conf
- AUTO_PATH_CORRECTION entry in vm.conf
- AUTO_UPDATE_ROBOT entry in vm.conf
- AVRD_PEND_DELAY entry in vm.conf
- AVRD_SCAN_DELAY entry in vm.conf
- CLEAN_REQUEST_TIMEOUT entry in vm.conf
- CLIENT_PORT_WINDOW entry in vm.conf
- CLUSTER_NAME entry in vm.conf
- DAS_CLIENT entry in vm.conf
- DAYS_TO_KEEP_LOGS entry in vm.conf
- EMM_RETRY_COUNT entry in vm.conf
- EMM_CONNECT_TIMOUT entry in vm.conf
- EMM_REQUEST_TIMOUT entry in vm.conf
- ENABLE_ROBOT_AUTH entry in vm.conf
- INVENTORY_FILTER entry in vm.conf
- MAP_ID entry in vm.conf
- MAP_CONTINUE_TIMEOUT entry in vm.conf
- MEDIA_ID_BARCODE_CHARS entry in vm.conf
- MEDIA_ID_PREFIX entry in vm.conf
- MM_SERVER_NAME entry in vm.conf
- PREFERRED_GROUP entry in vm.conf
- PREVENT_MEDIA_REMOVAL entry in vm.conf
- RANDOM_PORTS entry in vm.conf
- REQUIRED_INTERFACE entry in vm.conf
- SERVER entry in vm.conf in NetBackup versions 8.0 and earlier
- SSO_DA_REREGISTER_INTERVAL entry in vm.conf
- SSO_DA_RETRY_TIMEOUT entry in vm.conf
- SSO_HOST_NAME entry in vm.conf
- TLH_mediatype entry in vm.conf
- TLM_mediatype entry in vm.conf
- VERBOSE entry in vm.conf
- Example vm.conf file
- How to access media and devices on other hosts
- Host name precedence in the vm.conf file
- Holds Management
- Menu user interfaces on UNIX
- About menu user interfaces
- About the tpconfig device configuration utility
- About the tpconfig utility menu
- Starting the tpconfig device configuration utility
- Adding robots
- Adding drives
- Updating a robot configuration
- Updating a drive configuration
- Deleting a robot
- Deleting a drive
- Configuring drive paths
- Configuring host credentials
- Displaying and writing the device configuration
- 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
- Methods for determining the NetBackup transfer rate
- NetBackup notify scripts
- backup_notify script
- backup_exit_notify script
- bpstart_notify script (UNIX clients)
- bpstart_notify.bat script (Windows clients)
- bpend_notify script (UNIX clients)
- bpend_notify.bat script (Windows clients)
- bpend_notify_busy script (UNIX clients)
- child_end_deployment_notify
- child_start_deployment_notify
- diskfull_notify script
- drive_mount_notify script (on UNIX)
- drive_unmount_notify script (on UNIX)
- mail_dr_info script
- media_deassign_notify script
- nbmail.cmd script (on Windows)
- parent_end_deployment_notify
- parent_end_notify script
- parent_start_deployment_notify
- parent_start_notify script
- pending_request_notify script
- restore_notify script
- session_notify script
- session_start_notify script
- shared_drive_notify script
- userreq_notify script
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup selects drives
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About SCSI reserve requirements
- About SCSI reserve limitations
- About SCSI reservation logging
- About SCSI reserve operating system limitations on Windows
- About checking for data loss
- About checking for tape and driver configuration errors
- About configuring SCSI reserve
- How NetBackup selects media
- Volume pool and volume group examples
- Media formats
- Media and device management processes
- About Tape I/O commands on UNIX
About direct I/O for backups on Windows
By default, the buffer size for disk storage units is 256 KB. If the buffer size is set to a value greater than 256 KB, backups written to that storage unit automatically use direct I/O. An increased buffer size can improve backup speed.
To increase the buffer size, the following conditions must be met:
A Windows media server must own the storage unit.
The storage unit must be either a BasicDisk or an Array Disk storage unit.
The backup to be stored cannot be multiplexed.
The touch file that disables direct I/O must not be present.
(install_path\VERITAS\NetBackup\bin\DISABLE_DIRECT_IO)
To increase the buffer size, create one of the following touch files on the media server that owns the storage unit:
For backups to disk
install_path\VERITAS\NetBackup\db\config\ SIZE_DATA_BUFFERS_DISK
For backups to disk or tape
install_path\VERITAS\NetBackup\db\config\ SIZE_DATA_BUFFERS
If both touch files are present, SIZE_DATA_BUFFERS_DISK overrides the value in SIZE_DATA_BUFFERS. At this time, Veritas recommends that you use SIZE_DATA_BUFFERS_DISK.
Table: Absolute byte values for SIZE_DATA_BUFFERS_DISK, SIZE_DATA_BUFFERS shows the possible values to include in SIZE_DATA_BUFFERS_DISK or SIZE_DATA_BUFFERS.
Table: Absolute byte values for SIZE_DATA_BUFFERS_DISK, SIZE_DATA_BUFFERS
For a data buffer of this size (kilobytes) | Enter this touch file value |
|---|---|
32 | 32768 |
64 | 65536 |
96 | 98304 |
128 | 131072 |
160 | 163840 |
192 | 196608 |
224 | 229376 |
256 | 262144 |
Data buffer sizes continue in multiples of 32. Multiply the buffer size by 1024 for the touch file value.
A direct I/O backup triggers the following message: "Enabling direct I/O. Buffer size: <buffer size>."
To disable direct I/O
- Create the following touch file on the media server that owns the storage unit:
install_path\VERITAS\NetBackup\bin\DISABLE_DIRECT_IO