Solved Backup of Office 365 Sharepoint sites
-
We do not. If Sharepoint Online goes down, we wait for Microsoft to resolve. We've had no noticeable (to us, at least) downtime since moving to the service.
-
I am checking if there are any option to have a sync tool of some sort (not sure is ODFB supports this) which will have a synced copy on a local storage, so just in case we have some connectivity issues or some downtime on SP online, we have the data available somewhere.
-
@Ambarishrh said:
I am checking if there are any option to have a sync tool of some sort (not sure is ODFB supports this) which will have a synced copy on a local storage, so just in case we have some connectivity issues or some downtime on SP online, we have the data available somewhere.
ODfB definitely has a sync tool, the entire product was actually built on a sync tool. It's designed primarily around the client, not the server, going offline but is the same to the remote machine in either case.
-
@scottalanmiller I just tried ODFB with our test sp site. I got an option to sync one SP site on ODFB, but wanted to know if we can give a network drive location to save the files for ODFB?
-
@Ambarishrh said:
@scottalanmiller I just tried ODFB with our test sp site. I got an option to sync one SP site on ODFB, but wanted to know if we can give a network drive location to save the files for ODFB?
You want your "local" location of ODfB to be an SMB share?
-
I have not tried that but it would be easy enough to try. Be careful not to let more than one user use that space or you can imagine the weird things that might happen and all kinds of syncs start to happen of the same data.
-
Let's think about @Ambarishrh's goal though. He wants to use ODfB to create a local backup of everything on the O365 SP site on his server, to be used by all of his users in case of a O365 outage.
I don't think creating such a share on the network server would be advisable. The potential for sync issues, corruption, etc would be pretty high.
Also, how do your client devices switch from one to the other?
Under the proposed solution, All of the clients at your locations would have to have the local share connected all the time as to be prepared for a failure. Assuming that your Office installs are pointing logged in/connected to the O365 accounts, still, what keeps your users from working on the local network share instead of working directly with SharePoint?
-
@Dashrender said:
Let's think about @Ambarishrh's goal though. He wants to use ODfB to create a local backup of everything on the O365 SP site on his server, to be used by all of his users in case of a O365 outage.
I don't think creating such a share on the network server would be advisable. The potential for sync issues, corruption, etc would be pretty high.
You are correct, this will not work. It is fundamentally two different types and concepts of storage. Doing this would break all kinds of things like permissions, access controls, versioning, the ability to consistently locate files, etc.
ODfB works offline as it is. Just use it as it is meant to be used.
-
What he really wants to do it sounds like to me, is to create a backup in case Microsoft Whoopsies and deletes their Sharpoint stuff... Did you ever get yours fixed?
-
@scottalanmiller said:
ODfB works offline as it is. Just use it as it is meant to be used.
I.e. each end user will have to have ODfB setup and syncing everything they need offline access to synced directly to their own workstation.
-
@dafyre said:
What he really wants to do it sounds like to me, is to create a backup in case Microsoft Whoopsies and deletes their Sharpoint stuff... Did you ever get yours fixed?
ODfB has you covered for that already, though.
-
@scottalanmiller said:
@dafyre said:
What he really wants to do it sounds like to me, is to create a backup in case Microsoft Whoopsies and deletes their Sharpoint stuff... Did you ever get yours fixed?
ODfB has you covered for that already, though.
If you have ODfB setup.
What is NTG doing to backup their SP site on O365?
-
We let MS handle that. MS takes backups already, same as an internal IT department would. It is "do you feel that you need another vendor of backups too" that is the question there. And the answer is easily yes, but that's what is being asked.
-
@scottalanmiller said:
We let MS handle that. MS takes backups already, same as an internal IT department would. It is "do you feel that you need another vendor of backups too" that is the question there. And the answer is easily yes, but that's what is being asked.
If you want to recover a single file from yesterday, can you do that with MS and hosted SP?
-
@Dashrender said:
If you want to recover a single file from yesterday, can you do that with MS and hosted SP?
While that's an interesting question.... can you think of any scenario where this would be required?
-
@scottalanmiller If somebody accidentally deletes the Sharepoint document they were working on.
-
@scottalanmiller said:
@Dashrender said:
If you want to recover a single file from yesterday, can you do that with MS and hosted SP?
While that's an interesting question.... can you think of any scenario where this would be required?
Uh.. yes. this is the biggest request when it comes to file recovery. "Hey I screwed up my file I've been using for months. Can you restore to the last backed up copy?"
-
@scottalanmiller said:
@Dashrender said:
If you want to recover a single file from yesterday, can you do that with MS and hosted SP?
While that's an interesting question.... can you think of any scenario where this would be required?
100% of the recoveries I've done in the last 4 years have been because someone either deleted a file or saved the wrong data over the top of an old file (forgot to rename).
-
@dafyre said:
@scottalanmiller If somebody accidentally deletes the Sharepoint document they were working on.
That's a function of Sharepoint, though, there is no need to go to backups. That's one of the reasons that you use Sharepoint in the first place or else you have to add that functionality to the filesystem.
-
Sharepoint has built in versioning... this shouldn't be a call to IT users should have access to these versions of files.
