Druva Data Retention and Legal Hold Basics
Druva Data Retention and Legal Hold Basics can involve product configuration, account permissions, network connectivity, or backup policy settings. The right procedure depends on whether you use Druva endpoint protection, inSync, Phoenix or a cloud workload offering.
Understand the issue
Druva Data Retention and Legal Hold Basics can involve product configuration, account permissions, network connectivity, or backup policy settings. The right procedure depends on whether you use Druva endpoint protection, inSync, Phoenix or a cloud workload offering. Start by identifying the exact product and whether the issue affects one endpoint, a backup policy, or an entire tenant. Avoid making changes to production retention or deleting a backup as a first troubleshooting step.
Step-by-step troubleshooting
- Confirm the applicable product, tenant, user group and workload.
- Review the current policy, schedule, retention and role permissions before editing.
- Check for conflicts between device assignment, backup windows and organizational requirements.
- Test proposed changes on a limited non-production scope when possible.
- Document the change and verify backup and recovery outcomes afterward.
What to check before escalating
Keep a record of the time of failure, affected workload, relevant policy name, client or agent version, and a sanitized copy of the error message. If the problem is intermittent, compare the most recent successful job with the failing run. For changes involving recovery or deletion, validate a known-good restore point first.
How to confirm the issue is resolved
Run a limited backup or recovery test within your organization’s approved change process. Check the job history and verify that the protected data is recoverable. A successful login or completed backup notification alone does not prove a restore will work.
