Skip to content

Stalwart Migration Documentation - Families instead of Subspaces #101

@simprobe

Description

@simprobe

The stalwart migration documentation (here: https://stalw.art/docs/management/migration/) references that EXPORT_TYPES uses subspaces and specifically provides documentation to run code such as:

$ EXPORT_TYPES="j,k,t" /opt/stalwart/bin/stalwart --config /opt/stalwart/etc/config.toml --export ~/stalwart-export

This does not appear to be correct, updated (or at least with my tests of Stalwart windows, latest version). Looking at the code, in (common/src/manager/backup.rs), EXPORT_TYPES is parsed using function parse(family: &str). The family names are expected.

When you run it in this fashion, you get a "Backup failed: Unknown family " error.

The following example works:

$ EXPORT_TYPES="data,directory,config,changelog,queue,report,telemetry,tasks" /opt/stalwart/bin/stalwart --config /opt/stalwart/etc/config.toml --export ~/stalwart-export

Please update the documentation and the subspaces mapping table to also include the family names that can be used.

data - a, i, u, n, p
directory - d
blob - t, j, k
config - s
changelog - l
queue - e
report - h, r
telemetry - o, x
tasks - f

Thanks,
Simon

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions