Incremental File backup errors

When I do an incremental backup, it completes but with the errors below. I was thought it was something with hashes being to big, so I turned the “Local incremental file backup transfer mode” to RAW, and that didn’t change anything. Any ideas? I have posted the errors that are in the “log” area of the web frontend. Let me know if I’m supposed to post anything else.

Errors

05/25/17 13:07
Eattry key 0 for “/files/backup/cron/ur/clients/legacy/170525-1245/.hashes/web/.Trash-1000/files/add.2.a.clipart.1.pdf” too large with size 1.58541 GB in “/files/backup/cron/ur/clients/urbackup_tmp_files/19”
Errors

05/25/17 13:07
Error saving metadata. Could not save OS specific metadata to “/files/backup/cron/ur/clients/legacy/170525-1245/.hashes/web/.Trash-1000/files/add.2.a.clipart.1.pdf”

Bump. Anybody? No ideas?

Currently having this exact same error, also with Mac client. Did you ever figure anything out?

At least you are telling us what OS you are using. Please consult

for more information about error reports.

Sorry, I have one client on OS X 10.7.5 and the other on 10.7.4, server is 2.1.19 on Ubuntu 16.4, pool on ZFS. Both clients are now on 2.1.16, upgraded from 2.0.34. The exact errors I’m getting are:

Errors

13/07/17 13:40
Eattry key 0 for “/sahara/backup/urbackup/Asistente.local/170713-1339/.hashes/.symlink_Socket” too large with size 1.79971 GB in “/sahara/backup/urbackup/urbackup_tmp_files/56”
Errors

13/07/17 13:40
Error saving metadata. Could not save OS specific metadata to “/sahara/backup/urbackup/Asistente.local/170713-1339/.hashes/.symlink_Socket”

And:

Errors

13/07/17 12:43
Eattry key 0 for “/sahara/backup/urbackup/Finanzas/170713-1131/.hashes/.symlink_/Library/Server/Mail/Data/spool/private/anvil” too large with size 1.79971 GB in “/sahara/backup/urbackup/urbackup_tmp_files/40”
Errors

13/07/17 12:43
Error saving metadata. Could not save OS specific metadata to “/sahara/backup/urbackup/Finanzas/170713-1131/.hashes/.symlink_/Library/Server/Mail/Data/spool/private/anvil”

Could you post a complete log, please? This error does not cause the backup to fail in-itself.

I will send the log privately once I am on site, one of the computers is in accounting and I don’t think there is anything sensitive in the log but I’d rather be safe.

I figured out what the error is, it happens (at least for me) when urbackup tries to back up OS X Socket files (A special OS X only file type) or (more frequently) symlinks to them. This could be fixed by having urbackup avoid socket files and symlinks to them, since I don’t think they can be backed up anyhow (Not even the included OS X version of tar can back them up).

Hmm, OP’s file doesn’t look like a socket file. I’ll try to reproduce with that info. Did you have a look at the client log file for errors?

Same here - these are the only error lines in client log:

    Error reading eattr num from "/srv/clientbackup/urbackup/urbackup_tmp_files/8"
    Error saving metadata. Could not save OS specific metadata to "/srv/clientbackup/urbackup/mac-XXXX/170921-1322/.hashes/.symlink_ttys001"

I’ll try by excluding:
/Users/*/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty

This error isn’t every time, so may be only if docker is running …