VA for AIX non-root users

[philfreund]

I want to have an AIX non-root user able to access the VAA backups. I have added the user to the veeam group. However, that doesn't give them access to the executables. What are the various installation directories populated by the VAA installer? What directories need to be added to their shell profiles for them to execute veeamconfig and the man pages? I'm pretty sure there have to be the correct directories set in PATH and MANPATH for example.

[HannesK]

Hello,

However, that doesn't give them access to the executables.

I just tried it out and it works fine for me. I followed the user guide and created a new user just for this test. I get some warnings that it cannot create a logfile, but the veeamconfig command works perfectly fine.

Code: Select all

bash-5.0$ veeamconfig backup mount --id f5440aaf-6c82-49ec-a621-47b58af6574c --mountDir /home/backup1/flr/
Failed to initialize log [/var/log/veeam/config/veeamconfig.log].
No such file or directory
POSIX: Failed to create or open file [/tmp/VeeamBackup/veeamconfig.log].
Backup has been mounted.
Session ID: [{d054ad54-8732-4167-adff-8fdf33b9b0d6}].
Logs are stored in: [/var/log/veeam/Mount/Session_20201118_075957_{d054ad54-8732-4167-adff-8fdf33b9b0d6}].
bash-5.0$ ls flr/
FileLevelBackup_0
bash-5.0$ ls flr/FileLevelBackup_0/
etc
bash-5.0$ whoami
backup1
bash-5.0$ groups
staff veeam

The warnings can be fixed by creating /tmp/VeeamAgent/. Then it works without any warning:

Code: Select all

veeamconfig backup mount --id f5440aaf-6c82-49ec-a621-47b58af6574c --mountDir /home/backup1/flr/
Backup has been mounted.
Session ID: [{f260fc49-dd9e-4a30-8de1-af0bf3f32ef3}].
Logs are stored in: [/var/log/veeam/Mount/Session_20201118_080715_{f260fc49-dd9e-4a30-8de1-af0bf3f32ef3}].

If that does not work for you, did you already check with support? If yes, what's the case number?

Best regards,
Hannes

[philfreund]

I was trying to get a list of the required directories to see if I could get it to work before opening a case. By default, none of my regular users have /usr/sbin in their PATH. When I added /usr/sbin to their default path, and try to execute it, veeamconfig errors out:
Could not load program veeamconfig:
Dependent module /usr/lib/libiconv.a(libiconv.so.2) could not be loaded.
Member libiconv.so.2 is not found in archive

It looks like I'll have to open a case.

[HannesK]

I was thinking about to post the

Code: Select all

rpm -ql VeeamAgent

output, but I assume that's not what you are looking for?

[philfreund]

I wish it was but that doesn't account for the simlinks. BTW, man veeamconfig works fine. It's executing veeamconfig that blows up. I'll open a case and post the number here.

[philfreund]

Case #04502095

[HannesK]

hmm, I just checked the case and I cannot explain why sudo was the solution for you. As it is working fine for me without sudo, we will keep the user guide as it is.

I did not even have sudo installed before posting this right now.

[philfreund]

Interesting. Whatever is the cause, it is consistent across three servers.

[rhnmohite]

What solution get from support team.

[HannesK]

support suggested sudo as workaround. But in general, that's not needed. If you run into that issue, please check with support and post the case number.