Each next incremental backup needs needs more time

[Pagrossman]

Hello,

Please have somebody some experience with this behavior?

We are using S3 object storage for backup of our ShP and Teams data.
From the beginning of the backup process everything was ok, but after some time we found crazy behavior.



Backup job that performs backup into on-premises is stable, but backup job that performs backup to S3 object storage needs more and more time for backup and after some time the backup time is returned back to time that is ok... but again grows... We do not understand this behavior.

We created new separated Veeam server only for backup into S3 object storage with 10 new backup applications. Unfortunately, without any effect...

Now the time of backup is about 55 minutes. Normal time is about 10 minutes and less...

Case #04935908

[Mike Resseler]

Hi Jan,

Thanks for creating and posting the case number. Not sure what this behavior can cause, something seems indeed off. Hopefully our engineers can see what is going on

[Pagrossman]

Hello,

it is almost 2 months after the creation of service ticket and we still don't have any solution
By the support, there is problem with network load... If we moved database from AWS to local disk array, then the problem is on disk array. After testing of disk array, the problem is only on weekends (WHAT?!?!), then support told me that ok, it is not problem of weekend the problem is with proxy, etc... etc...

We backed up our data into AWS... due to testing we created a new repository on-premises on disk array where we created Compatible S3 object storage.
Our server for backup has 16CPU + 16GB RAM (Veeam uses maximal 11GB) + disk array that is reserved only for Veeam.

The behavior is the same on AWS and on-premises...
On-premises (each line is backup job = 7 backup jobs):


AWS (orange color):


Normal repository is stable...

Unfortunately, it seems that the solution with Veeam support frozen on the zero point...
All my arguments are ignored

Is it some way how to resolve this problem? Any ideas?

[Pagrossman]

After more than half year, I closed the ticket, because by the Veeam Support "Logs indicate that the backup job was performing operations correctly."

This is the correct behavior