Forum Discussion
Back-up tools for Office 365
I am also looking for a backup tool for my organization, and found this tool that have most of the features we are looking for. Not implemented yet still looking for "the One" all inclusive tool, that do not exist.
Keep it will backup your files and mails. Easy to use for ex support staff.
We cover all of your user generated Office 365 data within:
- Exchange Online (mails, calendar, In-Place Archive, etc.)
- Sites (SharePoint)
- OneDrive
Not a complete backup of office365 in all corners as discussed in this. But i covers the restoring of mailbox, sharepoint, onedrive.
If any find this "Backup Office365 all inclusive tool" i would also like to get notified Thanks.
Hi Nicolai,
I recommend Druva. They backup up all O365 documents, Exchange Online, OneDrive, SharePoint sites, and system/application settings.
If it's still relevant to you, send me a message and I can share more info.
Does Druva support Planner and Teams?
Their white paper about Office 365 backup talks about their advantages and contains some inaccuracies. For instance:
Office 365 doesn’t index all file types, so search results will not be inclusive of all criteria across non-Microsoft file types. [What file types are their worried about? Does Druva index all Office 365 data?]
Due to the lack of eDiscovery workflow, the review process can often be arduous. Search results are copied to an eDiscovery mailbox, which effectively looks and behaves like an online PST. This makes the review process time consuming and reduces accuracy [This is so outdated that I'm surprised that anyone could put this in a document. It's a description of Exchange on-premises eDiscovery and not Office 365 eDiscovery.]
Once I see inaccurate or misleading assertions in company documents, I start to worry about their technical capabilities.
- Hi Tony,
Good points here. Druva supports Teams but not Planner.
In regards to the inconsistencies, Druva updates their product so frequently ambiguous/outdated whitepapers still float around... definitely a DevOps focused company.
Here's the update to the above:
Office 365 legal hold workflows:
"Search results for Exchange Online, SharePoint Online and OneDrive must be exported from Office 365 to facilitate the review process; the Exchange content as one or more PST files, and the SharePoint and OneDrive content as individual files (with an option for all versions). There are multiple problems with the Office 365 approach: it creates a duplicate set of content outside of Office 365 which must be protected, there is no reporting on actions taken on the exported content in the eDiscovery case in Office 365 because Office 365 is blind to post-export actions, if the search is run again in Office 365 then a subsequent export is required along with integration of multiple sets of data, and there is no connection between what was collected and the coding decisions made to that content in order to inform future cases and reduce the volume of potentially responsive content in Office 365. The need to export content to Azure – with the time delays that are introduced from Office 365 to Azure and then Azure to a local computer – creates unhelpful delays in an urgent process for compliance officers. With GDPR in effect, the potential existence of personal data in additional locations will raise significant data governance concerns."
I know that's long winded, but if you want to get more in the weeds, send me a dm.Let's look at some of these points.
First, support of Teams. Is this through the capture of the compliance records found in group and personal mailboxes? If so, that might not be enough for some eDiscovery because these records are copies, not the actual data. For instance, they do not store records of user likes for a conversation (which might show that someone accessed a message).
Second, you're correct that there is no sight of post-search/post-export actions inside Office 365. Most companies have pretty stringent directions for how these searches are performed and the actions taken are recorded there. At least, that's been my experience (and recommendation). This also makes sure that the actions taken in Office 365 are integrated with all the other activities associated with eDiscovery.
Second, in practical terms, I don't think there is much wrong with the temporary (and secure) export of information gathered from across Office 365 workloads to Azure followed by the export/download from that location. It works, it handles different output formats (for instance, Exchange content can be exported to a PST or ZIP file, or as separate message files), and it doesn't take as long as the text seems to say that it does. I doubt that compliance officers will wait too long - and they probably have a lot more to get on with while the export proceeds.
Third, multiple content searches can be combined into one Office 365 eDiscovery case. The idea is that compliance officers can take several different approaches to finding the content they need. At the end of the day, they can combine all the search results that they want into a single export.
Fourth, for people who need to process large quantities of data, the Office 365 Advanced eDiscovery feature is available (E5 or separate add-on). It's really quite good.
Last, the GDPR point is pure unadulterated FUD. Any competent compliance officer will have secured the authority to process personal data according to whatever regulations are in force. I don't like exporting data to PST but it seems to be an industry standard, so we have to do our utmost to protect that data when it is in temporary use for search purposes.
All in all, the description seems to have been written with a certain lack of knowledge about what standard Office 365 functionality can do. Or perhaps that's the intention.
