Symptoms

Review the data-collector.log files and observe the data-collector is not utilizing activity_v3 calls. (a) Identify the last activity collection. 2026-04-14T17:29:31.427Z I [DataCollectionService$ResourceCollectTask.run(189)] - Finished collect activity_v2 from ppdm-core (596f0c69-d95b-484b-bb15-eb7aabdf2340), successful: true The collector is only supporting v2 calls! 2026-04-14T17:35:00.384Z I [PPDMServiceUtil.isResourceApplicable(46)] - Checking applicability - Product: PowerProtect Data Manager, SystemId: 596f0c69-d95b-484b-bb15-eb7aabdf2340, Resource: activity_v2, isV2: true, isV3: false, isPPDM: true 2026-04-14T17:35:01.775Z I [PPDMServiceUtil.isResourceApplicable(57)] - Is PPDM resource activity_v2 applicable for data collection: false (b) Check the yaml file an observe no entry in the EveryFiveMinute section for activity_v3. > cat /opt/dpsmsm/instance/data-collector/config/application.yaml - name: EveryFiveMinutes cron: '0 0/5 * * * ?' resources: - asset_v2 - activity_v2 - alert_v2 - audit_v2 - copy_v3 - resource_deletion_detail_v2 - system_health_metric_and_issue_v2

Cause

During the upgrade from X to 20.1 or 20.2 the reporting node upgrade is successful but starting from 20.1 the data collector will make call to /api/v3/activity API to collect the activity related data. As we will utilize the Activity v3 API.Whenever the reporting-engine container is upgraded, restarted or rebooted, an internal configuration script is triggered that copies the application.yaml file from /var/lib/dellemc/reporting/config/dcs-backup/ to /opt/dpsmsm/instance/data-collector/config/ in reporting-engine container.By copying the old/stale config file over the newer file it resulted in the old activity v2 calls being utilized on startup for activity data collection.

Resolution

A resolution will be included in PPDM version 20.2 Workaround (a) SSH to the reporting node. (b) Both of following yaml files must be updated. You must maintain indentation! /var/lib/dellemc/reporting/config/dcs-backup/application.yaml /opt/dpsmsm/instance/data-collector/config/application.yaml Note: The objective is to add the activity_v3, the missing entry under the resources in EveryFiveMinutes section. > vi <filename> certificates: cert-base-path: /var/lib/dellemc/reporting/config/certs collected-system: data-collection: schedules: - name: EveryFiveMinutes cron: '0 0/5 * * * ?' resources: - asset_v2 - activity_v2 - activity_v3 - alert_v2 - audit_v2 - copy_v3 - resource_deletion_detail_v2 - system_health_metric_and_issue_v2 - name: Daily cron: '0 10 2 * * ?' resources: - application_agent_v2 - configuration_v2 - fetb_v2 - license_info_v1 - license_v2 - node_v2 - policy_summary_v3 - policy_v3 - resource_group_v2 - server_dr_configuration_v2 - storage_system_v2 - telemetry_setting_v2 - upgrade_history_v1 - upgrade_package_v2 products: - name: PowerProtect Data Manager min-version: 19.18.0 - name: PowerProtect Data Manager Appliance min-version: 5.15.0 httpclient: ppdm: x-ppdm-caller: reporting-data-collector (c) Restart the data collector service. > /opt/dell/reporting/scripts/collector_service.sh restart

Support Cases