Overview
When you restore data, the Restore Scan feature allows you to scan the data for malicious files and pre-defined file hashes from the IOC library. This ensures that the restored data is clean and devoid of viruses and malware. You can scan the data regardless of the restore location.
When Restore Scan is enabled, you will see the Restore Scan section in the Restore window for EC2 (Restore as an Instance) and EBS resources (Restore as an Instance/ Restore as a Volume).
[ EC2 and EBS Resource Restore window] In the Restore Scan section, toggle the Enable Restore Scan. If the scan is mandated during a data restore activity, then you will not be able to disable it. Contact your Druva Cloud administrator for more details.
A Druva Cloud Admin can also enable and update the Restore Scan Settings from the Cyber Resiliency > Ransomware Recovery > Restore Scan > Settings tab. For more information, see Enable Restore Scan.
However, the time taken to restore the data increases when the scan is enabled. You can view the progress of the scan job from the Jobs page. There is an option to cancel the scan job if you feel it’s taking longer than what you expected and restoring the files is urgent. This will cancel the restore job as well.
On the restore Jobs page for EC2 and EBS resources, the green sign is present beside every restore job that has malicious file scan enabled.
❗ Important
Restore scan is not supported for files beyond 1 GB in size.
If the checkbox for Override Scanning is NOT selected from the Cyber Resiliency > Restore Scan Settings > Override Scanning section, you cannot edit or update the Quick Scan settings from the Restore to Location UI for EC2 and EBS resources.
Things to consider for EC2 and EBS Cyber Restore (Restore Scan)
Supported Partition Types and File Systems for AWS Workloads (EC2 and EBS Volume) also apply for Cyber Recovery for AWS Workloads (EC2 and EBS Volume).