Standalone backup agent for Linux servers and workstations on-premises or in the public cloud
Post Reply
doublem
Influencer
Posts: 11
Liked: 2 times
Joined: Jul 01, 2016 4:07 pm
Contact:

Problems with update of veeam agent

Post by doublem » Aug 16, 2019 10:55 am

I get this on CentOS 7 when going from 3.0.2.1185 to 3.0.2.1190.

What is the best method of solving this without unistall + install ?

Code: Select all

Resolving Dependencies
--> Running transaction check
---> Package veeam.x86_64 0:3.0.2.1185-1.el7 will be updated
---> Package veeam.x86_64 0:3.0.2.1190-1.el7 will be an update
--> Processing Dependency: veeamsnap = 3.0.2.1190 for package: veeam-3.0.2.1190-1.el7.x86_64
--> Running transaction check
---> Package kmod-veeamsnap.x86_64 0:3.0.2.1190-1.el7 will be installed
--> Processing Conflict: veeamsnap-3.0.2.1185-1.noarch conflicts kmod-veeamsnap
--> Finished Dependency Resolution
Error: veeamsnap conflicts with kmod-veeamsnap-3.0.2.1190-1.el7.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

P.Tide
Product Manager
Posts: 5221
Liked: 450 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Problems with update of veeam agent

Post by P.Tide » Aug 16, 2019 4:06 pm

Hi,

Please check this page of the user guide to learn about possible options.

Now, here is why that happens:

If the dkms package had been already installed in the OS before you installed VAL for the first time, then VAL is installed with open-source version of its driver (veeamsnap-<version.noarch). That package conflicts with a pre-built binary (kmod-veeamsnap).

Thanks!

doublem
Influencer
Posts: 11
Liked: 2 times
Joined: Jul 01, 2016 4:07 pm
Contact:

Re: Problems with update of veeam agent

Post by doublem » Aug 17, 2019 8:36 am

Thanks,

This information solved the problem.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests