PowerProtect Data Manager 19.16 Virtual Machine User Guide

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.

Network-attached storage and DD-system storage units

If the storage unit of a protection policy is different or changed from the destination asset source, you must assign a network to the destination asset for a successful restore. For example, if your source asset is backed up in an IPv6 network, you must assign an IPv6 network to the destination asset for the restore to be successful.

To assign a network for the destination asset, perform the following steps:

1. In the PowerProtect Data Manager UI, select Infrastructure > Assets > NAS.
2. Select the destination asset, click More Actions and select Assign Network. The Assign Network page appears.
3. Select a network from the Network Label list, click Save.
4. If a restore failed because of the wrong destination address, retry the operation.

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.
• The FQDNs of application-agent hosts that use FQDN as their preferred host address resolve to a valid IPv4 or IPv6 address.
• Each application-agent host that uses FQDN as its preferred host address resolves the FQDN of PowerProtect Data Manager to an IP address of the same protocol that it uses. For example, if a host uses IPv4, it resolves the FQDN of PowerProtect Data Manager to an IPv4 address.

Search Engine indexing and adding IPv6 to an IPv4-only system

If you add IPv6 to an IPv4-only system, indexing from any existing Search Engine cluster becomes unavailable. After adding IPv6, you must delete all IPv4 Search Engine nodes to remove the Search Engine cluster, and then add new IPv6 nodes to a new cluster.

Unlike other PowerProtect Data Manager components, if IPv6 is used with a Search Engine, the FQDN of all Search Engine nodes and related DD systems must always resolve to an IPv6 address and never to an IPv4 address.

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.