Using a Centos 7 Linux as a Backup Repository; how to?

[tinto1970]

Hallo, i'm trying to work with my first centos7 installation... and i'd like to use this new linux machine as a backup repo.

Unfortunately adding it as a repo hangs when i click "populate" in "connecting to the server".

I've found this how to but probably it's a bit outdated...
http://blog.dewin.me/2013/05/veeam-and- ... itory.html

has anyone already tried to ose a centos7 as repo?
Thanks in advance

[Vitaliy S.]

Hello,

Does this distribution meet the following requirements for the Linux-based repository?

-Linux (bash shell, SSH and Perl are required)

Thank you!

[tinto1970]

yes it should... i am already using a previous version centos linux as repo.

the needed packages seem installed, firewall is off, i'm wondering if selinux could be involved: i'll try disabling it and post results

Code: Select all

[root@bslin03 ~]# rpm -qa | grep ssh
openssh-6.4p1-8.el7.x86_64
openssh-clients-6.4p1-8.el7.x86_64
openssh-server-6.4p1-8.el7.x86_64
libssh2-1.4.3-8.el7.x86_64

[root@bslin03 ~]# rpm -qa | grep perl
perl-podlators-2.5.1-3.el7.noarch
perl-threads-1.87-4.el7.x86_64
perl-Carp-1.26-244.el7.noarch
perl-Pod-Usage-1.63-3.el7.noarch
perl-Scalar-List-Utils-1.27-248.el7.x86_64
perl-Getopt-Long-2.40-2.el7.noarch
perl-parent-0.225-244.el7.noarch
perl-Text-ParseWords-3.29-4.el7.noarch
perl-libs-5.16.3-283.el7.x86_64
perl-Filter-1.49-3.el7.x86_64
perl-Time-Local-1.2300-2.el7.noarch
perl-File-Path-2.09-2.el7.noarch
perl-macros-5.16.3-283.el7.x86_64
perl-HTTP-Tiny-0.033-3.el7.noarch
perl-Pod-Escapes-1.04-283.el7.noarch
perl-constant-1.27-2.el7.noarch
perl-Socket-2.010-3.el7.x86_64
perl-Exporter-5.68-3.el7.noarch
perl-PathTools-3.40-5.el7.x86_64
perl-5.16.3-283.el7.x86_64
perl-Encode-2.51-7.el7.x86_64
perl-threads-shared-1.43-6.el7.x86_64
perl-Pod-Simple-3.28-4.el7.noarch
perl-Pod-Perldoc-3.20-4.el7.noarch
perl-Storable-2.45-3.el7.x86_64
perl-File-Temp-0.23.01-3.el7.noarch

[root@bslin03 ~]# rpm -qa | grep bash
bash-4.2.45-5.el7_0.4.x86_64
bash-completion-2.1-6.el7.noarch

[tinto1970]

disabling selinux did not change the behaviour

[Vitaliy S.]

What about the article that you've referenced?

[tinto1970]

the article is referred to centos6: in fact i've just installed another new centos6 and adding it as a repo was an immediate success

[tsightler]

I am seeing the same behavior with a test CentOS 7 system in my lab setup. I'll dig a little deeper but at least you know you're not alone!

[tsightler]

Looks like the perl Data::Dumper module isn't part of the default perl install on RHEL/CentOS 7 but some of the code included in veeam_soap.pl has a dependency on this module. Try running the following to install it:

Code: Select all

yum install perl-Data-Dumper

This resolved the issue for me, at least, it let me add the box as a repository with no issues. I haven't actually run a job to it yet.

[dellock6]

Thanks Tom, I was going to prepare my first CentOS 7 repo too...
Maybe it's time to be less generic on the requirements, and instead of simply asking for SSH and Perl, also specify the list of Perl modules we need? Tom can you retrieve a list and post it here for everyone?

Luca.

[tsightler]

OK, the following is a list of all optional perl modules used by the code currently included in veeam_soap.tar:

Code: Select all

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

This list looks long, but it's important to note that the vasy majority of these modules are included in the "base" perl install for most distros because they are so commonly used by other perl modules and they are still core perl modules. Note that they may still be separate packages, but are simply part of the dependency string for the base perl install. For example, on my CentOS 7 install simply running "yum install perl" installed the following packages in addition to perl-5.16:

Code: Select all

perl-constant-1.27-2.el7.noarch
perl-Carp-1.26-244.el7.noarch
perl-Encode-2.51-7.el7.x86_64
perl-Exporter-5.68-3.el7.noarch
perl-File-Path-2.09-2.el7.noarch
perl-File-Temp-0.23.01-3.el7.noarch
perl-Scalar-List-Utils-1.27-248.el7.x86_64
perl-Socket-2.010-3.el7.x86_64
perl-Storable-2.45-3.el7.x86_64
perl-threads-1.87-4.el7.x86_64

This satisfied all of the dependencies except for the Data::Dumper module, which I believe was part of the base perl install on earlier RHEL/CentOS releases. Also, I unfortunately don't know any way to determine the minimum version needed for each of these modules but, based on the fact that we know the code works on RHEL5 I'd assume any version of these modules in the last 5 years or so is probably good enough.

[dellock6]

Thanks Tom!

[tinto1970]

Thanks Tom, I'll try it asap... I'm a bit overloaded in these days

[scidoner]

Looks like the perl Data::Dumper module isn't part of the default perl install on RHEL/CentOS 7 but some of the code included in veeam_soap.pl has a dependency on this module. Try running the following to install it:

Code: Select all

yum install perl-Data-Dumper

This resolved the issue for me, at least, it let me add the box as a repository with no issues. I haven't actually run a job to it yet.

I can confirm that this solves the issue on Centos 7 for me as well. Got jobs running to it with no issues

I was pulling my hair out over this one, so I actually switched to Debian 7 until I saw this post when I brought the Centos 7 box back

[rickstromberg]

The idea of a linux repository is very interesting to me. I've found quite a bit of guidance about HOW to set up a linux repostiroy, but not so much on the WHY.

What benefits are gained by having Veeam talk to a Linux instance for storage operations?
I still need a Windows based proxy right?

In my case, I have a Windows based proxy at my remote office(s) connected back to the datacenter where the main Veeam management server sits. The Windows proxy at the remote office also acts as a repository connecting to a share from a Synology NAS. For the sake of simplicity, I don't have the remote proxy connected to the Synology via iSCSI but merely via SMB. (Well, in come cases I am using iSCSI from the Synology, but not NFS.) The proxy receives the job from the main veeam server, backs up the remote office Vmhost to the SMB share, and then a Copy job using wancache brings it back to the datacenter.

Thanks for any insight as to the why of linux repo.

RS

[scidoner]

The idea of a linux repository is very interesting to me. I've found quite a bit of guidance about HOW to set up a linux repostiroy, but not so much on the WHY.

What benefits are gained by having Veeam talk to a Linux instance for storage operations?
I still need a Windows based proxy right?

In my case, I have a Windows based proxy at my remote office(s) connected back to the datacenter where the main Veeam management server sits. The Windows proxy at the remote office also acts as a repository connecting to a share from a Synology NAS. For the sake of simplicity, I don't have the remote proxy connected to the Synology via iSCSI but merely via SMB. (Well, in come cases I am using iSCSI from the Synology, but not NFS.) The proxy receives the job from the main veeam server, backs up the remote office Vmhost to the SMB share, and then a Copy job using wancache brings it back to the datacenter.

Thanks for any insight as to the why of linux repo.

RS

For me, backup targets are connected via VMware iSCSI to Linux VM, thus its nice that Veeam provides Linux agent for backup target storage. Its been on Linux for ages so it made sense for me to be able to easily just add a Linux repository to Veeam

[dellock6]

Rick,
our datamover works in the same exact way on Windows and Linux. Having the possibility to choose a preferred platform is something that gives our many customers to use what they prefer.
One "why" for using linux repos however is when the final storage is an NFS share: since proxies cannot write directly to smb, you need a gateway server. Linux can mount an nfs share via fstab as a regular mount point, on windows nfs can only be mounted in userland, thus is cannot be used by our datamover that runs as system.
Other than that, as said, is a matter of preferences (and some scenarios like a failover cluster where I personally prefer linux servers, but again is MY personal taste, not a suggestion as Veeam employee)

[Chris2015]

Hey i found a installation guide for cent os 6.5.
Link: http://community.spiceworks.com/how_to/ ... repository

I installed it last week with cent os 7. Some commands had changed in the new cent os version but the backupjobs are running fine at the moment.