Veritas Access Solutions Guide for NetBackup
- Veritas Access integration with NetBackup
- System requirements
- Configuring Veritas Data Deduplication with Veritas Access
- Migrating the NetBackup images from existing storage to Veritas Data Deduplication storage
- Configuring Veritas Access backup over S3 with OpenDedup and NetBackup
- 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
- Troubleshooting
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