Required modules and permissions for Multi-OS FLR and Repository support for Linux

KB ID: 2216
Product: Veeam Backup & Replication
Published: 2017-01-05
Last Modified: 2022-01-18
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

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

error icon

Oops! Something went wrong.

Please try again later.

Purpose

This document provides information about required applications that must exist on Linux machines to function with Veeam Backup and Replication.

Solution

Permissions Requirements

Permissions are dependant 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

    Note: Starting with Veeam Backup & Replication v11, Perl is only required when using non-persistent data movers. Non-persistent data movers are only used when the account used by Veeam Backup & Replication to connect to the Linux server is not root or cannot elevate (su/sudo) to root.

    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

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.

 

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
To disable the automatic launching of tmux, edit the /etc/bashrc file and comment out the line with tmux. When complete, the bashrc should be as shown in the grep output below.
[user@rhel8 ~]$ sudo grep tmux /etc/bashrc
  #case "$name" in sshd|login) exec tmux ;; esac
Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

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

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.