Sure, you can define more savesets in order to do concurrent backups, but
that might not get you faster thoughput. You need to take a closer look at
where the bottleneck is. If you look on PowerLink, there is a guide there
called something like "NetWorker Performance and Tuning Guide" which has
some good tips on addressing situations such as this.

On 7/7/11 4:54 AM, "jojo123" <networker-forum AT BACKUPCENTRAL DOT COM> wrote:

>Dear forum-members,
>
>we do have a Windows2003 server which has a D-Partition with 600GB and
>~1Million Files inside. The backup takes so long that when it trys to
>start again, the last one is still running (daily schedule).
>
>So I am thinking about ideas how to speed this up. Will it be possible to
>define more savesets (for each folder instead of D:\) or to define more
>clients with differents savesets in order to improve this situation?
>
>Best Regards and thanks
>
>Jojo
>
>+----------------------------------------------------------------------
>|This was sent by jochen.willeke AT wincor-nixdorf DOT com via Backup Central.
>|Forward SPAM to abuse AT backupcentral DOT com.
>+----------------------------------------------------------------------
>
>To sign off this list, send email to listserv AT listserv.temple DOT edu and
>type "signoff networker" in the body of the email. Please write to
>networker-request AT listserv.temple DOT edu if you have any problems with this
>list. You can access the archives at
>http://listserv.temple.edu/archives/networker.html or
>via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER