What is default behaviour for reports scheduling in Centralized reporting?
The admin who creates the report schedule can only see and edit it after login. Other admins who might be even part of the recipients list can not see the schedule.
For example Admin A has configured the report schedule for "Failed Backups” report then he would only be able to see the configuration and edit it.
Admin B who is added as recipient by admin A would not be able to see the configuration.
How can I determine which administrator has configured the report?
If there are less number of admins like 5 you can let every admin login and check.
For more than 5 admins you can contact Druva support.
Will I be able to access my old data if I subscribe to centralized reporting?
Yes, you will still have full access to your existing historical records going back 18 months in corresponding Centralized Reports.
Does migration to centralized reporting affect backup or restore operations?
No. This change impacts reporting and subscriptions only.
Where can I configure subscriptions for centralized reporting?
Subscriptions for Centralized Reporting can be managed within the individual reports. For detailed information, see Manage Reports.
Will my old subscriptions carry over to centralized reporting?
No. You must manually subscribe to the new reports in the Centralized Reporting section as legacy reports will soon be deprecated.
Can I filter reports by Admin Group?
Yes. Custom reports support Admin Group-based filtering, and the system automatically respects user roles to ensure data privacy.
Where can I find Storage Consumed details that were previously available in the legacy Cost Allocation report for Hybrid Workloads?
For the applicable AWS Marketplace customers, storage consumption insights that were previously available in the legacy Cost Allocation report for Hybrid Workloads are now available in the Storage Consumption by Backup Set Report.