Learn about the known issues found in Data Protection Central.
Issue ID | Functional area | Description | Workaround or resolution |
---|---|---|---|
DPC-10262 | Avamar Manage Policies page | The list of clients that is retrieved from Avamar is displayed on the Available Clients page . The expected behavior is to also retrieve the preselected clients that are applicable for the policy in Avamar. However, the clients are not selected. | Select the required clients manually by editing the policy. |
DPC-1227 | Activities | In Asset Activities and Job Activities, when filtering on the Started column and specifying the end time for the custom date range, the filtered list does not include the end time. | Specify an end time that is 1+ minute beyond the current time to ensure that the filtered list includes the end time. |
DPC-1366 | Audit | Audit shows failed status. Completed with Exceptions jobs show as Failed in the Audit login Comments section:
Comments Exception: null [Exception: null] |
Do not rely on the Audit Log for Job or Asset Activity status. To get an accurate status for activities, use the Job Activities or Asset Activities pages. |
DPC-5141 | Avamar | When an Avamar system is added to Data Protection Central, the Health status shows that Avamar garbage collection has not occurred in 24 hours. | The Health status is corrected when the next Avamar garbage collection occurs overnight. |
DPC-1006 | Avamar | Evaluation licenses are reported as invalid in Data Protection Central. When an Avamar or NetWorker system with an evaluation license is added to Data Protection Central, the page incorrectly reports the license as invalid. | None. |
DPC-500 | Avamar | Avamar retention policy may end a day early due to daylight saving time offset. Due to daylight saving time, when you create an Avamar retention policy with a specific end date in Data Protection Central, the exact end date may be one day earlier. This behavior is due to a time zone offset, which may convert the end date to one day earlier. | Use one of the following solutions for this issue:
|
299768 | Avamar | Attempting to reactivate an Avamar system while activation is already in progress causes issues. When you add an Avamar system to Data Protection Central, the system remains in the NotReporting state until the activation completes. During this period, clicking the Reactivate button on the , interferes with the system and cause issues with the activation. | Wait until activation completes before you attempt to reactivate reporting. You can track the status of the activation in the Audit page. |
298749 | Avamar | AUI invalid redirect message when the override IP address is not configured in the network interfaces of the Avamar client host. | The best practice for specifying both the hostname and override URL for a system is to use a fully qualified domain name. However, if you must use an IP address, ensure that the IP is configured in the network interfaces of the
Avamar client host. If you configure
Data Protection Central to use an IP address that is not configured in the network interfaces of the
Avamar client host, the following message may appear:
Invalid redirect: https://12.3.456.789/aui/ does not match one of the registered values: [https://localhost/aui/] This message does not prevent you from logging into AUI. |
293891 | Data Domain | Data Protection Central does not report Data Domain systems with expired passwords as NotReporting. If the password for the user who is associated with a Data Domain system has expired, Data Protection Central is unable to report version, capacity, mtree, and alert information. However, Data Protection Central fails to mark the Data Domain system as NotReporting. Instead, the system is reported as Good or Unhealthy, based on the last successful communication with the system. | Perform one of the following actions as a workaround:
|
DPC-3699 | IPv6 | Use of an IPv6 address as hostname to add any type of elemental fails. | Use a valid hostname in the hostname field instead of an IPv6 address when you add an elemental using the Add System wizard. |
DPC-3698 | |||
285578 | Lockbox | When a VM migrates from one ESXi server to another, stable system values may change which may result in an inaccessible lockbox.
Data Protection Central uses a lockbox to encrypt and store the credentials of the systems that it monitors. Migrating a virtual machine from one ESXi server to another may result in an inaccessible lockbox and prevent
Data Protection Central from being able to read the system credentials. When a lockbox becomes inaccessible, the following symptoms occur:
|
To make the lockbox accessible again, reset the system fingerprint. To reset the system fingerprint, see the 'Reset the lockbox' procedure in the Data Protection Central Administration Guide. |
DPC-5184 | PowerProtect Data Manager | Data Protection Central forces PowerProtect Data Manager into account lockout when the PowerProtect Data Manager password is changed unilaterally. | Do the following steps:
|
298650 | SSO | If the system times are not synchronized, the management applications cannot launch with SSO. If the system times on the Data Protection Central system and the managed system are not synchronized (if the time difference between them is greater than one minute), management applications that are launched from Data Protection Central cannot use Single Sign-on (SSO) to complete the authentication process. However, you can log in to the system management application using the username and password. | See the "Configuring Network Time Protocol" section in the Data Protection Central Security Configuration Guide for more information about establishing time synchronization. |
296164 | SSO | When you edit the system management application launch URL, you must re-register SSO. When you edit any of the following fields for a system, you must re-register SSO to update the system management application launch URL:
|
Perform the following steps to re-register SSO:
|