Creating OneDrive Backup Task always fails. timeout?

Hi everyone,
I hope I can find some smart help with a problem I have…:

Creating a OneDrive Backup task always fails (OneDrive → local file store).

I have a OneDrive Account that holds ~400GB,
in addition it has linked in a folder shared from another OneDrive Account holding another 500GB so the total backup volume is about 880GB.

It takes about 1h to “calculate” the OneDrive source and when it is finished and I press “start” to save the backup task then it always reports the error as in screenshot.

Steps to Reproduce

  1. Create Backup task → select OneDrive account and local target
  2. It “calculates”
  3. It shows the task ready to be started
  4. klick “Start”
  5. Error message appears.

Note:
There are no extra large files in the OneDrive, it’s just a lot of stuff, but no individual file exceeds “a few 100 MB”. Also there’s no folder with a really high number of files and also the length of total URL should be fine as far as I can see.

Possible root causes for the error IMHO

  • the backup is simply to large and Zima has some sort of general size-limit for backups.
  • some timeout due to long time to “calculate” the backup?
  • the “shared folder” that is incorporated from the other account breaks it somehow.
  • ZimaOS is installed on a dedicated SSD (only for the OS, not used for storage) with 512 GB. Of these almost all is free, but it’s still less than the volume of the backup. Maybe it needs more space on the system drive to cache the download? (no individual file is larger than ~300MB)

System Details
Small PC, 2x SSD (512GB for ZimaOS, 4TB for storage)
OS is running from the SSD, NOT FROM A USB STICK!!
ZimaOS v1.5.3

Is there any way I can dig in deeper (check logs etc)?
Anyone who has a helpful suggestion?
Thanks so much!

I would be really grateful for any insight or help with this.
Thanks,
Jan

That said…
Basically the main purpose of this Zima Box for me is to have a backup of 2x OneDrive accounts and allow me to work on files locally (faster).
These two accounts have shared folders linked into each other.
Is there any option to configre backups to NOT include the content of any “folder shared from external”, since right now it will create backups in each account, meaning i’ll have ~500GB twice.

Add images

Could you try refreshing the page? We had a bug where creating a backup would show as failing, even though it was actually successful.

1 Like

Interesting!
I always aborted then.

Yes indeed it does create a job.
Then it gradually “finds” content on the source
…while at the same time already downloading.

See here:

Cool that could just be it.
Let me watch it over the day, this will probably take quite a while :slight_smile:

Thanks!!

Funny thing is… it really seems constrained more by whatever it needs to do to identify the data in the cloud rather that by downloading it…:slight_smile:

Well, this is going to be a week.
I’ll report back then :slight_smile:

I had a similar issue with my Qnap NAS and OneDrive and Dropbox back up, or sync. ended up being the folder or share name, and it was not the share name it was just a / instead of a share name on remote.

1 Like

We will fix it in 1.5.4, and the beta version is expected to be released today. You can test it out.

1 Like

Thanks for fixing the bug…
…but with the workaround to just ignore the error, it is actually working right now.

“working-ish”, so to speak:
It’s been syncing for ~30h now and over my 600MBit line I have so far received ~200GB of…
~400GB on the OneDrive itself
~400 GB in a shared folder that is linked into the account from a different account.

…of course that might be more due to OneDrive speed or my local hardware speed rather than due to software.

I do however have one suggestion:
This is awefully confusing here:
Look at the numbers:

Why does it have TWO different numbers of “how much is already downloaded”?
I mean, the upper number doeds NOT reflect the real amount of data in that OneDrive, that number is ~400GB.
It is counting up slowly, since 30h.
So is THIS the “amount alreeady downloaded”? Or the second line?
Which of both is the “real” data and why are there two different?

And why does the lower number very often jump to “0” just to jump back up a minute later?

I haven’t done anything to alter files on the cloud side since yesterday but I am really curious if this holds up in daily use (file changes on both sides being synced properly) or if it’s just too slow and causes forks and problems.

But anyway, thanks for your help!
I’ll update to the latest beta once this download is complete in maybe a couple days, don’t want to break it.

No more movement since more than 24 hours.

Again: This OneDrive Account holds 400GB plus another 400 linked into it from a shared other account.

The backup process took 1.5 days to read and download ~200GB, then it just stopped.
Are there any logs I can check to see what’s going on?

I fear that if I reboot that it will start from scratch and never finish -
@777-Spider - Did you guys fix more than just the “wrong error message” in the latest release => is there hope starting from scratch might be worth it or is this just not going to work?

This is exactly the same behaviour I have seen in unRAID (which is why I dumped it) and I feel: what good is a backup system if I can’t even trust it to get the initial full download right?

Any suggestions on what I might be doing wrong?

  1. Regarding the 400GB size you mentioned, may I ask whether it refers to the storage space occupied by the file system or the actual total content size of all files? These two may differ in certain situations (such as when duplicate data, compression, or sparse files are involved).
    please provide screenshot.
  2. It should be noted that, to ensure backup efficiency and compatibility, ZimaOS’s current design skips backing up certain specific types of files and objects, such as:
  • Temporary files (typically ending with .tmp, etc.)

  • Hidden files generated by the system or applications (usually starting with . or $)

  • Symbolic links (soft links) themselves

These items are not included in the total estimation or actual transmission of the backup task.

  1. We have observed that some third-party cloud storage mounts may exhibit instability during prolonged, high-volume data transfers, which can sometimes cause delays or temporary stagnation in the progress display. This may be one of the reasons why you are experiencing prolonged inactivity in the progress.

Hi,

Thanks for your response!

Regarding the 400GB size you mentioned, may I ask whether it refers to the storage space occupied by the file system or the actual total content size of all files?

Again: the backup should actually have not 400GB but 800GB because there are “shared with me” folders included.

This is the size of my OneDrive Account itself:

On Zima what has arrived is 226GB.
This has not changed any more since 1.5 days. It doesn’t upload any more.

In fact what has arrived is a mix of both: the source OneDrive AND ALSO some of the “shared with me”.

I narrowed it down:
See this screenshot of the root directory of the backup target folder on ZimaOS:

All the GREEN folders have been completely backed up including everything.
The one to the very left, 2nd line (“Camera Roll K…”) has been backed up ~half, about half the content is there (see below). This is actually a “shared with me” from a different OneDrive Account.
After that ALL, EVERY SINGLE of the RED marked folders is completely empty. No documents, photos, mp3, all kinds of files, all completely and entirely missing.

“Cameras Roll K..”-folder with SOME content missing:
Source (“shared with me” in OneDrive)

Received on ZimaOS:

  1. We have observed that some third-party cloud storage mounts may exhibit instability during prolonged, high-volume data transfers, which can sometimes cause delays or temporary stagnation in the progress display. This may be one of the reasons why you are experiencing prolonged inactivity in the progress.

Is the OneDrive-plugin “3rd party”?
Is there a log file that might help finding out what’s wrong?
Right now I would say it’s not reliable.

  1. Could you please provide information about all the folders in your cloud drive? Specifically, are there any folders that you created yourself with names identical to those shared with you by others?
    Like this:

  2. To clarify again, does the backup include hidden files?

  3. Please provide a screenshot of the cloud drive size information in the “Files” section.

  4. Try manually starting the backup to check if it resumes. If it does not, upload a new file to your OneDrive cloud drive (do not upload it via ZimaOS “Files”) and then click “Start” again.

  5. We have plans to implement a series of performance optimizations for third-party cloud drives. Please allow us some time to address these improvements.

  6. Considering the sensitivity of the information in your screenshots, I suggest we continue our communication via email at dingwen@icewhale.org.