[New User] Config store, Dedup, Change Track & History, Save excluded data metadata, .include, custom .ignore

Support
#1

A. Basic Question where config is stored

  1. Can I backup same data from same PC (but from different OS) to same external disk .

2.1 Everything I need except the config is in the repo ? If I loose access to current PC and just remember the password I will be able to restore ?

2.2 Is repo config stored in repo ? Kopia has this, i keep every policy inside repo.

B. Backup method

  1. Forever full backups/DeDuplication - Option Delete changes older than x, Where only fullbackup is taken once then incrementals are merged. I have heard terms like, snapshot and CBT but understand it.

C. How to

  1. How to check Backups ?

  2. How to restore selective directories ?

D. Features 1

  1. Save “Ghost” of excluded data i.e. only Filename, Metadata and Folder-Structure.

Use Case: I exclude data from internet but I want to know that data is excluded when I restore so I want to save/restore filenames, directory structure, and metadata like file created , last edited.

E. Weird Questions

  1. “File Change Tracker” to see summary of what files are moved/deleted/renamed between to backups.
    Like kopia has diff(https:// kopia. io/docs/reference/command-line/common/diff/)

  2. “File History” to see previous version of files.
    Like kopia https:// kopia.discourse .group/t/is-there-a-way-to-view-a-single-file-history-across-all-snapshots/1378/4

F. Feature 2

9.1 Multi-profile using custom .ignore filename ?
Use Case: Create “profile 2” which backups “super important” to cloud with stronger password. Can I create .ignore2 or .IgnoreCloud.

9.2 .ignore files custom names, like kopia has -

image
image1768×340 17.2 KB

  1. Option to “only include” what is selected e.g. .include ?

G. Feature 3

  1. How to Backup Selective Parts without it creating another repo inside repo ?

I don’t want to spend 30m waiting for it to snapshot the whole disk with no changes, so is there a way to tell Duplicacy “look here I made changes backup those” (and in doing so It should consider the part-backup part of the whole disk backup so to not create “another backup inside the same repo with duplicate data”).

H. Weird Questions

  1. Is Duplicacy considered enterprise level ?

  2. Is Duplicacy UI good enough? What can I get extra after learning CLI, how much time it would take ?

#2

A few quick answers: the repository plus password is the important part for restore; the local config is mostly convenience for paths/storage settings, so keep a copy if you want an easy rebuild but do not treat it as the backup itself. To check backups, run a normal check first and occasionally a fuller chunk check; for restore, use the snapshot id and restore only the path you need. Duplicacy stores separate snapshot IDs in the same storage and deduplicates across them, so backing up a subset does not duplicate unchanged chunks, but it will be a separate snapshot/history line. For filters, I would keep one clear filter file per job/profile rather than relying on renamed ignore files unless the command you run explicitly points to that file. The “ghost metadata for excluded files” idea is not really what backup exclusions are for: if the names/metadata matter, I would keep a small manifest separately or include that tree. CLI is worth learning for repeatable jobs and debugging; the UI is fine for basic scheduled backups.