Retention policy vs Ransomware
We have the following set up for 5-6 folders(over 500gb in size):
6 months retention policy from last back up date.(no file version history enabled or any other option).
Incremental backups every 90 days: block level back ups every 1 day.
Questions about this policy and how it relates to ransomware, I am not sure if this is a good approach the way it is now. But I'd like to understand this more:
1.If we get a ransomware and it's dormant for 7 days, will we able to go back 7 days before and access all our previous files ?
2. Also, according to the site it says that "To recover a file in the block-level backup you need all consequent blocks to remain in their places. If by any chance, blocks become inconsistent, you will lose the ability to recover."
If a ransomware attack happens, will we be able to recover, won't we be losing the consistency in blocks if an encrypted file is uploaded ?
3. According to this link
it says that we should enable Keep number of versions (for each file) to 3 , is this necessary with a retention policy of 6 months the way we have it now ?
Starting with #2, this is all handled by the software. There's nothing a user needs to do to manage the block-level backups and related retention. Even if you are infected, then the only thing that might be affected is the last block-level, but previous ones will remain in place and allow for restores to any point-in-time across those backups. More likely though, the ransomware will cause the full file to be backed up (since the entire file changes) and in that case, previous versions would be flagged for deletion - and this is bad. Easy to fix though - just keep at least 2 versions of files and the previous backup set (full file backup + any block-level backups) would remain in storage. The other thing you should consider is adding a Purge Delay. That way, files that are to be deleted have their deletion delayed a # of days before it actually happens.
Moving on to 3: Yes, it's a good idea and since you keeping files for at least 90 days, you're going to end up with multiple versions for frequently edited files, but what if a file is not changed during that time and 90 days has passed since its backup and the ransomware attack. The whole point of backup is flexibility in restoring. Keeping more than 1 version is ideal.
And now 1: You may lose everything in that case without a purge delay and only keeping one version. if the ransomware changes the file extension *file is renamd)e, the old file is considered deleted and the software may remove the deleted file if you don't have versions and / or a purge delay (or both) in place. If the ransomware simply encrypts the file in place without a rename, you have effectively created a new version and the old one could be removed depending on when the last backup of that file took place. So add versions and a purge delay.
Sign in or register to add a comment.
Add a Comment
Welcome to MSP360 Forum!
MSP360 Managed Products
Managed Backup - General
Managed Backup Windows
Managed Backup Mac
Managed Backup Linux
Managed Backup SQL Server
Managed Backup Exchange
Managed Backup Microsoft 365
Managed Backup G Workspace
Backup for Linux
Backup SQL Server
Connect Free/Pro (Remote Desktop)
Local backup possible issues if Block Level, Retention policy, and Full Backup Schedule?
Warning 'cannot be purged' on retention policies MSP 360 backup in combination with Wasabi retention
Retention policy understanding
Feature Request: Expanded Backup Retention Policies
Terms of Service
Useful Hints and Tips
Created with PlushForums
© 2024 MSP360 Forum