Veritas Access Appliance 8.2 Solutions Guide for NetBackup
- Access Appliance integration with NetBackup
- System requirements
- Configuring Veritas Data Deduplication with Access Appliance
- Configuring Veritas Data Deduplication without WORM
- Configuring Veritas Data Deduplication with WORM
- Managing Veritas Data Deduplication using GUI
- Accessing Access Appliance storage shell for management tasks
- Support for NetBackup Auto Image Replication
- NetBackup Dedupe Direct for Oracle
- Configuring MSDP-C with Access Appliance
- Migrating the NetBackup images from existing storage to Veritas Access storage
- Configuring Access Appliance with the NetBackup client
- Configuring isolated recovery environment (IRE)
- Troubleshooting
About Veritas Data Deduplication
Access Appliance is integrated with a duplication engine which is based on Media Server Deduplication Pool (MSDP) technology for storing backup data. The storage server component of Veritas Data Deduplication runs on the Access Appliance nodes with high availability in active/passive mode. The deduplication plug-in of the NetBackup media server does segmentation and finger printing of the backup data and sends the deduplicated data to Access Appliance. The Veritas Data Deduplication storage server stores and manages the deduplicated data. The deduplication storage server provides high availability to protect against storage, node, and network failures. It supports client direct as well as media server deduplication configurations.
Considerations before configuring Veritas Data Deduplication:
All storage that is provisioned for Veritas Data Deduplication is displayed as a single storage pool on NetBackup.
Access Appliance supports two storage pools for Veritas Data Deduplication with up to 2.48 PiB capacity. Each storage pool has a capacity of 1.24 PiB.
The import operation may fail if you export the Veritas Data Deduplication configuration (on Access Appliance 8.0 or previous versions) and try to import it after upgrading to Access Appliance 8.2 version.
Maximum cache size is set based on the storage consumption of the container and the number of containers running on that node. It also considers the affinity of the containers running on that node. The maximum cache size is managed internally by the Access Appliance and the user is not required to modify it. During operations such as dedupe shrink and dedupe grow, this value is tuned as required.
500 GB of system memory is required for every 1 PB of storage when you configure the Veritas Data Deduplication server. If you want to configure 1.24 PiB storage, you require 768 GB of system memory as additional system memory kit can be purchased in 386 GB increments. You can install additional memory and retry the configuration. This also applies to upgrade and dedupe grow operation.
Access Appliance supports multiple versions of Veritas Data Deduplication. You can configure Veritas Data Deduplication version of your choice, which is compatible with the NetBackup primary server version in the domain. You can upgrade from a lower version to a higher version of Veritas Data Deduplication without loss of data. For supported versions, See Supported configurations and versions for NetBackup with Veritas Data Deduplication.
Note:
Veritas is aware of the recently announced high severity vulnerability in Curl and Libcurl (CVE-2023-38545). For Access Appliance, Veritas recommends that you use the latest Veritas Data Deduplication version 19.0.1. If it is not possible, then it is recommended that you use Veritas Data Deduplication version 17.1 version. The following security advisory should be followed to install the EEB.