Comprehensive data protection for all workloads
sorell.it
Novice
Posts: 4 Liked: 3 times
Joined: Oct 24, 2016 10:22 pm
Full Name: Sorell IT
Contact:
Post
by sorell.it » Oct 24, 2016 10:32 pm
2 people like this post
In order to get this to work we had to be running Veeam 9.0.0.1715 & these commands were run on a Ubuntu 16.04 Server installation.
Run the following on the ubuntu server, this installed the required software needed to build the perl modules required by Veeam
Code: Select all
sudo apt-get install build-essential
Now you can install the perl modules with cpan
Code: Select all
sudo cpan 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 Socket Storable threads
Note: I actually install all the perl modules with seperate commands however it
should work all as one
Now that all the modules are installed you need to enable sued to elevate without prompting for a password
And then put in the line
After that you should now be able to connect Veeam to a Ubuntu server
PTide
Product Manager
Posts: 6582 Liked: 798 times
Joined: May 19, 2015 1:46 pm
Contact:
Post
by PTide » Oct 26, 2016 11:35 am
this post
Hi,
Have you tried to add
in your sudoers file for the veeamuser that you use to connect to the server?
sorell.it
Novice
Posts: 4 Liked: 3 times
Joined: Oct 24, 2016 10:22 pm
Full Name: Sorell IT
Contact:
Post
by sorell.it » Dec 07, 2016 10:52 pm
this post
Sorry for the crazy delayed reply, Just had the opportunity to run up another Ubuntu repo for Veeam so I tried out what you suggested and it still didn't play ball for me. Went back to using:
and then it started working.
tsightler
VP, Product Management
Posts: 6038 Liked: 2867 times
Joined: Jun 05, 2009 12:57 pm
Full Name: Tom Sightler
Contact:
Post
by tsightler » Dec 08, 2016 1:46 am
2 people like this post
Just in case others read this, sudo is not required for a Linux repository, as long as the user that you are connecting with has permissions to the directory you want to use to store backups. It generally not considered best practice to provide sudo access to accounts used for Linux repositories. Far better is to create a restricted user and set the permissions on the repository directory to u+rw only by that user.
Users browsing this forum: Amazon [Bot] , Bing [Bot] , Google [Bot] , Semrush [Bot] and 43 guests