Veritas Access Appliance 8.2 Solutions Guide for NetBackup
- Access Appliance integration with NetBackup
- System requirements
- Configuring Veritas Data Deduplication with Access Appliance
- Configuring Veritas Data Deduplication without WORM
- Configuring Veritas Data Deduplication with WORM
- Managing Veritas Data Deduplication using GUI
- Accessing Access Appliance storage shell for management tasks
- Support for NetBackup Auto Image Replication
- 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 isolated recovery environment (IRE)
- Troubleshooting
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.
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.