"Neulinger, Nathan R." wrote:
>It might be worth considering the AfsWebSecure approach - which bypasses the
>cache entirely. Although you'd have to come up with client code at that
>point to integrate directly into the tool you were using.
>
>The biggest problem we've run into with backups is that the volume dumps are
>just so slow. On a server that we can pull 25 MB/sec sustained off the
>disks, we still can't get any more than 3MB/sec or so with vos dump.
>
>I believe my next backup approach is going to be putting a server in between
>the backup host and the file servers, and somehow interleaving (or starting
>in parallel in some fashion) multiple vos dump processes. One to each file
>server. It'll mean a bunch of extra space would be required on that machine,
>but hey, 40GB IDE disks are cheap.
>From the 'easier said than done' department: It sounds to me like the
answer is to get rid of the performance problems in the volserver :)
We use vos dump, with a backup system that allows us to multiplex
multiple backup streams onto a single tape. We run as many as 6
simultaneous vos dumps against an afs server to keep the data rates
up.
We have also considered using 'staging' disks on our backup servers;
we've been able to avoid it up to this point.
--
Dave Thompson <[EMAIL PROTECTED]>
Associate Researcher Department of Computer Science
University of Wisconsin-Madison http://www.cs.wisc.edu/~thomas
1210 West Dayton Street Phone: (608)-262-1017
Madison, WI 53706-1685 Fax: (608)-262-6626
--
