Account data (cubes, reports / published reports, workspaces) 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 only 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 a backup/restore functionality it's easy to organize a typical development flow:
Deployment may be automated with the restore API endpoint:
||(required)||API key of the user account with "admin" role + login email of this user should be specified in
||(required)||ID of the account where cubes/reports are restored.|
|Response||HTTP/200 (OK) if restore operation executed successfully.|
curl -k -H "Content-Type: text/xml" -H "Authorization: SEEKTABLE_ADMIN_ACCOUNT_API_KEY" --data-binary "@seektable_backup_YYYYMMDD.xml" SEEKTABLE_BASE_URL/api/account/ACCOUNT_ID/restore?mode=allowUpdate
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.