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
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.
Reconfiguration is a two-step process involving unconfiguring the Veritas Data Deduplication without destroying the filesystems and configuring it again with the same existing filesystems. After an upgrade, if you want to reconfigure the Veritas Data Deduplication service, the following checks are performed:
If a separate catalog file system existed before reconfiguration, then the same catalog file system is passed to the dedupe config command during reconfiguration.
If a separate catalog file system did not exist before reconfiguration, then the catalog file system cannot be passed to the dedupe config command during reconfiguration.
After unconfiguration, you can use dedupe config command to reconfigure the deduplication server.
Reconfiguration of Veritas Data Deduplication can be done only using CLISH.
Starting with the 8.1 release, MSDP has to be reconfigured. For detailed steps, refer to the Veritas Access Appliance Upgrade Guide.
To reconfigure Veritas Data Deduplication
- Run the dedupe show command and make a note of the file system names for both the data and catalog file system.
- Unconfigure Veritas Data Deduplication using the dedupe unconfig command.
Dedupe> unconfig
- Run the following command to configure Veritas Data Deduplication:
Dedupe> config filesystem_list virtual_IP username [catfs_name] vdd_version [encryption] [worm] [minret] [maxret] [node_name] [config_name]
where the catfs_name depends on the configuration and filesystem_list is a comma-separated list of filesystems without space.
The vdd_version should be specified as 17.1.
The credentials should be the same that you used when you previously configured Veritas Data Deduplication.
The catalog file system needs to be mentioned only if the previous Veritas Data Deduplication configuration had a catalog file system.
Note:
If encryption was not enabled during initial configuration but is enabled during reconfiguration by specifying encryption=yes, encryption is enabled for the reconfigured Veritas Data Deduplication server. Any new data sent to the deduplication server is encrypted.
If encryption was enabled during initial configuration but it is not enabled during reconfiguration, then encryption is not disabled.