I am preplexed… I can’t tell is this failure is from the local PC file system or on the remote storage server end. Details below. Thanks in advance for any thoughts!
Duplicati.Library.Interface.RemoteListVerificationException: Found 404 files that are missing from the remote storage, please run repair
at Duplicati.Library.Main.Operation.FilelistProcessor.VerifyRemoteList(BackendManager backend, Options options, LocalDatabase database, IBackendWriter log, IEnumerable`1 protectedFiles)
at Duplicati.Library.Main.Operation.BackupHandler.PreBackupVerify(BackendManager backend, String protectedfile)
at Duplicati.Library.Main.Operation.BackupHandler.<RunAsync>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at CoCoL.ChannelExtensions.WaitForTaskOrThrow(Task task)
at Duplicati.Library.Main.Controller.<>c__DisplayClass14_0.<Backup>b__0(BackupResults result)
at Duplicati.Library.Main.Controller.RunAction[T](T result, String[]& paths, IFilter& filter, Action`1 method)
at Duplicati.Library.Main.Controller.Backup(String[] inputsources, IFilter filter)
at Duplicati.Server.Runner.Run(IRunnerData data, Boolean fromQueue)
There is too little information provided to attempt much further guessing at this. Some questions:
What was the history of the backup before original post? Was it a longtime backup that suddenly gave the reported error? Was it on a schedule? Was it new? How large is it (see home screen)?
Were there any known unusual actions seen or done in the backup before the issue appeared? Stack trace says PreBackupVerify, but there is also the same verification at each backup end.
There is a lot of information in the job logs (especially if you are on current 2.0.8.1 Beta or later). Missing file names are logged there, although the list is truncated. You could still post a sample, however the names are clues. Source data typically is in dblock files. Each dblock has a dindex.
Repair with an intact database can upload missing dindex and dlist files, but source data is hard.
The Complete log gives “KnownFileCount”. This is another way to see if 404 files is everything. Alternatively, maybe part of the destination is not being listed. You can check your actual names, taken from the job log. Is a file that is seen missing really on the destination? If so, it’s a list error.
What is the destination storage type, and is it easy to get a listing sorted chronologically? Backup that completes normally would upload the above-mentioned dblock and dindex files, then at end there is a dlist file uploaded that says what was backed up. Any early ending would not have that.
Are you sure you didn’t post the results from a second backup, since
would have a hard time happening on the very first backup ever done.
It’s comparing database from a backup against files at the destination.
Some files that the prior backup uploaded were not actually seen now.
If Destination silently lost files during initial backup, PostBackupVerify
(Verifying backend data … on status bar) would have noticed that.
Next backup run would have quickly noticed in the PreBackupVerify.
I’m glad it worked, but on that point I’d note that deleting the Destination
without deleting the database could also lead to a surprised backup that
is wondering where files in its database went to. Still too little data given.
Now, with the new backup, the system hangs at the following message. To test, I paused and resumed it but no change. Just sits there. Does this code assume that once logged into the remote storage server, the connection will stay open forever? If so, that may be a problem.
Netware Backup JEM Folders :
Waiting for upload to finish …
Log text (Yes, that is all there is!)
Jun 19, 2024 11:38 PM: put duplicati-b55cf8d028bf24c93aeac0895b35d7917.dblock.zip.aes
Storage Providers describes the available choices. What did you put on Destination screen?
EDIT:
Maybe because you began logging late. Did backup do successful uploads for awhile before? Live log (if that is what this is) should be set up in advance, though it seems to go back a little.
What is shown depends on the chosen level too. What level is this? Does system seem busy?
Sometimes database operations at end of backup (visible at Profiling level) can run for awhile.
Generally this also shows up in CPU and drive usage, for example in Windows Task Manager.
This is way way off. The default is 50 MB. Please read the description linked on the Options screen. You might be trying to put the entire backup in one file, which might be why the upload takes awhile.
EDIT:
OS monitors such as Task Manager can show upload rate, though other things might be sending.
What is Duplicati status bar showing? That has a lot of upload stats, and not-very-human-friendly details are at About → System info where you can see if any of the progress counters are moving.
I checked the profiling log and got this: Jun 21, 2024 5:16 PM: Cannot open WMI provider \localhost\root\virtualization\v2. Hyper-V is probably not installed.
I verified that the backup was on the remote server. It looks like return status is not getting back to duplicati…
This program is still hung waiting for the upload to finish!
That’s just an Information level message (I’m not sure how helpful) when you start editing a job.
Not changing in size but about the full size of Source, given your way too large remote volume?
Just seeing a bit of a file means little. You could download it and decrypt it, e.g. with AES Crypt.
or if you prefer command line with already installed Duplicati software tool, SharpAESCrypt.exe
Better is to see About → System info as requested in edit above. If lastPgEvent is there, post it.
Are you going through a router? This matters because of the below behavior of the FTP backend:
--ftp-passive (Boolean): Toggles the FTP connections method
If this flag is set, the FTP connection is made in passive mode, which
works better with some firewalls. If the "ftp-regular" flag is also set,
this flag is ignored
* default value: false
which means that the router must translate the FTP control connection, and sometimes it drops it because the connection has been open too long. This could prevent return of a completion code.
If you see a huge file on destination now, I suggest you change the remote volume size to default or maybe something somewhat higher depending on how fast your network and FTP can transfer.
I can’t think of any reason why a Task Manager or similar process kill wouldn’t work instead of that. Duplicati is a little confusing currently (design is being changed), as processes often come in pairs.
I ran a new backup with a couple of directories and got this error message. Can you tell me how you are handing extended file open error messages? These files are coming off a mapped network drive that is using the OES Netware Client . It looks like your driver on your side is getting unexpected status from the file call. Is this something you can check please? My guess is that these files are being decompressed on the fly and the driver is saying you have to wait to get it…and your drive is failing. Our network driver is Client for Open Enterprise Server 2 SP7 (IR3). THANKS!
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileBlockProcessor.FileEntry-PathProcessingFailed]: Failed to process path: Q:\JEM\Special Issue Mental Health in EM\dreamstime_xxl_197002960-Modified.psd IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileBlockProcessor.FileEntry-PathProcessingFailed]: Failed to process path: Q:\JEM\Special Issue Mental Health in EM\dreamstime_xxl_197002960-Modified1024.png IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.MetadataPreProcess.FileEntry-TimestampReadFailed]: Failed to read timestamp on “Q:\JEM\Special Issue Mental Health in EM\dreamstime_xxl_197002960-Modified_2000x1333.jpg” IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\dreamstime_xxl_197002960-Modified_2000x1333.png IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\dreamstime_xxl_197002960.jpg IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\Ejaz.zip IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\Issue Paper - Maximizing Horizontal Integration 10.7.19.docx IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover 2021 edition.indd IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover 2021 edition.pdf IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover 2021 edition_150dpi.png IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover 2021 edition_300dpi.png IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover 2022 edition.indd IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover 2022 edition.pdf IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover 2022 edition_150dpi.png IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover 2022 edition_300dpi.png IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover.indd IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover.pdf IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover_150dpi.jpg IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover_150dpi.png IOException: The request is not supported.
2024-06-24 18:31:55 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: Q:\JEM\Special Issue Mental Health in EM\JEM COVID-19 Mental Health Special Cover_300dpi.png IOException: The request is not supported.
That’s nothing that I have, but if it’s supported, I wonder if they can advise on the problem?
Historically, it looks like Netware was Micro Focus awhile, but now is technically OpenText.
I have no idea how much Netware has evolved, but not supporting things seems plausible.
Figuring out exactly what might require you to run Sysinternals Process Monitor to observe.
If everything on Q: drive is getting a Warning (I have no idea – do you?), it should be quick.
There is no driver, but if you mean your network driver is causing an error status, seems so.
There’s no decompressing by Duplicati going on. This is just enumerating available files.
I suppose you could see if you can get a better stack trace. You said you have no advanced options, so I probably don’t have to worry about VSS snapshots, and therefore an error like:
2024-06-25 21:34:02 -04 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: C:\backup source\no_administrators\ UnauthorizedAccessException: Access to the path ‘\?\C:\backup source\no_administrators’ is denied.
should make something like this in About → Show log → Live → Warning
Jun 25, 2024 9:34 PM: Error reported while accessing file: C:\backup source\no_administrators
{“ClassName”:“System.UnauthorizedAccessException”,“Message”:“Access to the path ‘\\?\C:\backup source\no_administrators’ is denied.”,“Data”:null,“InnerException”:null,“HelpURL”:null,“StackTraceString”:" at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)\r\n at System.IO.FileSystemEnumerableIterator1.CommonInit()\r\n at System.IO.FileSystemEnumerableIterator1…ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)\r\n at System.IO.Directory.GetDirectories(String path)\r\n at Duplicati.Library.Snapshots.NoSnapshotWindows.ListFolders(String localFolderPath)\r\n at Duplicati.Library.Utility.Utility.d__23.MoveNext()",“RemoteStackTraceString”:null,“RemoteStackIndex”:0,“ExceptionMethod”:“8\nWinIOError\nmscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089\nSystem.IO.__Error\nVoid WinIOError(Int32, System.String)”,“HResult”:-2147024891,“Source”:“mscorlib”,“WatsonBuckets”:null}
Your error was different (and in its entirety has never been reported, but Netware may be rare).
Your stack trace will possibly be different. Another way to grab these (and less run together) is:
log-file=<path> will make a file of the Warning and Error messages. It might still not be enough because one would like to find at least the relevant source line – or the Process Monitor failure
