Veritas Access Solutions Guide for NetBackup
- Veritas Access integration with NetBackup
- System requirements
- Configuring Veritas Data Deduplication with Veritas Access
- About Veritas Data Deduplication
- Add-on license for using Veritas Data Deduplication
- Benefits of using Veritas Data Deduplication with Veritas Access
- Configuring Veritas Data Deduplication using the GUI
- Configuring Veritas Data Deduplication using the Veritas Access command-line interface (CLI)
- Configuring a Veritas Data Deduplication storage unit on NetBackup
- Configuring global deduplication using the Veritas Data Deduplication storage server across the domain
- Migrating the NetBackup images from existing storage to Veritas Data Deduplication storage
- Configuring Veritas Access as a cloud storage server with NetBackup CloudCatalyst
- Configuring backup and restore using NetBackup policies
- Configuring Veritas Access with the NetBackup client
- Prerequisites for configuring the NetBackup client
- About the NetBackup Snapshot Client
- About NetBackup snapshot methods
- Enabling or disabling the NetBackup SAN client
- Workflow for configuring Veritas Access for NetBackup
- Registering a NetBackup master server or adding an optional media server
- Displaying the excluded files from backup
- Displaying the included and excluded files for backups
- Adding or deleting patterns to the list of files in backups
- Configuring or resetting the virtual IP address used by NetBackup
- Configuring the virtual name of NetBackup
- Displaying the status of NetBackup services
- Configuring backup operations using NetBackup or other third-party backup applications
- Performing a backup or restore of a Veritas Access file system over a NetBackup SAN client
- Performing a backup or restore of a snapshot
- Installing or uninstalling the NetBackup client
- Configuring Veritas Access for NetBackup cloud storage
- Troubleshooting
- Unmounting the SDFS volume before restarting Veritas Access or the NetBackup media server
- Upgrading SDFS from earlier versions to 7.4.2
- Log locations for troubleshooting
- Changing log levels
- Additional resources
- Generating Veritas Access S3 server keys using the helper script
- OpenDedup tuning recommendations
- Index
OpenDedup tuning recommendations
OpenDedup has a flexible design that works for small users as well as large data enterprises. You can tune OpenDedup as per your requirements to serve your use case. Veritas recommends that you perform the following tuning before you start using the LTR solution.
Table: XML tags
XML parameter | Value |
|---|---|
max-open-files | 200 |
write-threads | 32 |
io-threads | 64 (within extended config) |
map-cache-size | 1024 |
local-cache-size | 500 GB (as per your local cache) |
sync-on-write | false |
refresh-blobs | true (only to be set when Glacier cloud tier is used) |
glacier-archive-days | 30 (only to be set when Glacier cloud tier is being used) |
sync-files | true (within extended config) |
chunk-size | 40960 |
hash-type | VARIABLE_MD5 |
max-file-writebuffers | 80 |
On the media server for the ODD-on-Media_Server use case:
# echo "* hard nofile 65535" >> /etc/security/limits.conf # echo "* soft nofile 65535" >> /etc/security/limits.conf # exit
Based on the system workload, ensure that the number of portal threads are increased (on Veritas Access):
/opt/VRTSnas/conf/portald.conf >> cf_max_s3_threads