- Veeam Support Knowledge Base
- Required Applications and Permissions for Multi-OS FLR and Repository Support for Linux
Required Applications and Permissions for Multi-OS FLR and Repository Support for Linux
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Purpose
Solution
Permissions Requirements
Permissions are dependent on the intended role of the Linux server. For more information, review this page of the user guide.
Authentication Requirements
Linux servers registered with Veeam Backup & Replication infrastructure must use Password or Certificate-based authentication methods and bash shell.
Required Applications
- bash
- ssh
- scp
- sftp
- gzip
- tar
- perl
Required perl modules (Click to expand)
When Perl is required, the following Perl modules must be installed:
In most scenarios, these will be installed by default.
- constant
- Carp
- Cwd
- Data::Dumper
- Encode
- Encode::Alias
- Encode::Config
- Encode::Encoding
- Encode::MIME::Name
- Exporter
- Exporter::Heavy
- File::Path
- File::Spec
- File::Spec::Unix
- File::Temp
- List::Util
- Scalar::Util
- SOAP::Lite
- Socket
- Storable
- Threads
Starting with Veeam Backup & Replication 11, Perl is only required when using non-persistent data movers. Non-persistent data movers are used when a non-root account is used by Veeam Backup & Replication and the option Elevate account privileges automatically is not enabled.
Persistent data movers are required if the Linux server being added to Veeam Backup & Replication will function as a VMware Backup Proxy or a Hardened Repository.
Known Limitation
Veeam Backup & Replication does not support SSH connections to a server where the user Veeam logs in as is configured to have tmux automatically started when logging in.
- For non-persistent agents, it must be disabled completely for the user Veeam Backup & Replication is configured to connect as.
- For persistent agents, it must be disabled at the time of deployment.
- For Hardened Repositories, review: KB4250: How to Configure Hardened Repository on Red Hat Enterprise Linux 8 With NIST 800-171 Security Profile
Example:
The NIST 800-171 security profile on Red Hat Enterprise Linux 8 includes tmux automatic startup system-wide. To successfully deploy the Veeam services on the system, tmux must be temporarily disabled. Usually, it is configured in /etc/bashrc for all users on the system as shown here:
[user@rhel8 ~]$ sudo grep tmux /etc/bashrc
case "$name" in sshd|login) exec tmux ;; esac
[user@rhel8 ~]$ sudo grep tmux /etc/bashrc
#case "$name" in sshd|login) exec tmux ;; esac
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.