Passing Options via CLI (pack-size)

[jordantrizz]

Hello,

I'm able to set the pack-size via rustic.toml, but via the cli it doesn't seem to work. I'm assuming this isn't possible, or am I doing something wrong?

rustic -r 'rclone:onedrive:backup' backup '/mnt/backup' -- --pack-size 128 --one-file-system -v

For instance, shouldn't this work? I've tried with out -- but this ends up being wrapped into the pathList.

[kapitainsky]

--pack-size

Where did you get this flag from? Any reference?

Datapack size is property of the repository you can set during rustic init or change later using rusitic config, e.g.:

$ rustic config --set-datapack-size 64MiB

and inspect using rustic cat config

To see what is options are available use built-in help.

$ rustic config --help

[jordantrizz]

Where did you get this flag from? Any reference?

I got it from restic, but I see now it wasn't carried over in a similar way and is a repository setting. https://restic.readthedocs.io/en/latest/047_tuning_backup_parameters.html#pack-size

[aawsome]

I think you are mixing https://github.com/bnavetta/rustic with this project.

The first is a wrapper for restic written in Rust, 5 years old and has never since got any update.
This rustic project is a complete re-implementation of restic in Rust with many unique features, see https://rustic.cli.rs/docs/comparison-restic.html.

(I must say I didn't realize that this wrapper existed when starting with rustic, but anyway now we won't change the name anymore and the other project seems to be abandoned)

For this project, there is no CLI and toml option to set the pack size, but there are various options to tweak the pack-size once (and forever) for a repo during initialization - no need to think about it after (unless you want to change it)

[jordantrizz]

I think you are mixing https://github.com/bnavetta/rustic with this project.

No, I was using restic and then started using rustic and realized the pack-size option wasn't available via the CLI. But I see the mistake I made, it's available via the repository configuration.