Linux Repo - What is sudo used for?

[justyjusty123]

When adding a linux repo, there is the option to sudo the account. What is this for and, is there any exact information what permissions are required on the target server where my repo is running? It's a Debian 8.
Is there any folder apart from /tmp where I need to assign permissions, or is there software installed? (We don't want to "try out" the sudo on productive server w/o knowing what it is about).

We have added the server successfully, and the rescan of the server completes without errors.
When I rescan the repo I get this error:

Code: Select all

30.03.2016 11:33:36          Starting backup repositories synchronization
30.03.2016 11:33:36          Enumerating backup repositories
30.03.2016 11:33:36          Found 1 backup repository
30.03.2016 11:34:11 Warning    Processing local backup repositories
30.03.2016 11:34:11 Warning    Failed to synchronize xrepo Details Host not found (authoritative)
30.03.2016 11:34:11 Warning    Backup repositories synchronization completed with warnings

Also, which logfile should I consult?

[tsightler]

There should be no requirement for sudo just for a repository, as long as the account you are using has permissions to write in the location you select for the repo files. The above error does not appear to be a permissions issue to me as "Host not found" almost always indicates DNS related issues.

[justyjusty123]

Thanks a lot tsightler. We did upgrade to v9 U1 and got it working w/o sudo in the meanwhile.

I was wondering that if we create a firewall rule, and allow 4 connections as is the default, will it be enough to allow 2501-2508 or will the higher ports also be used? We are not running more than 1 job in parallel. In the documentation it says 2500-5000.

Also, do I see it right, that the perl script that runs on the linux target repository, needs to access the backup proxy as well, and not just the other way round?

Just to mention btw, we had to manually create /var/log/VeeamBackup with the user's permissions, so that our dedicated, non-root, user could write the log file.

[justyjusty123]

allowed 2500-5000 and works. thanks.

[tsightler]

You can almost certainly get by with less than 2500-5000, but I'd also suggest more than just 8 ports, although it might be enough for one task, but Veeam uses mulitple TCP streams for each connection so normally I'd recommend around 8 ports per task as a minimum. Veeam uses ports from the bottom up, and you can actually customize the range if you select server settings. For a Linux machine on the SSH tab select "Advanced" and that will let you define an alternative range or shrink the existing port range.