But I also would like to tell you that it might not be necessary to bring it back on-prem. Those are just a few reasons that I would use. If you run the O365 solution as a VM, you can then protect that VM with VBR (and send it to another location/ cloud/ tape.) and comply with the 3-2-1 rule * But you will still have the data and the possibility to export/ restore (even to on-prem or to another O365 tenant) When you stop with O365, it literally stops. * I'm sure you can understand that users will make more mistakes in those (as in: let's delete some files we don't need anymore or similar )ĥ. ![]() ![]() * At least if you start using OneDrive for Business and/ or SharePoint Online which will be included in the next version You can even view headers now in case something bad came in. Now you will be able to do all those searches on your backup. * Maybe you are familiar with our Veeam explorer for Exchange technology, which we continue to improve. You can do eDiscovery on those backups and export/ restore/ save. * While Microsoft hosts it, if something happens and you need to prove things legally but you can't, then you won't be able to blame MSFT. It still remains your data and you are responsible for it. * Hackers or malware (even ransomware which has happened already once on the O365 serviceĢ. * Or even worse: an angry admin who goes in and starts deleting users. * It doesn't save you from accidental deletion (both from the user side or an administrator mistake) Microsoft does provide some sort of backup and is presenting you with an SLA to keep everything up and running, but: ![]() There are a few reasons why you want to do that:ġ.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |