Veritas Access Appliance 8.4 Solutions Guide for NetBackup

Last Published:
Product(s): Appliances (8.4)
Platform: Veritas 3350,Veritas 3340,Veritas 3360
  1. Access Appliance integration with NetBackup
    1.  
      About Access Appliance as a NetBackup client
    2.  
      About Access Appliance as backup storage for NetBackup
    3.  
      Use cases for long-term data retention
  2. System requirements
    1.  
      Supported configurations and versions for NetBackup with Veritas Data Deduplication
    2.  
      Supported configurations and versions for NetBackup with MSDP-C
  3. Configuring Veritas Data Deduplication with Access Appliance
    1.  
      About Veritas Data Deduplication
    2.  
      Benefits of using Veritas Data Deduplication with Access Appliance
    3.  
      Supported features with different versions of Veritas Data Deduplication
    4. Configuring Veritas Data Deduplication without WORM
      1.  
        Configuring Veritas Data Deduplication using the GUI
      2.  
        Configuring Veritas Data Deduplication using the Access CLISH
    5. Configuring Veritas Data Deduplication with WORM
      1.  
        Configuring Veritas Data Deduplication with WORM using GUI
      2.  
        Configuring Veritas Data Deduplication with WORM using the Access CLISH
    6.  
      Managing Veritas Data Deduplication using the Access CLISH
    7. Managing Veritas Data Deduplication using GUI
      1.  
        Viewing information about Veritas Data Deduplication
      2.  
        Starting or stopping the Veritas Data Deduplication service
      3.  
        Increasing storage for Veritas Data Deduplication
      4.  
        Unconfiguring Veritas Data Deduplication
      5.  
        Adding secondary IP for Veritas Data Deduplication
      6.  
        Deleting secondary IP for Veritas Data Deduplication
      7.  
        Changing the primary IP for Veritas Data Deduplication
      8.  
        Upgrade the deduplication version for Veritas Data Deduplication
      9.  
        Setting affinity node for Veritas Data Deduplication
    8. Accessing Access Appliance storage shell for management tasks
      1. About the Access Appliance storage server shell
        1. About the dedupe command
          1.  
            Stopping and starting the MSDP services
        2.  
          About the retention command
        3.  
          About the setting command
        4.  
          About the support command
    9.  
      Support for multiple domains across networks for Veritas Data Deduplication
    10.  
      Veritas Data Deduplication storage layout
    11.  
      Configuring a Veritas Data Deduplication storage unit on NetBackup
    12.  
      Configuring global deduplication using the Veritas Data Deduplication storage server across the domain
    13.  
      Enabling Veritas Data Deduplication encryption
    14.  
      Support for bandwidth throttling during duplication
    15.  
      Setting up secure communication between Veritas Data Deduplication on Access Appliance and the NetBackup primary server
    16.  
      About MSDP encryption using NetBackup KMS service
    17. Support for NetBackup Auto Image Replication
      1.  
        Separating the duplication and replication network
    18.  
      Setting up Auto Image Replication (AIR) between two Access Appliances which have secure communication enabled
  4. NetBackup Dedupe Direct for Oracle
    1.  
      Support for NetBackup Dedupe Direct for Oracle
  5. Configuring MSDP-C with Access Appliance
    1.  
      Starting the Access S3 server and provisioning the S3 bucket
    2.  
      Configuring Access S3 bucket with NetBackup MSDP-C
  6. Migrating the NetBackup images from existing storage to Veritas Access storage
    1.  
      Migrating NetBackup images from CloudCatalyst/S3/MSDP-C to Veritas Data Deduplication storage
    2.  
      Migrating the NetBackup images from the Veritas Data Deduplication STU to the MSDP-C STU
  7. Configuring Access Appliance with the NetBackup client
    1.  
      Configuring Access Appliance for NetBackup client
    2.  
      Installing the NetBackup client add-on packages
    3.  
      Prerequisites for configuring the NetBackup client
    4.  
      Configuring the NetBackup client
    5.  
      Adding an optional media server
    6.  
      Adding multiple primary servers
    7.  
      Adding file systems to the backup configuration
    8.  
      Removing file systems from backup configuration
    9.  
      Changing the virtual IP address used by the NetBackup client
    10.  
      Upgrade the NetBackup client
    11.  
      Unconfiguring the NetBackup client
    12.  
      Enabling Veritas Data Deduplication catalog backup with NetBackup client
    13.  
      Disabling Veritas Data Deduplication catalog backup from NetBackup client
    14.  
      Displaying the status of NetBackup services
    15.  
      Configuring backup operations using NetBackup or other third-party backup applications
    16.  
      Restoring filesystems backed up with NetBackup client
  8. Configuring isolated recovery environment (IRE)
    1.  
      Requirements
    2.  
      Configuring the network isolation
    3.  
      Configuring an isolated recovery environment using the command line
    4.  
      Configuring an isolated recovery environment on a storage server
    5.  
      Managing an isolated recovery environment on a storage server
    6.  
      Configuring data transmission between a production environment and an IRE storage server
  9. Troubleshooting
    1.  
      Additional resources
    2.  
      Generating Access Appliance S3 server keys using the helper script
  10.  
    Index

About Veritas Data Deduplication

Access Appliance is integrated with a duplication engine which is based on Media Server Deduplication Pool (MSDP) technology for storing backup data. The storage server component of Veritas Data Deduplication runs on the Access Appliance nodes with high availability in active/passive mode. The deduplication plug-in of the NetBackup media server does segmentation and finger printing of the backup data and sends the deduplicated data to Access Appliance. The Veritas Data Deduplication storage server stores and manages the deduplicated data. The deduplication storage server provides high availability to protect against storage, node, and network failures. It supports client direct as well as media server deduplication configurations.

Considerations before configuring Veritas Data Deduplication:

  • All storage that is provisioned for Veritas Data Deduplication is displayed as a single storage pool on NetBackup.

  • Access Appliance supports a single deduplication pool of size upto 2.478 PiB (approximately) if the Veritas Data Deduplication version is 20.4.0.1 or later. If the Veritas Data Deduplication version is 19.0.1, you can create two storage pools with up to 2.478 PiB (approximately) capacity wherein each storage pool has a capacity of 1.236 PiB (approximately).

  • The import operation may fail if you export the Veritas Data Deduplication configuration (on Access Appliance 8.0 or previous versions) and try to import it after upgrading to Access Appliance 8.4 version.

  • Maximum cache size is set based on the storage consumption of the container and the number of containers running on that node. It also considers the affinity of the containers running on that node. The maximum cache size is managed internally by the Access Appliance and the user is not required to modify it. During operations such as dedupe shrink and dedupe grow, this value is tuned as required.

  • 500 GB of system memory is required for every 1 PB of storage when you configure the Veritas Data Deduplication server. If you want to configure 1.24 PiB storage, you require 768 GB of system memory as additional system memory kit can be purchased in 386 GB increments. You can install additional memory and retry the configuration. This also applies to upgrade and dedupe grow operation.

  • Access Appliance supports multiple versions of Veritas Data Deduplication. You can configure Veritas Data Deduplication version of your choice, which is compatible with the NetBackup primary server version in the domain. You can upgrade from a lower version to a higher version of Veritas Data Deduplication without loss of data. For supported versions, See Supported configurations and versions for NetBackup with Veritas Data Deduplication.

  • If you configure Veritas Data Deduplication version 19.0.1, the Finger Print (FP) cache mechanism is used to allocate the cache size. If you configure Veritas Data Deduplication version 20.4.0.1 or later, the Predictive and Sampling cache mechanism (PS) cache mechanism is used to allocate the cache size.

  • If you have upgraded to Access Appliance 8.48.4 from an earlier version, the previously configured Veritas Data Deduplication instances continue to use the FP cache mechanism. In order to leverage the 2.478 PiB storage, the type of cache mechanism of the Veritas Data Deduplication container instance should be converted to PS cache, Veritas strongly recommends that the operation be performed under the supervision of Veritas Technical Support.

  • If you have newly configured an instance of Veritas Data Deduplication version 20.4.0.1 on Access Appliance version 8.3.100 and then upgraded the appliance to version 8.4, then the type of cache mechanism of the Veritas Data Deduplication container instance automatically gets converted to PS cache.

    To convert the cache mechanism of the Veritas Data Deduplication container instance to FP, perform the following steps:

    • After the upgrade is completed, login to the the MSDP container shell of version 20.4.0.1 using the following command:

      podman exec -it <container_name> bash

    • Execute the following commands to disable PS cache inside the MSDP container. 

      /opt/veritas/vxapp-manage/pdde_cmds tune --write 
--enable-local-predictive-sampling-cache false

    • Write the sample FP value in terms of bytes as follows: 

      /opt/veritas/vxapp-manage/pdde_cmds tune --write 
--max-cache-size "1GiB"

    • Restart the Veritas Data Deduplication instance using the following commands: 

      dedupe stop <config_name>
dedupe start <config_name>