Office 365 Backup Tool

SaferTech Description: Microsoft/Office 365 est de plus en plus populaire, mais il n'est pas fourni avec une sauvegarde. Avec un nombre sans cesse croissant d'organisations qui perdent des données dans le cloud, avez-vous besoin de sauvegarder vous-même Office 365 ?.

Now as a side note, that's almost never the right thing to do, but unfortunately it's something a lot of admins jump to. You can enable retention for the mailboxes themselves, well that just adds an extra step for the admin to purge it. Now you can argue that's bad administration, and I would agree with you; but let's face facts. People make mistakes. If your data recovery plan relies on people having not made mistakes, then that is a bad plan. One option that sometimes gets touted as a potential solution to this problem is preservation lock. With that enabled, even your admins can't override or change your retention policies. Now that is a potentially dangerous option.
Once it's enabled you can't turn it off until the defined period of time has elapsed. Even if you want to. I'm not a lawyer so don't take this as legal advice, but there are a number of data privacy laws which might take issue with that. The European GDPR being one, potentially. It might not take kindly to being unable to delete certain types of data. So please use that option with caution. Certainly, I wouldn't advocate enabling it across the board. Now I've been focusing on the actions of your admins, but this problem extends beyond your admins, and beyond the admins at any of your support partners. I've seen Microsoft's own support team cause data loss. They accidentally wiped out two weeks worth of data at one of my customers.
To be fair to them they put their hands up, they apologized, and they provided compensation; but, they couldn't bring the data back. So retention policies: they're really useful if you want to preserve and locate data in your live system, but it's in your live system, and if you try to view it as a recovery solution, that is a major weakness. Our fourth scenario is malicious destruction of data. Now I don't think I need to spend a lot of time in this one. I've already explained a number of scenarios where you could lose data accidentally, so if someone wants to destroy the data on purpose they have options. The really scary scenario here is if one of your admin accounts was compromised, or if an admin went rogue for that matter. If that happens there's not a lot you can do.

You can enable retention policies, but then they can just turn them off and purge the data anyway. About the only thing that might help is preservation lock; but I've already told you why that one could be a bad idea. The fifth and final scenario is recovery from data corruption. Data corruption can and does happen - even in Office 365. Whether that happens on Microsoft's end, your end, or somewhere in-between... it doesn't really matter - the effect is the same. The fact is that your data can be damaged or destroyed through no fault of your own.
start download

Microsoft do have protections in place is to prevent catastrophic corruption from causing large-scale data loss. Your data exists in multiple replicas, and they replicate using transactions (that's planned changes) rather than the underlying storage. So if the storage itself becomes corrupt they can just flip over to a different replica. This doesn't prevent small-scale data corruption from damaging or destroying individual files, though. Retention policies won't help either. They are triggered in response to planned changes.
Prix: 95 000 $.