[SOLARIS] FYI: veeamconfig grablogs is broken

[VAB]

Hello all!

Just a heads up to let you know that on Solaris, "veeamconfig grablogs" is broken. This is because the script assumes it is running on Linux and collects files that have completely different content on Solaris (like /var/log/syslog), while missing others (like /var/adm/messages.0).

The /var/log/syslog file is critical as it may contain email addresses and thus personal data. Hence, every time we send logs to Veeam we potentially violate the GDPR in the EU. This may result in significant fines.

Regards,
VAB

[PTide]

Hi,

I understand your point. What would you suggest? Have you considered cleaning up syslog archive before sending it to Veeam?

Also, Veeam does not store logs obtained from users - everything gets deleted once the support case is closed.

Please take a look at these:

1. Sensitive data types in Veeam Backup & Replication and Veeam Backup for Microsoft 365 log files

2. Processing of sensitive data in Veeam Technical Support

Thanks!

[VAB]

Hi!

Sorry if I have not expressed the problem clearly enough. There is no point in sending the syslog file to Veeam support. There are only logs of email exchanges in it. So no need to clean up anything.

This is Solaris, not Linux!

The files you want are /var/adm/messages and the rotated /var/adm/messages.[0-4]. Those contain the important kernel messages that you need to diagnose problems. However, these files are not collected at all. Hence my opinion that "veeamconfig grablogs" is broken on Solaris.

Regards,
VAB

[rovshan.pashayev]

Hello @VAB

Thank you for your clarification. We appreciate your feedback, and we will certainly look into making further improvements.

Rovshan.