07-13-2017 10:51 PM
07-13-2017 11:13 PM
07-13-2017 11:23 PM
I see a lot of references on the internet to the folllwing statement:
"Microsoft takes backups of site collections every 12 hours and keeps these backups for 14 days"
Is there any truth in this ?
07-13-2017 11:24 PM
Like Loryan said you can see the trust center.
I advice to have at least E3 licences and use Preservation Policy - https://support.office.com/en-us/article/Overview-of-preservation-policies-9c3b1d52-40ce-4ba3-a520-9...
07-14-2017 12:56 AM
Don't use preservation policies as they a SharePoint-only option (still existing, still active, but the wrong choice). The long-term solution for retention of information inside Office 365 is in the new data governance framework where you can create retention policies that apply across more than just SharePoint and classification labels that dictate precisely what happens to information when a retention period expires. See https://www.petri.com/office-365-data-governance for more.
07-14-2017 01:37 AM
Yes, I agree with Tony.
Has you can read the Tony article it explains the best way to acomplish your goal and move to a integrated solution.
03-15-2018 02:44 AM
What relevance does a PST-based backup tool have to a discussion about backing up documents from SharePoint and OneDrive? Why would anyone use an insecure, prone to failure file format to backup information in such a way that it instantly breaks any notion of compliance? Unless of course this is a thinly-veiled attempt to sell the product... Which it is... and it doesn't work. PST-based backup products are bad. End of story.
03-26-2018 06:09 AM
Once more to make the same comment...
Why would anyone consider it a a good idea to backup Office 365 data to PSTs? It is a horrible, brain-dead suggestion. All you do is dump data out into an insecure format that is well known for its ability to corrupt information. Does that seem like the right kind of backup strategy?
09-19-2018 06:09 AM - edited 09-20-2018 09:36 PM
I got this link explaining about Office 365 Backup & Recovery Policy. You may also have a look
Hope this will help you!!!
09-19-2018 06:47 AM
Would anyone really take a document purporting to the the ultimate guide to Office 365 backup seriously when the text is so horribly written? https://www.systoolsgroup.com/updates/backup-recovery-policy-office-365/
"Now days, Microsoft Office 365 is the most popular business productivity suite. Around 23 million users are using Office 365 application across the globe. With the help of Office 365 suite, users can work online, share many files or spreadsheets, work from their home or mobile devices. It is the perfect Cloud solution for any business."
The official number for monthly active Office 365 users is 135 million, not "around 23 million." This document is no more than a thinly-disguised attempt to make people believe that they need Office 365 backups. In most case, they don't.
10-29-2018 01:06 PM
I'm curious why you think companies don't need backup for Office 365? Built-in tools handle things like accidentally delete emails and files, but don't handle things like:
- accidentally or maliciously purging recycled/deleted items.
- well meaning admin deleting or purging things they weren't supposed to
- malicious person gaining unauthorized access to an admin account
- massive ransomware attack that encrypts files stored in Office365
The built in tools are not built to handle these situations.
It might be a true statement to say that most companies will not experience these things, but that's also true of traditional IT and disasters. Yet will still have a DR plan, even though the vast majority of companies will never fire their DR plan in anger.
So why do you believe companies don't need to backup Office 365?
10-29-2018 01:23 PM
10-29-2018 02:10 PM
Agreed on the on-premises comments. (Disclaimer: I work for a cloud-to-cloud backup company. But, FWIW, I've specialized in backups for 25 years and always been a fan of cloud-based backup.)
My concern about the built-in Sharepoint backup is that restore is all or nothing, AND it's only the last 14 days. I'm also not sure what the SLA is there (RTOs RPOs). It seems very similar to the built-in Salesforce backup that Salesforce will tell you is an absolute last resort. From a backup perspective restoring your entire environment because a part of it is damaged has never been a good idea.
The Onedrive restore features handles the last 30 days. If the thing you're trying to fix is over 30 days old, you're out of luck.
10-29-2018 02:19 PM
10-29-2018 02:40 PM
"for most people" is the key phrase there. Most people don't get ransomware. (But it happens every day.) Most people don't have a hacker gain access to a privileged account. (But it happens every day.) So most people won't end up really needing something outside what MS give them.
BUT if your company DOES have one of these things happen to them, you're out of luck if you don't have a third-party backup of your O365 data.
That's why I think it's irresponsible to say that you don't third party backup of any computing service.
10-29-2018 02:53 PM
10-29-2018 04:43 PM
IMO it's only overkill if you don't care about your company's data stored in Office365. If a company is prepared to take the risk of losing everything stored there, then sure. They don't need 3rd party backup. Short of that, I can't think of a single use case where it's overkill.
That's my story and I'm sticking to it.
10-30-2018 10:11 AM
In what universe does it make sense to extract email data from a cloud service and save them to a PST?
Apart from needing to do this to provide the results of an eDiscovery search to investigators, I can't see any reason to encourage people to save email to a workstation. All this does is create a horrible security issue like the one experienced by Sony when hackers cracked their network and retrieved sensitive email stored inside PSTs.
PSTs and backup should not be used in the same sentence. They just don't belong together.
11-01-2018 06:48 AM
Does Your Office 365 Tenant Need Backups?
Do you need to backup Office 365 data? The question isn't simple because technology changes all the time and it's hard to backup some applications like Teams and Planner because APIs don't exist. The important thing is for companies to review what data they use, the features available to them, and then figure out if any gaps exist.
07-21-2019 06:55 AM
07-21-2019 06:59 AM - last edited on 06-29-2020 01:51 PM by Eric Starker
The answer is simple; if you want an unlimited retention period, with a point-in-time restore, it cant be done without 3rd party backup.
If you wish to restore in case of an outage on MS Azure (happened recently), or without putting information at risk and not complying with your regional legislation by activating eDiscovery, there is only one solution. 3rd party cloud to cloud backup.
07-21-2019 07:12 AM
@Micha1735 I am amused at how the proponents of backup software always make sweeping statements without taking into account the functionality built into Office 365. If you want unlimited retention, you can apply Office 365 retention policies to SharePoint. This has a consequence for storage https://www.petri.com/how-retention-impacts-office-365-storage but no more than if you engage a third-party backup solution. And if you keep everything online inside Office 365, you have the full suite of data governance functionality available to manage the data. Third party backups have some value, but companies should always understand what's available (and they are paying for) inside Office 365 and how the available functionality can meet business goals before considering deploying a third-party solution that only complicates the overall retention/data governance picture.
07-21-2019 08:57 AM
07-21-2019 09:34 AM
@Dominic Horne I completely agree that retention and backup are different. However, I make the following observations:
Again, I make the point that a third-party backup can be useful but you should fully understand the range of functionality available in Office 365 before you commit to anything that complicates your operational landscape.
07-21-2019 09:52 AM
07-21-2019 10:08 AM
@Dominic Horne Yep. Which has been my entire point all along. Naturally enough, backup vendors aren't keen to recommend that people understand what they pay for (a difficult task sometimes given the rate of development inside Office 365) nor do they like people to understand the difficulty of restoring data from a cloud backup repository. Everything works swimmingly in a demo; things are different when systems fail and data is needed fast.
07-26-2019 07:50 AM
@Michael82 It's wonderful to have a vendor representative hyping their product in a thinly disguised answer to someone's request for help. If CloudAlly was any good, it would even be worthwhile. I've never seen a reputable MVP or other subject matter expert recommend this service. All I hear are claims of its brilliance.... which doesn't say much.
09-11-2019 01:38 AM
@ManojDwivedi Yet another thinly-disguised attempt by a backup vendor to lure people into believing that their software will do wonderful things? In this case, the backup product copies mail to PST files, which is just about the most brain-dead and stupid approach to backup of a cloud email solution known since the dawn of Office 365.
04-15-2020 12:19 PM
05-24-2020 08:16 AM - edited 05-24-2020 08:18 AM
I think backup in this context is more of a legacy to on-premises data. In cloud services it's more integrated into the storage fabric, which is why little is published.
Old style - take full backups and incremental backups off site.
Cloud - distribute multiple copies of data and version histories across multiple data centres. Apply version history policies and data retention policies, giving administrators and staff the ability to go back in time and restore content. Then present back as SLAs.
So the question to ask is not "how to MS backup", but 1) are the SLAs good enough and 2) do i trust MS enough. If no, then there are plenty of cloud backup providers that integrate into O365.
Because there are plenty of O365 cloud backup providers, suggests there are plenty of customers who are nervous about MS SLAs. I would suggest it is best practice to have another copy with another cloud service provider.
Just my thoughts,