Actions79
- Admin Actions
- Alert Summary Actions
- Backup Health Summary Actions
- Consumption Billing Analyzer Actions
- Customer Actions
- Event Actions
- Report - Cyber Resilience Actions
- Report - Endpoint Actions
- Report - Enterprise Workloads Actions
- Get Alert History Report
- Get Backup Activity Report
- Get DR Failback Activity Report
- Get DR Failover Activity Report
- Get DR Replication Activity Report
- Get Resource Status Report
- Get Storage Consumption by BackupSets Report
- Get Google Alerts Report
- Get Google License Usage Report
- Get Google Preserved Users Datasources Report
- Get Google Shared Drive Backup Activity Report
- Get Google Shared Drive Restore Activity Report
- Get Google Storage Consumption Report
- Get Google User Count and Status Report
- Get Google User Last Backup Status Report
- Get Google User Provisioning Report
- Get Google User Restore Activity Report
- Get Google User Workload Report
- Get M365 Alerts Report
- Get M365 Groups Backup Activity Report
- Get M365 Groups Discovery Report
- Get M365 License Usage Report
- Get M365 Preserved Users Datasources Report
- Get M365 Public Folder Backup Activity Report
- Get M365 SharePoint Backup Activity Report
- Get M365 SharePoint Site Discovery Report
- Get M365 Storage Consumption Report
- Get M365 Teams Backup Activity Report
- Get M365 Teams Discovery Report
- Get M365 User Count and Status Report
- Get M365 User Last Backup Status Report
- Get M365 User Provisioning Report
- Get M365 User Restore Activity Report
- Get M365 User Workload Report
- Report - Usage Actions
- Service Plan Actions
- Storage Region Actions
- Task Actions
- Tenant Actions
- Tenant Config - Enterprise Workloads Actions
- Tenant Config - inSync Actions
Report - Enterprise Workloads → Get Google Preserved Users Datasources Report
AI-generatedOverview
This node operation fetches the 'Google Preserved Users Datasources Report' from the Druva MSP API under the 'Report - Enterprise Workloads' resource. It is useful for enterprises needing detailed reports on preserved user data sources within their Google environment, aiding in data management, compliance, and auditing. For example, an IT administrator can use this to monitor and analyze preserved user data sources across their organization.
Use Case Examples
- Retrieve a report for a specific date range to analyze preserved user data sources activity.
- Fetch all available data sources reports without date filtering for a comprehensive overview.
- Filter the report by specific customers to focus on particular organizational units.
Properties
| Name | Meaning |
|---|---|
| Return All | Determines whether to return all results or limit the number of results returned. |
| Limit | Specifies the maximum number of results to return when 'Return All' is false. |
| Date Selection Method | Selects the method for filtering report data by date: no filter, specific dates, or relative date ranges. |
| Start Date | The start date for filtering report data (inclusive), used when 'Specific Dates' is selected. |
| End Date | The end date for filtering report data (inclusive), used when 'Specific Dates' is selected. |
| Date Range | Predefined relative date ranges for filtering report data, used when 'Relative Date Range' is selected. |
| Filter by Customer(s) | Determines whether to filter the report results by specific customers. |
| Customer IDs | IDs of the customers to filter the report by, used when 'Filter by Customer(s)' is true. |
| Wrap Output Items | When enabled, wraps all output items into a single item containing an array to prevent the next node from executing multiple times. |
| Wrapper Property Name | The property name to use for the wrapped array of items in the output. Default is 'items'. |
Output
JSON
items- An array containing the report data items when output is wrapped.count- The total count of items in the wrapped output.json- Individual report data items returned by the operation.
Dependencies
- Requires Druva MSP API access with appropriate API key credentials.
Troubleshooting
- If the API returns an error, check that the API credentials are valid and have the necessary permissions.
- Ensure the date filters are correctly set; invalid or conflicting date ranges may cause errors or empty results.
- If filtering by customers, verify that the customer IDs are correct and accessible by the API credentials.
- If 'Return All' is false and the limit is set too low, the report may return incomplete data.