Slow restore explorer or robocopy

[toreml]

Hi.

I have an issue with that the speed I have on restore of files are extremely slow.
I have mounted the disk in VeeamFLR folder - locally on my computer.
I've tried both with explorer and RoboCopy - but the speed i get is slow.
Restore is done to my local computer.

I'm currently running Robocopy - and I have copied about 16 MB in four minutes.
Anything I could do to be able to get an higher speed?

I've also tried the same on a proxy server which is in the same datacenter.
No great speed there either

Tore

[foggy]

Hi Tore, could you describe your setup in more detail, please? What kind of repository do you have and how it is added to Veeam B&R?

[toreml]

The storage is Cohesity and connected to Veeam as a Cifs share.

[foggy]

Am I understanding right that you're using the Copy To option? Where is the mount server for this repository located?

[toreml]

I've tried both the copy to - and explorer - copy / paste.
Both cases I've restored / copied to the same server as the backup image is mounted - if this is what you think of as mount server.

this is a Cifs share - so there is no repository server attached.

[foggy]

What if you just try to copy data out of the storage without Veeam B&R in picture? It is a deduplication device, so data rehydration is required, which could be the reason of slow performance. Feel free to contact technical support to evaluate the setup.

[toreml]

Hi.

We have an extremly slow restore speed.
I'm restoring from a proxy server and to the server - but to another directory

I now restoring some favorites - 101.9 kb - and estimated time remaining is more that 2 hours!!!!
What am I doing wrong - and what can I do to speed this up?

We are currently using 9.5 update 3 - and are using Cohesity as storrage.

In addition is the mounting process of the backup image very long - severall hours.

Tore

[DGrinev]

Hey Tore,

Have you tried to copy data out as it was mentioned by Foggy in the previous post?
I've merged your topics as it's the same issue. Thanks!