Warning received: "Error setting time on ...." during file backup

UrBackup is a great product. Thanks for bringing it to the market!

I am running UrBackup 2.0.38.1660 server on Ubuntu 16.04. My root drive is on a single SAS drive and my backup storage is on a ZFS RAID with 3 storage drives and separate log & cache drives. I am backing up multiple Windows 8.1 computers running the 2.0.36 client.

I just started using UrBackup at the beginning of December. Starting with the first file backup, “Error setting time on…” appeared. Here’s an example “Error setting file time of /test_pool//urbackup/WS-01/161210-0002/C/Users/Goofy/AppData/Local/Packages”. It occurs on every backup, but the number of files affected varies. Its been as low as 3 files to a high of over 12,000 files affected.

Here’s an excerpt from last nights log files with debug on where there were only 3 warnings:

2016-12-12 03:30:58: HT: Copying file: “/test_pool//urbackup/WS_01/161212-0329/C/Users/jkunc_000/ntuser.dat.LOG1”
2016-12-12 03:30:58: HT: Copying file: “/test_pool//urbackup/WS_01/161212-0329/C/Users/jkunc_000/ntuser.dat.LOG2”
2016-12-12 03:30:58: Waiting for file transfers…
2016-12-12 03:31:01: Waiting for file hashing and copying threads…
2016-12-12 03:31:01: Server timeout (2) in FileClient
2016-12-12 03:31:01: Reconnected successfully,
2016-12-12 03:31:01: Flushing FileClient…
2016-12-12 03:31:02: Saving file metadata…
2016-12-12 03:31:02: WARNING: Error setting file time of /test_pool//urbackup/WS_01/161212-0329/C/Users/Goofy/AppData/Local/Microsoft/CLR_v4.0/UsageLogs/sdiagnhost.exe.log
2016-12-12 03:31:02: WARNING: Error setting file time of /test_pool//urbackup/WS_01/161212-0329/C/Users/Goofy/AppData/Roaming/Mozilla/Firefox/Profiles/0tapl0l1.default/cert8.db
2016-12-12 03:31:02: WARNING: Error setting file time of /test_pool//urbackup/WS_01/161212-0329/C/Users/Goofy/AppData/Roaming/Mozilla/Firefox/Profiles/0tapl0l1.default/key3.db
2016-12-12 03:31:02: Writing new file list…
2016-12-12 03:31:03: All metadata was present
2016-12-12 03:31:03: Creating symbolic links. -1
2016-12-12 03:31:03: Creating symbolic links. -2
2016-12-12 03:31:03: Symbolic links created.
2016-12-12 03:31:03: Transferred 315.91 MB - Average speed: 117.181 MBit/s
2016-12-12 03:31:03: Script does not exist urbackup/post_incr_filebackup
2016-12-12 03:31:12: Time taken for backing up client WS_01: 1m 20s
2016-12-12 03:31:12: Backup succeeded

Any ideas?

1 Like

You can ignore those warnings. Setting the file time is purely cosmetic.

if it is only cosmetic…
could you suppress this warning?
or is there anything we could do to resolve this warning?

What’s the complete warning you have?

about 5000+ of those:

Warnings 16.07.19 13:04 Error setting file time of /mnt/nas3/urbackup-vm02-storage/LUX1/190716-1302/C/GIT/NavApp2018/.git/index . Permission denied (code: 13)

/mnt/nas3 is a NFS-Mount from a Synology NAS with a Raid5 Volume with EXTFS.

Hi I solved the Problem with the mount option “lookupcache=none” and activate NFS Version 4 on the Synology System.

I found this post [NFS: 'Permission denied' for attributes after file move | Support | SUSE] (NFS: 'Permission denied' for attributes after file move | Support | SUSE) and gave it a try. Now from full file backup and more then 8000 log entries with Error setting file time to full file backup with 0 Error logs.

The post mentioned a small performance penalty with this setting. I haven’t done any performance test.

@uroni: maybe this post helps to solve the problem without this nfs mount option?

Here are an example of the fstab entry:

Synology:/volume1/backup_urbackup /mnt/backup nfs lookupcache=none 0 0