backdown apply

backdown apply [OPTIONS] <PLAN>

Arguments#

<PLAN>

The plan's number, as backdown plan and backdown plans show it.

Options#

--go

Actually copy (without it: a dry run).

Also takes the global options --db and --local.

Good to know#

Every copy is written beside its destination under a temporary name, read back and compared before it takes its name. An existing destination is never overwritten: if it differs, it's reported as a conflict. Runs can be interrupted and resumed. Copies are clones or kernel copies where the drives allow, and are read back either way. A name the archive's drive would take for another, or can't hold, is copied under another name (photo (2).jpg) and journaled; extended attributes (macOS) and alternate data streams (Windows) are copied, and what couldn't be kept is listed. Exits 2 when there were conflicts or failures. With a daemon running, --go is handed to it, and it indexes the archive afterwards.

Examples#

# what plan 3 would do (writes nothing)
backdown apply 3
backdown apply 3 --go

See also#

• File your old drives into one archive