Migrating Backup (problem with "PoC" & How to do it properly)

Google Drive Destination (ignore the wrong subtitle saying it’s Dropbox) says:

googledrive://<folder>/<subfolder>?authid=<authid>

Yours looks similar to my reading, except you somehow wrote ggoogledrive.

Fixing that should remove Backend not supported. error.

Your second link is to https://duplicati.commandline.backendtool.xn--exe-jga/ somehow. The first is generic info. It’s a tool. It can be used in many ways. Aside from not telling you what to do in this very new use, is there any problem?

One of my own complaints (which I have to make up for in directions) is where to obtain the URL. I usually suggest GUI Export As Command-line. The full path of the command is also not always obvious, and assumes some knowledge of the installation folder. It might also vary depending on what was installed, e.g. 32 bit Windows programs use a different (x86) folder.

Those are your backup files and are portable to other storage. Move all of the files.

With three, you can do them by hand. You probably have one ready after a typo fix.

Assuming you don’t want to try to script something, there’s a new tool to try, but it’s only in Canary (test release) so far. I have it here from a .zip install, on the side…

C:\Duplicati\duplicati-2.1.0.111_canary_2025-03-15-win-x64-gui>Duplicati.CommandLine.SyncTool --help
Description:
  Remote Synchronization Tool

  This tool synchronizes two remote backends. The tool assumes that the intent is
  to have the destination match the source.

  If the destination has files that are not in the source, they will be deleted
  (or renamed if the retention option is set).

  If the destination has files that are also present in the source, but the files
  differ in size, or if the source files have a newer (more recent) timestamp,
  the destination files will be overwritten by the source files. Given that some
  backends do not allow for metadata or timestamp modification, and that the tool
  is run after backup, the destination files should always have a timestamp that
  is newer (or the same if run promptly) compared to the source files.

  If the force option is set, the destination will be overwritten by the source,
  regardless of the state of the files. It will also skip the initial comparison,
  and delete (or rename) all files in the destination.

  If the verify option is set, the files will be downloaded and compared after
  uploading to ensure that the files are correct. Files that already exist in the
  destination will be verified before being overwritten (if they seemingly match).


Usage:
  Duplicati.CommandLine.SyncTool <backend_src> <backend_dst> [options]

Arguments:
  <backend_src>  The source backend string
  <backend_dst>  The destination backend string

Options:
  -y, --confirm, --yes               Automatically confirm the operation [default: False]
  -d, --dry-run                      Do not actually write or delete files. If not set here, the global options will be checked [default: False]
  --dst-options <dst-options>        Options for the destination backend. Each option is a key-value pair separated by an equals sign, e.g. --dst-options key1=value1 key2=value2 [default: empty] []
  -f, --force                        Force the synchronization [default: False]
  --global-options <global-options>  Global options all backends. May be overridden by backend specific options (src-options, dst-options). Each option is a key-value pair separated by an equals sign, e.g.
                                     --global-options key1=value1 key2=value2 [default: empty] []
  --log-file <log-file>              The log file to write to. If not set here, global options will be checked [default: ""] []
  --log-level <log-level>            The log level to use. If not set here, global options will be checked [default: Information]
  --parse-arguments-only             Only parse the arguments and then exit [default: False]
  --progress                         Print progress to STDOUT [default: False]
  --retention                        Toggles whether to keep old files. Any deletes will be renames instead [default: False]
  --retry <retry>                    Number of times to retry on errors [default: 3]
  --src-options <src-options>        Options for the source backend. Each option is a key-value pair separated by an equals sign, e.g. --src-options key1=value1 key2=value2 [default: empty] []
  --verify-contents                  Verify the contents of the files to decide whether the pre-existing destination files should be overwritten [default: False]
  --verify-get-after-put             Verify the files after uploading them to ensure that they were uploaded correctly [default: False]
  --version                          Show version information
  -?, -h, --help                     Show help and usage information

You could try that with your three-file backup. The URL for a local folder can be the Windows path (quote if it contains spaces), assuming you have a folder ready to go. Possibly you have other things in D:\tmp? If so, create a new folder with three files.

EDIT:

https://github.com/duplicati/duplicati/releases usually has a Canary near the top. Current latest one is v2.1.0.111_canary_2025-03-15, so maybe you can get duplicati-2.1.0.111_canary_2025-03-15-win-x64-gui.zip to unzip somewhere.

2 Likes