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.
-- Nathan
> -----Original Message-----
> From: Brian T. Huntley [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 03, 2000 6:15 AM
> To: Paul Blackburn
> Cc: [EMAIL PROTECTED]
> Subject: Re: AFS backup/restore using ADSM
>
>
> On Tue, 3 Oct 2000, Paul Blackburn wrote:
>
> // One thing puzzles me: if I run an ADSM file backup
> // (or any backup that traverses directories like tar)
> // doesn't that mean that the entire filetree being
> // backed up has to be accessed via the AFS cache?
> //
> // It doesn't seem very efficient compared with
> // doing a regular AFS backup by volume.
> // --
> // cheers
> // paul http://acm.org/~mpb
> //
>
> You are correct on both counts... everything does go through
> the cache,
> and it's not as efficient as doing backup by volume (for more reasons
> than just the cache). However, using a memory cache rather
> than a disk
> cache reduces this. We have been doing back by vol and are currently
> investigating going to a combination of back by vol and by
> file so that we
> don't have to keep as much data around.
>
> There are advantages and disadvantages to both methods; the trick is
> finding the right choice for your site based on data retention, backup
> window, and TSM(ADSM) server requirements.
>
>
> -
> Best regards,
> Brian
>
> +-------------------------------------------------------------
> ----------+
> | Brian T. Huntley Systems and
> Network Engineer |
> | Campus Information Services, Clarkson University
> |
> | Ph/FAX: 315.268-6723/6570
> |
> | [EMAIL PROTECTED]
www.clarkson.edu/cis |
+-----------------------------------------------------------------------+
UNIX *is* user friendly. It's just selective about who its friends are.
PGP Public Key available. finger [EMAIL PROTECTED]
