Data Protection Central: Problem Resolution Path

Introduction:

Data Protection Central or DPC is a tool that unifies the UI experience for Data Protection Suite users. The intention is for users to leverage DPC as the starting point for monitoring their critical activities and assets. This includes job status (backups, replications and snaps) along with critical events, system health, and capacity across the enterprise (instead of using the native management interfaces for each product in the portfolio).

Data Protection Central supports:

• Avamar
• Data Domain
• Data Protection Advisor
• Search
• NetWorker 
• PowerProtect Data Manager 

 

Deployment: 

DPC can be deployed in two ways:

• Using an OVF file in vCenter or vSphere
• On a SUSE Linux server deployed in accordance with DPC Admin guide, with a java jar file installs

Before you open a case with Dell, check that the services are up. Collect the output and the following relevant information, and attach this to the Service Request on creation. This helps the support engineer troubleshoot your issue quicker.
     

1. Verify if all DPC and System Manager Services are active and online and provide support with the output.
   1. Open PuTTY or SSH to DPC Component as 'admin' user.       
   2. Run the following command to fetch Services Status and provide the output:

~admin/bin/dpc status

3. Gather environmental data and logs.

~admin/bin/dpc-data_int.sh
Select option 2
This will create two file that you will need to gather and upload to the SR.
/tmp/dpc-data.out
/tmp/dpc-logs.tgz

 

2. If System Reporting Issues are seen with Avamar, Data Domain, DPA, or SEARCH, provide remote support with the output.
   1. Run the following command on IDPA Avamar and DPC and System Manager as 'root' user.
   2. Open PuTTY or SSH to Avamar as admin.     
   3. Switch to the root user using following command su - and provide the password. 
   4. Run the following commands and provide the output. 

rabbitmqctl list_queues
rabbitmqctl eval 'rabbit_shovel_status:status().'

3. If Lightweight Directory Access Protocol (LDAP) related or if login issues are seen while logging into the System Manager UI using idpauser or NT/AD Credentials:

   1. If External LDAP/Active Directory is in use, Run the following commands on Active Directory or domain controller (PowerShell):

Get-ADUser -Identity "ldap_query_username"
Get-ADGroup -Identity "ldap_search_group_name"

2. If internal IDPA LDAPs, run the following command on ACM and provide the output:

cat /usr/local/dataprotection/var/configmgr/server_data/ldapconfig.xml

4. Attach the UI Screenshot of failure or issue.