Ransomware is right up there as one of the worst types of malware your clients are likely to come across.

Not only is there the risk of being locked out of computer systems or important databases, but there's the additional risk of public backlash and damages to reputation. 

As you'll have no doubt seen in the press - if the breach is large enough, ransomware attacks can easily become high-profile media events and the ransom demands can be incredibly tricky to manage.

If they do pay the ransom for their data, not only is it an admission of defeat, but it can also be a significant financial hit.

What's more, there's really no guarantee they’ll gain access to their systems again.

Once the scammers have their money, there isn’t anything but goodwill compelling them to return what was already taken. 

A recent update for BackupAssist Classic v11.1 has now been released which includes an improvement to the Exchange Granular Restore module along with a whole host of other enhancements and fixes. If you're working with customers using BackupAssist to protect their on-premise Exchange installations,  you'll be pleased to know BackupAssist have now improved their Microsoft Exchange Granular Restore module which includes support for Exchange 2019 up to CU9 and 2016 up to CU20.

The BackupAssist Classic cloud backup addon historically supported 3 different backup destination types - Amazon S3, Microsoft Azure and WebDAV. This would give users the option to perform file and application backups to remote cloud-based destinations by simply configuring a compatible backup container.

Technically this works well but can be a bit overwhelming for customer who don't already have either a Microsoft Azure account or Amazon AWS Account and are happy to ignore 99.9% of the features those accounts provide and focus on just the creation of backup storage. WebDAV is more used for remote NAS support so is only an option for customers with suitable hardware.

So you are using MailStore  to archive all your company email, and to manage mailbox sizes you have chosen to delete all email from users mailboxes older than 1 year. Its all working great, but then you receive a support call from one of your customers who is having issues reading an email that is only in their archive. All they get is a content unavailable error when they select the message in the archive?