Over the last few months it’s been amazing sharing Corso with more and more users. One pleasant surprise has been users who are operating in large, often multi-tenant deployments of Microsoft 365 who want to use Corso to back up all their data. In our discussions on the Corso User Discord, we’ve found some best practices for backing up large Exchange mailboxes with Corso.
The Corso team is all about making sure that your data never goes away. We've worked hard making the industry's only free and open-source tool for backing up Microsoft 365 data. And that's why we're not letting anything from Microsoft die, certainly not 2006's best personal media player, the Zune.
Ummm… look, this all made sense when I bought the Zune and found someone to refurbish it. Just play along with me here, okay?
We all know that Corso is a free and open-source tool for creating backups of your Microsoft 365 data. But where does that data go?
Corso creates a repository to store your backups, and the default in our documentation is to send that data to AWS S3. It's possible however to back up to any object storage system that has an S3-compatible API. Let’s talk about some options.
It’s 10:00 in the morning, and you need coffee and a snack. You know you’re supposed to back up the company’s Microsoft 365 instance, but it takes so long! Surely a quick break won’t matter.
Wrong! While you were in the break room, your organization was hit with a malware attack that wiped out many critical files and spreadsheets in minutes. Now your cell phone’s ringing off the hook. Slapping your forehead with the palm of your hand, you shout, “If only backups were faster and easier!”