Jump to content

how to maximise backup throughput performance?

Recommended Posts

Hey all;


I've been doing some tests tonight on a problem I have with matching seemingly not working, but I have also noticed a degrade in data througput between our file server and backup server. The file server is runnng 2k Server, Raid5 SCSI drives, gigabit LAN and Retrospect. The backup server is running XP Pro SP2, SATA drives etc


I thought I'd do some performance monitoring whilst waiting for results of my matching tests and have noticed, strangly that something appears to be throttling back the throughput. Looking at the drives, neither the source or the destination drives are reaching 30% capacity, and the CPUs seem fine also (source ~20% destination ~50%).


This, to me, is a strange result as I would have imaged that Retrospect would spank the servers until one ofthem was flat out. I do wonder if the Retrospect server, which uses Hyper Threading on a Xeon CPU is causing a data bottle neck and not 'threading' as it should. Has anyone got experience of this?


The network adapters seem to be ticking over with peaks of ~20% across the gigabit LAN, which is confirmed by checking the HTTP management console on the HP switch.


Has anyone come acorss this before and has it ever been solved? I can't stop thinking that I should be getting MUCH better performance from these servers than I am at present!


Many thanks for any help you can give,



Link to comment
Share on other sites

I have also noticed that through the logs it appears all our backups are loading/preparing/idling for about half the time it takes for the data to be dragged across. That seems a long time to me?


- 09/03/2007 08:53:47: Copying Local Disk (C:) on *** Suse Server

Can't back up IIS Metabase, error -1017 (insufficient permissions)

09/03/2007 09:05:19: Snapshot stored, 83.9 MB

09/03/2007 09:07:08: 1 execution errors

Completed: 830 files, 641.3 MB, with 0% compression

Performance: 166.5 MB/minute

Duration: 00:13:21 (00:09:30 idle/loading/preparing)



- 09/03/2007 09:07:11: Copying Local Disk (D:) on *** Suse Server

09/03/2007 09:10:11: Snapshot stored, 7,042 KB

09/03/2007 09:10:17: Execution completed successfully

Completed: 2002 files, 526.9 MB, with 0% compression

Performance: 367.5 MB/minute

Duration: 00:03:06 (00:01:39 idle/loading/preparing)



- 09/03/2007 07:30:49: Copying Local Disk (C:) on Application Server

09/03/2007 07:35:55: Snapshot stored, 42.8 MB

09/03/2007 07:36:50: Execution completed successfully

Completed: 2493 files, 24.5 MB, with 45% compression

Performance: 18.7 MB/minute

Duration: 00:06:01 (00:04:42 idle/loading/preparing)


Would this issue be down to our data type (i.e. web /java based files) which are all very small in size?


Again, thanks for any help you guys / gals can throw on these issues.



Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...