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

Support for multiple domains across networks for Veritas Data Deduplication

You can use a single deduplication pool to backup data from multiple NetBackup domains. The Veritas Data Deduplication server deduplicates backups originating from different subnets. Use the network ip addr show command to list the multiple subnets that have been created.

Network> ip addr show
IP 												Netmask/Prefix 	Device Node 				Type 				Status
-- 												-------------- 	------ ---- 				---- 				------
192.168.10.5 		255.255.255.0 		eth5		 vaupg_01 Physical
192.168.10.13 	255.255.255.0		 eth5 		vaupg_02 Physical
192.168.30.2 		255.255.255.0 		eth4 		vaupg_01 Physical
192.168.30.10 	255.255.255.0 		eth4 		vaupg_02 Physical
10.209.192.206 255.255.252.0 		eth1 		vaupg_01 Physical
10.209.192.208 255.255.252.0 		eth1 		vaupg_02 Physical
10.209.194.38 	255.255.252.0 		eth1 		vaupg_01 Virtual 	ONLINE (Con IP)
192.168.10.22 	255.255.255.0 		eth5 		vaupg_01 Virtual 	ONLINE
192.168.10.25 	255.255.255.0 		eth5 		vaupg_02 Virtual 	ONLINE
192.168.30.15 	255.255.255.0 		eth4 		vaupg_02 Virtual 	ONLINE
192.168.30.20 	255.255.255.0 		eth4 		vaupg_01 Virtual 	ONLINE

You can use the following command to configure the deduplication server with a virtual IP.

Dedupe> config filesystem1[,filesystem2,...] IP username
[catfs_name] vdd_version [encryption] [worm=yes] [minret] [maxret]
[node_name] [config_name]

For example:

Dedupe> config D3_3533793 192.168.10.22 dedupeuser CAT_3088152 19.0.1 
enable_encryption=no enable_worm=yes 3600s 1892160000s cluster1_01 msdp-worm
Access Appliance dedupe INFO V-493-10-3732 Deduplication server configured successfully

You can verify that the IP has been added successfully using the dedupe show command.

Dedupe> show
Parameter                   msdp-worm
==========================  ========================
Catalog_Filesystem          CAT_3088152
Virtual_IP                  192.168.10.22
Secondary_IP                -
Filesystem                  D3_3533793
Deduplication_Storage_Size  500.0TB
WORM_enabled                True
Hostname                    cluster1_01
Server_Status               ONLINE
Minimum_Retention_Value     3600
Maximum_Retention_Value     1892160000
Max_Cache_Size              250GiB
Percentage_Memory_Usage     5.59%
Affinity                    cluster1_01
Encryption_enabled          False
KMS_enabled                 False
KMS_server                  -
KMS_keygroup                -
Shrink_status               -
Shrink_errors               -
Dedupe_FQDN                 accessvip01.vxindia.veritas.com
Dedupe_Version              19.0.1

You can add another IP from a different subnet.

Dedupe> addip <IPaddress>

For example:

Dedupe> addip 192.168.10.25
ACCESS dedupe INFO V-493-10-0 IP has been successfully added to the 
deduplication server.
Dedupe> addip 192.168.30.15
ACCESS dedupe INFO V-493-10-0 IP has been successfully added to the 
deduplication server.
Dedupe> addip 192.168.30.20
ACCESS dedupe INFO V-493-10-0 IP has been successfully added to the 
deduplication server.

You can verify that the virtual IP is added successfully. The dedupe show command is used to display information about the deduplication server that has been configured. The output of this command includes the file system(s) being used, deduplication server status, storage capacity, secondary IPs used, percentage of memory usage, maximum cache size, and the IP and the cluster node on which the server is running.

Dedupe> show
Parameter                   msdp-worm
==========================  ========================
Catalog_Filesystem          CAT_3088152
Virtual_IP                  192.168.10.22
Secondary_IP                192.168.10.25,192.168.30.15,192.168.30.20
Filesystem                  D3_3533793
Deduplication_Storage_Size  500.0TB
WORM_enabled                True
Hostname                    cluster1_01
Server_Status               ONLINE
Minimum_Retention_Value     3600
Maximum_Retention_Value     1892160000
Max_Cache_Size              250GiB
Percentage_Memory_Usage     5.59%
Affinity                    cluster1_01
Encryption_enabled          False
KMS_enabled                 False
KMS_server                  -
KMS_keygroup                -
Shrink_status               -
Shrink_errors               -
Dedupe_FQDN                 accessvip01.vxindia.veritas.com
Dedupe_Version              19.0.1

Use the network ip addr show command to list the multiple subnets that have been created.

Network> ip addr show
IP 												Netmask/Prefix 	Device Node 				Type 				Status
-- 												-------------- 	------ ---- 				---- 				------
192.168.10.5 		255.255.255.0 		eth5		 vaupg_01 Physical
192.168.10.13 	255.255.255.0		 eth5 		vaupg_02 Physical
192.168.30.2 		255.255.255.0 		eth4 		vaupg_01 Physical
192.168.30.10 	255.255.255.0 		eth4 		vaupg_02 Physical
10.209.192.206 255.255.252.0 		eth1 		vaupg_01 Physical
10.209.192.208 255.255.252.0 		eth1 		vaupg_02 Physical
10.209.194.38 	255.255.252.0 		eth1 		vaupg_01 Virtual 	ONLINE (Con IP)
192.168.10.22 	255.255.255.0 		eth5 		vaupg_01 Virtual 	ONLINE (Dedupe IP)
192.168.10.25 	255.255.255.0 		eth5 		vaupg_01 Virtual 	ONLINE (Dedupe IP)
192.168.30.15 	255.255.255.0 		eth4 		vaupg_01 Virtual 	ONLINE (Dedupe IP)
192.168.30.20 	255.255.255.0 		eth4 		vaupg_01 Virtual 	ONLINE (Dedupe IP)

You can also add a second user. The second user is used to add the second NetBackup domain, if required. You should use a different user for every new NetBackup domain.

Dedupe> adduser user1
Enter Password:
Confirm Password:
ACCESS dedupe INFO V-493-10-0 Adding new user user2 to deduplication server.
ACCESS dedupe INFO V-493-10-0 Added new user user2 to deduplication server 
successfully.

You can perform backup and restore operations from the NetBackup domains from the two subnets.

Note:

You can remove the virtual IP that you added later after the initial configuration. But you cannot remove the virtual IP specified during the initial configuration.

Dedupe> removeip IPaddress

For example:

Dedupe> removeip 192.168.30.15
ACCESS dedupe INFO V-493-10-0 IP has been successfully removed from the 
deduplication server.

You can verify that the second virtual IP has been removed from the configuration using the dedupe show command.

Dedupe> show
Parameter                   msdp-worm
==========================  ========================
Catalog_Filesystem          CAT_3088152
Virtual_IP                  192.168.10.22
Secondary_IP                192.168.10.25,192.168.30.20
Filesystem                  D3_3533793
Deduplication_Storage_Size  500.0TB
WORM_enabled                True
Hostname                    cluster1_01
Server_Status               ONLINE
Minimum_Retention_Value     3600
Maximum_Retention_Value     1892160000
Max_Cache_Size              250GiB
Percentage_Memory_Usage     5.59%
Affinity                    cluster1_01
Encryption_enabled          False
KMS_enabled                 False
KMS_server                  -
KMS_keygroup                -
Shrink_status               -
Shrink_errors               -
Dedupe_FQDN                 accessvip01.vxindia.veritas.com
Dedupe_Version              19.0.1

You can use the dedupe unconfig command to free up all the virtual IPs added to the deduplication server. This command also unconfigures Veritas Data Deduplication from the cluster.

Dedupe> unconfig destroy_fs=yes config_name
ACCESS dedupe INFO V-493-10-0 Removing deduplication server configuration...
ACCESS dedupe INFO V-493-10-0 Deduplication server unconfigured successfully.
Upgrade considerations

You cannot use the same virtual IP for both the CIFS and Veritas Data Deduplication server. So, if a virtual IP is used by the Veritas Data Deduplication server, then you cannot use the same virtual IP for adding CIFS shares or setting the CIFS home directory.

You cannot use the IP of one deduplication server for another Veritas Data Deduplication server.

During the upgrade, the virtual IP which is shared between CIFS and Veritas Data Deduplication server is removed from the CIFS configuration and the next available free virtual IP is assigned to the CIFS server.

  • If a free virtual IP is available, the deduplication continues to work without any issues once the upgrade is complete.

  • If there is no free virtual IP, then the upgrade fails. You can add a free virtual IP to the configuration and try to upgrade again.

  • If the virtual IP is shared between the Veritas Data Deduplication server and a segregated CIFS share, then the upgrade fails even if an additional free virtual IP is available in the configuration. You can move the segregated CIFS share to different virtual IP and try the upgrade again.