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
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).