Issue Summary

The /rest/backup/1/export/runbackup endpoint sometimes returns an HTTP 500 error, even though the export process is successfully triggered. This behavior is misleading, as HTTP 500 suggests a server failure, while the actual functionality remains unaffected.

Steps to Reproduce

1. Make a request to /rest/backup/1/export/runbackup.
2. Observe that an HTTP 500 error is returned intermittently.
3. Check the export process, which continues to execute despite the error.

Expected Results

• The endpoint should return a more descriptive status code, such as HTTP 202 (Accepted) or HTTP 200 (OK), to indicate that the process has been initiated correctly.

Actual Results

• The endpoint returns HTTP 500, even when the export starts successfully.

Impact:

• Misleading error handling can cause unnecessary debugging efforts and confusion for users or systems relying on the response.

Workaround

Creating the backup from the UI.