Limitations in MSDP Scaleout
MSDP Scaleout has the following limitations:
It is not fully compliant with Federal Information Processing Standards (FIPS).
The internal services MSDP operator, MSDP Controller, and MDS of a MSDP Scaleout are not compliant with FIPS.
MSDP is FIPS compliant. For more information, see the NetBackup Deduplication Guide.
Does not support SELinux.
Supports only NBCA. Does not support ECA.
Does not support availability zones for AKS cluster.
For more information about the limitation see Create an Azure Kubernetes Service (AKS) cluster that uses availability zones topic of the Azure documentation.
Limited AKS node failure tolerance.
Backup and restore can fail if AKS node fails. If MSDP operator detects the MSDP Scaleout pod failure, it attempts to restart it and perform a repair operation automatically. The repair operation can be delayed if Azure infrastructure or Kubernetes do not allow the pod to be restarted.
An Azure volume cannot be attached to two different nodes at the same time. When the node which Azure volume is attached to fails, MSDP operator cannot run the same pod with the same Azure volume on another node until the failed node is repaired or deleted by AKS.
AKS node auto-repair may take more than 20 minutes to finish. In some cases, it may be necessary to bring the node backup manually.
IPv6 is not supported.