When the Australian development team at BackupAssist let me know there would be an anti-ransomware feature available so soon after the recent high profile cryptolocker attacks, I have to admit, the timing seemed almost a little too convenient.
Until any concrete evidence comes to light, we’ll work on the basis they just know the market, but my investigations will continue nonetheless 🙂
It’s been a couple of months since we announced the launch of BackupAssist v10 and its super efficient new cloud backup engine. The significance of the new engine is that it unlocks the possibility of using public cloud giants AWS and Azure as backup destination options.
While the BackupAssist side of things is typically easy to configure, I’ve had a few requests for help navigating Azure’s configuration options, so in this article, I’ll be walking through the steps as they are today.
Legally secure, fully automated email archiving is something that every business can benefit from, regardless of size or industry.
Today MailStore Server, the world’s leading e-mail archiving solution expands its extensive feature set, to include individual email reports, advanced search settings for users, and further enhancements for administrators.
We recently needed to migrate our own internal MDaemon and SecurityGateway server to a new location. Luckily we often do this for customers and we have guides specifically written to help with this process.
We often get support queries where the PC clock has been the cause of an issue but never have I seen a few minutes of drift make such a difference.
This one isn’t actually specific to BackupAssist but it did rear its head with a customer who happened to be storing their backups on a local NAS. The backup job in question was a ‘file protection’ one, so the simple backup of files to a local network share as a destination. The job had run fine for many days without errors but suddenly overnight the job would fail with an error like the one below:-
We have seen two instances recently where BackupAssist has been used to run an image job on HP Proliant servers but the job fails 98% through the image of the C: drive with the error ‘Drive Cannot Find the Sector Requested’.
This would usually point to physical drive sector issues and a possible dying disk, but after some further investigation it would appear that this is actually a specific issue to do with the pre-installed status of System partitions on HP Proliant range of Server platforms.