Skip to content

Path usage for backup/restore not consistent. #446

@lImbus

Description

@lImbus

I promised to fd0 I would create an issue for this, although by now, I am not entirely sure of the problem anymore. What I was trying to do can be seen in #407.

The core of the issue here is that "backup" and "restore" behave slightly differently in handling paths. From the internals of the workings, this is totally understandable, for an operator it is not. Sitting in a working copy directory ("foo") and calling restic backup . will backup not all the contents of this directory, but this directory. Sitting in the same directory ("foo") and calling restic restore <ID> --target . will create a new sub-directory "foo".

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions