- Notes, cautions, and warnings
- Preface
- Getting started
- Preparing for deployment
- Deployment
- Configuration
- Glossary
PowerProtect Data Manager and its components support IPv4 and IPv6 addresses in certain configurations.
Component | Internet Protocol |
---|---|
PowerProtect Data Manager core | IPv4 only or both IPv4 and IPv6 |
PowerProtect Data Manager cloud deployments (AWS, Azure, GCP) | IPv4 only
NOTE:Despite other entries in this chart to the contrary, if
PowerProtect Data Manager is deployed to a cloud environment, no component in the cloud can use IPv6.
|
VM Direct, TSDM, 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 and TSDM 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.
|
|
IPv4, IPv6, or both |
|
IPv4 only or both IPv4 and IPv6 |
|
IPv4, IPv6, or both |
|
IPv4 only or IPv6 only
NOTE:Only the Microsoft SQL Server agent supports
VM Direct.
|
|
IPv4, IPv6, or both |
|
IPv4, IPv6, or both |
Standalone application agents | IPv4 only |
Network-attached storage (NAS) | IPv4, IPv6, or both |
Storage arrays (PowerMax) | IPv4 only |
Storage arrays (PowerStore) | IPv4 only |
Kubernetes | IPv4 only |
PowerProtect Data Manager management | IPv4 or IPv6 |
PowerProtect DD communication | IPv4 or IPv6 |
Report Browser | IPv4 only
NOTE:
If
PowerProtect Data Manager is configured to use both IPv4 and IPv6, configuring an NTP server and setting a time zone is required for accurate date and time information in reports.
|
SupportAssist | IPv4, IPv6, or both |
Syslog Log Server Gateway | IPv4 or IPv6 |
The following limitations and considerations apply.
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.
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.
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:
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 and reverse IP lookup must be configured to ensure the following:
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.
If using vCenter or ESXi 7.0u2 or earlier with only IPv6, SPBM providers must be added using their PowerProtect Data Manager FQDN.
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.
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.