But also because I was not expecting Duplicati to actually set access times - that it was the filesystem/os that does that implicitely. Partly to make it work on existing backups with broken/missing access times. You tested the code change? It will not prevent broken access times, but I hoped it would accept them and not throw exception.
#Win32 api gettimestamp as file time manual
I ran a manual backup after testing the above and it's still creating files with broken access timestamps. I have other backup jobs to this same backend that is running with issue. System.ArgumentOutOfRangeException: Not a valid Win32 FileTime. End of stack trace from previous location where exception was thrown -Īt .Throw()Īt (Task task)Īt .c_Displa圜lass14_0.b_0(BackupResults result)Īt .RunAction(T result, String& paths, IFilter& filter, Action`1 method) Details: System.ArgumentOutOfRangeException: Not a valid Win32 FileTime.Īt .List()Īt .FilelistProcessor.RemoteListAnalysis(BackendManager backend, Options options, LocalDatabase database, IBackendWriter log, IEnumerable`1 protectedFiles)Īt .FilelistProcessor.VerifyRemoteList(BackendManager backend, Options options, LocalDatabase database, IBackendWriter log, IEnumerable`1 protectedFiles)Īt .BackupHandler.PostBackupVerification(String currentFilelistVolume)Īt .BackupHandler.d_20.MoveNext()
0 kommentar(er)
