I don't know how to do what you ask, but as a workaround you could map to the individual volumes on the server from another host and backup from there.
Keep in mind though that it's usually the speed of reading from disk that causes backups to take a long time so if you don't have seperate underlying disks for each of the backup jobs, you might not save much time (if any.)
Not sure if it's possible to do this on a Windows client but see the following for Solaris client. The same principle applies for other Unix based clients.
Bear in mind that you need to have enough RAM on the client for both caches to be loaded into memory simultaneously and (as described in the previous reply) any other bottlenecks will still potentially apply.
DaveH8888
36 Posts
163
0
Posted December 2nd, 2009 06:00
I don't know how to do what you ask, but as a workaround you could map to the individual volumes on the server from another host and backup from there.
Keep in mind though that it's usually the speed of reading from disk that causes backups to take a long time so if you don't have seperate underlying disks for each of the backup jobs, you might not save much time (if any.)