Veritas Access Appliance Solutions Guide for NetBackup
- Access Appliance integration with NetBackup
- System requirements
- Configuring Veritas Data Deduplication with Access Appliance
- About Veritas Data Deduplication
- Benefits of using Veritas Data Deduplication with Access Appliance
- Configuring Veritas Data Deduplication using the GUI
- Configuring Veritas Data Deduplication using the Access CLISH
- Support for multiple domains across networks for Veritas Data Deduplication
- Veritas Data Deduplication storage layout
- Configuring a Veritas Data Deduplication storage unit on NetBackup
- Configuring global deduplication using the Veritas Data Deduplication storage server across the domain
- Enabling Veritas Data Deduplication encryption
- Migrating the NetBackup images from existing storage to Veritas Data Deduplication storage
- Configuring Access Appliance as a cloud storage server with NetBackup CloudCatalyst
- Configuring backup and restore using NetBackup policies
- Configuring Access Appliance with the NetBackup client
- Configuring Access Appliance for NetBackup client
- Installing the NetBackup client add-on packages
- Prerequisites for configuring the NetBackup client
- Configuring the NetBackup client
- Adding an optional media server
- Adding multiple master servers
- Adding file systems to the backup configuration
- Removing file systems from backup configuration
- Changing the virtual IP address used by the NetBackup client
- Upgrade the NetBackup client
- Unconfiguring the NetBackup client
- Enabling Veritas Data Deduplication catalog backup with NetBackup client
- Disabling Veritas Data Deduplication catalog backup from NetBackup client
- Displaying the status of NetBackup services
- Configuring backup operations using NetBackup or other third-party backup applications
- Configuring Access Appliance for NetBackup cloud storage
- Restoring file systems backed up with NetBackup client
- Troubleshooting
- Index
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 100TB and a separate catalog file system of size 5TB are created.
The dedupe grow command creates a new file system for every 100TB. 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 the data file systems is more than 100 TB, then multiple directories are created in proportion to the size considering 100 TB as the threshold. If multiple directories are already present, then they are not created again
Note:
Veritas Data Deduplication configuration requires 5 TB 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 system followed by configuration. 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.
Configuration fails if there is a directory mismatch before and after configuration.
You can use the dedupe config command to configure the deduplication server.
Dedupe> config filesystem1 [, filesystem2,...] ip [username catalogfilesystem]
This command configures the deduplication server using the given set of data file systems, IP address, username and catalog file system. The data and catalog file systems are used to store the deduplicated data and its metadata respectively.
Reconfiguration of Veritas Data Deduplication can be done only using CLISH.
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.
- Run the following command to configure Veritas Data Deduplication:
dedupe> config filesystem_list virtual_IP username catfs_name
where the catfs_name depends on the configuration.
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.
You can use the dedupe catgrow <size> command to grow the catalog file system to the specified size. The default dedupe grow command does not modify the size of the catalog file system. If there are multiple data file systems, specify the file system names in the same order in which you specified them in the dedupe show command previously.
The default size of the stripe unit of the deduplication file system created is 64K. As a result of the creation of catalog file system and VxFS and VDD optimizations, performance improvements can be seen in optimized duplication and restore.