Restoring for another Backup Device/Job

[stan464]

Before you post: have you tried searching the forum? If you have found related posts that didn’t quite solve your issue, please mention (link) them in your post.

Appears none are easy to find for the following query.

Hi Guys.

Query:

If you have 2 Devices backed up with 2 different Configs/Locations, how can you Temp Restore a Folder/Directory from the other backup and then remove that backup/restore job from the working Machine.

Does that make any sense at all?

Tl;dr: Restoring a backup from another backup Device/Location on-behalf of a none-working machine temporarily.

[Droolio]

CLI or Web UI?

With Web UI, it’s pretty straightforward as you’re asked to specify a restore location and this can be a temporary location.

With CLI, you just create an empty temp directory, init to the storage with the repository ID you want to restore from, and do the restore.

Restoring doesn’t alter the configuration on the storage server and you don’t have to delete any jobs after.

[stan464]

How can this be converted from WebUI to “CLI” as far as Command Conversions? as webUI takes the need to Command Line away from the user (not complaints of course).

What if the Location is different from the working machine as the “ID’s” wouldn’t be discover-able would they?

Thanks Droolio!

[Droolio]

Basically, a restore in Web UI does more than just restore command… It lets you pick from a storage, select a (existing) backup ID from a pull-down, pick a revision (it runs a list), select a restore location (which can be empty).

When you run the restore in the UI, it has to do an init first and then the restore. See:

Setting a custom directory for restore

You can restore to a different directory as long as you use the same repository id. cd path\to\restore duplicacy init original_repository_id storage_url duplicacy restore -r 1 files_to_be_restored This works even on a different computer. All Duplicacy cares is the repository id – repositories with the same id act like the same repository no matter where they are.

So with CLI, you may have to perform other commands like list -all in order to discover these extra parameters so that you can manually specify them in the init and restore step.

[stan464]

Makes sense now!

Thanks for the help Droolio! appreciate it!

Thanks Kindly!