Skip to main content

How can we help you?

Druva Documentation

Rollback actions for accidental and malicious deletes

To enhance the data security posture and to safeguard backup data from deletions triggered by rogue administrators, ransomware attacks, or operational incidents, you can configure the Rollback Actions. 

With Rollback Actions, you can roll back deleted entities within a configurable rollback window. 

When you configure the rollback window, the deleted entities are available for rollback for the specified days before they are permanently deleted.  This provides the administrator the ability to revert malicious or unintended deletes without any loss of data and enables the restoration of productivity rapidly. If everything is exactly how you wanted it to happen, no problem, those safety net copies will be permanently deleted after the rollback window expires and there will be no impact on what you were trying to do. 

 Since the deleted entities reside in the Druva cloud for a specified period, the storage and credits are consumed till the entities are not permanently deleted.

Use case

On June 1st, a rogue administrator deleted 500 VMs and 300 users configured for backup. Now, these entities will be unprotected, and you will lose all their backups. With rollback actions and rollback window configured for seven days,  these entities are not permanently deleted; you can rollback them to their original state with their backups anytime within the next seven days, i.e., till June 8th.  

Implementation

The following diagram illustrates the capability:

Rollback_Actions.gif

Get started

Here’s a quick video to get you started

 

High-level steps

Step 1: Plan and prepare

Step 2: Configure rollback action window

Step 3: Rollback deleted entities

Step 4: Monitor rollback requests

Related topic

FAQs

 

  • Was this article helpful?