If you need urgent assistance, please open a support case with Veeam. You can see how to do that here: https://www.veeam.com/kb1771

From the error, it sounds like you are potentially backing up directly to object storage, is that correct?

You shared very few details, so let me ask a few questions:

• What are we backing up here? A single virtual machine on vSphere?
• What is the backup target? Local object storage? Public cloud object storage?
• If public cloud object storage, what is the available internet bandwidth?
• If public cloud object storage, which provider are you sending the backups to? Which region?
• What is the current bottleneck listed on the job?

@haslund We r backing  up a single virtual machine on vSphere
Backup Target is local object storage.
Avaible Bandwidth is I think high but the backup is showing 11MB/s speed.
No bottleneck, now it is saying processing 89% processed.
Let me attach a screenshot also for this.
 

Now it is stuck at 89%, any help please

@sheh_41  - in the job history click on the VM on the left column to show more details in the right column on what is going on then take a screenshot and post it. 

@sheh_41  take a screenshot of the same 1st window you did previously, but click on the VM on the left. Thanks. 

@coolsport00 Thanks for the prompt responses, below is the screenshot for that, Thanks.
 

Ok thanks. So you have several noticeable issues going on here causing the increased delay in getting your VM backed up. 

1. The backup processing speed is significantly low (2-10MB is really bad).

2. The speed is bad because your job is using the NBD (network) backup Transport method. You should be using hotadd or direct san.

3. Also, your job is using your Veeam server as the backup Proxy, which could be the reason your job is using NBD. 

4. Last, for some reason, your backup job isn't using CBT (change block tracking), essentially causing Veeam to read the entire disks of the VM, which causes the backup job to take a long time 

@coolsport00 Thank you for your answers, also can you please explain this steps a bit. I mean I understand them, but a little bit of explanation would be better.

@sheh_41 -

You need to determine the cause of the behavior of the bullet items I shared to make your job(s) perform better.

To increase your backup speed, use Virtual Appliance (hotadd) or DirectSAN, assuming your computer you’re backing up is a VM. At the very least, create a Windows or Linux OS VM and add it to Veeam as a Managed Server, then add it as a Proxy:
https://helpcenter.veeam.com/docs/backup/vsphere/backup_proxy.html?ver=120
and 
https://helpcenter.veeam.com/docs/backup/vsphere/transport_modes.html?ver=120

Then configure your job to either ‘Automatic’ or explicitly assign the newly added VM/Proxy to your Job (Storage section). This will help with processing speed.

A reason your Veeam Backup server is being used by the job for Proxy could be you just installed it using ‘defaults’ to where Veeam Backup is used for all your components (Veeam server, Proxy, and Repository). This is ok if your environment is small. But you also need to make sure you have enough compute resources on your Veeam server to handle all the components. So, you need to add what up all the compute resources required by each componenet (Veeam server, Proxy, and Repo) and make sure the Veeam server has at least that many resources (CPU, RAM, storage).
https://helpcenter.veeam.com/docs/backup/vsphere/system_requirements.html?ver=120

For the CBT issue, make sure your Job(s) are configured to use CBT:

https://helpcenter.veeam.com/docs/backup/vsphere/backup_job_advanced_vsphere_vm.html?zoom_highlight=cbt&ver=120

There could be other reasons CBT is not enabled..using NFS o 1st job run, for example. And, there could be other reasons. Read more about CBT here:

https://helpcenter.veeam.com/docs/backup/vsphere/changed_block_tracking.html?zoom_highlight=cbt&ver=120

Hopefully, all those info/link can get you started on helping getting your Job(s) to work better.

Best.

 

on this screenshot, we can see the reason why CBT couldn’t be enabled:
There is a snapshot (not inital from Veeam) on this particular VM present.
If it’s possible, and that snapshot is not needed anymore, delete it - so that CBT can be used.

Also, as mentioned NBD is for sure not the fastest mode - i would prefer HotAdd as well, but if NBD is the only option in your environment, please also make sure to use the latest 12.1.2 VBR build, as its nearly doubled the performance for the NBD mode.
Your report shows a VBR on V10, which is not supported anymore, maybe consider also an upgrade to a supported version.

best regards Markus

Do you have another proxy server? 

CoolSport nailed it with his comment. NBD isn’t the way to go if you have other options. Plus, I’d bet your using 1Gbps management in your environment on the servers?

Those speeds are incredibly slow. 

Do you have a license/support, or is this a lab/test environment? 

It sound more like issues with configuration, which I recommend you read the Veeam best practices and check out this site.

https://www.veeambp.com/