Horrible backup performance

[mwk]

I'm trying to find the cause of our slow backup speed.

All systems are running Windows Server 2019 and are connected via 10GBit/s.

Source:
Xeon E3-1270v3, 32 GB RAM
6x 1TB SSD (Hardware RAID 10), ReFS
6 VMs

Backup Server (Veeam running in VM):
Xeon E3-1270v3, 12 GB RAM for VM

Backup storage (internal):
4x 8TB HDD SAS (Hardware RAID 10), ReFS + Data Deduplication

I'm running reverse incremental with the recommended settings for data deduplication.
Usually I get read speeds in the 100s of KB/s range, during off hours without load on the source.

[Egor Yakovlev]

Hard to say from this info.
- What is your Bottleneck % displayed in the job statistics?
- Backup storage(internal) is mounted on Hyper-V host(say, V:) or Veeam Server?
- How does Backup Storage added to Veeam B&R console under Backup Infrastructure - Backup Repositories?
/Thanks!

[foggy]

4x 8TB HDD SAS (Hardware RAID 10), ReFS + Data Deduplication

Also take a look at this thread.

[mwk]

- What is your Bottleneck % displayed in the job statistics?

My stats are Source 68% > Proxy 2% > Network 35% > Target 33%

- Backup storage(internal) is mounted on Hyper-V host(say, V:) or Veeam Server?
- How does Backup Storage added to Veeam B&R console under Backup Infrastructure - Backup Repositories?

The storage is mounted on the host which acts as a repository server. It shows up as type "Windows".

Also take a look at this thread.

Thanks for the link. I already knew about that. I never deduplicate the latest backup (always a full backup), so that should not be a bottleneck. Restore speed is fine btw.

[foggy]

The only guess I have is that you're under specced in terms of the host RAM. You have 32 GB overall for 6 running VMs, out of which 12 are assigned to the backup server, plus the repository components located on the host itself also require at least 4 GB + up to 4 GB for each concurrently processed machine. I'd try adding RAM to the host and contact support for further investigation if that doesn't help. Thanks!

[mwk]

RAM was my guess as well, but the backup VM never consumes more than 8 GB, so it seems unlikely. Maybe support is the way to go from here.

[Egor Yakovlev]

Please make sure to share the case ID here - I would be happy to follow it.
/Thanks!

[mwk]

Here's my case ID: 04232069. Unfortunately, since I'm evaluating the product and thus don't have a license yet the ticked has already been closed.