Troubleshooting

Bacula Enterprise Only

This solution is only available for Bacula Enterprise. For subscription inquiries, please reach out to sales@baculasystems.com.

This section provides suggested solutions to common situations that can cause issues when using the IRIS Plugin.

Common issues:

Permission denied writing dump/journal files: verify destination_path_dump and destination_path_journals are writable by the File Daemon user.
IRIS backup already running: the plugin waits and retries, but concurrent IRIS backups can delay or fail jobs.
Full backup required: if the IRIS volume indicates a mismatch with the local delta catalog, the plugin upgrades to Full automatically.
Instance not found: verify instance values match output of iris qlist.
Out of Memory: see Out of Memory.

Monitoring Recommendations

Review Bacula job logs for warnings such as “backup already running” or “Full Backup is mandatory”.
Check the plugin debug log path (log parameter) for detailed IRIS command output.
Track job duration and throughput; sudden changes often indicate storage or IRIS load issues.
Ensure filesystem space is available under path for temporary files and restored artifacts.