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 Access CLISH
This section describes how you can configure Veritas Data Deduplication without WORM using the Access Appliance command-line interface.
You can use the dedupe> config command to configure the deduplication storage server using the given set of filesystems and IP address.
Prerequisites:
The filesystem should be striped and should be already created with size not exceeding 100 TiB and the IP should be online before you start configuring Veritas Data Deduplication.
If the total deduplication pool size required is larger than 100 TiB, then create multiple data filesystems.
The total data filesystem size should not exceed 1.24 PiB.
The data filesystems are used to store the deduplicated data and its metadata.
You are required to create a separate catalog file system to store the Veritas Data Deduplication catalog. The minimum size of the catalog file system should be 5 TiB.
The deduplication storage server uses the specified IP address to receive the backup data from NetBackup.
To configure the deduplication storage server
- To configure the first deduplication storage server, enter the following:
dedupe> config filesystem1[,filesystem2,...] IP username [catfs_name] vdd_version [encryption] [worm=no] [minret] [maxret] [node_name] [config_name]
Where:
filesystem1, filesystem2,...
Specifies the data filesystem names.
IP
Specifies the interface IP. You can check for the IP using the network IP address show command.
username
Specifies the username.
catfs_name
Specifies the catalog filesystem of the deduplication server.
vdd_version
Specifies the version of Veritas Data Deduplication sever. This is a mandatory parameter.
For supported version, See Supported configurations and versions for NetBackup with Veritas Data Deduplication.
encryption
Enables encryption. The possible values are enable_encryption=yes/enable_encryption=no. If enabled, all data sent to the deduplication server is encrypted but without KMS.
worm
Enables WORM. The possible values are enable_worm=yes/enable_worm=no. This is an optional parameter.
minret
Specifies the minimum image retention period. This is an optional parameter.
If you want to specify the config_name parameter, then you should pass the value, vxdefault as the minimum retention value.
maxret
Specifies the maximum image retention period. This is an optional parameter.
If you want to specify the config_name parameter, then you should pass the value, vxdefault as the maximum retention value.
node_name
Name of the node on which deduplication service is to be configured.
If node_name is provided, the affinity of the server is set to that node.
If node_name is not provided, and if there is only one container in the cluster, the affinity is not set to any node. After the second container comes into existence, irrespective of whether affinity (node_name) is provided or not, the affinity is set to the node other than the node where the first container is running, as it does not have any running container with storage consumed.
If you want to specify the config_name parameter, then you should pass the value, vxdefault as the node name.
config_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.
You are prompted to enter your password. After you specify your password, Veritas Data Deduplication is configured.
If you configure a second deduplication server, then you have to specify the config_name parameter and specify the maximum and minimum retention values as vxdefault. For example:
dedupe> config filesystem1[,filesystem2,...] IP username [catfs_name] vdd_version [encryption] [worm=no] [minret=vxdefault] [maxret=vxdefault] [node_name=vxdefault] [config_name]
Note:
Make a note of the password that you use. You have to use the same password when you configure the storage server on NetBackup and also when you reconfigure Veritas Data Deduplication.
Note:
Configuring Veritas Data Deduplication requires an FQDN entry which resolves to a specific IP. You can either have a DNS entry or you can add an entry in the /etc/hosts file of both the NetBackup media and primary servers.on all the nodes to resolve the FQDN to a specific IP.
Note:
If you have to reconfigure deduplication, you have to pass all the filesystems in the same order that is displayed in the output of the dedupe show command before deduplication was unconfigured.
If a new IP is used for the deduplication server during reconfiguration, the new IP should map to the old FQDN. You can either have a DNS entry or add an entry in the /etc/hosts file on all the nodes to resolve the FQDN to a specific IP.