Veritas Access Appliance 8.2 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
- Supported features with different versions of Veritas Data Deduplication
- Configuring Veritas Data Deduplication without WORM
- Configuring Veritas Data Deduplication with WORM
- Managing Veritas Data Deduplication using the Access CLISH
- Managing Veritas Data Deduplication using GUI- Viewing information about Veritas Data Deduplication
- Starting or stopping the Veritas Data Deduplication service
- Increasing storage for Veritas Data Deduplication
- Unconfiguring Veritas Data Deduplication
- Adding secondary IP for Veritas Data Deduplication
- Deleting secondary IP for Veritas Data Deduplication
- Changing the primary IP for Veritas Data Deduplication
- Upgrade the deduplication version for Veritas Data Deduplication
- Setting affinity node for Veritas Data Deduplication
 
- Accessing Access Appliance storage shell for management tasks
- 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
- Support for bandwidth throttling during duplication
- Setting up secure communication between Veritas Data Deduplication on Access Appliance and the NetBackup primary server
- About MSDP encryption using NetBackup KMS service
- Support for NetBackup Auto Image Replication
- Setting up Auto Image Replication (AIR) between two Access Appliances which have secure communication enabled
 
- 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 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 primary 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
- Restoring filesystems backed up with NetBackup client
 
- Configuring isolated recovery environment (IRE)- Requirements
- Configuring the network isolation
- Configuring an isolated recovery environment using the command line
- Configuring an isolated recovery environment on a storage server
- Managing an isolated recovery environment on a storage server
- Configuring data transmission between a production environment and an IRE storage server
 
- Troubleshooting
- Index
Configuring Veritas Data Deduplication using the GUI
This section describes how you can configure Veritas Data Deduplication using the Access Appliance GUI.
To configure Veritas Data Deduplication
- Log on to the Access Appliance application.- Select the Quick Actions icon present on the dashboard page. Navigate to Provision Storage > Storage for Netbackup > Veritas Data Deduplication. Click Next. You have to use this option if any instance of Veritas Data Dedupication is already present on the cluster. 
- Or, navigate to Settings > Veritas Data Deduplication Management. Click Configure. This option is available only if no Veritas Data Dedupication instances are present on the cluster. 
 
- A default storage pool is created at the time of initial configuration with all the available disks.
- Under the Activate Policy tab, select the Veritas Data Deduplication policy. Click Complete prerequisites. 
- Complete all the prerequisites such as, selecting the storage pool  to activate the Veritas Data Deduplication policy and click Activate policy.After the policy is activated, click Finish. 
- Under the Provision storage tab, specify all the required fields.Select storage policy From the dropdown menu, choose Veritas Data Deduplication policy. Storage size Mention the capacity for Veritas Data Deduplication storage (size should be less than 1.24 PiB) Note: Reducing the storage for Veritas Data Deduplication is not supported using GUI. You can reduce storage for Veritas Data Deduplication using CLISH. See Managing Veritas Data Deduplication using the Access CLISH. for more details. Username Specify the username to be used Password/Confirm Password: Enter the password for the above username VIP (Virtual IP address) From the drop-down list, select any virtual IP. Node Name of the node on which deduplication service is to be configured (default is None which means any node can be configured) Configuration name Name for the deduplication service. Default value is msdp-engine. Note: This is an optional parameter when the first deduplication server is configured. It is mandatory when you configure the second deduplication server. Dedupe version (NBU version) Select the required version of Veritas Data Deduplication server (NetBackup version) from the drop-down list. This is a mandatory parameter. Enable encryption Select this check box to enable encryption. Click Provision storage. If you configure a second deduplication server, then you have to specify the name of the deduplication service in the Configuration name field. View the Recent Activity panel for the status of the task. The storage provisioning is now complete. 
An alert appears in the GUI when the memory usage of the Veritas Data Deduplication server is more than 80%. The alert displays the amount of memory used and the total RAM usage. If the situation persists for more than 24 hours, an AutoSupport alert is raised and an email is sent.
If you receive this alert, go to > and restart the service once you reach this threshold. For information about the issues that are caused when the Veritas Data Deduplication service consumes large amount of memory, see https://www.veritas.com/support/en_US/article.100045745.