To configure Linux guests and repositories to work with Veeam Backup and Replication and utilize our software’s features.
There are several requirements that must be met, by a Linux OS, in order for us to effectively utilize all of our features and make sure they run consistently. On top of that we require root permissions to launch several modules. If these settings are not in place, then we won’t be able to properly write to and recover the system.
In order to launch our script we require the "sudo" command to be able to launch from the credentials we are given at the time of setup. "sudo" is a command that allows us to make administrator level (root) changes and executions in the Linux environment.
One of the primary reasons that we use "sudo" is to make sure that we can access the /tmp folder and launch a script from it. There are many other ways you can launch scripts from the "/tmp" folder but "sudo" is the most consistent way across multiple distribution’s to do it. This also allows us to complete the operation without having change user permissions so the user doesn’t have to modify them afterword’s to get them back to their original configuration, as well as we will be able to relinquish root privileges on the fly.
Here is a list of the modules that we require for Veeam to work properly with a Linux install:
One of the most widely used Linux distribution’s currently is CentOS 6/7 and in this distribution the "Data::Dumper Perl" module is not installed by default.
The configuration of your SSH install must allow using tunneled clear text passwords. Info on how to do this can be found on this KB: http://www.veeam.com/kb1512
Subsystem sftp internal-sftp
"mlocate", "gzip" and "tar"
"gzip" and "tar" are archive tools very much like WinZip. We use these to compress and decompress files going to and from the server.
All of these files and their required configurations must be installed on the Linux environment prior to its usage with Veeam Backup and Replication to fully use all of our features.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.