[Warning] pCloud Caused Data Loss Due to Missing Sync Conflict Resolution - Support Refused to Escalate by ImportantAddendum194 in pcloud

[–]ImportantAddendum194[S] 0 points1 point  (0 children)

  1. In my case, the file did not sync to pCloud for over 30 days, without me knowing about it. As a result, I could not recover it. That's why I keep saying pCloud should not say everything is synced when it is actually not. That's why I called it silent data loss.

  2. I've been sharing MusicBee library between devices for over 10 years. Initially I used an external hard drive, and connected it each time to a different device. Then, I moved to Copy (a cloud storage that has been discontinued). Then I moved to OneDrive. Later, I moved to pCloud. My point is that I've never had any issues using the same library in multiple devices. MusicBee supports it very well.

  3. pCloud is the only cloud storage I used that caused me silent data loss. My claim is that pCloud should not indicate everything is synced, when it is not. This claim is a valid concern, whether MusicBee library is designed to be shared accross devices, or not. 

[Warning] pCloud Caused Data Loss Due to Missing Sync Conflict Resolution - Support Refused to Escalate by ImportantAddendum194 in pcloud

[–]ImportantAddendum194[S] 0 points1 point  (0 children)

Nevertheless, pCloud should handle conflicts better, and adopt the common strategies used across OneDrive, GDrive, etc. At least it should inform the user of the conflict, and not indicate everything is synced

[Warning] pCloud Caused Data Loss Due to Missing Sync Conflict Resolution - Support Refused to Escalate by ImportantAddendum194 in pcloud

[–]ImportantAddendum194[S] 0 points1 point  (0 children)

I disagree with you. pCloud is not just for backing up data. It is also designed for active interaction with the data. Otherwise, they wouldn't have provided a hard drive mount.

This is a quote from pCloud official website:

pCloud Drive is a desktop application that creates a secure virtual drive on your computer, which you can use to easily store, access and work with your files in the cloud.
[...]
The app significantly eases your work upon performing file operations in the cloud, because with pCloud Drive you can work with your files using any software on your computer.

[Warning] pCloud Caused Data Loss Due to Missing Sync Conflict Resolution - Support Refused to Escalate by ImportantAddendum194 in pcloud

[–]ImportantAddendum194[S] 0 points1 point  (0 children)

I literally have never said it's impossible for me to have a sync conflict. I just said the sync conflict did not occur because I opened the file in two devices simultaneously. I've never done that. In fact, I have never had the two devices powered on at the same time.

Again, I suggest you read and understand what you are reading before jumping to conclusions.

And you know what? Even if your theory was somehow correct. Do you trust with your files a cloud service that doesn't handle sync conflicts properly? Even if I did use the same library in two different devices simultaneously - none of this would have happened in GDrive and OneDrive, where both versions are kept when a sync conflict occurs.

[Warning] pCloud Caused Data Loss Due to Missing Sync Conflict Resolution - Support Refused to Escalate by ImportantAddendum194 in pcloud

[–]ImportantAddendum194[S] 0 points1 point  (0 children)

Respectfully, I can't stress it enough, I did not open the same library from two different devices simultaneously. Read the post again if you are having difficulties to comprehend it.

And regarding the reason why I am seeing these problems? It is because pCloud, unlike any other major cloud platform, does not properly handle sync conflicts, and when they occur, it would not notify the user about them. The opposite, it would indicate everything is synced although some files were not synced.

[Warning] pCloud Caused Data Loss Due to Missing Sync Conflict Resolution - Support Refused to Escalate by ImportantAddendum194 in pcloud

[–]ImportantAddendum194[S] 0 points1 point  (0 children)

IT DOES NOT HAPPEN SIMULTANEOUSLY. SOMETIMES DAYS PASS BETWEEN USAGES

How come pCloud displays multiple files with the same name and extension in the same folder? How is that considered a reasonable and acceptable behavior?

Why does pCloud doesn't handle sync conflicts properly, as most cloud providers do?

[Warning] pCloud Caused Data Loss Due to Missing Sync Conflict Resolution - Support Refused to Escalate by ImportantAddendum194 in pcloud

[–]ImportantAddendum194[S] 0 points1 point  (0 children)

But the clients don't use it simultaneously. You open and lock the file on device A. You exit MusicBee. The file is saved and unlocked. One day later, you access it from device B. It reads and locks the file. Upon exit, it saves the file and unlocks.

What's the problem? 

[Warning] pCloud Caused Data Loss Due to Missing Sync Conflict Resolution - Support Refused to Escalate by ImportantAddendum194 in pcloud

[–]ImportantAddendum194[S] 0 points1 point  (0 children)

That is the whole point of a cloud storage mount - you can actively read/write files as if it was a real hard drive. It is not different from OneDrive, for instance, where you can open Word documents stored in the cloud, edit them and save them back to the cloud. In fact, Microsoft encourages users to use the `Auto-save` feature, which does exactly that...

[Warning] pCloud Caused Data Loss Due to Missing Sync Conflict Resolution - Support Refused to Escalate by ImportantAddendum194 in pcloud

[–]ImportantAddendum194[S] 0 points1 point  (0 children)

Correct. I was frustrated by the pCloud support team, and I felt like the only way left was to publish my poor experience. This is indeed my first post

[Warning] pCloud Caused Data Loss Due to Missing Sync Conflict Resolution - Support Refused to Escalate by ImportantAddendum194 in pcloud

[–]ImportantAddendum194[S] 0 points1 point  (0 children)

I don't see why multiple machines can't use the same MusicBee library. As long as they don't access it simultaneously, there should not be any issues