The support forum

Error: SetFileTime() failed with 87

theedge :

Jul 11, 2015

Hello,

First of all, thank you for this great product ! I very recently started testing bvckup and finished the backup of about 1.3 TB of data.
But there are twelve files that keep showing this error : "SetFileTime() failed with 87" on every backup.
How could I fix this ?

Alex Pankratov :

Jul 11, 2015


This means that these files have timestamps too far in the past so that they are unsupported by the file system on destination device. For example, any date before 01-01-1980 will be rejected by FAT or ExFAT.

This should be easy to check if you expand the backup log entry for the file and look at the Timestamps section.

The simplest thing to do here is to reset file timestamps to something more recent. You can do it with PowerShell using the following command:

   ( Get-item Path\To\YourFile.Ext ).LastWriteTime = (Get-Date)

or

   ( Get-item Path\To\YourFile.Ext ).CreationTime = (Get-Date)

whereby "Path\To\YourFile.Ext" is what you think it is. If PowerShell sounds alien to you, let me know and I'll explain how to reset the timestamps differently.

PS. Thanks for the compliment, great to hear it! :)

theedge :

Jul 12, 2015

Excellent. Didn't know about PowerShell, but it was easy following your instructions. The culprit files are now fixed and the backup ends with no errors.
Thank you !

MPE :

Aug 01, 2015

Hello, I am experiencing the same issue.
178 errors returned with "SetFileTime() failed with 87".
I am not familiar with PowerShell. Is there an alternate fix?

Thanks

Example from the log:
2015.08.01 17:35:19.580 (UTC-5) 2 2         627. Copying file Documents\Garmin download error 11-30-14.xlsx
2015.08.01 17:35:19.580 (UTC-5) 3 3             Details
2015.08.01 17:35:19.580 (UTC-5) 3 4                 Source: created  1969.12.31  20:00:00.000 , modified  2014.11.30  15:53:08.000
2015.08.01 17:35:19.580 (UTC-5) 3 5                     116444736000000000 and 130618507880000000 respectively
2015.08.01 17:35:19.580 (UTC-5) 3 4                 Size: 156.31 KB
2015.08.01 17:35:19.580 (UTC-5) 3 5                     Exactly 160062 bytes
2015.08.01 17:35:19.674 (UTC-5) 0 3             SetFileTime() failed with 87
2015.08.01 17:35:19.689 (UTC-5) 3 3             Performance
2015.08.01 17:35:19.689 (UTC-5) 3 4                 1.49 MBps / 1563961 bps
2015.08.01 17:35:19.689 (UTC-5) 3 4                 Content - 102 ms, extras - 6.96 ms
2015.08.01 17:35:19.689 (UTC-5) 3 5                     Raw metrics - 22491 / 11 / 6237 / 10 / 262144 / 262144 / 4 / 58440 / 127 / 7125 / 4226 / 2 / 0 / 0
2015.08.01 17:35:19.689 (UTC-5) 3 3             Completed in 109 ms, copied in full

Alex Pankratov :

Aug 01, 2015

Another option is to copy affected files into another location and then copy them back (not move, copy). This sets "created" timestamp on files to current time. For 178 files though ... not sure how feasible that would be.

bestik :

Mar 01, 2017

Hello, I got the same problem. I've been using SSHFS (mounting disk over SSH via WinSshFs) that doesn't support created timestamps:
Source
Type : NTFS
Created timestamps : supported
Destination
Type : SSHFS
Created timestamps : NOT supported

Every file is included every time in the copying and ending with the error SetFileTime() failed with 87

    Source: 269.34 KB, created  2013.03.06 10:17:30.861, modified  2014.01.11 13:24:21.529, archived
        Raw: 275809 / 130070350508618024 / 130339166615295685 / 00000020
    Backup: 269.34 KB, created  2013.03.06 10:17:30.000, modified  2013.03.06 10:17:30.000, archived / normal not-indexed
        Raw: 275809 / 130070350500000000 / 130070350500000000 / 000020a0
Copying timestamps...
    SetFileTime() failed with 87

Any idea how to avoid this? Thanks.

Alex Pankratov :

Mar 01, 2017



You can suppress copying of 'created' timestamps.
See this topic for details - https://bvckup2.com/support/forum/topic/139

PS. Though I suspect the error is not due to that as "created" timestamps aren't copied if they are not supported by either side.

New topic

Create
Made by Pipemetrics in Switzerland
Support


Follow
Twitter
Dev blog
Miscellanea Press resources
Testimonials
On robocopy
Company
Imprint

Legal Terms
Privacy