Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

The "Get Rollback Actions Report" operation under the "Report - Cyber Resilience" resource in this node fetches detailed reports about rollback actions performed within a specified time frame. Rollback actions typically refer to operations like file or data restores and deletions that are part of cyber resilience activities, such as recovering from ransomware attacks or accidental data loss.

This node is beneficial for security analysts, IT administrators, and compliance officers who need to monitor and audit rollback activities across their managed customers and entities. It helps track what rollback actions were taken, on which entities (files, folders, devices, users), and their statuses (pending, completed, failed).

Practical examples:

  • Generating a report of all restore actions performed last month to verify recovery efforts.
  • Filtering rollback actions by specific customers or entity types to focus on critical assets.
  • Auditing failed rollback attempts to identify potential issues or security incidents.

Properties

Name Meaning
Date Selection Method Choose how to filter the report by date:
• All Dates (no date filter)
• Specific Dates (select start and end dates)
• Relative Date Range (predefined ranges like current month, last 30 days, etc.)
Start Date The start date/time for the report period (required if using Specific Dates).
End Date The end date/time for the report period (required if using Specific Dates).
Date Range Select a predefined relative date range for the report (used if Date Selection Method is Relative Date Range). Options include Current Month, Previous Month, Last 30 Days, Year To Date, etc.
Filter by Customers Boolean flag to enable filtering results by specific customer IDs.
Customer IDs List of customer IDs to include in the report (required if filtering by customers).
Filter by Entity Types Boolean flag to enable filtering results by entity types.
Entity Types Entity types to filter by when enabled. Options: File, Folder, Device, User.
Filter by Action Types Boolean flag to enable filtering results by action types.
Action Types Action types to filter by when enabled. Options: Delete, Restore.
Filter by Action Status Boolean flag to enable filtering results by action status.
Action Status Action status values to filter by when enabled. Options: Pending, Completed, Failed.
Return All Whether to return all matching results or limit the number of results returned.
Limit Maximum number of results to return if not returning all. Default is 100.

Output

The output JSON contains an array of rollback action records matching the specified filters. Each record typically includes details such as:

  • The action type (e.g., delete, restore)
  • The entity involved (file, folder, device, user)
  • The status of the action (pending, completed, failed)
  • Timestamps related to the action
  • Associated customer information
  • Other metadata relevant to the rollback event

If binary data is included (not indicated explicitly here), it would represent attachments or files related to rollback actions, but this operation primarily returns structured JSON data.

Dependencies

  • Requires an API key credential for authenticating with the Druva MSP API.
  • The node uses the Druva MSP API endpoint https://apis.druva.com.
  • The "Customer IDs" property loads options dynamically via an API call to retrieve available customers.
  • Proper configuration of the API credentials and network access to the Druva MSP API is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or expired API credentials will cause authentication failures.
    • Specifying invalid date ranges (e.g., start date after end date) may result in errors or empty results.
    • Filtering by customers or entity/action/status types without selecting any options may lead to no data returned.
    • Network connectivity issues can prevent API calls from succeeding.

  • Error Messages:

    • Errors related to fetching customers or other dynamic options usually indicate API access problems or permission issues.
    • If the resource or operation is not implemented, the node throws an error indicating the unsupported resource.
    • Rate limiting or quota exceeded errors from the API should be handled by retrying later or adjusting usage.

Links and References

Discussion