Slow backup over LAN

[jaclar]

Hi

I have a backup which runs over LAN, is has been performing very good, but now it's running with a processing rate of only 7-8 MB/s, previously is has run with up 300-400MB/s.

The vSphere - "Use changed block tracking data" and "Enable changed block tracking for all processed VMs" are enabled.

Some of the servers is running backup without changed block tracking although it's enabled.

Does anyone have an idea to what's wrong?

[Vitaliy S.]

Jacob,

Sounds like your backup job is running a full pass. Could you please tell me about recent changes in your VI? Do these VMs have anything in common (datastore location, host, etc.)? What does backup job bottleneck statistics say?

Thank you.

[jaclar]

Hi

The VI has been changed, one of the servers has harddisk and RAM increased.

There are 2 LUNs and 3 ESX hosts which the servers are speard over.

I can see that after a manual full backup, the backup mode has changed to “with changed block tracking” on every server again.

You mention the bottle neck statistics, where can I see that.

I’m running Veeam v. 5.0.2.230

Thanks for your reply.

[Gostev]

Bottleneck statistics is a v6 features only, it really helps with troubleshooting performance issues. In your case, it looks like changed block tracking is no longer functional for some of those VMs. Running full backups on all jobs should re-initialize CBT. If this does not help, check the sticky Known Issues topic for how to reset CBT on a VM (last post).

One other common reason of network backups slowing down is some piece of network equipment had failed over from 1Gbit to 100 Mbit. However, in your case I am 99% sure the reason is CBT not working.

[dellock6]

Maybe you have moved the VM from a datastore to another while powered off? This usually reset the CBT data ,and next Veeam job needs to do a full pass. It also happens sometimes CBT data got problems and you need to reset them.
About bottleneck stats, they are only available on v6.

Luca.

[jaclar]

Hi,

The Veeam backup is running fine, after the full backup has run.

Thank you for the replies.