What this solves
This procedure gives an operator one controlled path to keep nodes, listeners, host health and configuration backup in one recoverable operating baseline.
When to use it
Use it during initial setup, a planned change or incident recovery when you need to keep nodes, listeners, host health and configuration backup in one recoverable operating baseline.
Dashboard path
/clusterNodes/list/ports/list/app/editPrerequisites
Administrator access to the Callaba instance and permission to change this module.
A maintenance window or a non-production resource plus a real test source or client.
A record of the current values, allocated ports and credentials before you save changes.
Steps in the Callaba UI
- 01
In the dashboard sidebar, follow Advanced → Cluster nodes. Open the source-backed route /clusterNodes/list. In the dashboard sidebar, follow Advanced → Active ports. Open the source-backed route /ports/list. In the dashboard sidebar, follow Advanced → General settings → Global export settings. Open the source-backed route /app/edit.
- 02
Before changing Cluster, ports, health and backup, record these current values: node_type, host, api_token, port, transport, exporting_modules.
- 03
In Cluster, ports, health and backup, set node_type, host, api_token, port, transport, exporting_modules so you can keep nodes, listeners, host health and configuration backup in one recoverable operating baseline. Keep unrelated values unchanged.
- 04
Run Save [creating-form-save] → Export [export-button]. Wait for the form or listing to settle before testing another variable.
- 05
Use a real source, destination or browser client and confirm these live signals: cpuUsage, drive, RAM, processErrors, srtErrors.
node_typehostapi_tokenporttransportexporting_modules
- Save
creating-form-save - Export
export-button
cpuUsagedriveRAMprocessErrorssrtErrors
Expected result
The runbook is complete when Save [creating-form-save] → Export [export-button] succeeds and a real workflow reports cpuUsage, drive, RAM, processErrors, srtErrors.
Troubleshooting
The saved change does not appear
Confirm the save response, refresh the module once and compare the visible values with the record made before the change. Correct validation errors before retrying.
The connection or playback path fails
Check the exact host, port, protocol, credentials and firewall path used by the real client. Test one source and one destination before restoring the full workflow.
The module starts but health is unstable
Return to the last known working values, inspect live statistics and process errors, then reintroduce one change at a time.
Product page / Exact API reference
Continue with the commercial product context or automate the same operation from its verified API endpoint.