Feature request - Easier way of checking logs in V13 on Linux

[Jonsson411]

Hello,

When migrating to V13 and installing the Linux appliance, I noticed that it has become much harder to check logs for errors. Currently, the only ways I know to access them are by extracting a support bundle or by opening an SSH session to the VBR.

It would be appreciated to have an easier way to review logs. I understand that the appliance is hardened by default, which makes direct access more restricted. However, would it be possible to introduce a feature that allows logs to be sent to an SMB share?

For example, after logs are written on the appliance, it could periodically (e.g., once per minute) copy them to an SMB share. This would allow administrators to browse and review logs in near real time without needing SSH access or generating support bundles.
Regards
Elias Jönsson

[Mildur]

Hi Elias,

Welcome to the forum and thank you for the request.
We are discussing some ideas to make consuming logs easier, but there is no ETA on when it will become available.

May I ask: instead of sending logs to an external server (which would require opening additional network ports and hardware resources from the customer), would it also work for you if we provided direct access to view and download individual log files through one of the existing web UIs (e.g., Backup Server Web UI or Host Management UI)?

Best regards,
Fabian

[Jonsson411]

Yes, that would work. However, the text needs to be searchable within the GUI, and having a download feature would also be beneficial.

The main concern I see is that technicians (myself included ) would end up with thousands of log files downloaded to the console server or jump host. One advantage of the Windows version is that you can browse and open log files “live,” while Veeam handles retention and deletion automatically.

That’s why I would prefer having a copy written to an SMB share, where Veeam can manage retention and cleanup.

From my perspective as an MSP, the additional infrastructure required for a Windows host to store the logs is not an issue. However, I can see how this could be a concern in smaller installations.

This might be a case where both suggestions could be implemented together.
Best regards
Elias Jönsson