I do this too. Thankfully the revert to earlier version has got me out of jail a few times.I am realising though that onedrive is a cloud sync rather than a straight backup. So if I corrupt a file on my HDD, onedrive will work to ensure it has synced that corrupt file in the cloud.
I dislike this autosave in office 365 though I have yet to remember to switch it off. Should do that next. So what happens is I have a file called June21.docx and I want to make a july21.docx. The simplest way is to open june and make a few changes then save that as july. But with autosave that would be bad, because it would overwrite june with the first data I have added for july. With autosave I have to immediately create july then savings will be to the right file. I have to overcome years of working in a particular way.
Exactly. Cloud backups are a no brainer for an average user, you just don't have to remember.
When our desktop died I knew I could just wipe it and all my partners important work was backed up and ready to go.
Clearly I'm not an average user, since local backups have served me well enough for just over a decade. If cloud sync isn't a backup, then what the hell is it? All OneDrive has done is annoy the fuck out of me, with its endless whinging about running out of space and splashing ugly little icons everywhere.
Clearly I'm not an average user, since local backups have served me well enough for just over a decade. If cloud sync isn't a backup, then what the hell is it? All OneDrive has done is annoy the fuck out of me, with its endless whinging about running out of space and splashing ugly little icons everywhere.