IPv6 Limitations in NetBackup 7.1 for various NetBackup features.

Article:TECH168171  |  Created: 2011-08-26  |  Updated: 2013-05-07  |  Article URL http://www.symantec.com/docs/TECH168171
Article Type
Technical Solution


Issue



 The following list contains known IPv6 limitations for various NetBackup features.


Solution




The following list contains known IPv6 limitations for various NetBackup features.
 
1. In IPV6-enabled NetBackup 7.1 environments, granular (GRT) backup and recovery is not supported for Microsoft Exchange Server or Microsoft Sharepoint Server.
 
2. Backup and restore are not currently supported using IPv6 addresses as server host names.
 
3. The following two NetBackup limitations can occur if an IPv6 address is used as a client name or an image name:
a. Using IPv6 addresses as client names in a policy do not work with Instant recovery (IR) snapshots on Windows systems. That can cause a backup to fail. Specify a hostname instead of an IPv6 address. Image names are created automatically in NetBackup, and consist of a combination of the client name and a timestamp. If the client name is configured in the policy as the IPv6 address, the result is an image name (in the image catalog) that includes the IPv6 address. That causes the backup to fail.
b. Using IPv6 addresses as image names under the catalog do not work with Instant recovery (IR) snapshots on Windows systems.
 
4. Symantec has not qualified the Dynamic Host Configuration Protocol (DHCP) version 6.
 
5. As of August 2011, IPv6 is not supported for Symantec's Storage Foundation for Oracle RAC (SFRAC).
 
6. The use of IPv6 link-local addresses (addresses that start with fe80::) are not supported in NetBackup.
   
7. NetBackup BMR cannot restore on an IPv6-only network. BMR can back up IPv6 information, however an IPv4 network connection is required for BMR to perform restores.
 
8. For clustered configurations, the virtual name must resolve to either an IPv4 address, or an IPv6 address, but not both.
In a clustered environment, the clustered environment defines a highly available resource with a virtual name that is only a single address. You can make that address an IPv4 address that is highly available or an IPv6 address is highly available. You cannot have a virtual name that resolves to both.
 
9. For the 7.1 release of NetBackup, Symantec does not fully qualify the SAN Client to support IPv6.
 
10. For the 7.1 release of NetBackup, OpsCenter cannot monitor an IPv6-only server. Each server must have an available IPv4 address for it to be monitored. However, this release does support a dual-stack server. For a dual stacked server, the available IPv4 address is used.
 
11. Upon upgrading to NetBackup 7.1, a configuration that lists an IP address for the REQUIRED_INTERFACE entry may experience a change on the choice of interfaces after the upgrade. For instance, REQUIRED_INTERFACE = IP_address.
If the hostname that is associated with the IP address resolves to more than one IP address, each of those addresses is used, rather than the first address. Symantec recommends the use of a hostname that resolves to one address
with REQUIRED_INTERFACE or replacing it with the PREFERRED_NETWORK equivalent in NetBackup 7.1.
 
12. In an IPv4 environment, if you attempt an NDMP three-way backup using NAS Filers that are configured to use IPv6, the backup fails with an error: "Too many datablocks". The error occurs when you run the backup to a tape drive that is attached to a NAS FILER that is configured for IPv6. To avoid this issue, add the entry: NDMP_IPV6_DISABLE in the /db/config/ndmp.cfg file to tell NetBackup that IPv6 is not to be used.

 




Article URL http://www.symantec.com/docs/TECH168171


Terms of use for this information are found in Legal Notices