| Git Clone URL: | https://aur.archlinux.org/veeam.git (read-only, click to copy) |
|---|---|
| Package Base: | veeam |
| Description: | Veeam Agent for Linux |
| Upstream URL: | https://repository.veeam.com/backup/linux/agent |
| Keywords: | backup veeam |
| Licenses: | custom |
| Submitter: | CodeImp |
| Maintainer: | None |
| Last Packager: | theokonos |
| Votes: | 12 |
| Popularity: | 0.22 |
| First Submitted: | 2019-01-25 09:05 (UTC) |
| Last Updated: | 2023-05-27 13:10 (UTC) |
@StarTroop: you're correct -- veeamconfig (and the rest of the veeam applications) are intended to be run as root or a user with sudo privileges.
As for the autocomplete, the behavior on my system is the same. veeamconfig does not autocomplete unless I change my user to root.
Veeamconfig does not start without root privileges, even though my user is in the veeam group. I've logged out/in, rebooted, restarted veeamservice, but no dice. Furthermore, veeamconfig is not autocompleted in my terminal (xfce4-terminal with bash). Are these bugs or am I missing some configuration?
Many thanks for the agent. Now I dont have to setup another backup solution :) #voted
@k0ste oh! thank you for that. I bumped it to 8 since that's the number of changes I've made to the PKGBUILD/other files since upgrading the base package to v5. Should be reflected in your AUR manager now.
@theokonos please don't forget bump pkgrel if you uprade PKGBUILD, but not upgrade version. Thanks
@washed Sure thing! And thanks for the feedback! The original packager included a veeam.install file that took care of system service restarts and adding the veeam group. When I was updating the PKGBUILD for version 5 and running into issues, I got help from the Arch forums and a guy there revamped the PKGBUILD and recommended removing the veeam.install file entirely. I've restored it now, including the service restarts and groupadd as you suggested.
Thanks!
Hey, thanks for taking care of this package and updating it!
I just tried to install it on Manjaro with KDE (5.10) and it had trouble starting the service because of a missing group "veeam".
Running groupadd veeam followed by systemctl restart veeamservice fixed it for me. Maybe an install step is necessary to add this group before it tries to start the service? Thanks!
Hey all, I'm taking over maintenance of this AUR package and the veeamsnap one since they went stale enough to get orphaned.
This update brings veeam and veeamsnap to 5.0, which includes changes to how the job information databases are formatted (moved from SQLite to SQL) but is backward compatible with existing installations.
@k0ste, the extraction process should have changed the permissions for veeamservice.service. I also added mlocate as a dep per your request.
Cheers!
Please, add mlocate to deps list.
The veeamservice.service have chmod issues:
systemd[1]: Configuration file /usr/lib/systemd/system/veeamservice.service is marked executable. Please remove executable permission bits. Proceeding anyway.
systemd[1]: /usr/lib/systemd/system/veeamservice.service:7: PIDFile= references a path below legacy directory /var/run/, updating /var/run/veeamservice.pid → /run/veeamservice.pid; please update the unit file accordingly.
Pinned Comments
theokonos commented on 2021-12-26 20:53 (UTC)
Good news everyone: As of release 5.0.2, veeamsnap (and the veeam agent by extension) support Linux kernels up to and including 5.16. The AUR build has been updated to use the new 5.0.2 source and I have tested on my own machine on 5.10 LTS. Snapshotting works as it should.
Thanks!