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 data transmission between a production environment and an IRE storage server

Once the configuration of an isolated recovery environment (IRE) is completed, the production Access Appliance hosts are no longer able to access the storage server. You need to add MSDP reverse connections to allow data transmission between the production MSDP storage server and the IRE storage server. Then you can add the replication operation.

To configure data transmission between a production environment and an IRE

  1. Open an SSH session to the IRE storage server. Run the following command to determine if the external network is open:

    setting ire-network-control external-network-status

    If it is not, run the following command:

    setting ire-network-control external-network-open

  2. Run the following command to add an MSDP reverse connection:

    setting ire-network-control add-reverse-connection remote_storage_server=<production MSDP server> [remote_primary_server=<production primary server>] [local_storage_server=<IRE network interface>]

    Where:

    • <production MSDP server> is the fully qualified domain name (FQDN) of the MSDP server in your production environment.

    • [remote_primary_server=<production primary server>] is an optional parameter for the FQDN of the primary server in your production environment. This parameter is required if the IRE domain uses an alternative name to access the production primary server. This scenario usually occurs if the production primary server runs on multiple networks with multiple hostnames.

    • [local_storage_server=<IRE network interface>] is an optional parameter for the hostname of the network interface to use for image replication on the IRE storage server. This parameter is required if the network interface for replication is different than the IRE storage server name.

  3. If necessary, repeat the previous step to add additional MSDP reverse connections.
  4. If Auto Image Replication (AIR) is not already configured on the production domain, run the following command to copy the IRE schedule to the production domain as a storage lifecycle policy (SLP) window:

    setting ire-network-control sync-ire-window production_primary_server=<production primary server> production_primary_server_username=<production username> [slp_window_name=<SLP window name>]

    Where:

    • <production primary server> is the FQDN of the primary server in your production environment.

    • <production username> is the username of the NetBackup primary user with permission to list SLPs and SLP windows in the production environment. For Windows users, enter the username in the format <domain name>\<username>. For other users, enter the username only.

    • [slp_window_name=<SLP window name>] is an optional parameter to give a name for the SLP window. If you do not provide this parameter, the name of the SLP window is IRE_DEFAULT_WINDOW.

  5. If you do not have them already, create a source SLP on the production primary server and a target import SLP on the IRE primary server.

    See Support for NetBackup Auto Image Replication.

    Note:

    You cannot add the replication operation from the production NetBackup primary when you create the SLPs as the target storage is air gapped. Continue to the next step to add the replication operation.

  6. Run the following command to add the IRE storage server as a replication target of the production Access Appliance domain and to add the replication operation to the SLP:

    setting ire-network-control add-replication-op production_primary_server=<production primary server> production_primary_server_username=<production username> production_storage_server=<production storage server> ire_primary_server_username=<IRE username> source_slp_name=<production SLP name> target_import_slp_name=<IRE SLP name> target_storage_server=<target storage server> target_storage_server_username=<target storage server username> production_storage_unit=<MSDP storage unit> [slp_window_name=<slp window name>]

    Where:

    • <production primary server> is the FQDN of the primary server in your production environment.

    • <production username> is the username of the NetBackup primary user with permission to list SLPs and SLP windows in the production environment. For Windows users, enter the username in the format <domain name>\<username>. For other users, enter the username only.

    • <production storage server> is the FQDN of the production storage server in your production environment.

    • <IRE username> is the username for an administrator on the IRE NetBackup primary server. For Windows users, enter the username in the format <domain name>\<username>. For other users, enter the username only.

    • <source SLP name> is the SLP name from the production primary server to add the replication operation to.

    • <target SLP name> is the import SLP name from the IRE primary server.

    • <target storage server> is the FQDN of the target storage server in your IRE environment.

    • <target storage server username> is the username of the MSDP storage server used while configuring the target storage server .

    • <MSDP storage unit> is the name of the MSDP storage unit that is the replication source in the source SLP.

    • [slp_window_name=<slp window name>] is an optional parameter for the name of the SLP window that is synced with the IRE schedule. This parameter must match the SLP window name from the previous step, if applicable. If you do not provide this parameter, the default name is used.

  7. If you opened the external network at the beginning of this procedure, run the following command to close it and resume the air gap schedule:

    setting ire-network-control resume-schedule

Note:

The setting ire-network-control allow-devices is not supported in Access Appliance.