Forum Discussion
The standard backup/restore options aren't enough for SPO
Recently, a client contacted me to ask for help with a workflow that they'd been using, quite successfully, to manage a very important business process on SP Online. The workflow gathered evaluation ...
A Developer could easily create a backup process that export all the Tasks to another list...this process could run on a schedule and simply copy tasks as soon as the 60 day notice is being reached
We're helping the client with this, actually. As said, there are several ways this cat can be skinned, either by copying to another list or, in our case, copying the task data to an Azure database to avoid list view threshold issues and keep the data more firmly under the client's control.
But the point is that the damage has already been done, and Microsoft's backup policy does not help recover the data at all. There are gaps in MS's backup approach that would not usually be a problem on-prem. It's a downside to going online that I think people need to be more generally aware of and plan for when migrating.