Cristalink Support Forums

Ok, one last try... I have taken some stack traces in Process Explorer during backup, maybe they contain some hints. The CPU use is divided between Interrupts and the System process. Inside system, I captured the stack of the two threads that momentarily used the most CPU time. I also had a look at ...

Thanks, will do.

I had a screenshot of the process list as well, but didn't save it. Bottom line, there was no process showing up with abnormal use of memory. But in the two taskman screenshots, the main difference is in the amount of kernel memory ("Kernel-Speicher"), which seems to support a driver-relat...

And some more...

So, here I am again, with some logs. I have plotted some performance indicators vs time. The backup started on 8/12 at 21.00h. Sorry for the German labels.

Hmm, memory leak... But why would this cause excessive CPU load? And I didn't get the impression that the machine was under memory pressure as well, just maxing out the CPU.
I'll try to get the logs running during next weekend's backup.

OK, I logged into the server on Friday, half an our after the backup started. The backup file was already around 30GB and CPU usage was very low (around 10%). At this rate, the task should have completed in approximately 15h. However, on Monday, the backup task was still running, using the CPU at 10...

Thanks for your continued interest. We are running the large backup tasks over the weekend, so I will watch what happens on Friday and get back to you.

If by size of the tape you mean the size of the resulting backup file, this varies between 800GB and 1.2TB. This huge size also means I can't just perform the backup locally. For testing, I have copied 16GB to the iSCSI drive, both as one large file and a collection of small files. CPU use was aroun...

Thanks for your reply. I will try to narrow the problem down. Normal use, however, such as copying files to the iSCSI drive in explorer, does not seem to cause high CPU load.