Veritas Access Appliance 8.2 Solutions Guide for NetBackup

Last Published:
Product(s): Appliances (8.2)
Platform: Veritas 3340,Veritas 3350,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

Configuring Veritas Data Deduplication with WORM using the Access CLISH

This section describes how you can configure Veritas Data Deduplication with 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 file systems 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.

  • The lockdown mode should be enterprise or compliance.

To configure the deduplication storage server with WORM

  • To configure the deduplication storage server, enter the following:
    dedupe> config filesystem1[,filesystem2,...] IP	username
[catfs_name] vdd_version [encryption]	[worm=yes] [minret] [maxret]
[node_name] [config_name]

    Where:

    filesystem1, filesystem2,...

    Specifies the data filesystem names.

    IP

    Specifies the interface IP.

    username

    Specifies the user name.

    catfs_name

    Specifies the catalog file system 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.

    minret

    Specifies the minimum image retention period in seconds. It can contain: [1-9](s|S). The minimum value is 3600s.

    maxret

    Specifies the maximum image retention period in seconds. It can contain: [1-9](s|S). The maximum value is 1892160000s.

    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 has any running container with storage consumed.

    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.

    Note:

    You have to use the same password when you configure the storage server on NetBackup.

Note:

Configuring Veritas Data Deduplication requires a 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 on all the nodes to resolve the FQDN to a specific IP.

If the FQDN entry is not found, <catfs>.vdd.com is used as the FQDN entry during configuration.

Note:

If you have to reconfigure deduplication, you have to pass all the file systems in the same order that is displayed in the output of the dedupe show command.

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.

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.