OneDrive for Business Critical error!
-
@Dashrender Local drive has 113 GB free.
-
Try renaming one of those files without the dot in the front. I bet that it syncs.
-
@scottalanmiller said:
Try renaming one of those files without the dot in the front. I bet that it syncs.
Agreed.
-
Very inconvenient to rename xyz.jason files or .htaccess files, especially since they are backup website files.
I am now zipping all the website backups, again inconvenient, I have had 1 to 1 backups since 2003 without issues with other backup programs.
-
@technobabble said:
I have had 1 to 1 backups since 2003 without issues with other backup programs.
OneDrive for Business is not a backup program.
-
Yeah, I know I saw that I wrote that after I hit submit.
However the ability to have my data in ODfB for my clients websites means that I can do a restore from anywhere.
-
I think that there are probably better ways to get similar results. A sync system for backup works pretty poorly. Why not just SFTP? Or RSYNC? Or even SVN or GIT?
If you are automating ODFB, though, you could automate the zipping.
-
@JaredBusch said:
OneDrive for Business is not a backup program.
Why not? I'm interested in this because I'm planning on using it for a backup program at home.
-
@Carnival-Boy said:
@JaredBusch said:
OneDrive for Business is not a backup program.
Why not? I'm interested in this because I'm planning on using it for a backup program at home.
Backup means a decoupling. ODFB is coupled to the source. If you build your own decoupling mechanism (see below) you can use it as storage for your own backup mechanism, but it is just synced storage intended for another purpose.
-
..that and the fact that it seems a bit crap and unreliable.
-
If you attach ODFB to the filesystem you want to back up, it is coupled and not a backup (deletion or corruption of the source destroys the replicant automatically.)
So to use as a backup component you need to decouple the original file from the replicant location. You can do this with a script easily enough. Take an hourly zip of a directory and copy it to the replicant folder for example.
To make this better, make it make copies with the date in the name so that you have multiple restore copies at different times. If you don't do that, you'll accidentally recompile the naturally decoupled piece.
In this scenario, though, your script is the backup system and ODFB is just online storage. You could do the same thing with Rackspace CloudFiles
-
@Carnival-Boy said:
..that and the fact that it seems a bit crap and unreliable.
Seems unreliable when attempted to be used outside of its use case, yes. Does that make it crap?
-
@scottalanmiller said:
So to use as a backup component you need to decouple the original file from the replicant location.
Does ODFB not store previous copies, so if you corrupt the source, you can just restore from an earlier version?
-
or to put it another way, if ODFB is not a backup, how do Office 365 users backup their data?
-
@Carnival-Boy said:
or to put it another way, if ODFB is not a backup, how do Office 365 users backup their data?
O365 is a big licensing thing. Every component of O365 is completely unique vis-a-vis backups. Typically ODFB isn't primary storage so backups are done traditionally.
-
@Carnival-Boy said:
@scottalanmiller said:
So to use as a backup component you need to decouple the original file from the replicant location.
Does ODFB not store previous copies, so if you corrupt the source, you can just restore from an earlier version?
I've actually never tried. I don't believe that it stores versions like Sharepoint does but will need to look. Maybe it does.
-
Yes it does offer that. You have to manually turn on versioning or else it only keeps the last edit. But the option is there.
-
@scottalanmiller said:
Typically ODFB isn't primary storage so backups are done traditionally.
I may be missing something here. Surely it's intention *is *to be primary storage? Otherwise, what's the point of it exactly?
-
@Carnival-Boy said:
I may be missing something here. Surely it's intention *is *to be primary storage? Otherwise, what's the point of it exactly?
The primary storage is the local HDD. ODfB is secondary storage.
-
Bad marketing I reckon, then. If it's not primary, they should call it TwoDrive or SecondDrive.
So instead of:
"OneDrive - One place for all your work files" its "TwoDrive - a secondary place for all your work files"I thought the local HDD was basically a local cache - used solely for performance and offline access, like an OST file is used for Exchange.
Also, regarding my original question: if ODFB isn't a backup, how do you backup your primary storage (the local HDD)? Backing up local hard drives isn't an option in a corporate environment. And if you're still running traditional file servers and syncing those to ODFB, my other question stands - what's the point of ODFB?
