The support forum

Several failures

wlie :

Jan 13, 2018

When doing backup I got several hundred failure saying: "NtSetInformationFile() failed with c0000d" and just under the this a text saying:"Context: 7 0"
What does it means?

William

Alex Pankratov :

Jan 13, 2018



Which version are you running?


Scratch that. What this typically means is that the device you are backing up to doesn't correctly implement Windows compatibility interface. What you can do is to tell Bvckup to use slower way to do the same thing that is known to have less problems of this kind.

This is done by creating a file called override.ini in the backup's configuration folder and adding the following line to it:

        conf.copying.general.use_fast_api   0

To find the folder - right-click on the backup entry in main window, select Open Folder > Configuration and Logging. Once you add the file, restart the program to make it pick up the override.

Finally, for my records:

1. Please get me an extract from the log with the error - right-click on the "Copying file ..." line and select "Copy block to clipboard".

2. Let me know what you are backing up to exactly, so that we can try and working around this issue automatically if we can detect a similar setup.

wlie :

Jan 14, 2018

As a precaution I am running release 78.15

I backup to an ekstern drive attach to an USB 3 port. The drive is 1Terra byte FAT32 formatted. Should I format it to NTFS ??
Two jobs are failing. My document folder 77GB and My Picture 27GB.
After I have attach the suggested file to the Configuration and Logging folders the error change.

Here before the change:
2018.01.10 14:58:16.229 (UTC+1) 2 2         6362. Updating file Arduino\libraries\Adafruit_Circuit_Playground\utility\ffft.S
2018.01.10 14:58:16.229 (UTC+1) 3 3             Details
2018.01.10 14:58:16.229 (UTC+1) 3 4                 Source: 9.63 KB, created 2017.12.26 12:39:13.582, modified 1979.11.30 00:00:00.000, archived
2018.01.10 14:58:16.229 (UTC+1) 3 5                     Raw: 9857 / 131587619535827506 / 119572380000000000 / 00000020
2018.01.10 14:58:16.229 (UTC+1) 3 4                 Backup: 9.63 KB, created 0000.00.00 00:00:00.000, modified 0000.00.00 00:00:00.000, archived
2018.01.10 14:58:16.229 (UTC+1) 3 5                     Raw: 9857 / 0 / 0 / 00000020
2018.01.10 14:58:16.463 (UTC+1) 3 3             Copying file details...
2018.01.10 14:58:16.463 (UTC+1) 0 4                 NtSetInformationFile() failed with c000000d
2018.01.10 14:58:16.463 (UTC+1) 3 5                     Context: 7 0
2018.01.10 14:58:16.463 (UTC+1) 3 3             Performance
2018.01.10 14:58:16.463 (UTC+1) 3 4                 0.04 MBps / 41159 bps, 239 ms
2018.01.10 14:58:16.463 (UTC+1) 3 3             Completed in 234 ms, copied in full

And here after the change:
2018.01.14 10:16:57.184 (UTC+1) 3 3             Copying file details...
2018.01.14 10:16:57.184 (UTC+1) 0 4                 SetFileTime() failed with 87
2018.01.14 10:22:15.020 (UTC+1) 3 3             Copying file details...
2018.01.14 10:22:15.020 (UTC+1) 0 4                 NtSetInformationFile() failed with c000000d
2018.01.14 10:22:15.020 (UTC+1) 3 5                     Context: 7 0


Alex Pankratov :

Jan 14, 2018



Yes, formatting it with NTFS will resolve the issue.

The issue itself is caused by the fact that last-modified timestamp on this file (1979-11-30) falls outside of the time range supported by FAT, which starts at 1980-01-01.

Also, see this topic for an alternative solution - https://bvckup2.com/support/forum/topic/982 - though switching the drive to NTFS is a good idea for other reasons (performance and resilience).

wlie :

Jan 15, 2018

Formatting to NTFS did the trick and about 100Gbyte backed up without a single failure.
Thanks for Your support.

William

New topic

Create
Made by Pipemetrics in Switzerland
Support


Follow
Twitter
Blog / RSS
Miscellanea Press resources
Testimonials
On robocopy
Company
Imprint

Legal Terms
Privacy