Account data (cubes, reports and published reports) may be downloaded as an XML file in this way:
This XML file can be restored on self-hosted SeekTable instance with an active "System/users admin" subscription:
Keep record IDs, do not restore if IDs already exist: use this option to restore removed cubes/reports.
Keep record IDs, overwrite existing records with same IDs: use this option to transfer/update account data between SeekTable instances.
Generate new record IDs: use this option to 'clone' cubes with reports.
With backup/restore functionality it's easy to organize a typical development flow: use 'development' SeekTable instance to configure cubes/reports, then restore them on 'staging' SeekTable instance (for QA) and finally publish a new version on 'production' SeekTable instance simply by restoring the backup file with an appropriate restore mode.
To backup self-hosted SeekTable installation it is enough to make a copy of files in the docker volumes
csv-files-volume + docker-compose configuration files.