Slow backup problem

By throttle, do you mean enabling network throttling, or are you limiting concurrent tasks (Proxy and Repository), or with Repositories..setting Read and Write latency metrics?

Ok...yep, that would be Network. Is your Repository storage local to the Windows 10 computer (i.e. direct-attached disk), or is it some external storage...for ex. external NAS or some storage, connected to your Windows 10 desktop as SMB, NFS, or other?

If external storage, then that would make sense your jobs would be running significantly less speeds with netwk throttling set.

Hmm...not sure. I’m perplexed at that one too. Let me think about that, unless someone else chimes in with their thoughts.

Ok wait... I'm a bit confused at what you're using. Are you running Veeam Agent for Windows on this Win10 desktop or Veeam Backup & Replication Community Edition? Those are 2 separate products and both are not needed if you have them both installed on the same computer. 

Ok, that sounds better.

Let’s take a step back to see maybe why that behavior is occurring. You really don’t need throttling on because everything is local. That is more a feature for latent networks, or to give more bandwidth to production loads over backup loads. I know it helps with the browser and app latency. But, really throttling isn’t the solution.

Let’s start with your Win10 recources, specifically what Veeam requires at a minimum to run as noted in the Guide. Do you have enough resources on your Win10 desktop to handle backups, even if it’s just 1 job? You require a minimum of 1 core and 4GB RAM for VBR. Using the Console requires an additional 2GB RAM; since you also use the default Proxy (i.e. the default Proxy installed with VBR on the desktop itself), that’s an additional 2 cores + 1 core per 2 concurrent tasks (disks) and 2GB more RAM + 500MB per concurrent task; then last, the Repository requires at least another core + 4GB RAM and additional one GB RAM per concurrent task. That totals to about 6 cores and 12GB RAM minimum, and that doesn’t include what the OS requires to run satisfactorily.

If you don’t meet those resource requirements, plus have additional resources to run OS apps/tasks, then there is where your browser/app latency is more than likely coming from when running your backup job.

When you throttle your network, which you are using network because the 2nd desktop you’re backing up is a remote computer, your backup speed will decrease because Veeam pulls data from the Source/backed up desktop to the target Repository, which when you don’t configure an external one, runs on the main desktop/computer Veeam is installed on.

When you run your backup job with throtlling and get low speeds, if you look at your backup job statistics (double-click the job), there are 4 metrics Veeam determines latency on: Source (source storage containing the data you wanna back up), Proxy (Veeam Component which performs all the data transfer, compression, dedup, etc. tasks), Network, then Target (Repository; storage location backups are written to). The metric with the highest number is where you’d start looking at for poor backup performance. I assume the Network metric would be the highest with throttling on. And that makes sense.

Anyway, that info hopefully should help. But, for your app latency during backups, I’d first look at your desktop resources to see if you meet those. If not, somehow add some if you can.

Hi @ptmy305 -

Anything further you found to resolve this, or is your workaround of letting the Client do Standalone instead of Managed an ok resolution? Curious what your found, if anything.

Thanks.

Thanks for the update @ptmy305 

Best regards.