Veritas Access Appliance 8.4 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
Veritas Data Deduplication storage layout
The layout of the Veritas Data Deduplication storage is such that when you configure Veritas Data Deduplication, multiple file systems of 100TiB and a separate catalog file system of size 5TiB are created.
The dedupe grow command creates a new file system for every 100TiB. If you perform upgrade and you had previously configured Veritas Data Deduplication, then the old layout of Veritas Data Deduplication is preserved. If a separate catalog file system existed before upgrade, the same catalog file system is present after the upgrade also. If the size of data filesystems is more than 100 TiB, then those filesystems remain as it is but new data filesystems are created for every 100 TiB that is grown using the dedupe grow command.
Note:
Veritas Data Deduplication configuration requires 5 TiB for creating the catalog file system. This is over and above the size specified for the deduplication pool in the GUI.