PowerProtect Data Manager 19.12 Network Attached Storage User Guide

PDF

Supported Internet Protocol versions

PowerProtect Data Manager and its components support IPv4 and IPv6 addresses in certain configurations.

Table 1. Supported configurationsSupported configurations
Component	Internet Protocol
PowerProtect Data Manager core	IPv4 only or both IPv4 and IPv6
VM Direct and Search	IPv4 only or IPv6 only NOTE Virtual machines that are backed up must use the same protocol that VM Direct uses. Virtual machines can use both IPv4 and IPv6, even though VM Direct cannot.
Application agents integrated with PowerProtect Data Manager:	NOTE If both IPv4 and IPv6 are configured and the PowerProtect Data Manager FQDN is used, the agent uses IPv6 for network communication.
File System	IPv4, IPv6, or both
Microsoft Exchange Server	IPv4 only or both IPv4 and IPv6
Microsoft SQL Server (Application Direct)	IPv4, IPv6, or both
Microsoft SQL Server (VM Direct)	IPv4 only or IPv6 only NOTE Only the Microsoft SQL Server agent supports VM Direct.
Oracle RMAN	IPv4, IPv6, or both
SAP HANA	IPv4, IPv6, or both
Storage Direct	IPv4 only
Standalone application agents	IPv4 only
Network-attached storage (NAS)	IPv4 only
Kubernetes	IPv4 only
PowerProtect Data Manager management	IPv4 or IPv6
PowerProtect DD communication	IPv4 or IPv6
Report Browser	IPv4 only
SupportAssist	IPv4, IPv6, or both
Syslog Log Server Gateway	IPv4 or IPv6

The following limitations and considerations apply.

Communication with components

If PowerProtect Data Manager is configured to only use one protocol, all components it communicates with must also use that protocol. If some components that PowerProtect Data Manager communicates with use IPv4 and others use IPv6, PowerProtect Data Manager must be configured to use both IPv4 and IPv6.

DD systems and DDVE

If a DD system or a DDVE instance uses only IPv6, the required IPv6 interface must be manually selected when a protection policy is added or edited.

Disaster recovery

Recovering a PowerProtect Data Manager server might result in a conflict with protection-policy configurations. For instance, if the recovered server is configured to use only IPv4, a protection policy that is configured to use IPv6 cannot run.

Name resolution

Name resolution and reverse IP lookup must be configured to ensure the following:

Fully qualified domain names of PowerProtect Data Manager, its components, and DD components resolve to a valid IPv4 or IPv6 address.
If both IPv4 and IPv6 addresses are used for DD, both addresses resolve to the same FQDN.
All IPv4 and IPv6 addresses are valid and reachable.

Server updates

IPv6 is only supported with new installations. Using IPv6 after updating from PowerProtect Data Manager 19.11 or earlier is unsupported.

Storage Policy Based Management

If using vCenter or ESXi 7.0u2 or earlier with only IPv6, SPBM providers must be added using their PowerProtect Data Manager FQDN.

Service Unavailable messages with the vSphere Client PowerProtect plug-in

If vCenter uses the vSphere Client PowerProtect plug-in with IPv6 and the vCenter host is added to PowerProtect Data Manager using its IPv6 address or FQDN, Service Unavailable messages might be seen for the protected virtual machine. Backups and restores of the protected virtual machine are unaffected, and these messages can be ignored.

Uncompressed IPv6 formatting

Network interfaces that exist on a DD 7.4.x or earlier system and that are configured to use an uncompressed IPv6 format cannot be discovered. An example of an uncompressed IPv6 format is 2620:0000:0170:0597:0000:0000:0001:001a. An example of a compressed IPv6 format is 2620:0:170:597::1:1a. To use these network interfaces, reconfigure them to use either an IPv4 address or a compressed IPv6 address, and then initiate a discovery.