OneDrive Sync Mechanics
-
@BRRABill said:
I'm not sure in an industry where we preach backups how we can be confident in any of these cloud services. Even if they do "backup" our data. Has anyone actually tested that yet?
Confidence in a specific service (never lump any two services together, that makes no sense and never think of "cloud" as a single thing, each service is unique, just as Super Mario Bros. 3 and MS Office 2013 are not related but both are proprietary, on premises software) has no relationship to preaching backups. We preach backups as a specific thing that is needed. This is no way violates that any more than a user relying on their IT department to run backups violates that rule.
Do you expect your users to all run their own backup mechanisms at work because "would they look foolish if they trusted that IT guy... does he even test his restores... and all their data was lost?"
Remember, you are the end user, they are IT. If you don't trust your provider, okay. But then, why are you using them, really?
-
But data loss happens in more ways than your provider losing data.
Are you not a fan of the 3-2-1 philosophy?
I mean, we have no idea what these services are doing, right? You are contending that by "trusting" them we'll be able to reliably get back data?
-
@BRRABill said:
I mean, we have no idea what these services are doing, right? You are contending that by "trusting" them we'll be able to reliably get back data?
So.... this is how you feel that your customers or users should feel about you or your IT department?
-
@BRRABill said:
But data loss happens in more ways than your provider losing data.
Give an example that isn't covered by versioning.
-
@scottalanmiller said:
Give an example that isn't covered by versioning.
I inadvertently overwrite all this week's soccer pictures with pictures of the same name by mistake.
-
@BRRABill said:
@scottalanmiller said:
Give an example that isn't covered by versioning.
I inadvertently overwrite all this week's soccer pictures with pictures of the same name by mistake.
But versioning would cover that.
-
@scottalanmiller said:
So.... this is how you feel that your customers or users should feel about you or your IT department?
No, but I still have multiple copies of stuff as an IT person for them, because stuff happens.
-
-
@BRRABill said:
@scottalanmiller said:
So.... this is how you feel that your customers or users should feel about you or your IT department?
No, but I still have multiple copies of stuff as an IT person for them, because stuff happens.
So you feel that in your role as a user that you should act differently than you want other users to act? Do as I say, not as I do?
-
@BRRABill said:
@scottalanmiller said:
But versioning would cover that.
Not using OneDrive.
Versioning covers it, plain and simple. What does OneDrive have to do with it?
-
@scottalanmiller said:
Versioning covers it, plain and simple. What does OneDrive have to do with it?
OneDrive only versions Microsoft files.
Granted, there are services that do versioning of ALL files.
-
@BRRABill said:
@scottalanmiller said:
Versioning covers it, plain and simple. What does OneDrive have to do with it?
OneDrive only versions Microsoft files.
Granted, there are services that do versioning of ALL files.
Right, versioning covers it. If you don't version, it doesn't cover it.
-
@scottalanmiller said:
Right, versioning covers it. If you don't version, it doesn't cover it.
How am I supposed to "version it" in OneDrive? If you mean that I should have known and renamed the files appropriately, I agree. But sometimes mistakes happens.
Hence the need for backup.
-
@BRRABill said:
@scottalanmiller said:
Right, versioning covers it. If you don't version, it doesn't cover it.
How am I supposed to "version it" in OneDrive? If you mean that I should have known and renamed the files appropriately, I agree. But sometimes mistakes happens.
Hence the need for backup.
You don't version in OneDrive, in that case, you version locally. Same with normal backups.
If you are using a Wiki, the wiki handles the versioning. Then you take a backup of the whole mechanism. That puts the full versioning into the backup. Now you have versioning and backups. You don't backup just one version, you backup the full data set.
-
I just don't see the argument for not wanting to have another copy of the data in another place.
I acquiesced to your concept of not having data locally. I don't personally like it because I think it makes working on stuff (using older or non-cloud aware apps) harder. (Yes, that is another thing I'll need to acquiesce on.)
But I don't understand why it wouldn't make sense to have another copy of my entire OneDrive file structure in another cloud service, like Amazon Cloud Drive.
-
@BRRABill said:
Hence the need for backup.
You can use a complicated backup mechanism for this, to handle backup versions. But this is overkill and, to some degree, archaic. The backup system doesn't understand your triggers, applications do. Versioning should be done closer to the data and backups be at a high level for the most efficiency and functionality.
Pictures are a difficult one because they are hard to deal with because you don't version them like that. Having a read only system is the best bet, normally.
-
@BRRABill said:
I just don't see the argument for not wanting to have another copy of the data in another place.
Ah, you are getting my point wrong. I never said that at all. I'm saying that you always need a copy in another place. I'm saying that you don't need to be the one that takes that copy.
-
@BRRABill said:
But I don't understand why it wouldn't make sense to have another copy of my entire OneDrive file structure in another cloud service, like Amazon Cloud Drive.
Again, would you tell your users not to trust you? If not, why do you feel that you should act differently than you advice others to act?
-
I am not arguing that what you are saying doesn't make the most sense.
But haven't you ever had something go wrong when it was good to have TWO backups of it?
I'll give you two examples.
Back in the day of tapes, I once had a backup job running that was looking for a tape. It had jumped a day, and long story short I put a tape in to do a restore, and the data got wiped out. Since then, I used the write tab every time I did a restore. Did I NEED to do that? No, but since I had been burned, it made for one more level of protection.
Also, back when iPhones were backed up to the machine, I had many instances where it would do an update, then backup the bad data. After getting burned a few times, I learned to do a backup of the iPhone, then do a backup of that backup. Overkill, perhaps. But I got burned enough times for it to make sense.
I am sure we've all been burned at one time or another by our friendly computers. Having a backup of the backup I think makes absolute sense.
-
@scottalanmiller said:
Ah, you are getting my point wrong. I never said that at all. I'm saying that you always need a copy in another place. I'm saying that you don't need to be the one that takes that copy.
I just do not believe that OneDrive (or even Amazon Cloud Drive, for that matter) would take your support call and pull something off a backup for you.
I could be entirely wring, in which case I will take a very small picture of my screen and pretend to eat it.
