Job compression being ignored

[hkraal]

Hi, I've just been testing the waters with the VeeAm Agent for Linux and after a couple of rounds of backup, filerestores and a full restore I must say I'm liking it very much. I do notice that the agent puts quite a load on the client in terms of CPU usage, which is probably due the applied compression (which I've seen on backup proxies as well).

So I thought lets see what happens without compression and adjusted the job accordingly using:

Code: Select all

# veeamconfig job edit --compressionLevel 0 for --name vps06-vagrant

The job config afterwards seems valid (besides the creation time):

Code: Select all

# veeamconfig job info --name vps06-vagrant
Backup job
   UUID: {13654bfa-ce9f-4d5c-9b82-eb85b44e4f1b}
   Name: vps06-vagrant
   Repository UUID: {8bf0e2cd-a7da-484f-9841-3b46dc239673}
   Repository name: Repository_1
   Creation time: [b]1970-01-01 00:00:00[/b]
   Options:
      Compression: [b]NoCompression[/b]
      Deduplication: no
      Max Points: 14
   Objects for backup:
   Include All System:

Code: Select all

# veeamconfig repository list
Name          UUID                                    Location                  Type  Backup server
Repository_1  {8bf0e2cd-a7da-484f-9841-3b46dc239673}  192.168.160.3:/srv/vps06  nfs

It seems the compression however is still applied as the CPU usage maxes out processing around 50MB/ps of data (full backup). In the logs I noticed the following:

Code: Select all

Agent.Target.log:[27.10.2016 11:10:21] <140677862110976> dt     |     Source requested traffic compression level: [Lz4].
Agent.Target.log:[27.10.2016 11:10:21] <140677862110976> dt     |       Traffic compression enabled: [Lz4].
Agent.Target.log:[27.10.2016 11:10:21] <140677862110976> dt     |       Block decompression is required.

Am I hitting a bug/feature here I did not anticipate?

[nielsengelen]

This currently isn't implemented in beta2.

[PTide]

One question - what is the target for the job - local, shared folder, or VBR?

[hkraal]

One question - what is the target for the job - local, shared folder, or VBR?

Target is an NFS (3) share

[PTide]

Confirmed to be a bug, thanks for heads up!

[JWester]

Is this bug not yet fixed in v1? I still get Lz4 compression even with a "no compression" backup job.

[nielsengelen]

No compression should work (just did a test on update 1). Please contact support for investigation.

Code: Select all

Job.log:[13.06.2017 09:23:57] <139701930510080> lpbcore|     Backup compression level: [NoCompression].

Agent.Target.log:[13.06.2017 09:24:01] <140058245969664> dt     |     Source requested traffic compression level: [No compression].
Agent.Target.log:[13.06.2017 09:24:01] <140058245969664> dt     |       Traffic compression enabled: [No compression].

[JWester]

Hm, ok.
Perhaps because the initial backup was done with compression, then I changed it to "no compression".
I'll try it with a new backup job.