That’s the procedure I was following, however the beta version was painfully slow at recreating the database. The latest canary version seems to be at least 4x faster, however will still take 5 days at this rate. I’ts using about 20% CPU, 7.5 GB of RAM, and reading from local disk. It’s not bottlenecked by anything that I can see.
Currently using the main GUI.
I think there may be a bug, where my original backup method was via a linux docker container. So when I do a Commandline --list, the folder hierarchy has the format of /folder1/folder2/folder3. Even when I try and do a full restore of that into a windows folder, it fails saying it can’t parse the folder structure.
I tried something like this, according to the documentation after the backup location you can enter a specific file to recover.
C:\Program Files\Duplicati 2>Duplicati.CommandLine.RecoveryTool.exe restore \\TOWER\Media\backups\microsoftbackup "/backups/192.168.2.2_seagate_backup_plus_drive/file1" --targetpath="C:\Users\name\Desktop\myrcovery\"
Program crashed:
System.Exception: Failed to parse the segment: /backup, invalid integer
at Duplicati.Library.Utility.Timeparser.ParseTimeInterval(String datestring, DateTime offset, Boolean negate)
at Duplicati.CommandLine.RecoveryTool.List.SelectListFile(String time, String folder)
at Duplicati.CommandLine.RecoveryTool.Restore.Run(List1 args, Dictionary2 options, IFilter filter)
at Duplicati.CommandLine.RecoveryTool.Program.RealMain(String _args)
I’ve been trying various ways of restoring this. Canary build via GUI is the only one that seems to be working, although still recreating the partial database… I"ll make sure to capture any errors in case it doesn’t make it to 100%… in 4 days.