Backup gets slower and slower...

[umenz]

Hello,

i am Backup a 1860GB Volume filled with compressd data from local Host (Veeam installed on it) to a windows network share.
the jobs starts with 20MB/s and after 1 day it was only 8MB/s, after 6 days 3MS/s and 50% only done
my calculation is 4 weeks to complete ? - Problem is: the Replication Jobs are blockt the next weeks.

parameter: no compression, no deduplication

HW 2 Hosts QC,16GB, SmartArray 2TB RE Singledrives at Targe Site.

But Replication runs with 100MB/s to this target. Only Backup is going slow.

have you any hints for me ? shoud i stop the job ?

thanks
Ulrich

[Vitaliy S.]

Since replication jobs for the same server are running well, looks like destination target for your backup job (CIFS share) is painfully slow and that affects overall job performance. I would recommend choosing another destination target to see if it changes the situation or not.

On top of that, here is a good topic describing common troubleshooting steps, please take a look: New user, need help optimizing backups

[umenz]

Hello Vitaly,

yes CIFS writes are slow, when I copy some files to the share the Network speed is not growing, actual 2MB/s.
CPU at the Target Machine ist >50% on 2 CPUs - process system - this Windows Server ist dedicatet for the BackupShare.
The Job ist running 72% in 7days, i will wait 3 Days to complete and analyse the CIFS speed after that.

thanks

Ulrich

[umenz]

Hello

changing NIC from E1000 -> VMXNET3 solve the main problem, now the speed is starting with 20MB/s

thanks

[Vitaliy S.]

Glad that you've nailed this issue by changing NIC adapter type. By the way, what about your replication job? Has it also improved?

[umenz]

no, it startet with 20MB/s but after 7 Days runtime it runs only with 3MB/s
- 50% (800GB) done,
i have abort the job.

replicating is no option i think, I have already an replication of this Machine with excludet this drive #3 (2TB) - no more space in the Target Store.
can i make a second replication whis excludest Drive #1 and #2 to this bigger second Storage Target ?

Ulrich

[Vitaliy S.]

Yes, why not. In case of a disaster you will have an ability to re-use this disk with replicated VM.

[umenz]

oh, replicating Job 2 needs another Name for the Target "xxx_relica2" , my mistake. Now ist runs.
35 MB/s - 1.8TB in one day, perfekt, My Target is now a 4TB (LUN append) and can store a lot of history restore Points. perfect

this Case is fixed.

Thanks

Ulrich